Draft for review · Not yet published
Privacy Policy
A working account of how the current product handles data. This policy is not yet published. It identifies confirmed data flows and keeps unresolved details visible for review.
1. Who operates Globoox
The operator’s legal identity has not yet been confirmed for this document. Privacy questions and data requests can be sent to the contact below.
Privacy contact: support@globoox.co
2. Information handled by the product
Depending on how you use Globoox, the product handles:
- Account identifiers, email address and sign-in information provided through the authentication service.
- Uploaded EPUB files, filenames, file sizes and book metadata.
- Book content, generated translations, library activity, reading position and language or display preferences.
- Browser and request information, usage events, performance measurements and error diagnostics.
- Campaign parameters from a link you followed, when present.
3. Books, translation and local storage
EPUB files are uploaded to Supabase Storage using a signed upload URL. The backend then processes the uploaded file. Reading and translation requests pass through the service’s backend; this is not processing that happens only on your device.
The browser also stores book metadata, chapter structure and text, generated translations and reading-related data in local caches, including IndexedDB. Reading position is synchronized with the server.
4. Services involved
The current implementation uses the following services. Their inclusion here describes the product’s integrations, not a guarantee about their retention or contractual terms.
- Supabase provides account authentication and cloud file storage. Google sign-in is available through the authentication flow.
- PostHog provides product analytics. Events can include account identifiers and email, book titles or filenames, reading activity and translation performance. These events are not described as anonymous.
- Microsoft Clarity is currently disabled.
- Sentry provides error and performance diagnostics. Server and edge configurations allow personal data; upload error reports can include the filename and file size.
6. Retention and deletion
The library’s Delete action removes a book from the visible library. The implementation does not establish a complete deletion timetable for the original upload, translations, local caches, backups or analytics records.
A self-service account-deletion or personal-data export flow has not yet been confirmed for this policy. Requests can be sent to the privacy contact below. No specific retention period or complete-erasure guarantee is made in this draft.
7. Processing locations and legal details
Cloud storage, translation and diagnostic services may involve processing outside your device. The relevant locations and arrangements have not yet been confirmed for publication.
8. Questions and requests
For privacy questions or requests to access, correct or delete personal data, email the contact below. The full handling process and scope of data removal still need to be confirmed.
This document has no effective date. It remains a review draft while the operator, providers, retention practices and request process are being confirmed.
Privacy and data requests: support@globoox.co