Privacy

The free check needs no account. When you leave a question, your answer and its criterion go to our writing provider for checking. We do not store them for this check. If you buy a pass, you make an account and your work is saved in it until you delete it. When you press Write, your answers go to our writing provider with contact details removed, and it may keep them for up to 30 days. Dodo Payments takes your payment. We use one cookie, to keep you signed in. This page says exactly what happens.

Last updated 9 November 2026. Questions: hello@supportingstatement.co.uk

Who is responsible

Supporting Statement (supportingstatement.co.uk) is the controller for the personal data described here. The controller is the one who decides how your data is used. Contact: hello@supportingstatement.co.uk.

The short version

Making your checklist runs in your browser. Finished answers go to our writing provider for checking, without an account. We do not store them for this check.
To buy a pass you make an account with your first name and email. You sign in with a code we email you. There is no password.
In an account, your jobs, answers and statements are saved on our server. You can delete them, or the account, in Settings. We delete them 3 months after your last sign-in, and email you 7 days before.
When you press Write, your answers go to our writing provider with contact details removed. It may keep them for up to 30 days.
Dodo Payments takes your payment. We never see your card.
One cookie keeps you signed in, so there is no cookie banner. No tracking and no advertising from us.
We count how many checks, paywall openings and orders happen each day, as totals only.
You have rights over your data, and using them takes one email. See your rights.

In your browser

The tool saves your work in your browser's local storage, so it is still there when you come back. That is what the job asks for (the person specification) as you pasted it, the form type, the checklist made from it, your answers, any draft and the results of the check. If you bought a pass, the browser also keeps a pass token, which is a code the server can check. The pass token does not hold your statement. What you paste on the home page waits in this tab's session storage for a moment, until the tool opens.

Without an account, your saved work stays in this browser. Answer checking and writing send text as described below. Once you have an account, the same work is also saved there (see your account and saved work). The "Remove everything from this device" button removes the copy in this browser, including the pass token. Your account keeps its own copy.

Making the checklist, hints while you type, length checks and text checks run inside the page. When you leave a question, a separate check sends that answer and its criterion to our writing provider.

Your account and saved work

You need an account to buy a pass. The free check never asks for one. Here is what we keep for an account, and why:

Your first name and your email, so we can address you, send you a sign-in code and match a payment to you. We keep the email as you typed it, in lower case.
The date you last signed in, to know when to send the warning and when to delete.
Your jobs: what the job asks for as you pasted it, the form type, the checklist, your answers, any draft, the statements we wrote and the results of the check, so you can carry on from any device. A job is named after its first requirement until you rename it.
Your pass, kept with your account. It is linked to you by an account id, and your payment records are described under when you pay.
A sign-in code, for as long as it works, which is 10 minutes, and a sign-in session. We keep only a scrambled form of each, made with a secret only we hold.

Statements and answers can include health or other sensitive details if you type them. They are saved with the rest of your job, and you can delete them at any time.

We email you a 6-digit code. It works for 10 minutes and for five tries. When you enter it, we set a cookie that keeps you signed in for up to 30 days, or until you sign out. See cookies and similar storage.

Deleting

Settings, then "Delete my data", removes your jobs, answers and statements. Your account and your pass stay.
Settings, then "Delete my account", removes everything saved in your account and ends your pass. Records of payments stay, as described under how long we keep things. A copy of your work on another device stays in that browser until you remove it there.
If you do not sign in for 3 months, we delete your account and your saved work. We email you a warning 7 days before. Signing in before then keeps it.

Your name, your email and the text of your jobs are not written to our logs.

Checking your answers

When you leave a question, we send that answer and the criterion to OpenAI, our writing provider, to check the evidence and suggest a next step. This is free and needs no account. If the answer has not changed, we reuse the result saved in your browser.

Phone numbers, emails, capitalised postcodes, National Insurance and professional registration numbers are removed before sending and again on our server. Names and street addresses are not removed, so leave out details the criterion does not need.

We do not store your answers or the reply for this check, and never log the text. OpenAI may keep them for up to 30 days under the same terms as writing below. Signed in work is also saved in your account as described above. If checking is unavailable, the hints in your browser carry on.

When you write a statement

Writing needs a pass. This is what happens when you press Write:

The page looks for UK phone numbers, email addresses, postcodes written in capitals, National Insurance numbers and professional registration numbers (NMC, HCPC, GMC). It also looks for greeting and sign-off lines ("Dear ..." and "Yours sincerely" or "Yours faithfully"). It replaces each one with [removed]. It does not remove names or street addresses, so leave out anything the criteria do not need.
The rest goes to our server: the criteria, your answers, any draft you pasted, the form type and its word or character limit.
Our server passes it to our writing provider and sends the draft back to you.
The writing step keeps none of it. Its log line holds only the route, the result, the time taken, the number of attempts and the token counts (how much text the provider processed). The draft is then saved in your job, as above.

Our server also removes contact details again before sending, and the draft is checked for them before it is shown. When you ask for a change (Make it shorter, Use simpler words or Add more detail), the same steps run with your current draft and the change you picked.

Our writing provider

Our writing provider is OpenAI (the OpenAI API). OpenAI does not use what we send through its API to train or improve its models unless the customer opts in, and we do not opt in. OpenAI keeps abuse-monitoring logs of all API use for up to 30 days. These may contain what we sent and the checking reply or draft that came back. It keeps them longer only where the law requires it or to protect against harm. Source: OpenAI, data controls in the platform, checked 31 October 2026.

OpenAI is in the United States. It processes the text for us as our processor, which means it works for us on our instructions. The transfer is covered by the EU Standard Contractual Clauses, which are standard legal terms approved for sending data abroad. They come with the UK Addendum issued by the Information Commissioner. Both are set out in OpenAI's data processing addendum, which you can read in full.

Health and other sensitive details

Answers and statements sometimes mention health, disability or other sensitive matters. If you include them in an answer, they go to our writing provider when you leave the question, and again if you ask for writing. The provider may keep them for up to 30 days. In an account they are also saved in your job like the rest. You can delete saved work in Settings. Leave out anything the criteria do not need.

When you pay

Dodo Payments runs the checkout page and is the merchant of record. That means it is the seller on your bank statement and your receipt. It collects your name, email, billing country and payment details, charges you and applies VAT. It issues an invoice, and the licence key it makes for your pass may arrive by email from it. You never need to paste the key: the pass is added to your account.

We never receive your card details. We send Dodo Payments your email and an account id, so it can fill in the checkout and tell us which account paid. Messages from Dodo Payments to our server can carry your email and your licence key. We do not read or keep the email. We keep the key only as a salted hash (a scrambled form that cannot be turned back into the key).

We also keep the payment id, the product, the amount, the currency, the time and the status of each payment, with the pass dates and counts. If a payment is refunded, in whole or in part, we also keep the total refunded so far and a record of each refund: the refund id fromDodo Payments (or the message id when it sends none), the payment id, the amount and the time. For the 5-job pass we also store a hash of each criterion in each advert, so the pass can tell its jobs apart. We do not store the criteria text itself.

With the pass we keep the id that Dodo Payments gives your licence key. Dodo Payments can link that id to your customer record, so we list it here. We use it to check that the key is still valid and to match a refund to the pass.

Each message that Dodo Payments sends our server about a payment leaves a short record: the message id, the type of event and the time it arrived. It stops us handling the same message twice. A new message clears the records older than 30 days.

The page you come back to after paying removes the licence key and your email from the address bar before anything else loads. What Dodo Payments does with your details is in the privacy policy of Dodo Payments.

Security check

We use Turnstile from Cloudflare to tell a person from a script. It runs when you ask for a sign-in code, when we check a licence key after paying, and when an answer is first checked in a browser session or you first ask for writing. It does not read what you type into the page.

To do the check, Cloudflare receives signals from your browser. They are your IP address, a fingerprint of the secure connection, your browser's User-Agent header (the name and version it sends), and our site key (a public code that names this site) with the site's address.

Our server then confirms the result with Cloudflare and passes it your IP address for that check. Cloudflare says it cannot directly identify you from these signals. It handles them for us, and also uses them on its own account to improve Turnstile. Details are in Cloudflare's Turnstile privacy addendum, checked 31 October 2026. How long Cloudflare keeps these signals is set in that addendum, which we do not control.

The check runs in Cloudflare's own frame on challenges.cloudflare.com. We set no cookie for it and read none. What Cloudflare stores for the check is described in its cookie policy and the addendum. After a check passes, a token in this tab's session storage stands in for it for 12 hours.

Limits and your connection

So that one person cannot flood the service, we count requests per connection for up to a minute. The counter uses your IP address, or only its first part for an IPv6 address (the newer, longer kind), your account, or the pass id, or a scrambled form of the email you ask a code for. It lives in Cloudflare's rate limiting service for that minute. We do not store it and never write it to a log.

Hosting and logs

The service runs on Cloudflare Workers and Cloudflare D1, its hosting and database services. Cloudflare's automatic per-request log for our Worker, which would hold your IP address and the URL, is switched off. Our own log has one line for each answer checking, writing, payment, sign-in, account, activation and status request, and for each refused count, plus a daily-cap alert that holds only numbers.

Each line holds the route, the result, the time taken, a fixed word for the cause of any error, and token counts. No text, no email, no code, no name, no IP address and no web address.

Cloudflare keeps these log lines for up to 7 days (source: Workers Logs, checked 31 October 2026). We also keep a count of the statements written each day. It is a number only.

Cloudflare's servers may be outside the UK. Those transfers are covered by the EU Standard Contractual Clauses with the UK Addendum. Cloudflare also states it follows the Data Privacy Framework, a US scheme for data sent from Europe, with its UK extension. See Cloudflare's data processing addendum.

Cookies and similar storage

When you sign in, we set one cookie, ss_session. It holds a random session id that keeps you signed in, for up to 30 days or until you sign out. It is only readable by our server, is sent only to this site, and carries no tracking. The free check sets no cookie. It is strictly necessary for the account you asked for, so there is no cookie banner. We use no advertising or analytics cookies.

We also use local storage and session storage in your browser for the things on this page: your work in the tool, the pass token, a note that you are signed in, and the security check token. They are needed to run the tool you asked for. The law allows both without asking first (Privacy and Electronic Communications Regulations, regulation 6 and Schedule A1).

The checkout page runs on the site of Dodo Payments. Dodo Payments may set its own cookies; see its policy.

Counting, without tracking

We count six things, each as a number added to that day's total: a check finished, the paywall opened, a checkout started, an order, a statement written and a statement we could not write. The page sends the first two as they happen. Our server counts the other four.

The request the page sends holds only the name of the event in its body. We read nothing else from it and store nothing else. It carries no cookie, no account and no identifier that we store, and none of your text. A total cannot be traced to a person or to a browser, and only we read the totals.

As on every other route, your connection's address is used for up to a minute to limit how often one connection can send these. We do not store it. See limits and your connection.

Why we may process this

What we do	Why the law allows it
Running the free check	Our contract with you (UK GDPR Article 6(1)(b)): checking a finished answer needs the answer and its criterion. They go to our writing provider and are not stored by us for this check. Leave out sensitive details the criterion does not need.
Your account, sign-in and saved work	Our contract with you (UK GDPR Article 6(1)(b)): you cannot buy a pass, or carry on from another device, without them. For any sensitive detail you chose to type into saved work, your explicit choice to save it (Article 9(2)(a)); you can delete it at any time. Deleting an inactive account after 3 months is our legitimate interest in not keeping data we no longer need (Article 6(1)(f)).
Writing your statement	Our contract with you (UK GDPR Article 6(1)(b)). For any sensitive detail you chose to include, your explicit request when you press Write (Article 9(2)(a)).
Payments and passes	Our contract with you (Article 6(1)(b)). Our legitimate interest in handling refunds and disputes (Article 6(1)(f)); a legitimate interest is a good reason that does not override your rights. Dodo Payments keeps the payment records the law requires of it.
Security checks, rate limits and logs	Our legitimate interest in keeping the service working and free from abuse (Article 6(1)(f)), using only the detail described above.

You do not have to give us anything. The free check needs nothing from you. Without your answers we cannot write a statement.

We make no automated decisions about you that have a legal or similarly significant effect. Our rate limits and security check can refuse a request automatically. They do not look at who you are.

How long we keep things

What	How long
Your text in the free check (specification, answers, drafts)	Saved in your browser until you clear it. Finished answers and criteria are sent for checking but not stored by us for that check.
Your account: first name, email, last sign-in	Until you delete your account, or 3 months after your last sign-in. We email a warning 7days before.
Your saved work: jobs, answers, drafts, statements	Until you press "Delete my data" or delete your account, or 3 months after your last sign-in.
Sign-in session	Up to 30 days, or until you sign out or delete your account.
Sign-in code (scrambled)	Works for 10 minutes. The record is removed by a daily clean-up.
Text held by our writing provider	In its abuse-monitoring logs for up to 30 days.
Pass records (hashed licence key, the Dodo Payments id for the key, payment id, dates, counts, and the criterion hashes of a 5-job pass)	If you delete your account, the pass ends. The record of it stays as long as business and tax records must be kept, then is deleted on request.
Order records (payment id, product, amount, currency, time, status, refund time, the total refunded so far, and for each refund its id, the payment id, the amount and the time)	Kept for as long as business and tax records must be kept, then deleted on request.
Records of messages from Dodo Payments (message id, event type, time received)	30 days. A new message clears the older ones, so a quiet spell can keep them a little longer.
Log lines	Up to 7 days at Cloudflare.
Rate-limit counter	Up to a minute at Cloudflare, not stored by us.
Security-check signals	Kept by Cloudflare for the period in its Turnstile addendum, which we do not control.
Daily counts	Numbers only, kept.

Your rights

You have the right to see the data we hold about you and to have it corrected or erased. You can limit or object to how we use it, and get a copy you can take elsewhere. You can also withdraw your consent at any time.

To use any of these, email hello@supportingstatement.co.uk. So we can find the record, send the payment id from your Dodo Payments receipt. Never send your statement or your card number. We answer within one month (UK GDPR Article 12(3)).

You can delete your saved work and your account yourself in Settings, and change your first name there. For anything else, such as a copy of your data, email us from the address on your account. The saved text and checking results are in your browser, and "Remove everything from this device" removes it.

If you are unhappy with how we handle your data, you can complain to us first at hello@supportingstatement.co.uk. We answer within 2 working days. You can also complain to the Information Commissioner's Office (ICO, ico.org.uk), the UK's data protection regulator.

Children

The service is for people applying for jobs. This service is for people aged 16 or over, and we do not knowingly process a child's data.

Changes

We date every change at the top of this page. If how writing works changes in a way that matters, we also say so beside the Write button.