Privacy policy
This page explains how the self-hosted version handles accounts, uploaded images, generated results, and logs.
What we store
The site stores the email address from your Google account, credit balance, generation history, uploaded source images, and generated results. Source images are stored in storage/uploads, results are stored in storage/generated, and SQLite is used for the database.
How images are processed
The browser never calls the image processing service directly. Images are uploaded to this site's server first, then the server completes the image cleanup. CleanerPix uses third-party AI image-processing services to clean up images. Users do not directly access the model or API. Sensitive configuration is stored only in server environment variables and is never exposed to the browser.
Usage events
To improve the product we record a small set of first-party events: visits to public pages, opening the editor, choosing an image, completing an edit, downloading a result, signing up, and completing a payment. Events store a public page path, the tool used, an account ID or anonymous visitor ID, and a session ID from our own cookie. We also retain the first public landing path, referrer hostname (without its URL path or query), and limited campaign identifiers from utm_source, utm_medium and utm_campaign. The browser keeps this first landing information in session storage when available; our session cookie expires after 30 minutes of inactivity. After sign-in, stored guest-session evidence may be linked to your account. Logout and account changes reset attribution, and a payment may use account evidence recorded within 30 days before checkout. We do not store IP addresses with these events, we do not use third-party analytics, and we delete events after 180 days.
Deletion and backups
The current version does not provide self-service deletion yet. In production, the database and image storage directories should be backed up regularly, and image retention should be defined based on business needs.