Privacy

Privacy Policy

Buyer-configurable transfer template — not legal advice. Before public launch, the operator must obtain legal review and add its legal name, address, privacy contact, governing privacy regime, retention periods, lawful bases, user-request procedure, transfer disclosures, and last-updated date.

Data we process

We process account identifiers, profile details, project metadata, uploaded screenshots, subscription records, usage counters, and security logs required to provide and protect the service.

How images are handled

Source screenshots are stored in a private, owner-scoped bucket. Final PNG and ZIP rendering occurs in your browser; the export canvas is not sent to an image-generation service.

Service providers

Supabase provides authentication, database, and private storage. Stripe processes checkout, subscription billing, and the customer portal. Analytics and error monitoring are not active in this sale build; the buyer must identify any providers added later before enabling them.

Purpose, retention, and security

Data is used to operate accounts, save projects, verify paid access, enforce usage limits, prevent abuse, and support the service. Records are retained only as long as reasonably needed for those purposes and applicable legal obligations. Access controls, private storage, row-level security, and encrypted transport are used to reduce risk.

Your choices

You may update profile details, cancel billing through Stripe, and request access, correction, export, or deletion where applicable. Some billing and security records may be retained when required by law or legitimate fraud-prevention needs.

Contact

Privacy requests should be sent to the support address published by the service operator. The operator must complete every buyer-configurable field listed above before launch.