Security and data protection
Praxel platform. Last reviewed: September 2026.
This page states what we actually do, including what we do not yet have. Where a control is listed as planned, it is not in place today. If you need evidence for any item below, or a copy of our data processing agreement, contact security@praxel.co.uk.
Roles
- Controller
- The training provider or college that enrols the learner.
- Processor
- Praxel, acting on the controller's documented instructions.
- Data we process
- Learner identity and contact details, eligibility and enrolment information, coursework submissions, assessment decisions and feedback, IQA activity, attendance and engagement, and support records.
Where data is held
- Primary database and file storage
- Supabase, UK (London, eu-west-2). Learner data is held in the United Kingdom. Migrated from the EU (Stockholm) region on 9 August 2026.
- Application hosting
- Vercel.
- Error monitoring
- Sentry, EU region (Frankfurt).
- Transactional email
- Resend.
- AI-assisted feedback
- Anthropic. Learner work is sent for the purpose of drafting assessor feedback only, and is not used to train models.
- Spreadsheet export
- Google (Apps Script / Sheets), where an organisation has asked us to mirror enrolment and progress data to a sheet it controls. Off unless requested.
That is the complete list. It is the same list as the register in our processor agreement, and if it changes we tell you before the change takes effect rather than after.
Protecting the data
- Encrypted in transit and at rest. HTTPS only, with HSTS. Storage and database encryption at rest is provided by the hosting platform.
- Row-level isolation between organisations. Every table carrying customer data is protected by a database policy scoping it to the owning organisation. This is enforced by the database, not by application code, and is verified by an automated probe that signs in as a real learner and confirms it cannot read another organisation’s records.
- Role-based access. Learner, assessor, IQA, liaison, administrator and external provider roles each see only what their role requires.
- Multi-factor authentication is required for staff, not merely offered. Each organisation sets its own enforcement date; once it passes, a staff account without a second factor is asked to enrol before it can use the platform. Every administrator on our live organisations holds one.
- Additional encryption of sensitive identifiers held in the learner record.
- Uploaded files are checked for type and size, and passed to malware scanning where an operator has configured it. Scanning fails closed.
Audit trail
Assessment decisions, enrolment changes, evidence and quality-assurance activity are written to an append-only audit log. Each entry is cryptographically chained to the one before it, so any alteration or deletion of a historic record is detectable rather than merely discouraged. The chain is verified automatically and can be re-verified on demand for an external verifier.
Availability and monitoring
- Automated checks run hourly against the live platform, asserting that learner work is saving, that the evidence trail is intact, that no approved unit lacks evidence, and that scheduled jobs are running.
- Failed saves are recorded and surfaced to staff, including failures that occur in the learner’s browser and cannot reach us at the time.
- Learner work is mirrored in the browser as it is typed, so a failed save can be recovered rather than lost.
- Backups are taken daily by the database provider and retained for seven days, in the same UK region as the live data. Write-ahead logs are archived continuously. Point-in-time recovery is not currently enabled, so the recovery point in a total-loss scenario is the most recent daily backup rather than the last few minutes. A documented restore procedure exists; we do not claim a tested recovery time.
Backups are for recovery, not archiving — the retention period below is met by the live record, which is never silently deleted.
Retention
Learner records are retained for seven years after completion or withdrawal, to meet awarding-organisation and funding requirements. Disposal is a deliberate, recorded action — records are never silently deleted, and every disposal decision is written to the audit log.
Your rights as the data controller
On this platform your organisation is the controller and we are the processor. That means these are your obligations and our job is to make them answerable.
- Data processing agreement
- Available on request, as an Article 28 processor agreement. It names every sub-processor, the categories of data, the security measures above, and what happens to your data when the contract ends.
- Subject access requests
- An administrator can export a single learner's complete record — profile, enrolments, application data, submissions, assessment decisions, reviews, diagnostics, contact log and attendance — as one readable document, so a statutory response does not depend on us.
- Erasure
- An administrator can erase a learner, including their uploaded files. Erasure is refused where a retention obligation or an open appeal applies, and the refusal and its reason are recorded — so a request you must decline is documented rather than simply not actioned.
- Portability and exit
- Evidence exports and funder reports are produced from the platform at any time and are yours. There is no lock-in mechanism: your records leave with you.
- Breach notification
- We notify you without undue delay and within 24 hours of becoming aware, which is tighter than the 72 hours Article 33 allows you as controller — so you keep most of the window.
Separation between organisations
The platform is shared infrastructure with per-organisation isolation enforced in the database, and we would rather be specific about that than let you assume either more or less than is true. Every table holding customer data carries a policy scoping it to the owning organisation, so a query that forgets to filter returns nothing rather than someone else’s learners. That isolation is demonstrated, not asserted: an automated check signs in as a real account in a real browser and proves it can reach its own organisation’s learner and cannot reach another’s — including positive controls, so the test cannot pass simply by being broken. The evidence is dated and available to you.
Two honest limits. It is a single database, so infrastructure-level faults are shared rather than isolated per customer. And our own platform-operator accounts can cross organisations by design, because somebody has to be able to support you — those accounts are named, require a second factor, and every action they take is in the audit log.
Certifications and independent testing
- Certifications and testing
- Our current position, including what we do and do not yet hold, is set out in our security and data protection pack. Email security@praxel.co.uk and we will send it.
- UK data residency
- In place. Database and file storage are both in London (eu-west-2), since 9 August 2026.
- Accessibility
- Partially conformant with WCAG 2.2 AA — see our accessibility statement.
Reporting a problem
If you believe you have found a security vulnerability, email security@praxel.co.uk. Please give us a reasonable period to investigate and fix before disclosing publicly. We will acknowledge your report and tell you what we find.
In the event of a personal data breach affecting a controller’s data, we will notify that controller without undue delay and within 24 hours of becoming aware of it.