Privacy Policy

Last updated: 6 October 2026

This page explains what we process when you use Still Needs a Human, why we process it and who else sees it. It is written to be read rather than to be technically unassailable. If something here is unclear, ask us and we will answer plainly.

Who we are

Still Needs a Human Ltd is a UK company based at Building 3, Chiswick Park, 566 Chiswick High Road, London W4 5YA. This policy covers the Still Needs a Human platform (the What's Wrong QA checks, LQA scorecards and Eval engine bake-off), the in-editor browser extension and the TMS and editor integrations. We act as the controller for your account data, and as a processor for the translation content you send us to check.

What we process

• Account data: your name and email used to sign in and run your workspace. If you choose to sign in with Google, Google shares your account email and basic profile with us for authentication only.
• Translation content: the source and target segments, files and job metadata you upload, connect through a TMS or editor integration or send from the browser extension. We process it to produce your QA reports, LQA scorecards and MT evaluations.
• Requests from the site: the email, company and message you send through the contact or request forms, kept so a person can reply.
• Connection token and settings: for the browser extension, a connection token and your settings are stored locally in your browser (chrome.storage.local) so it can authenticate you. The token is revocable from the panel.
• Where you came from: when you first visit our site we set one small first-party cookie, snh_ft, for up to 30 days. It holds the date of your first visit, the page you landed on, the site that sent you (its name only), any campaign tags in the link and a count of the pages you viewed. It holds no identifier, is not shared with anyone and is used only to know how people find us when they sign up. When you sign up we keep what it holds with your workspace and remove the cookie. The sign-up form may ask how you found us (optional) and records your browser's time zone, language and device type with your sign-up.
• Usage events: which features a workspace uses, for example that a check ran and how many words it had, under a pseudonymous id rather than your name or email. Never the content itself.
• Operational logs: minimal technical logs needed to run and secure the service.

How your content is used and kept separate

Your content is processed only to produce your own quality results. Each workspace is isolated: content, configurations and reports are never shared between workspaces. We do not use your content to train our models, we do not sell or share your data and we run no advertising and no cross-site tracking. The one cookie our site sets before you sign in is snh_ft, described above: it holds no identifier and is never shared.

Checks can also be run from an AI assistant through a personal MCP link; the text is handled as any other check.

AI-assisted review (opt-in)

The AI review layer is a profile setting: the profiles we ship have it on, and a profile can switch it off. When it is on, the relevant segment text is sent to an AI model provider to help grade quality. AI calls run on our own accounts with each provider (platform keys), not on keys you supply.

Your workspace chooses which providers may receive its text. A workspace admin ticks them in Settings under AI providers, and the choice also holds for fallbacks and second opinions. New workspaces allow Google Gemini, OpenAI and DeepInfra; DeepSeek and the machine translation engines stay off until an admin allows them.

Text sent for review is fenced as untrusted content and used only to return findings for that run. We do not use it to train our models.

The browser extension

When you click Run What's Wrong inside a supported CAT editor, the extension reads the job you currently have open (source and target text plus match and lock metadata) from your own logged-in editor session and sends it to your workspace server to produce a report. It never modifies the job, and it activates only on the supported editor sites, never on any other website.

Emails we send

Some emails are part of running your account and always go out: the link that confirms your address, invitations, password resets, receipts, failed payments, the codes that confirm deleting a workspace or an account and the note that confirms an account is deleted.

Others help you get going and keep you posted on your plan: a welcome email when your workspace opens, one nudge a few days later if no check has run yet, a notice before a trial ends and a notice when your workspace is close to its monthly allowance of AI-reviewed words. Each of these carries an unsubscribe link at the foot. One click stops them for your address and changes nothing else, and you can also ask us through the contact form. None of our emails carries a tracking pixel or a tracked link.

Service providers

We rely on a small set of subprocessors. Each one handles data only to run the service.

• Railway: hosting for the application and its data.
• Resend: transactional email, such as invitations, password resets and contact messages.
• Sentry: error tracking, so we hear about a fault before you have to tell us. It receives the error, where in the service it happened and a pseudonymous id, scrubbed of your files, text, findings and reports.
• PostHog: product analytics, hosted in the EU, so we can see which features are used. Our server sends it usage events with a pseudonymous id, never your content, and it sets no cookie in your browser.
• Cloudflare Turnstile: a check on the sign-up form that a person, not a script, is signing up. It sees your browser and IP address, not your files.
• Cloudflare Web Analytics: page-view counts for this marketing site, without cookies. It sees the page address, your browser and your IP address. It runs on the public site and on the sign-up and sign-in pages. It never runs inside the signed-in app or on a link that carries a confirmation, invite or share key.
• Cloudflare Email Routing: forwards the email you send to your profile's QA address to us when your workspace uses QA by email. It checks the sender and passes the message on. It does not keep the message; its delivery log keeps the sender and recipient addresses. We keep the attached files as we keep any upload.
• Stripe: payments and subscriptions, when you buy a plan or a word pack. You enter your card on Stripe's own pages; we keep your billing email, country, company VAT number and invoices, never card details.
• Google Gemini: AI review and second opinions, when your workspace allows it.
• OpenAI: AI review and second opinions, when your workspace allows it.
• DeepInfra: AI review and second opinions on open models, when your workspace allows it.
• DeepSeek: AI review and second opinions, only if your workspace allows it.
• DeepL: machine translation in Eval, only if your workspace enables it.
• Google Translate: machine translation in Eval, only if your workspace enables it.
• Microsoft Translator: machine translation in Eval, only if your workspace enables it.
• Google: sign-in, only if you choose to sign in with Google.
• Crowdin: when you connect it, we read the strings you check and post findings back as comments.
• Smartling: when you connect it, we read the jobs you check and post findings back as issues.
• Phrase: when you use the browser extension in Phrase, it reads the job you have open in your own session.
• Dropbox: when you connect a folder, we read the files you drop there and write the reports back.

The fonts on this site are served from our own servers, so reading these pages sends no request to a font provider.

Storage and retention

Reports and scorecards are stored under your workspace account. Uploaded job files used to produce a report are removed automatically (within 24 hours). The locally stored extension token is removed when you disconnect.

Cookies: before you sign in our site sets only snh_ft, the first-visit cookie described under What we process. It expires 30 days after your first visit and is removed when you sign up. Signing in to the app sets a session cookie that keeps you signed in.

A workspace admin can delete the workspace in Settings, and you can delete your own account in User settings. You can also ask us to do either. Deleting a workspace cancels its paid plan first. Stripe keeps the customer and invoice records we must keep for accounting. When you delete your account, the checks you ran stay with their workspace and show a deleted user instead of your name and email.

Deleted data leaves the live service at once. It stays in our nightly backups for up to 14 days, and then those backups are deleted. We always keep the newest complete backup, so if the nightly backup stops working for a while, that one copy can be older until a new backup completes. If we ever restore a backup, every workspace and account deleted after that backup was taken is deleted again before the service opens.

Your rights

Under UK GDPR you can ask to access, correct or delete your personal data, and object to certain processing. You can download your own account data from User settings at any time. To make a request, reach us through the contact form.

Contact

Still Needs a Human Ltd, Building 3, Chiswick Park, 566 Chiswick High Road, London W4 5YA. Questions or requests? Reach us through the contact form.

Back to home · Terms · Security