iSomor Privacy Policy

Updated: 2026-09-17

Who operates the service

Planet Edmunds Labs Limited operates iSomor. For privacy questions or requests, contact [email protected].

Information processed

Google or email-link sign-in provides your email address and verification information. Google sign-in also supplies an account identifier and may provide a display name and avatar. We keep internal account identifiers, sign-in and account timestamps, language preferences, and credit and task records. The current sign-in flow does not ask for a password, and the free stage does not collect payment details. Older accounts may retain information supplied previously.

Uploaded PDFs, extracted text, translated files, filenames, sizes, page counts and translation settings are processed to provide translation and downloads. Browser requests also expose an IP address and browser information. The service can record these and an approximate IP-based location even without sign-in, alongside referral and usage information.

Why and where processing happens

We use information to sign you in, perform translations, store and deliver files, apply credit limits, maintain the service and investigate problems or abuse.

Document text, translation instructions, language settings and, when used, glossaries or earlier translated text are sent to Google's official Gemini API. Personal information inside a document is part of that input. Google's data-handling rules are described in the Gemini API terms.

Originals and results are stored in private Cloudflare R2 object storage. Uploads and downloads use time-limited signed links; anyone holding a valid link may be able to use it, so do not share it unintentionally. Application services and database backups use Google Cloud infrastructure in the United States. Resend processes recipient email addresses and sign-in emails or translation-task notifications. These messages may include a filename, translation status, language settings or a link to the result. Google processes Google sign-in. Providers may process data outside your country; private storage is not a promise of storage exclusively in your country.

Cookies, logs and optional analytics

Analytics and masked session replay are on by default when no preference is saved. The Cookie panel does not open automatically. You can change your preference at any time using “Manage Cookies” in the footer; existing refusals remain in effect. When analytics is enabled, PostHog receives selected usage events and may replay website interfaces and interactions using DOM data, not a video of your screen. Account areas, filenames, PDF content and text layers are excluded; inputs are masked. URLs are normalized, referral information is limited to external domains and approved campaign values. An internal account ID connects anonymous and signed-in activity. Turning analytics off stops events and replay and discards pending browser data; it cannot recall data already sent. Sentry separately receives filtered technical faults, error types, code locations and release information to maintain reliability, without document contents, request bodies or credentials. Replay links are attached only while analytics is enabled. Necessary functionality remains available when analytics is declined. No advertising, general automatic click collection or Sentry replay is enabled.

Storage, deletion and your choices

A file's disappearance from history or expiry of its download access does not prove erasure. The current history delete action hides the record; it does not automatically erase the original, translated objects or backup copies. Normal temporary translation files are cleaned up after processing, but files for uncertain or interrupted tasks can remain for investigation. Database backups can retain account and task records after changes to live data. We do not currently publish a fixed physical erasure deadline for these copies or provide automatic deletion across all storage and backups.

Keep your own copies. You can contact us to request access, correction, account deletion or removal of stored documents, identifying the account and relevant files without sending passwords or sign-in links. Requests require review of the affected live records, files and backups; this page does not promise immediate or complete erasure through the history button. Changes to this policy will be posted here with a revised date.

Collection and withdrawal

While analytics is enabled, we also collect coarse device, browser and operating-system categories; approved traffic sources; translation task status and page counts; and limited preview, download and history interactions. Search text and document contents are excluded. Preview depth means the furthest page displayed, not that you read it. Visible preview time excludes hidden pages. The server may send the results of tasks submitted while analytics is enabled after you close the page. Previously saved choices are retained without another prompt. Withdrawal immediately stops browser collection. The server cancels unsent events when it receives the withdrawal; if offline, your browser keeps a pending withdrawal and retries when connected. Accepting again does not restore the old queue. Failed server delivery payloads are retained for up to 30 days; successful payloads are removed from the local queue while deduplication records remain. Already transmitted data is not recalled.