Privacy policy
Effective 7 October 2026
1. Who we are
Scriptolo turns photos and scans of handwritten documents into searchable text. The data controller for the personal data described here is Mark Hammonds, a sole trader trading as Scriptolo, based in the United Kingdom. Contact: [email protected].
Scriptolo is currently open by invitation only.
2. What we collect
- Account details
- Your email address and sign-in records. Your password is held by our sign-in provider, Clerk, never by us.
- Your documents
- The photos, scans and PDFs you upload, their original filenames, and page order and rotation.
- Transcriptions and edits
- The text of each page, and any corrections you make.
- Batch details
- Batch titles and notes, and AI summaries you choose to generate.
- Context you give the AI
- Names, places or terms you enter as additional context (optional).
- Preferences
- Whether you want “batch finished” emails, and whether the upload form is collapsed.
- Page credits
- Your credit balance and its history: free pages, pages used, and any credits added or removed.
- Activity records
- When you were last active (at most once a day), which transcripts you downloaded and when, and processing usage per page (the AI model used and its cost).
- Invitation records
- The email address invited, who invited it, an optional note, and when it was used.
- Invite requests
- If you ask for an invite on our home page: your email address, and your name, note and preferred pack if you give them.
- Error reports
- Technical details of an error, the page address (without anything after a “?”), and your internal account ID — see “Error monitoring”.
We don’t use analytics or advertising trackers, and we don’t sell or share your data for marketing.
3. Why we use it, and our lawful basis
Under UK data protection law (UK GDPR), we rely on these lawful bases:
- Providing the service — storing, transcribing, showing, searching, exporting and deleting your documents
- Contract
- Signing you in and keeping your account secure, including bot protection at sign-up
- Contract; legitimate interests (security)
- Sending “your batch has finished” emails (you can turn these off in Settings)
- Contract
- Sending notices about your account, such as warnings before an inactive account is deleted
- Legitimate interests
- Running and fixing the service: error monitoring, usage and cost tracking, rate limits
- Legitimate interests (keeping the service working and affordable)
- Managing invitations and invite requests while Scriptolo is invitation-only
- Legitimate interests
- Making sure each person gets the free pages only once
- Legitimate interests (preventing abuse of the free allowance)
- Generating an AI summary of a batch — only when you ask for one
- Contract
The documents you upload may contain personal data about other people — for example, names in family letters. You’re responsible for having the right to upload them.
4. Who we share it with
We use these service providers to run Scriptolo. Each receives only what it needs, under a data processing agreement.
Anthropic
- What for
- Transcribing pages, and generating batch summaries when you ask
- Receives
- Page images and your optional context; for a summary, that batch’s transcriptions
- Where
- Stored in the US; requests may be processed in the US, Europe, Asia or Australia
- Safeguard
- Anthropic’s Data Processing Addendum, with the UK Addendum to the Standard Contractual Clauses. Anthropic may not train its models on your content. It deletes inputs and outputs within 30 days, but keeps them for up to 2 years if they’re flagged for breaking its usage policy.
Railway
- What for
- Hosting the app, database and file storage
- Receives
- Everything stored in the service
- Where
- United States (US West)
- Safeguard
- Railway’s Data Processing Agreement (signed), with the UK Extension to the EU–US Data Privacy Framework or the UK Standard Contractual Clauses.
Amazon Web Services
- What for
- Off-site nightly database backups
- Receives
- A copy of the database (account details, transcriptions, batch details — not photos)
- Where
- United States (N. Virginia)
- Safeguard
- AWS’s Data Processing Addendum, with the UK Addendum to the Standard Contractual Clauses.
Clerk
- What for
- Sign-in and account management
- Receives
- Email address, password (hashed), session data
- Where
- United States
- Safeguard
- Clerk’s Data Processing Addendum, under the UK Extension to the Data Privacy Framework and the UK Addendum to the Standard Contractual Clauses.
Cloudflare
- What for
- Our domain, bot protection at sign-up, and forwarding email sent to [email protected]
- Receives
- Technical data from your browser during the sign-up check (IP address, browser details); emails you send us
- Where
- Cloudflare’s global network, including outside the UK
- Safeguard
- Cloudflare’s Data Processing Addendum, under the Data Privacy Framework and the UK Addendum to the Standard Contractual Clauses.
Resend
- What for
- Sending our emails
- Receives
- Your email address, batch title and page counts; for an invite request, the details you gave, sent only to us
- Where
- Sent from Ireland; stored in the US
- Safeguard
- Resend’s Data Processing Addendum, under the UK Extension to the Data Privacy Framework and the UK Addendum to the Standard Contractual Clauses.
Sentry
- What for
- Error monitoring
- Receives
- Error details with filenames, email addresses and document text removed; your internal account ID
- Where
- Error reports in the EU (Frankfurt); account settings in the US
- Safeguard
- Sentry’s Data Processing Addendum (accepted), under the Data Privacy Framework and the Standard Contractual Clauses with the UK Addendum.
Where your data is stored. Your documents, transcriptions and account data are stored in the United States (Railway; database backups with Amazon Web Services). Transfers from the UK are protected by the safeguards above.
We may also disclose data if the law requires it.
5. Error monitoring
When something goes wrong, an error report goes to Sentry so we can fix it. Before a report leaves our servers or your browser, we remove request contents, cookies, headers and anything after a “?” in the address (search terms included); we remove email addresses, filenames and any quoted text; and we attach only your internal account ID, never your email. Sentry is set not to store IP addresses, though it may record an approximate location (city).
6. How long we keep it
- Your documents, transcriptions and batch details
- As long as your account is active, until you delete them.
- A page or batch you delete
- Removed from your account straight away. The database record is deleted; the files are moved to a holding area and permanently deleted after 30 days.
- Your whole account (when you delete it, or after inactivity — below)
- Deleted straight away: every batch, page, transcription, photo, preference, download record and invitation, and your sign-in account at Clerk. Records about you in our admin log keep no email address.
- Database backups
- Each nightly backup is kept for 30 days, then deleted automatically.
- Usage, cost and credit records
- Kept after your account is deleted, with the link to you removed, for our accounts.
- Free-pages record
- If you received the free pages, we keep a one-way, keyed fingerprint of your email address — not the address itself — even after your account is deleted, so the free pages can’t be claimed again.
- Invite requests
- Until Scriptolo opens to everyone, then deleted. You can ask us to delete yours sooner. If you get an account and later delete it, your request is deleted with it.
- Error reports
- Up to 90 days, at Sentry.
- Emails we send
- Resend keeps their content and logs for 30 days.
- Pages and text sent to Anthropic
- Deleted by Anthropic within 30 days, or up to 2 years if flagged for breaking its usage policy.
Inactive accounts. An account with no sign-in for 6 months will be deleted entirely. We’ll email you 30 days and 7 days beforehand, with a link to export everything, and signing in at any point resets the clock. We won’t delete an account unless a warning actually reached you. The rule started on 7 October 2026, so no account can be deleted under it before 7 April 2027.
So anything you delete is gone from every system we control — the app, its file storage and our backups — within 30 days.
7. Your rights
Under UK data protection law you can:
- access your data — use Settings → Export everything, or ask us;
- correct it — edit any transcription in the app, or ask us;
- delete it — delete pages, batches or your whole account in the app (Settings → Delete my account), or ask us;
- restrict or object to processing based on legitimate interests;
- take it elsewhere — the export gives you .txt and .docx files and your original photos;
- withdraw consent where we rely on it.
To exercise any right, email [email protected]. We’ll respond within one month. If you’re unhappy with how we handle your data, you can complain to the Information Commissioner’s Office (ico.org.uk, 0303 123 1113).
8. Cookies and similar storage
We use only what’s needed for the service to work — no analytics or advertising cookies — so there’s no consent banner.
__client (on clerk.scriptolo.com)
Clerk — the record that you’re signed in
Up to 400 days in your browser; a sign-in itself lasts 7 days
__session (on scriptolo.com, once signed in)
Clerk — a short-lived sign-in token
60 seconds, renewed automatically
__client_uat, __client_uat_… (on scriptolo.com)
Clerk — checks your sign-in is still valid
Up to 400 days
__cf_bm, _cfuvid (on clerk.scriptolo.com)
Cloudflare, for Clerk — bot protection for sign-in
30 minutes; until you close your browser
__clerk_environment (local storage)
Clerk — caches sign-in settings so pages load faster
Until cleared
scriptolo-upload-collapsed
Scriptolo — remembers whether you collapsed the upload form
1 year
The sign-up check (Cloudflare Turnstile) uses a one-time token, not a cookie.
9. Children
Scriptolo is for people aged 18 and over, and we don’t knowingly collect children’s data.
10. Security
Data is encrypted in transit (HTTPS). Access is limited to the operator. Passwords are handled by Clerk, not stored by us. The site sends strict security headers, including a Content Security Policy. Our logs hide filenames. Backups are kept with a separate provider, encrypted at rest, using write-only credentials.
11. Changes
We’ll post any changes here with a new effective date, and email you about significant ones.
12. Contact
Mark Hammonds, trading as Scriptolo — [email protected]