This draft privacy page is part of the preview lane so the future public site can be assessed for trust, data clarity, and billing-provider readiness before release.
Draft preview for product and legal review before publication. Not legal advice.
These draft legal pages live inside the preview lane so the final marketing surface can be reviewed as one coherent product before publication or Paddle domain submission.
PixelClear collects account and workspace information such as email address, workspace name, billing state, connected storefront metadata, scan records, workflow actions, and report-delivery records needed to operate the product.
The platform may also store operational records such as provider event IDs, delivery events, and runtime diagnostics when needed for reliability, auditability, and support.
Data is used to authenticate users, provision workspaces, run scans, store remediation and reporting state, monitor recurring product activity, and support billing and transactional email workflows.
PixelClear uses data to improve product reliability, explainability, and operational support, but should avoid collecting unnecessary personal data beyond what is required for the service to function.
Current product posture includes Next.js for the application surface, Supabase PostgreSQL for durable hosted data, Resend for transactional email, Paddle for billing, and hosted deployment infrastructure for the live app runtime.
As the product evolves, additional service providers may be introduced for analytics, support, documentation, or distribution, but they should remain aligned with the product's founder-realistic and portable infrastructure posture.
PixelClear uses session-related technical data to keep users signed in, protect private routes, and preserve the handoff between public entry and authenticated app surfaces.
Any future cookie or consent messaging should remain readable, minimal, and consistent with the product's accessibility-first standards.
Workspace owners should be able to understand what operational data is retained, which third-party providers receive billing or email-related metadata, and how account-level requests can be routed.
As the public site and support flow mature, this page should clearly describe access, correction, deletion, and export expectations in the jurisdictions relevant to PixelClear's market.
This draft policy should later include a clear privacy contact path and the effective date for the production version.
If the product's processing posture changes materially, the published privacy page should be updated in a controlled release rather than through ad hoc copy edits on the live site.