HITLy™ Cloud Data Processing Agreement
This Data Processing Agreement ("DPA") forms part of the HITLy Cloud Terms of Service ("Terms") between Metaspan Ltd, trading as HITLy™ (company number 13641200, registered office 3 Saxon Way West, Corby NN18 9EZ) ("Processor", "Metaspan"), and the Customer ("Controller"). The Customer accepts it by accepting the Terms. No signature is needed. Enterprise customers can ask for a countersigned copy at support@hitly.net.
1. Definitions
"Data Protection Law" means the UK GDPR, the Data Protection Act 2018, the EU GDPR (Regulation (EU) 2016/679) and other data protection laws that apply to the processing. "Personal data", "processing", "controller", "processor", "data subject", "personal data breach" and "supervisory authority" have the meanings given in Data Protection Law. "Customer Personal Data" means personal data in Customer Data that Metaspan processes for the Customer under the Terms.
2. Roles and scope
2.1 The Customer is the controller, or a processor acting for its own controllers. Metaspan is the processor, or sub-processor, of Customer Personal Data.
2.2 Annex 1 describes the processing.
2.3 This DPA does not cover data that Metaspan processes as a controller, such as account, billing, security log and support data. The Privacy Notice (https://hitly.net/privacy) covers that.
2.4 This DPA does not apply to self-hosted HITLy. Metaspan does not process data from self-hosted installations.
3. Instructions
3.1 Metaspan processes Customer Personal Data only on the Customer's documented instructions, unless the law requires otherwise. If it does, Metaspan will tell the Customer before processing, unless the law forbids that.
3.2 The Customer's instructions are:
- the Terms and this DPA;
- the Customer's configuration and use of the Service;
- any further written instructions that the parties agree.
3.3 Metaspan will tell the Customer if it believes an instruction infringes Data Protection Law.
4. Confidentiality
Metaspan ensures that everyone authorised to process Customer Personal Data is bound by confidentiality.
5. Security
5.1 Metaspan implements the technical and organisational measures in Annex 2. They are designed to meet Article 32 of the UK and EU GDPR.
5.2 Metaspan may update the measures, provided the overall level of protection does not fall.
6. Sub-processors
6.1 The Customer gives general authorisation for Metaspan to engage sub-processors. The current list is at https://hitly.net/subprocessors and forms Annex 3.
6.2 Metaspan will notify the Customer at least 30 days before adding or replacing a sub-processor. Notice is given by email to workspace owners who subscribe, and on the subprocessor page.
6.3 The Customer may object on reasonable data protection grounds within those 30 days. If the parties cannot resolve the objection, the Customer may terminate the affected Service before the change takes effect. Metaspan will refund any prepaid fees for the unused period.
6.4 Metaspan imposes data protection terms on each sub-processor that are no less protective than this DPA. Metaspan remains liable for its sub-processors' performance.
7. Data subject requests and assistance
7.1 If Metaspan receives a request from a data subject about Customer Personal Data, it will pass the request to the Customer without undue delay and will not answer it itself, unless the Customer authorises it to.
7.2 Taking into account the nature of the processing, Metaspan will help the Customer, by appropriate technical and organisational measures, to respond to requests, to meet its security obligations, and with breach notifications, data protection impact assessments and prior consultations.
8. Personal data breaches
8.1 Metaspan will notify the Customer without undue delay, and in any event within 48 hours, after becoming aware of a personal data breach affecting Customer Personal Data.
8.2 The notice will describe, as far as is then known:
- the nature of the breach;
- the categories and approximate numbers of data subjects and records concerned;
- the likely consequences;
- the measures taken or proposed.
Metaspan will add more information as it becomes available.
8.3 This lets the Customer meet its own 72-hour obligation to notify the supervisory authority. Notifying a breach is not an admission of fault.
9. Deletion and return
9.1 When the Service ends, or when a workspace or account is deleted, Metaspan deletes the Customer Personal Data concerned from HITLy Cloud's live systems straight away. HITLy Cloud backup copies roll off within up to 5 months. Pre-release database copies are deleted from the server within 30 days; any copies inside HITLy Cloud backups roll off with the backups, within up to 5 months. Until backups roll off, they are kept secure and are not used for anything else. If we ever restore from a backup, we re-apply account deletions made since that backup before the service resumes.
9.1A Customer Personal Data that the Customer includes in support emails is kept in Metaspan's support system for 2 years after the request is closed. We may keep support backups for up to 12 months, then they are deleted. They will include a UK off-site backup. Until they are deleted, support backups are kept secure and are not used for anything else.
9.2 Before deletion, the Customer may ask support for a copy of its data through a Data request.
9.3 Metaspan may keep data where the law requires, and protects it while it does.
10. Audits and information
10.1 Metaspan will make available the information reasonably needed to demonstrate compliance with this DPA, including answers to reasonable security questionnaires.
10.2 If that information is not enough, or a supervisory authority requires it, the Customer may carry out an audit, no more than once a year. The Customer must give 30 days' notice, the audit must take place during business hours, it must avoid disrupting other customers, and the auditor must be bound by confidentiality. The Customer bears its own costs.
11. International transfers
11.1 Metaspan processes Customer Personal Data in the United Kingdom. The UK benefits from an EU adequacy decision, so EEA customers may transfer personal data to Metaspan without further safeguards.
11.2 If a transfer of Customer Personal Data between the parties is a restricted transfer under Data Protection Law, these instruments are incorporated into this DPA by reference:
(a) EU transfers: the Standard Contractual Clauses approved by Commission Implementing Decision (EU) 2021/914 ("EU SCCs"):
- Module 2 (controller to processor), where the Customer is a controller;
- Module 3 (processor to processor), where the Customer is a processor.
The following choices apply:
- clause 7: the docking clause applies;
- clause 9(a): option 2 (general written authorisation), with the 30-day notice in section 6;
- clause 11: the optional language does not apply;
- clause 13: the supervisory authority set out in clause 13(a), according to the Customer's establishment or representative;
- clauses 17 and 18: the law and courts of Ireland.
Annexes I to III of the EU SCCs are completed by Annexes 1 to 3 of this DPA.
(b) UK transfers: the International Data Transfer Addendum to the EU SCCs, issued by the Information Commissioner under s.119A of the Data Protection Act 2018 ("UK Addendum"). Its Tables 1 to 3 are completed with the details in this DPA and its Annexes. For Table 4, either party may end the Addendum as allowed by its Section 19. Where the UK Addendum cannot apply, the International Data Transfer Agreement ("IDTA") applies, completed in the same way.
11.3 For onward transfers to sub-processors outside the UK and EEA, Metaspan relies on:
- an adequacy decision or adequacy regulations (including the UK–US Data Bridge and the EU–US Data Privacy Framework, where the sub-processor is certified); or
- the EU SCCs (Module 3), the UK Addendum or the IDTA, with a transfer risk assessment.
11.4 If this DPA conflicts with the EU SCCs, the UK Addendum or the IDTA, the transfer instrument prevails.
12. Liability and term
12.1 The limits and exclusions of liability in the Terms apply to this DPA, to the extent Data Protection Law allows.
12.2 This DPA lasts as long as Metaspan processes Customer Personal Data.
12.3 The governing law and courts of the Terms (England and Wales) apply, except where the EU SCCs require otherwise.
Annex 1: Details of processing
| Item | Details |
|---|---|
| Parties | Data exporter: the Customer (controller or processor), with contact details as in its account. Data importer: Metaspan Ltd (processor), contact support@hitly.net |
| Subject matter | Providing HITLy Cloud: a human-in-the-loop approval inbox, API and MCP server for AI agent workflows |
| Nature and purpose | Receiving, storing, displaying, routing and notifying approval items from the Customer's agents; recording human decisions and evidence; returning decisions to the agents; sending notifications by email and mobile push; forwarding evidence and traces to destinations the Customer configures |
| Duration | The term of the Terms, plus up to 5 months for HITLy Cloud backup copies to roll off and up to 30 days for pre-release database copies to be deleted from the server (copies inside backups roll off within the same 5 months). Support emails: as in section 9.1A |
| Categories of data subjects | The Customer's authorised users (staff, contractors); people whose data appears in content that the Customer's agents submit, such as the Customer's own customers or end users |
| Categories of personal data | User names and work emails; workspace membership and roles; any personal data the Customer's agents include in approval requests, prompts, questions, answers, evidence, comments and attachments; push tokens; decision timestamps and audit trails |
| Special category data | None, unless agreed in writing (see the AUP) |
| Frequency | Continuous |
| Retention | Under the Customer's plan. Completed items: Solo 10 days, Pro 30 days, Team 90 days, Enterprise 1,000 days or the period in the Enterprise contract. Audit log: Solo 30 days, Pro and Team 365 days, Enterprise 7 years (2,555 days). HITLy Cloud backups: live data deleted at once; backup copies roll off within up to 5 months. Pre-release database copies: deleted from the server within 30 days; copies inside backups roll off with the backups, within up to 5 months. Support system backups: we may keep them for up to 12 months; they will include a UK off-site backup |
| Sub-processor processing | As listed in Annex 3, for the purposes shown there |
| Competent supervisory authority | For UK transfers, the Information Commissioner's Office. For EU transfers, as determined by clause 13 of the EU SCCs |
Annex 2: Technical and organisational security measures
- Hosting. The production application, database and MCP server run on servers owned and operated by Metaspan Ltd in a UK data centre (High Wycombe). The data-centre provider supplies space, power and network only and has no logical access to data and does not process data on our behalf. The database is not reachable from the internet. Public traffic goes through a TLS-terminating reverse proxy.
- Encryption. All public endpoints use HTTPS (TLS). WAL-G and PBS backups are encrypted. Live data is protected by access controls.
- Access control. Staff access to production is limited to named Metaspan personnel, uses SSH keys, and follows least privilege. Credentials and secrets are held in access-restricted storage, are moving to a password manager, and are never committed to source code.
- User authentication. Passwords are stored hashed. Passkeys and multi-factor authentication are available. Sessions are server-side. Password-reset and email-verification links are single-use and expire. API keys can be revoked.
- Tenant isolation. Every request is authorised against workspace and project membership.
- Logging and monitoring. Account security events (MFA changes, recovery-code use and lockouts, passkeys added or removed, email verified, account deleted) are logged and linked to the user's account while it exists. After account deletion, the ID and email are replaced by keyed hashes and the IP address is shortened. These pseudonymised events are kept for 90 days, then deleted.
- Backups and resilience. The HITLy Cloud database is backed up daily to separate Metaspan-owned servers in the UK. Deleted data leaves them as HITLy Cloud backup copies roll off within up to 5 months. WAL-G and PBS backups are encrypted. HITLy Cloud backups are also copied to an off-site backup in the UK operated by Metaspan. A database copy is taken before each release and deleted from the server within 30 days; any copies inside HITLy Cloud backups roll off with the backups, within up to 5 months. We may keep support system backups for up to 12 months. They will include a UK off-site backup. If we ever restore from a backup, we re-apply account deletions made since that backup before the service resumes.
- Secure development. Changes go through code review and automated tests, and are checked in a test environment before production deployment. Dependencies are kept updated.
- Vulnerability management. Vulnerabilities can be reported through https://github.com/hitly-net/hitly/security/advisories/new and https://hitly.net/.well-known/security.txt.
- Incident response. There is a documented process to contain, assess and notify personal data breaches (section 8).
- Sub-processor management. Sub-processors are assessed before they are engaged, bound by written data protection terms, and listed publicly.
- Data minimisation. Analytics is self-hosted and cookieless. Push notifications carry only what is needed to show the item. HITLy Cloud sends no Customer Data to third-party AI providers. AI-assisted support is not built yet. If it uses a third-party model provider when launched, Metaspan will add that provider to Annex 3 with 30 days' notice under section 6.2 before it processes Customer Personal Data.
- Staff. Personnel are bound by confidentiality and receive data protection guidance.
Annex 3: Sub-processors
The current list is at https://hitly.net/subprocessors.
Version r9.6 · Effective 19 November 2026