UMarkless — Privacy Policy

Last updated: 26 September 2026

UMarkless is a marking assistant for teachers. This policy says what it collects, who else sees it, what it cannot promise, and how to delete it — in plain language, because you are handing us other people's children's work.

The short version

• Student names are blacked out of a page before it is sent for marking, on every platform — with the limits set out under Where the promise stops.
• Page images are marked and discarded. We keep the marks, not the pictures.
• No ads, no analytics, no tracking, and students never have accounts.
• Deleting your account deletes everything, for good.

What we collect

Your account

Your email address, and the name, honorific, school and curriculum region you enter during setup. Your marking defaults (mode, strictness) are saved so they follow you to another device.

Student work you mark

Photos, PDFs, Drive files and Google Form or CSV responses you choose to mark. They are sent to the AI provider that marks them (see Who else sees it), and the resulting marks, feedback and annotations are stored on your account so they appear wherever you sign in.

Page images are not kept on our servers. They are passed through for marking and discarded. What we store is the result — scores, comments, question breakdowns — plus a one-way hash of each page, so that re-marking the identical page can be served from cache instead of being processed and paid for again. A hash cannot be turned back into the picture.

The pages themselves stay on your device: in the phone's own storage, or, in a browser, in that browser's storage on your computer. Deleting a marked result deletes its pages too. Papers you choose to mark overnight wait on your device and with Anthropic's batch service until they are marked, within 24 hours.

Students you enter

Names, your own student codes, class assignment and any notes you write. You type these; the app never gets them from anywhere else.

Usage

Which actions ran, token counts and the cost of each marking call. This enforces your plan's credit allowance and nothing else.

How names are kept out of marking

On a phone, on-device text recognition finds the Name:, Student: and Student ID: fields and paints them solid black in the copy that is uploaded. The unaltered page stays on your phone, and the name is read there only to file the result under the right student. The name is never sent.

In a browser, the same step runs on your own computer — nothing is sent anywhere to be read. A browser reads the printed Name: label rather than the handwriting, so it blacks out that whole line. The first time you upload student work in a browser, the app explains this and asks you to acknowledge it.

Imported Google Form and CSV answers go up keyed by row number, never by name. The name column is never sent, known student names are scrubbed out of the answer text, and multiple-choice questions are marked on your device and never sent at all.

What we do not collect

No location. No contacts. No photo library beyond the pages you pick. No device advertising ID. No analytics SDK. Students never have accounts and are never contacted.

Who else sees it

• Anthropic (Claude) — does the marking. Receives the redacted page images and the marking instructions. API data is not used for training.
• Google (Gemini) — fallback marking and page transcription, on the same terms. Not used for training under paid API terms.
• DeepSeek — a low-cost route for objective and short answers. Receives answer text only: never images, never names. Its terms store data in the People's Republic of China and permit training on submitted content. We can switch this route off for a school that needs it off; marking then uses Claude instead.
• Supabase — hosts the database and the marking service.
• RevenueCat, Google Play and Apple — handle subscriptions in the apps. Stripe handles them when you subscribe in a browser. We never see your card details.
• Google Drive — only if you switch on Drive export, and only inside the "UMarkless" folder the app creates. The app cannot see the rest of your Drive.

We do not sell your data, and we do not share it with anyone else.

Where the promise stops

Your responsibilities as a teacher

You decide what to mark. Your school or district likely has rules about sending student work to a third-party service — follow them. Where the law treats your school as the data controller, UMarkless acts as a processor on your instructions.

Deleting your data

Any single marked test — delete it in the app; the copy on our servers and the pages on your device go with it.

Your whole account — Settings → Delete my account. This erases, for good: your profile, every marked result, every class and student, your answer keys, your saved settings and your sign-in itself, on your device and on our servers. It cannot be undone by you or by us. Cancelling a subscription is separate and is done where you subscribed.

The only thing that survives is the anonymous marking cache described above: hashes and model output that carry no name, no email and no account id.

You can also ask us to delete your account, or email oscar.cs.lee@gmail.com.

Keeping it safe

Traffic is encrypted in transit. Your data is stored with row-level security, so a teacher can only ever see their own. Marking runs server-side with credentials that never ship inside the app, and spending caps limit what any one account can use.

Children

UMarkless is for teachers, not students. It has no student sign-up, sends nothing to students and shows no ads. Student work appears only because a teacher marked it, and only that teacher can see the result.

Changes

If this policy changes materially, you will be told in the app before the change takes effect.