This MVP collects only the data needed to authenticate requests, enforce quotas, process OCR jobs, support billing, and answer support requests. The current application stores profile data, usage events, processing job metadata, and Creem, Stripe, or Supabase identifiers when those integrations are configured.
Processing job metadata can include the operation type, platform, provider, status, stable error code, and timestamps. Comment source text and translated text are not stored in the processing job history.
Image uploads sent to the OCR route are processed in the request lifecycle. The current repository code does not define durable application storage for uploaded image bytes after the request completes.
If you submit a remote image URL instead of a data URL, the server temporarily fetches that image so OCR can run. That fetch is limited to HTTPS image content and size-checked before processing.
Supabase can store profiles, usage, and job metadata when repository credentials are configured. Creem is the public Merchant of Record and can process checkout, taxes, billing records, refunds, and Customer Portal sessions. Stripe identifiers may be retained for historical or future billing compatibility.
Optional translation provider credentials may send text to Azure, OpenAI, or DeepL only when you configure those services. Local OCR uses Tesseract worker files on your deployment and is not itself a third-party network service.
Signed-in users can permanently delete their Supabase identity, application profile, quota records, and processing job metadata after confirming their current password. Active subscriptions must be canceled before deletion.
Creem, Stripe, and support records can still be retained where accounting, dispute handling, fraud prevention, or legal obligations require it. Use the support contact on the Contact page if self-service deletion is unavailable, or use Delete account for the automated process.
This policy does not claim data export automation or zero-retention behavior that the current codebase does not implement.