1. The short version
DeepFrame requires an account to use photo tools. We store account details, uploaded originals, generated reports, plan usage, and material product and security actions so history works across devices and the service can enforce limits and respond to abuse. We do not sell personal information, collect payment-card numbers, or receive passwords from Google, GitHub, or your email provider.
2. Information we collect
Account data includes your user ID, username, email address, sign-in provider, plan, account status, legal-consent records, creation time, and recent account activity.
Photo data includes the original file you choose to upload, its file name and technical properties, the metadata and structural report DeepFrame produces, cryptographic fingerprints, cleaned-output records, and timestamps.
Activity and security data includes material actions such as signing in or out, starting and completing an inspection, viewing, exporting or sharing a report, opening an upgrade screen, removing metadata, hiding history, and requesting deletion. We do not record every mouse movement, keystroke, or unrelated click.
3. Why we use it
We use this information to provide saved cross-device history, enforce daily limits, operate account and privacy features, diagnose failures, prevent abuse, investigate security or safety concerns, respond to support requests, and comply with applicable obligations.
4. Storage and retention
Account history, uploaded originals, cleaned copies, and generated reports are stored in Supabase infrastructure while your account remains active so your history works across devices. Material product and security events are automatically removed after 180 days unless a longer period is reasonably required for an active security incident, dispute, fraud investigation, or legal obligation. You can request permanent account-data deletion from your profile.
Storage periods are maximum operational targets, not a promise that every backup copy disappears instantly. Backups and provider systems may take additional time to cycle out deleted data.
5. Who can access information
Users can access only their own account records. Other users cannot search for or view your profile or history. Authorized DeepFrame administrators can access account records only through restricted administrative controls. Individual records are not routinely reviewed and may be examined when there is a security, safety, abuse, support, or legal reason. Administrative changes are logged.
Supabase and Vercel process information as infrastructure providers. Third-party sign-in providers process login information under their own policies. DeepFrame does not sell personal information or use photo contents for advertising.
6. Your controls and privacy requests
You can review account history, change your username, hide individual history items, and submit an account-deletion request from your profile. Hiding is an archive action, not permanent deletion. The profile explains this before you confirm.
A permanent-deletion request covers account data and stored photo history, subject to limited exceptions for security, fraud prevention, disputes, and legal obligations. You can submit a request from your profile. If you cannot access your account, contact the project owner through the official DeepFrame GitHub profile or creator channels.
7. Security
DeepFrame uses passwordless or provider-managed authentication, private storage, row-level database access rules, server-controlled quotas, role-based administration, and audit logs. No online system can guarantee absolute security. Report suspected problems through the security contact listed by DeepFrame.
8. Children and sensitive use
DeepFrame is not directed to children under 13. Do not upload another person’s photo or sensitive location information without authority and appropriate consent. If you believe a child’s or another person’s information was uploaded improperly, contact DeepFrame to request review.
9. Changes and contact
We may update this policy when the service changes. Material changes may require renewed acceptance. Submit privacy requests from your profile or, if you cannot sign in, through the official DeepFrame GitHub profile or creator channels. This policy is a product disclosure and should be reviewed by qualified counsel before commercial launch.