Data protection
Data processing
Oor role wi personal data, whaur it is haudit, hoo lang it is keepit and hoo we support yer obligations as a controller.
Controller and processor roles
- RODMENA as controller
- For this wabsteid and oor ain business correspondence, as set oot in oor Privacy Policy.
- RODMENA as processor
- Whaur we operate or support seestems haudin yer uisers’ personal data unner contract, the wark is governed by a signed Data Processing Agreement (Article 28 UK GDPR).
Sub-processors
The providers ablow process personal data for RODMENA, ilk ane named by the company we contract wi. We gie customers wi a signed DPA at least 30 days’ notice o an intendit chynge, by email and in the sub-processor feed, and a customer may object afore the chynge taks effect.
| Provider | Company | Prupose | Whaur data is pitten throu | Transfer safeguard |
|---|---|---|---|---|
| OVHcloud | OVH Limited, England and Wales, company 05519821 | Virtual servers for the production database tier and some application services, and object storage for encrypted backups | Unitit Kinrick, France and Germany | France and Germany are covered by UK adequacy regulations |
| iDNet | Infinity Developments Ltd, England and Wales, company 03105579 | Virtual servers for the wabsteid and application services, and the office connection | Unitit Kinrick | Nane needit: processing bides in the Unitit Kinrick |
| UKNode | UKNode Ltd, England and Wales, company 15880458 | Servers in Manchester for a build runner, alerting, the partner portal and Tollgate | Unitit Kinrick | Nane needit: processin bides in the Unitit Kinrick |
| Google Workspace | Google Cloud EMEA Limited, Ireland | Staff email (Gmail), including correspondence with customers | Ireland, Unitit States and ither Google locations | UK Extension to the EU-US Data Privacy Framework (Google LLC), and EU Standard Contractual Clauses wi the UK International Data Transfer Addendum |
| Anthropic | Anthropic Ireland, Limited, Ireland | Claude Enterprise, the AI assistant RODMENA engineers use to operate its systems, which can see operational logs. AI tools see customer data only with the customer’s consent, and then through our secure multi-party computation (SMPC) technique. | Unitit States | EU Standard Contractual Clauses wi the UK International Data Transfer Addendum, in Anthropic’s data processing addendum |
| GitHub | GitHub, Inc., Unitit States | Hostin o source code an continuous integration | Unitit States | EU Staundart Contractual Clauses wi the UK Internaitional Data Transfer Addendum |
| OVHcloud (Canada) | OVH Limited, England and Wales, company 05519821 | A server in Canada that runs RODMENA’s own monitoring, security scanning and build jobs, and uptime.systems monitoring probes. A probe there may run a customer’s uptime check, and the monitored URL, request method and headers, any monitor credentials and the check result then pass through it | Canadae | Canada is covered by UK adequacy regulations for organisations subject to PIPEDA |
Chynges tae this register
3 November 2026
Anthropic: customer data only with consent
The Anthropic row said Claude Enterprise can see operational logs and data. It now says AI tools see customer data only with the customer’s consent, and then through our secure multi-party computation (SMPC) technique.
25 October 2026
UKNode named, Canada added
The register now names UKNode Ltd, which provides our Manchester servers. It had named Cloud Nord Limited, which owns the IP addresses UKNode uses. Tollgate is now listed among the services on those servers. The Google Workspace row now lists staff email only, the one service we use there. A server OVHcloud hosts for us in Canada was missing from the register. It runs our own monitoring, scanning and build jobs, and uptime.systems monitoring probes that may run a customer’s uptime checks.
5 October 2026
InferX remuived
InferX, whilk serves language-model inference ahint Prism, wis leetit in error acause nae customer personal data is sent til it. It noo appears unner the external services that process nae personal data.
5 October 2026
Registration completit
iDNet, Cloud Nord, Google Workspace, Anthropic and InferX war awready in uiss an war missin frae the earlier leet, whilk forby named the wrang OVHcloud company an descrived the iDNet servers as company-awned. The leet noo gies the providers’ contracting companies, processing locations an transfer safeguards.
External services that process nae personal data
RODMENA cmi5 airtins its audit chain wi a public RFC 3161 timestamp authority. That service gets a SHA-256 digest o a signed chain heid, aboot ilka fifteen meenits, and only for a customer whase chain has chynged. Nae personal data, nae identifiers and nae learning records are sent tae it. Whan it canna be reached, learning, launches, statements and evidence export are no affected, and anchoring retries on the next pass.
Prism, the model gateway o RODMENA, sends requests tae InferX Technologies, Inc. (Unitit States) for language-model inference. Nae customer personal data is sent tae it. Afore Prism is uised wi customer personal data, the model will be hostit in the Unitit Kinrick or providit unner a contract wi transfer safeguards.
Oor domain registrar an DNS provider hauds only domain an zone records.
RODMENA cmi5 as a processor
- Role
- A processor acting for the learning management system customer, which is the controller. Article 28 terms are on the Data Processing Agreement page.
- Whit is processed
- The learner identifier the customer’s system supplies, as an xAPI account of home page and name, and the learning records a course sends, including results and scores. Email-style identifiers are refused.
- Hou it is haudit
- Ilka customer’s data is separatit by rules the database enforces. Learner identities, xAPI statements and stored credentials are encryptit by the application afore storage. Learner identifiers are stored as keyed tokens thegither wi an encryptit copy the application can recover, and client IP addresses are never stored.
- Keepin
- Per tenant and contractual. The defaults are 1,095 days for registrations and statement bodies, configurable down to one day.
- Optional flows
- Aw inside RODMENA, wi nae new sub-processor. Whan a customer switches it on, saved-state and learner-preference documents, that can haud onything a course stores, includin free-text answers, are copied ae way tae the RODMENA LRS and deleted there wi the original or at retention. On request, statements are cross-checked against the LRS copy for the evidence pack. Statements cmi5 writes itsel can cairry RODMENA’s xAPI signature, removed wi the statement at retention or erasure.
- Wabhooks
- Sent anely tae HTTPS endpoints the customer registers, signed wi HMAC-SHA256, cairryin ids the customer awready hauds and timestamps. Nae learner identifier and nae learning record is sent. Events are keepit for 30 days.
- Delytion
- A learner’s records are pseudonymised in cmi5 straucht awa, their document copies in the LRS are stappit and taen awa, and the erasure is haundit tae the RODMENA LRS wi a recordit receipt, sae ae request reaches baith systems. Efter a database restore, ilka erasure is reapplied frae sealed records keepit ootside the database, as a step o the restore procedure. The reason recordit for it is a ticket reference or a code, never free text aboot a person.
- Return and deletion
- Under Article 28(3)(g), a customer’s export runs anely efter a second person approves it. It is encryptit tae the customer’s ain key and cairries a signed manifest o the tables the customer awns. At contract end, the customer’s data is deletit and the customer receives a signed, timestamped deletion certificate that lists whit wis remuived and whit is retainit for audit (the tamper-evident audit chain and its anchors). Backups and logs follow their ain retention, and LRS data has its ain erasure hand-off.
- Location
- The same database tier stated abuin, in the Unitit Kinrick, France and Germany, wi nae ither transfer. Course packages and erasure records are encrypted on oor host afore they are uplaidit tae object storage.
Processin locations an internaitional transfers
RODMENA is based in the Unitit Kinrick. Oor ain seestems an their data are hostit in Unitit Kinrick, France, Germany and Canadae. Some providers in the register process data elsewhere: Ireland, Unitit States and ither Google locations. Customer deployments rin whauriver the customer chooses, commonly on the customer’s ain infrastructure.
Ilka provider that processes data ootside the Unitit Kinrick, and the safeguard for that transfer, is shawn in the register abuin: OVHcloud, Google Workspace, Anthropic, GitHub and OVHcloud (Canada). Oor Terms are govrened by the law o England and Wales.
Keepin an deletin
As processor, we keep personal data only for the duration o the contract. Whan the engagement ends we delete or return it, as the controller chooses, and certify deletion on request. Retention for oor ain controller processing is descrived in the Privacy Policy. See forby exit & portability.
Data-subject requests
We help controllers respond tae data-subject richts requests (access, rectification, erasure, restriction, portability, objection) within the statutory ae-month period. Requests aboot data we control gang tae gdpr@rodmena.co.uk.
RODMENA Requests is whaur tae mak a data protection complaint, a data richts request, a complaint or feedback anent oor service, or a request frae a public authority. Oniebody can uise it by wab form, email, post or phone, an ye get a reference nummer for yer request.
- Complaint anent data protection
We acknowledge a data protection complaint within 30 days o receivin it.
- Data richts request
We answer within ae month. Gin a request is complex, we can extend that by twa mair months and tell ye why within the first month.
- Feedback or complaint
Anent oor products, oor service or this wabsteid.
- Request fae an authority
For public authorities and regulators.
Follae a request wi its reference · Prentable form for requests by post
Breach handling
Personal-data breaches are contained, investigated and documented. As processor, we notify the affected controller without undue delay after becoming aware of a breach. As controller, we notify the ICO within 72 hours where required, and affected individuals where the risk demands it.
DPA requests: legal@rodmena.co.uk · data-protection questions: privacy@rodmena.co.uk · see also the DPA summary and the Trust Centre.