Metrum AI Bench Data Processing Addendum
Last Updated: 28 October 2026
This Data Processing Addendum (“DPA”) forms part of the agreement for Metrum AI Bench (the “Agreement”) between the customer identified in the Agreement (“Customer”) and Metrum AI, Inc., 1717 N I-35, Suite 300, Round Rock, Texas 78664, United States (“Metrum AI”). It applies when Metrum AI processes Customer Personal Data on Customer’s behalf.
1. Definitions
Terms used in this DPA have the following meanings. Other capitalized terms have the meaning given in the Agreement or in Data Protection Laws.
Customer Content means the workloads, datasets, prompts, model and endpoint responses, judge outputs, endpoints, machine registrations, run configurations, performance results, run results, and run logs that Customer and its users put into or produce in the Service, as the Privacy Policy describes.
Customer Personal Data means personal data in Customer Content. It does not include the account, billing, security, and service operations data for which Metrum AI is an independent controller.
GDPR means Regulation (EU) 2016/679, and UK GDPR means the GDPR as it forms part of the law of the United Kingdom.
Privacy Policy means the Metrum AI Bench Privacy Policy published in the Service.
Service means the Metrum AI Bench platform, the Metrum agent, and its command-line tools.
Standard Contractual Clauses means the clauses in Commission Implementing Decision (EU) 2021/914, as Section 12 applies them.
Data Protection Laws means all privacy and data protection laws that apply to the processing, including the GDPR, the UK GDPR, the Swiss Federal Act on Data Protection, applicable UAE, DIFC and ADGM data protection laws, and applicable US state privacy laws such as the California Consumer Privacy Act.
Security Incident means a breach of security that leads to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to, Customer Personal Data.
Sub-processor means a third party that Metrum AI engages to process Customer Personal Data.
2. Roles and scope
Customer is the controller of Customer Personal Data, and Metrum AI is its processor. Where Customer is itself a processor, Metrum AI acts as Customer’s sub-processor. Metrum AI is an independent controller of account, billing, security, and service operations data, as its Privacy Policy describes.
Annex I describes the processing. If this DPA conflicts with the Agreement, this DPA prevails for the processing of Customer Personal Data. If the Standard Contractual Clauses apply and conflict with this DPA, the Standard Contractual Clauses prevail.
3. Customer instructions
Metrum AI processes Customer Personal Data only on Customer’s documented instructions. The Agreement, this DPA, and Customer’s use and configuration of the Service are Customer’s complete instructions.
Metrum AI tells Customer promptly if it believes an instruction violates Data Protection Laws. If a law requires Metrum AI to process Customer Personal Data in another way, Metrum AI tells Customer first, unless that law forbids it.
4. Confidentiality
Metrum AI ensures that every person it authorizes to process Customer Personal Data is bound by a duty of confidentiality and has access only as far as their role requires.
5. Security
Metrum AI implements and maintains the technical and organizational measures in Annex II. Metrum AI may update those measures, provided that an update does not reduce the overall level of protection.
6. Sub-processors
- Customer gives general authorization for Metrum AI to engage the Sub-processors listed in Annex III.
- Metrum AI gives Customer at least 30 days’ notice by email before it adds or replaces a Sub-processor.
- Customer can object on reasonable data protection grounds within that period. If the parties cannot resolve the objection, Customer can terminate the affected part of the Service and receive a refund of prepaid fees for the remaining term.
- Metrum AI imposes data protection terms on each Sub-processor that protect Customer Personal Data at least as well as this DPA, requires each Sub-processor to process Customer Personal Data only for the contracted services, and prohibits each Sub-processor from using Customer Personal Data to train or fine-tune models for its own purposes unless Customer expressly agrees otherwise in writing. Metrum AI remains responsible for each Sub-processor’s performance.
Providers that Customer selects itself are not Sub-processors. These include cloud accounts that Customer connects to the Service and model endpoints or judge models that Customer adds. Those providers act on Customer’s instructions under Customer’s own agreements with them.
7. Requests from individuals
Metrum AI tells Customer within 5 business days if it receives a request from an individual about Customer Personal Data and does not answer it unless Customer tells it to. Metrum AI helps Customer respond to such requests, taking into account the nature of the processing.
8. Assistance
Metrum AI gives Customer reasonable help with data protection impact assessments and with consultations with supervisory authorities, where they relate to the Service and Customer does not have the information itself.
9. Security Incidents
Metrum AI notifies Customer without undue delay, and in any case within 48 hours, after it becomes aware of a Security Incident that affects Customer Personal Data. The notice describes the incident, the categories and approximate number of individuals and records concerned, the likely consequences, and the measures taken or proposed. Where Metrum AI cannot give all of this at once, it gives it in stages without undue delay. Notice of a Security Incident is not an admission of fault.
10. Deletion and return
When the Agreement ends, Customer can choose to have Customer Personal Data returned or deleted. If Customer asks for a return within 30 days after the Agreement ends, Metrum AI exports Customer Content in a machine-readable format.
Metrum AI deletes Customer Personal Data within 60 days after the Agreement ends unless a law requires it to keep some of it. Deleted data remains in encrypted backups for up to 35 days, until those backups expire. On request, Metrum AI confirms the deletion in writing.
11. Audits
Metrum AI makes available the information Customer needs to show compliance with Article 28 of the GDPR. This includes written answers to a reasonable security questionnaire once a year and any independent security reports Metrum AI holds.
If that information is not enough, or a supervisory authority requires it, Customer can audit Metrum AI once a year, with 30 days’ notice, during business hours, at Customer’s cost, and under a confidentiality agreement. Customer can use an independent auditor that is not a competitor of Metrum AI.
12. International transfers
Metrum AI processes Customer Personal Data in the United States. Metrum AI staff in the United States and India can access it to operate and support the Service, and cloud machines process it in the region Customer selects for each run. Where Data Protection Laws require a transfer mechanism, the following terms apply and are incorporated into this DPA:
| Transfer from | Mechanism |
|---|---|
| European Economic Area | Module Two (controller to processor) of the Standard Contractual Clauses, or Module Three (processor to processor) where Customer is itself a processor. Clause 7 (docking) applies. Option 2 (general authorization) applies under Clause 9, with the notice period in Section 6. The optional language in Clause 11 does not apply. Clauses 17 and 18 select the law and courts of Ireland. Annexes I to III of this DPA complete the Clauses' annexes. |
| United Kingdom | The International Data Transfer Addendum to the EU Standard Contractual Clauses, issued by the UK Information Commissioner, completed with the information in this DPA. |
| Switzerland | The Standard Contractual Clauses as above, with references to the GDPR read as references to the Swiss Federal Act on Data Protection and the Federal Data Protection and Information Commissioner as the competent authority. Switzerland counts as a Member State for Clause 18(c), so individuals in Switzerland can bring claims there. |
| United Arab Emirates, DIFC, and ADGM | The Standard Contractual Clauses as above, to the extent they provide or support appropriate contractual safeguards under the applicable UAE, DIFC, or ADGM data protection regime. |
| Other countries | The Standard Contractual Clauses as above, to the extent the applicable law accepts them as contractual safeguards. |
Where a Sub-processor is certified under the EU-US Data Privacy Framework or its UK and Swiss extensions, Metrum AI may rely on that certification for onward transfers. Metrum AI keeps the Standard Contractual Clauses available as a fallback where appropriate.
13. US state privacy laws
Where the California Consumer Privacy Act or a similar US state law applies, Metrum AI acts as Customer’s service provider or processor. Metrum AI does not sell or share Customer Personal Data, does not retain, use, or disclose it outside the direct business relationship with Customer or for any purpose other than providing the Service, and does not combine it with personal data from other sources except as that law permits.
Metrum AI gives Customer Personal Data the level of privacy protection required by applicable law. Customer may take reasonable and appropriate steps to ensure that Metrum AI uses Customer Personal Data consistently with those requirements and to stop and remediate unauthorized use. Metrum AI helps Customer respond to consumer requests as Section 7 describes and tells Customer if it can no longer meet these obligations.
14. Restricted uses of Customer Content
Metrum AI does not use Customer Content, including performance results or run configurations, for public Metrum AI leaderboards, published benchmarks, marketing, or public performance comparisons.
Metrum AI does not use Customer Content to train or fine-tune AI models unless Customer expressly agrees otherwise in writing.
Metrum AI requires its Sub-processors to process Customer Content only for the contracted services and prohibits them from using Customer Content to train or fine-tune models for their own purposes unless Customer expressly agrees otherwise in writing.
Metrum AI may process Service telemetry that is separate from Customer Content, such as usage counts required for billing, error rates, and availability information, to operate, secure, and support the Service.
15. Liability and term
Each party’s liability under this DPA is subject to the limitations in the Agreement, except where Data Protection Laws do not allow such a limitation. This DPA lasts as long as Metrum AI processes Customer Personal Data.
Annex I. Description of the processing
A. Parties
| Role | Party | Contact |
|---|---|---|
| Controller, or processor on behalf of its own customers, and data exporter | Customer, as identified in the Agreement | The privacy contact named in the Agreement |
| Processor and data importer | Metrum AI, Inc., 1717 N I-35, Suite 300, Round Rock, Texas 78664, United States | privacy@metrum.ai |
B. Processing details
| Item | Description |
|---|---|
| Individuals concerned | People whose personal data Customer includes in Customer Content, such as in datasets, prompts, model responses, judge outputs, run logs, or machine names, including Customer's users where Customer Content names them. |
| Categories of personal data | Any personal data Customer includes in Customer Content. Hostnames, serial numbers, MAC addresses, and network addresses of registered machines where these identify a person. |
| Sensitive data | None intended. Customer agrees not to put special categories of personal data into the Service unless the benchmark requires it and Customer has a lawful basis. |
| Frequency | Continuous, for as long as Customer uses the Service. |
| Nature of the processing | Storage, retrieval, transmission to machines that run benchmarks, computation of results, display, support, security processing, and deletion. |
| Purpose | Running AI inference benchmarks and quality evaluations, operating and supporting the Service, and showing results to Customer in accordance with Customer's instructions. |
| Retention | Customer Content is kept while the workspace exists and deleted within 30 days after the workspace is deleted. Run logs are kept for 90 days, or a longer period Customer requests. Telemetry samples are kept for 90 days. Machine registrations and hardware inventory are kept while the machine is registered and deleted within 30 days after it is removed. Support screenshots are kept for 12 months after the support request is closed, or deleted within 60 days after the Agreement ends if that is sooner. Deleted data remains in encrypted backups for up to 35 days. Section 10 governs deletion when the Agreement ends. |
| Transfers to Sub-processors | As listed in Annex III, for the same purpose and duration. |
| Competent supervisory authority | The supervisory authority determined under Clause 13 of the Standard Contractual Clauses. |
Annex II. Technical and organizational measures
Metrum AI maintains the following measures.
| Area | Measure |
|---|---|
| Encryption in transit | HTTPS (TLS) between browsers and the Service, and between the Metrum agent and the Service. |
| Credentials | AES-256-GCM encryption of cloud provider keys, Hugging Face tokens, and model endpoint and judge API keys before storage. Personal API tokens are stored only as hashes. |
| Secrets in logs | The Metrum agent removes common secret patterns, such as API keys and bearer tokens, from run logs before upload. Benchmark tools started by the agent remove the machine's hostname from their results. |
| Encryption at rest | Encryption of databases, storage volumes, and backups. |
| Access control in the product | Role-based access control with organization, workspace, and project scopes. Data-changing operations are checked against role permissions before they run. |
| Machine authentication | Each registered machine's agent authenticates with a token issued to that machine. |
| Staff access | Production access limited by role, protected by multi-factor authentication, and logged. |
| Logging and monitoring | Activity records of workspace actions and records of each run-log read, kept for 90 days. |
| Availability and recovery | Regular database backups, kept for up to 35 days, with restores used only to recover from an incident. |
| Change management | Changes pass automated checks before release. Database changes go through versioned migrations that are checked before they apply. |
| Data minimization | Card data is entered only on Stripe forms and never reaches Metrum AI. Cloud machines receive only the prompts, datasets, credentials, and settings each run needs. |
| Incident response | A documented process to assess and contain Security Incidents and to notify Customer within the period in Section 9. |
Annex III. Sub-processors
| Sub-processor | Purpose | Location |
|---|---|---|
| Amazon Web Services, Inc. | Hosting, storage, and backups. | United States |
| Amazon Simple Email Service (Amazon Web Services, Inc.) | Delivery of run, invitation, billing, and support email. | United States |
| Google LLC (Google Workspace) | Email hosting for the support inbox, which receives support requests and their screenshots. | United States |
| Okta, Inc. (Auth0) | Sign-in and identity management. | United States |
| Shadeform, Inc. and RunPod, Inc. | GPU machines that Metrum AI rents for Customer's runs, used only when Customer launches a run on Metrum-provided machines. | The region Customer selects for each run |
Stripe, Inc. processes billing data as an independent controller for fraud prevention and compliance and as Metrum AI’s processor for payments. Billing data is Metrum AI controller data, not Customer Personal Data, so Stripe is not listed as a Sub-processor for Customer Personal Data in this Annex.
Signatures
| Field | Customer | Metrum AI, Inc. |
|---|---|---|
| Name | ||
| Title | ||
| Date |

