This page explains what CloudPix collects, how the platform uses that information, and the practical steps taken to reduce unnecessary exposure of user data. The goal is to keep the workflow useful, controlled, and clear for public visitors, registered users, and admins.
CloudPix tries to collect only what is needed for the tool, account, upload, delivery, or admin workflow that the user is actively using. Public browser tools are kept separate from hosted account features so people do not have to hand over more information than the task requires.
CloudPix may collect account details such as username, email address, password-related authentication data, verification state, and account security settings when a user signs up or manages an account.
For hosted workflows, the platform may store upload-related information, file metadata, storage usage, share and delivery records, and activity connected to account operations.
For security and reliability, the platform may also log request details, login attempts, audit events, security events, and related operational information used to detect abuse, investigate issues, and manage platform access.
CloudPix is designed so public browser tools can be used without forcing account creation first. Where a tool is built to work inside the browser, that tool is intended to keep the file task in the user session instead of turning it into a hosted account workflow.
Account and hosted workflow data may be used to:
CloudPix separates public tools from signed-in hosted features so the same user does not need to go through the same data flow for every task. Admin controls are also used to limit what becomes public, what stays account-based, and what should require tighter operational visibility.
CloudPix may send account-related emails such as signup verification, password reset messages, security alerts, and admin-triggered test or operational mail. These messages are used to support access control and account continuity rather than broad promotional communication.
CloudPix is intended to use service providers and infrastructure only where needed to run the application, deliver hosted workflows, send email, and maintain platform operations. Data may also be reviewed or disclosed when necessary to investigate abuse, respond to valid legal requirements, protect the platform, or protect other users.
Information is intended to be kept only as long as it remains useful for account access, hosted workflow continuity, operational visibility, legal obligations, or abuse prevention. Platform operators may review and remove data that is no longer needed for those purposes.
Users can choose whether to stay in the public tool flow or move into a registered hosted workflow. Registered users can manage account access, password updates, and security settings that are made available in the product. Admins can manage broader platform controls, but they are also expected to use those controls responsibly.
This policy may change as CloudPix grows, adds new workflows, or improves platform controls. When the privacy approach changes in a meaningful way, the published policy should be updated so users can review the current version before continuing to rely on the platform.
This page is written as a practical public-facing privacy policy for the current CloudPix product shape. Before a broader public launch, it is still wise to review it against your hosting setup, email provider, storage workflow, and the jurisdictions you plan to operate in.