Purifico OZONE Privacy Policy

Effective date: 19 September 2026

This policy applies to the Purifico OZONE Android and iOS applications (com.purifico.ozone), their account service, and the embedded system interface.

About the service

Purifico OZONE is operated by Purifico Ozone Inc. It allows authorised users to monitor assigned water-treatment and ozone systems, view equipment history, change permitted settings, and receive system alerts.

Authorised administrators create accounts and assign system access. The app does not offer self-service registration, and users can access only systems assigned to their account. The service is intended for adults aged 18 and over.

For app support, privacy enquiries, or requests concerning your information, email y.fedorenko@purifico-ozone.com. Please do not send passwords, authentication tokens, or security keys. The company website is purifico-ozone.com.

Information we process

How we use information

We process this information to authenticate users, manage accounts and assigned system access, register installations, show equipment information, perform authorised control requests, deliver alerts, provide support, investigate faults, maintain audit records, and protect the service from unauthorised use.

Purifico does not sell users' personal information, use it for advertising, or display advertising in the app.

Notifications and information stored on the device

The app uses operating-system-backed secure storage for its session token and app installation identifier. The embedded system interface uses an authenticated session cookie.

Firebase notification services initialise when the app starts and may process installation and technical service information before sign-in. Device notification controls and the app's per-system settings control displayed alerts. Disabling displayed notifications does not delete the account or all Firebase installation information.

Alert text may appear on the lock screen depending on device settings. Users should adjust notification visibility where equipment information should remain private.

Signing out requests deregistration of the current app installation and removal of the locally stored session token. A connection or storage failure can delay that operation. Signing out or uninstalling does not itself request deletion of the server account, equipment history, all local web data, or Firebase's installation information.

Service providers and authorised access

Authorised administrators manage accounts and system assignments. Technical development, administration, and support are performed on behalf of Purifico Ozone Inc. Providers acting on Purifico's behalf receive only information needed to supply the relevant service.

Security

The mobile app connects to the central service using HTTPS, and the release configuration disables cleartext traffic. The service uses password hashing, authenticated sessions, assigned-system access controls, restricted operational storage, and guarded backup and retention procedures. No technical or organisational measure makes every system risk-free, and not every internal equipment connection is end-to-end encrypted.

Retention

Older mixed recovery, incident, security, or deployment archives created before the registered processes are reviewed separately and may remain longer while a recovery or security need exists. They are protected from ordinary access and removed when no longer needed. Provider-held and residual copies may follow different deletion cycles. Account deletion therefore does not mean that every historical or provider copy disappears immediately.

Requests and account deletion

To request access to, correction of, or deletion of personal information, email y.fedorenko@purifico-ozone.com. Purifico verifies the requester's authority through the customer contact already known from onboarding. Passwords, tokens, or identity-document copies are not requested as routine verification.

The operational target is to process a verified request within 30 calendar days of receipt, subject to applicable requirements. Purifico will explain any needed clarification, justified exception, or separately retained information. This is not a promise that every backup or provider-held copy is erased within 30 days.

When remote access is no longer required, an administrator deactivates and deletes the account through the administration panel. Deletion removes the active account record and authentication hashes, system assignments, registered app installations, and account-linked notification preferences. Audit records, equipment history, technical logs, registered backups, legacy protected archives, and provider-held identifiers follow the separate periods and limits described above.

Deleting a Purifico account does not itself delete a separate provider account or all Firebase installation information. Purifico will address applicable provider or residual information as part of a verified request.

Changes to this policy

Purifico may update this policy when the service, providers, or legal requirements change. The current version and effective date will remain at this public URL. Material changes will be reviewed before implementation and, where appropriate, communicated through the app, service, or customer contact.