For employers and procurement
Trust and security
What we do to protect your company's data and your students' data, who processes it for us, where, and for how long.
Documents
- Sub-processorsWho processes data for us, why and where
- Data processing agreementFor company accounts, with a printable copy
- Terms for company accountsSeats, invoices, refunds and liability
- Privacy noticeWhat we tell students about their data
Security
- Encryption in transit
- Every page and API call uses HTTPS. Browsers are told to use HTTPS only (HSTS, two years), and a strict content security policy stops the site being framed or loading scripts from elsewhere. The one exception is Google Analytics, which loads only after a visitor accepts analytics cookies.
- Sign-in
- Passwords are stored only as bcrypt hashes. Password reset links last one hour and work once. Sessions are checked against the account, so a password change or account deletion signs them out within a minute. People can also sign in with Google or GitHub.
- Who can see what
- Every record a student sees is checked against their own account. A company's managers see only their own company's seats and students, and only what is listed below. Our admin area needs an admin account, checked on every page and action. Admins don't use the team dashboard: they work from their own admin pages.
- Seats and invites
- Seat codes and invite links are long random values, and we store only a hash of each. An email invite works only for the email address it was sent to, for 30 days. Codes can be withdrawn at any time before they are used.
- Payments
- Stripe takes every payment. We never see or store full card numbers. Payment messages from Stripe are checked with Stripe's signature before we act on them.
- AI processing
- Answers are sent to Anthropic (Claude) to mark them. Under our agreement it does not use them to train its models, and we never use them to train AI models either.
- Uploads and logs
- Mark any mock is no longer offered, so no new files are uploaded. Files uploaded for it are kept only for the existing reviews, never shown to anyone else, and deleted 30 days after the review is ready. Our error logs remove email addresses, tokens and keys before they are stored.
- Hosting, encryption at rest and backups
- The app and database are hosted by Railway. We rely on Railway for encryption of stored data and for database backups. Ask us at privacy@eightymarks.com for the current details.
What a company sees of its students
- Their name and email address, the level and plan of their seat, and when they started
- When they were last active
- How many tasks have been marked (this week, and since their seat started), and how many mocks they've completed
- Where their recent practice sits against the pass line, as a practice estimate, and a "ready to sit" flag once our marking for their level is calibrated
- The core activities (task types) their recent marked tasks are weakest in, by name only
Never their answers, the marks of individual tasks, their feedback or their conversations with Dot. Students are shown this list before they accept a seat.
Sub-processors
The services that process personal data for us. We tell company managers by email at least 30 days before we add or replace one.
| Service | What it does for us | Personal data | Where |
|---|---|---|---|
| Railway | Runs the app, the background jobs and the database | All account, study, seat and order data | Confirmed on request |
| Anthropic (Claude) | Marks answers and writes feedback, rewrites and in-depth reviews; runs Dot, the study mentor | Answers and the tasks they answer, messages to Dot, and the student's first name in Dot's conversations | United States |
| SendGrid (Twilio) | Sends our emails: invites, receipts, reminders and account emails | Name, email address and the content of each email | United States |
| Stripe | Card payments, invoices, refunds and tax | Billing contact, company name, billing email, invoice details and payment details (we never see full card numbers) | United States and the European Union |
| Google Analytics | Counts visits to our public pagesOnly for visitors who accept analytics cookies | Pages visited and device details, without names or email addresses | United States |
We also use services to make our own teaching material (video storage, AI images and narration). They never receive your company's or your students' data. If a person chooses to sign in with Google or GitHub, that provider confirms who they are; it gets nothing else from us.
Where data leaves the UK, we rely on an adequacy decision or on approved safeguards, as our data processing agreement sets out.
If something goes wrong
If a personal data breach affects your company's data, we tell your account's managers without undue delay, and in any case within 48 hours of becoming aware of it. We tell you what happened, what data is involved, what we have done and what we suggest you do.
How long we keep data, and deleting it
- Account and study data: while the account is open and for 24 months after the last activity, then deleted or anonymised.
- A student can download their data or delete their account in Settings at any time. Deleting erases their name, email and password, so their study record can no longer be linked to them.
- What a company sees of a student stops when the seat's access ends, or as soon as a manager chooses End reporting. The student keeps their own account.
- Company account data (managers, invites, orders): kept while the account is open. When a company asks us to close its account, we delete it within 30 days, except order and invoice records, which tax law makes us keep.
- Support conversations: up to 24 months after the last message. Past Mark any mock uploads: 30 days after the review is ready.
Questions
Email privacy@eightymarks.com with security or data protection questions, including a supplier questionnaire.