Privacy Policy

Launch note: this is an engineering/product privacy draft, not legal advice. Finalize retention, international transfer, processor and jurisdiction-specific disclosures with counsel before public launch.

Information used to provide PixelStory

PixelStory stores account information, secure session records, storyboard projects, collaborators, preferences, imported assets, subscription state, security/audit records and support feedback needed to operate the service.

Age data minimization

PixelStory currently stores an age-eligibility confirmation timestamp rather than a date of birth. This reduces collection of unnecessary personal data while still recording that the account holder confirmed the minimum-age requirement.

Authentication

Password accounts use salted password hashes. Google and Apple sign-in store provider account identifiers and verified email information needed to link the account. PixelStory does not store Google or Apple passwords.

Payments

Stripe processes payment-card information when production billing is enabled. PixelStory stores subscription/customer identifiers and billing-event metadata needed to provide paid entitlements; raw card numbers do not pass through PixelStory application code.

Optional analytics and marketing

Optional analytics and marketing tracking remain disabled until consent is given. Essential authentication, security and preference cookies do not depend on optional consent. Cookie preferences can be changed from the site footer.

Error reports

When something breaks, PixelStory can send an error report to its error-tracking service (Sentry) so the bug can be fixed. A report contains the error message and code location, the page or feature path, the release and an internal account ID. It does not include passwords, emails, cookies, project content or uploaded artwork.

Uploaded artwork

Custom artwork is stored to provide your storyboard workflow. Access is limited by project/account permissions. Production storage should use private object storage and short-lived authorized delivery URLs.

Retention, deletion and export

Before public launch, PixelStory must publish specific retention periods and provide account deletion/export workflows. Security and billing records may require different retention periods where legally permitted or required.

Contact and rights requests

Before public launch, configure a real privacy contact and procedures for access, correction, deletion and other privacy requests applicable to the user's jurisdiction.