Data processing agreement
Last updated 18 November 2026
This document is being reviewed by our legal adviser and may be updated. Questions? Email hello@los.digital.
This data processing agreement ("DPA") is between the business that subscribes to Rupert (the "Customer", the controller) and LOS Digital LTD (company number 16212975, "LOS", the processor). It forms part of the Rupert terms of service and applies whenever LOS processes personal data for the Customer in providing Rupert. It is intended to meet Article 28 of the UK GDPR.
1. Definitions
"UK GDPR", "personal data", "processing", "controller", "processor", "data subject" and "personal data breach" have the meanings given in the UK GDPR and the Data Protection Act 2018 ("Data Protection Law"). "Customer Data" means personal data that LOS processes for the Customer in providing Rupert.
2. The processing
| Subject matter | Providing Rupert: running the Customer's Rupert computer, carrying out jobs the Customer's staff ask for, and passing requests to AI models. |
| Duration | The length of the subscription, plus up to 30 days afterwards until deletion. |
| Nature and purpose | Hosting, storage, viewing, entering, changing and sending information in the Customer's systems at its staff's request; transcribing voice notes; producing summaries and records of what Rupert did. |
| Data subjects | The Customer's staff; and the Customer's clients and contacts whose details appear in the Customer's systems, emails and documents (for example customers, suppliers, applicants, landlords, tenants, buyers and sellers). |
| Types of personal data | Names and contact details; information in the Customer's records, emails, messages and documents; screenshots of pages Rupert works on; voice recordings sent to Rupert. Rupert is not designed for special category or criminal offence data, and the Customer should not ask it to process such data unless necessary. |
3. LOS's obligations
LOS will:
- process Customer Data only on the Customer's documented instructions, which are the terms of service, this DPA and the requests of the Customer's authorised staff through Rupert, unless the law requires otherwise (in which case LOS will tell the Customer first, unless the law forbids it). LOS will tell the Customer if it believes an instruction breaks Data Protection Law;
- make sure everyone at LOS who can access Customer Data is bound by confidentiality;
- take the technical and organisational measures in Annex 2 to protect Customer Data;
- use sub-processors only as set out in section 4;
- help the Customer, taking into account the nature of the processing, to respond to data subjects exercising their rights, and to meet its obligations on security, breach notification, data protection impact assessments and consultation with the ICO;
- notify the Customer without undue delay, and in any case within 48 hours, after becoming aware of a personal data breach affecting Customer Data, with the information the Customer reasonably needs;
- at the end of the subscription, delete Customer Data within 30 days, or return a copy of the Customer's documents first if the Customer asks within that time, unless the law requires LOS to keep it;
- make available the information reasonably needed to show compliance with this DPA, and allow audits by the Customer or its auditor on reasonable notice, no more than once a year (unless after a breach), at the Customer's cost and subject to confidentiality.
4. Sub-processors
The Customer gives general authorisation for LOS to use sub-processors. The current list is in Annex 1. LOS will tell the Customer's account owner by email at least 30 days before adding or replacing a sub-processor; the Customer may object on reasonable data protection grounds, and if the parties can't resolve it, the Customer may cancel without penalty. LOS will put data protection terms in place with each sub-processor that give at least the same protection as this DPA, and remains responsible for them.
5. International transfers
LOS will transfer Customer Data outside the UK only where Data Protection Law allows it: to a country covered by UK adequacy regulations (including the UK–US data bridge for certified organisations), or under the UK International Data Transfer Agreement or the UK Addendum to the EU Standard Contractual Clauses, with any additional measures needed.
6. The Customer's obligations
The Customer is responsible for having a lawful basis for the processing it asks for, for giving data subjects any required information, for the instructions its staff give Rupert, and for making sure it is permitted to use Rupert with each third-party system it asks Rupert to use.
7. Liability and precedence
The limits of liability in the terms of service apply to this DPA, except where Data Protection Law doesn't allow it. If this DPA and the terms of service conflict on data protection, this DPA wins.
Annex 1: Sub-processors
| Sub-processor | Purpose | Location |
|---|---|---|
| IONOS | Hosting of the Customer's Rupert computer, LOS's account system and email sending | UK and EU |
| OpenRouter, Inc. | Routing requests to AI models; speech-to-text. Configured to use only model hosts that don't store or train on data. | US |
| AI model hosts reached through OpenRouter (for the model the Customer's staff choose) | Running the AI model for each step of a job | Mainly the US; others depending on the model |
| Telegram (only if the Customer's staff connect it) | Carrying messages to and from Rupert | Telegram's data centres |
Stripe processes billing data as a separate controller for payment purposes.
Annex 2: Security measures
- Separation: each Customer has its own Rupert computer on its own server; no other customer's staff or Rupert can reach it.
- Access: the server accepts connections only over SSH with keys. Only the Customer's signed-in staff's computers, while the subscription is paid, are allowed; the list is refreshed every 30 seconds. LOS staff access is limited to administration and support.
- Sign-in: passwords stored as one-way hashes; a one-time emailed code for each new computer; limits on repeated attempts.
- Passwords for other systems: stored encrypted in Rupert Keychain on the Customer's Rupert computer; never shown to the AI, written to logs, or sent to LOS's account system or Telegram.
- Safety rules: Rupert treats text in emails, web pages and documents as information, not instructions; it asks a member of staff before changing, publishing, sending or deleting, unless that person's own words asked for the exact change; its own commands run in a locked-down sandbox.
- Records: every action is logged with time, who asked and before-and-after screenshots, on the Customer's Rupert computer.
- Updates: operating-system and browser security updates install automatically; LOS's own updates are signed and checked before installing, and roll back if a check fails.
- Data minimisation: LOS's account system holds only what's needed for accounts, billing and Telegram delivery; Telegram messages are deleted from it once collected (3 days at most).
- Backups: each Rupert computer's data is backed up, encrypted, so it can be restored if a server fails.