Privacy

Last updated 14 October 2026

Double Prime is a storefront at https://doubleprime.pro. We test page assessments, estimates, payments, and delivery in our current pilot. This page says what we collect, why, and who else can see it.

Google sign-in

A Customer signs in with Google. That is the only sign-in. We do not ask for a password and we do not run a sign-up form.

When you sign in, Google sends us the scopes we request: openid, email, and profile. From that we keep:

• your Google account identifier (sub), so the next sign-in is the same Customer
• your email address, so we can show who is signed in

We use this to recognise you as a Customer and attach your requests, material, assessments, Quotes, sandbox payment history, and results to you. We do not read Gmail, Drive, Calendar, contacts, or any other Google product. We do not sell Google account data. We do not use it for advertising.

Translation Requests and AI assessments

A Translation Request can contain several PDF files or JPEG, PNG, WebP, HEIC, and HEIF still photos. We retain the original files, full page images, thumbnails, and available same-page text. We also store preparation errors, page assessments, model and provider information, usage when available, document grouping revisions, and saved experimental Estimates.

When you start an assessment, page images and available text are sent through OpenRouter to the selected model providers. AI grouping uses retained page thumbnails and text excerpts. Model responses can be inaccurate. The workspace shows their separate results and lets you correct document groups.

Sandbox payment and fulfillment records

When you submit a Quote, we store its agreed document scope, price, contact email, and acceptance of the payment terms. For sandbox payment we store Stripe account and payment identifiers, amounts, status and deadlines, authorization attempts, refunds, and reconciliation records. Stripe hosts checkout and handles test card details; Double Prime does not store card numbers or security codes. Live payments are disabled in this pilot.

We also store the assignee name, service progress, uploaded result files, review and publication records, Claim reasons and supporting files, Remakes, delay reports, visible resolutions, and incident notes. Service emails use your contact email for work, payment, and results updates; delivery and retry outcomes are recorded. These records support the requested service flow and troubleshooting.

Service emails

Service emails are sent from service@doubleprime.pro through Cloudflare. They announce what happened and link to your account; we do not attach your documents or results. Each email is written in the language you use on the site, or in the language of your request. You can turn service email off at any time from the account menu or with the unsubscribe link in any email. Your requests and results stay available in your account, but you will not be told by email when a payment changes or results are ready. We keep the language you chose and whether email is on or off with your account. Operators and Translators receive the same kind of email about their own work at the Google address they signed in with.

Operator access

Authorized Operators can see submitted Quotes and their source files, payment history, results, and Claims to manage the test workflow. Unsubmitted drafts expose only request metadata to Operators, not their file contents. Other Customers cannot access your private files.

Where it is stored

Cloudflare Workers, D1, R2, and Workflows host the application, private originals and page artifacts, history, and background processing state. Your signed-in Customer identity controls access to your Translation Requests. Operator access is authorized separately; the pilot does not offer sharing between Customers.

Cookies

During Google sign-in we set a short-lived state cookie. After a successful sign-in we set a session cookie so the browser stays that Customer. We do not set advertising cookies.

Who we share with

• Google, to complete sign-in
• Cloudflare, to host the storefront, store records, and send service emails
• Stripe, to process sandbox checkout, authorization, collection, and refunds
• OpenRouter and the selected model providers, when you start page assessment or AI document grouping

We do not sell personal data. We may disclose records if Spanish or other applicable law requires it.

How long we keep it

Requests and material remain in your history until eligible deletion. Deletion is unavailable while payment or refund recovery, active work, an open Claim Window, a Claim, a Remake, or a delay report needs action. When eligible, deletion requires confirming the request name. It revokes file access immediately and queues removal of originals, page artifacts, assessments, groups, estimates, result files, and Claim evidence. Cleanup is retried if storage is temporarily unavailable. Payment and operational audit records can remain for reconciliation; records held by Stripe and email providers follow their own retention policies. Deleting a request does not delete your Google Customer account. Provider processing and retention are governed by the providers' policies.

Your choices

You can refuse Google sign-in; then the private request workspace is unavailable. You can revoke Double Prime in your Google account permissions. You can ask us for a copy of what we hold, or to delete it, at the support email shown on the Google consent screen.

Children

The storefront is for people who can commission a Sworn Translation. We do not seek data from children.

Changes

If this page changes, we will update the date above. The current text is always at https://doubleprime.pro/privacy.