Privacy notice

1. Who is responsible

Pixopea is operated on a self-hosted deployment. The operator of this installation is the data controller for account and project data. For requests about your data, contact the administrator of the instance where your account was created. Before a public launch the operator must publish a contact address and grievance officer details here.

2. What we collect

• Account data: name, email address, password hash, plan and credit balance, and sessions you create for signed-in devices.
• Project data: the projects, versions, assets and AI job records you create. The editor does not upload an image until a cloud feature or AI tool needs it.
• Visit analytics (only with consent): a random visitor ID kept in this browser, a session ID, pages viewed, referrer and campaign parameters, device category, browser and operating system, language, and coarse country/region/city when a local GeoIP database is configured.
• IP address: the server records the address it actually receives (proxy headers are only trusted when the deployment names its proxies). Raw addresses are visible only to administrators and are removed by the retention policy. Other screens show a shortened form.
• Product events (only with consent): sign-in, project saved, template used, export completed, AI job started or completed, and similar structured actions. Event properties are limited to short identifiers; page content, prompts, passwords, tokens and payment data are rejected.

3. Consent

Analytics and advertising are off until you choose. Necessary storage (your sign-in token, consent choice, visitor/session IDs and the offline app cache) is used to run the service. You can change your choice at any time:

Declining analytics does not limit the editor or your account. It only stops visit measurement.

4. Local storage

Pixopea stores a sign-in token, your consent decision, random analytics identifiers, local editor drafts and the PWA cache in your browser. There is no third-party analytics script. If visitor measurement is disabled, no analytics request is sent.

5. Advertising

Advertising is disabled by default on a new installation. When an administrator enables it and you consent to advertising, placements may appear on the home page, dashboard, templates, pricing and similar pages. Ads never appear in the editor canvas, on admin screens or on account pages.

Two kinds of placements exist: first-party house/direct creatives, whose impressions and clicks are counted by this server, and provider-served ads such as Google AdSense, whose measurement and cookie use are controlled by that provider. Provider credentials are stored encrypted on the server and are never sent to your browser. We do not estimate or fabricate provider metrics.

6. Retention

Identifiers are removed automatically by a daily job. These are the default windows; the administrator can shorten them.

Deleting your account removes your account and project records subject to legal and backup obligations.

7. Your rights

Depending on where you live — including under India's Digital Personal Data Protection Act, 2023 and the EU/UK GDPR — you may ask for access to your data, correction, erasure, a portable copy, withdrawal of consent, or raise a grievance. Signed-in users can update their profile, change their password, review signed-in devices and delete their account from the account page. Other requests go to the operator contact listed above.

8. Security and children

Access to identifiable visit data is restricted to administrators and sensitive admin actions are written to an audit log. Passwords are hashed, provider secrets are encrypted at rest, and analytics or advertising failures never block the editor. The service is not directed at children; do not create an account on behalf of a child without the consent required in your jurisdiction.

9. Changes

Material changes to this notice will be published on this page with a new version date. Continued use after a change is subject to the updated notice.