Privacy Statement

Short version: Your photos stay on your phone. The launch website collects signup and payment intent only. It does not collect gallery files, filenames, thumbnails, OCR text, hashes, EXIF, image content, video content, or personal media metadata.

Last updated: 2026-05-02. Operator details and final contact address must be completed before public paid launch.

What we collect

• Email address, so we can send launch updates.
• Signup interest, such as launch list, Founding Cleaner Pass, or free/ad-supported option.
• Consent version, source, and timestamp for basic record keeping.
• Payment status and payment reference from Stripe if you buy the Founding Cleaner Pass.
• Voluntary sanitized app error reports, only if you choose to submit them.

What we do not collect

• No photo or video uploads.
• No gallery-derived details, filenames, folder paths, thumbnails, OCR text, EXIF, hashes, or personal media metadata.
• No cloud media analysis and no server-side thumbnail generation.
• No automatic error reporting from the Android app.

Why we use this data

• To operate the waitlist and send relevant launch updates.
• To understand demand for the Android app and the Founding Cleaner Pass.
• To reconcile Stripe payments and support refund requests.
• To debug crashes or broken flows when a user explicitly submits a sanitized error report.

Processors

We may use hosting, database, email, and payment providers to run the launch site. Stripe processes payment details. We do not store card numbers on our servers.

Retention

Waitlist records are kept while the launch is active and for up to 24 months after the last meaningful product update, unless we need a longer period for accounting, dispute handling, or legal compliance. Voluntary sanitized error reports are kept for up to 12 months. You can ask to be removed earlier.

Your choices

You can unsubscribe from launch emails or request access, correction, deletion, or export of the signup data linked to your email. Contact details must be completed before public launch.

Cookies and analytics

The launch page should not use cookie-heavy tracking. If analytics are added later, they must be privacy-friendly and must not include media-related personal data.