Current status
document.cookie, load an analytics SDK, display advertising, or embed third-party media.It does use browser storage for features that a visitor explicitly requests. Cookie and similar-technology rules can also cover local storage or other access to a device, so this policy identifies those uses transparently.
Storage used by DuskTranslate
| Technology | Purpose | Choice |
|---|---|---|
| IndexedDB | Store local projects, original files, translations, glossary, and progress | Required for the device-only library; delete projects or clear site data |
| localStorage | Theme, library layout, authentication preference, and remembered Supabase session | Theme/layout are preferences; sign out or clear site data to remove them |
| sessionStorage | Guest mode and a tab-scoped Supabase session when "Remember me" is unchecked | Ends when session data is cleared; sign out explicitly on shared devices |
| Cookies | None intentionally set by DuskTranslate | Not applicable |
Third-party requests
The page currently requests Google-hosted fonts. Google OAuth redirects to Google when selected. Supabase handles account sessions and cloud storage when enabled. AI requests go directly to the selected provider only after you start a translation. These services may receive network metadata such as an IP address as part of delivering their requests; consult their policies.
Do you need consent?
For the current feature set, no analytics or marketing consent is being requested because those technologies are not installed. Strictly necessary storage may be exempt from consent in some jurisdictions, but transparency is still required and local-storage rules vary. Before adding analytics, advertising, personalization that is not necessary, or non-essential embeds, implement prior opt-in consent, equal reject/accept choices, withdrawal, and consent records.
This conclusion is based on the current code and should be rechecked by the operator before launch in each target market. UK guidance expressly covers storage or access technologies beyond traditional cookies; EU and other national rules may differ.
Contact
Questions or requests: [privacy email]. Operator: [legal name or business name].