Data Processing Terms

Last updated: November 5, 2026

1. Scope and when this DPA applies

These Data Processing Terms (the "DPA") supplement and form part of the AMP Terms of Service and Privacy Policy. They apply only where we process personal data contained in your request content on your behalf and applicable data-protection law requires a written processing agreement, for example where you are an organisation acting as a controller in the EEA, the United Kingdom, Switzerland or a US state with a comprehensive privacy law.

If you use AMP as an individual for your own purposes, this DPA generally does not create obligations between us: our handling of your account and usage data is described in the Privacy Policy instead. Where a customer is itself a processor for a third-party controller, we act as a subprocessor. Capitalised terms not defined here have the meaning given in the Terms of Service.

2. Roles of the parties

For personal data contained in Inputs and Outputs, you are the controller (or a processor acting for a controller) and we are the processor (or subprocessor). For account data, billing data and usage metadata we are an independent controller, not a joint controller with you; the Privacy Policy governs that processing.

Each party is responsible for complying with the obligations that data-protection law assigns to its own role. You are responsible for the lawfulness of the personal data you submit, for having a valid legal basis and for giving any required notices to data subjects. We are responsible for processing that data only as described here.

The processor is surfacecyber, a Delaware corporation, reachable at [email protected]. Its registered agent for service of process is Legalinc, 131 Continental Drive, Suite 305, Newark, DE 19713, USA (a registered agent address, not a place of business). The controller is the Customer identified in its AMP account, and its contact details are the email address on that account.

3. Details of the processing

ItemDescription
Subject matterRouting OpenAI-compatible API requests from the Customer to a selected model provider and streaming the response back
Nature of processingReceiving Inputs, transmitting them to the selected provider, returning Outputs, and logging usage metadata for billing and security
PurposeOnly to provide, meter, secure and support the Service in accordance with the Terms of Service
DurationFor the time needed to relay each request; request content is not retained after the response is delivered
FrequencyContinuous, as and when the Customer sends requests
Categories of data subjectsIndividuals whose personal data the Customer chooses to include in request content, and the Customer's own account users
Categories of personal dataAny personal data contained in prompts, transcript chunks or completions, plus account identifiers and usage metadata
Sensitive dataNone permitted. The Service is not designed for special categories of personal data and the Customer must not submit them

4. Documented instructions

We process personal data in request content only on your documented instructions, which are the Terms of Service, this DPA, the model and parameters you select in each request, and any additional written instruction we have agreed to. We will not sell or share that data, use it to train models, use it for advertising, or combine it with data from other customers for our own purposes.

If we are required by law to process personal data beyond those instructions, we will tell you before doing so unless we are legally prohibited. If we believe an instruction infringes data-protection law, we will notify you promptly. You remain responsible for ensuring your instructions are lawful.

5. Confidentiality of personnel

We limit access to systems that can carry request content to the small number of people who need it to operate the Service, bind them by confidentiality obligations, and remove their access promptly when their role ends. Request content is not exposed in our logs or analytics.

6. Technical and organisational measures

We maintain measures appropriate to the risk of a pass-through gateway. The table below is the description of measures referred to in any standard contractual clauses we enter into with you.

MeasureWhat we do
Encryption in transitTLS 1.2 or higher for requests to the gateway and console, and for connections to model providers
Encryption at restAccount, billing and usage data is stored on encrypted volumes; request content is not persisted
Pseudonymisation and minimisationUsage logs contain token counts, timestamps and key identifiers rather than request content; keys are shown in full only at creation
Access controlRole-based, least-privilege administrative access with individual accounts and periodic access review
Confidentiality, integrity and resilienceDocumented incident response, regular backups with periodic restore checks, and dependency and vulnerability scanning
Logging and monitoringLogging limited to usage metadata and operational events, used for billing, availability and abuse detection
Physical securityProvided by our hosting provider's data-centre controls; we do not operate our own data centre
Data minimisation and retentionRequest content is discarded after delivery; longer retention applies only to account, billing and usage data as described in the Privacy Policy
Erasure and portabilityAccount deletion removes profile and key records; usage and balance history can be exported from the console on request
Subprocessor assuranceWritten confidentiality and data-protection obligations for each subprocessor, with the list published in the Privacy Policy
We do not hold a SOC 2 report or ISO 27001 certificate and do not claim one. We may update these measures as the Service evolves, provided the overall level of protection is not materially reduced.

7. Subprocessors

You give us general written authorisation to engage the subprocessors listed in the Privacy Policy, including the model provider you select for each request. We will update that page and post a notice in the console before a new subprocessor begins processing personal data. You may object on reasonable data-protection grounds within 10 days of the notice.

If we cannot offer a commercially reasonable alternative, you may stop using the affected part of the Service. Because model providers are essential to the gateway, an objection may mean we can no longer offer you that model. We impose data-protection obligations on each subprocessor and remain liable to you for their performance of those obligations.

8. Personal data breaches

We will notify you without undue delay after becoming aware of a personal data breach affecting personal data we process on your behalf, and will take reasonable steps to contain and remediate it. We will give you the information and reasonable assistance you need to notify supervisory authorities and data subjects where the law requires. This does not apply where the breach results from your own acts or omissions, and a notice is not an admission of fault.

9. Data subject requests and assessments

If we receive a request from a data subject about personal data in request content, we will tell you promptly and advise them to contact you. You are responsible for responding, and we will provide reasonable technical and organisational assistance where you cannot respond without it. Because request content is not retained, our ability to assist with a specific past request may be limited; we will tell you when that is the case.

We will also reasonably cooperate with data-protection impact assessments and prior consultations that you are required to carry out, by providing information about the Service that you cannot obtain elsewhere. Each party remains responsible for its own obligations under those assessments.

10. Return and deletion

Request content is discarded after each response is delivered, so there is normally nothing to return. On termination of the Terms of Service, or on your written request, we will within 30 days delete the remaining personal data we process on your behalf and, where feasible, make your account and usage history available for export.

We may keep data where law requires it, in particular accounting records, or where it remains in routine backups that are cycled out on a short schedule. Retained data stays protected under this DPA and is not used for any other purpose. On request we will confirm in writing that deletion has been completed.

11. International transfers

Our infrastructure, subprocessors and model providers may be in countries other than yours. Where a transfer of personal data out of the EEA, the United Kingdom or Switzerland needs a safeguard, we will enter into the applicable standard contractual clauses with you (including the UK International Data Transfer Addendum where relevant) and carry out any required transfer assessment before the transfer takes place.

We are not certified under the EU-U.S. Data Privacy Framework and do not rely on it. If a transfer mechanism stops being valid, we will work with you to put a lawful alternative in place or to suspend the affected transfers. We will redirect a government request for personal data to you where we lawfully can, will not volunteer data to authorities, and will notify you of a legally binding demand unless prohibited.

12. Information and audits

On written request to [email protected], no more than once per calendar year, we will provide information reasonably needed to show compliance with this DPA: a description of our technical and organisational measures, relevant policies and answers to a reasonable security questionnaire. We do not hold third-party audit reports, so we cannot provide them.

If that information is not enough to meet a mandatory legal requirement, you may request a further audit, conducted remotely during normal business hours by an independent auditor bound by confidentiality, on reasonable prior notice and at your cost, in a way that does not disrupt the Service. Any such audit is limited to the processing of your personal data and our compliance with this DPA.

13. Precedence, term and liability

  • On the processing of personal data, the order of precedence is: any standard contractual clauses we have signed with you, then this DPA, then the Terms of Service, then the Privacy Policy.
  • This DPA takes effect when the Terms of Service do and stays in force for as long as we process personal data on your behalf; the confidentiality, deletion and liability provisions survive its end.
  • Claims under this DPA are subject to the exclusions and limitations of liability in the Terms of Service, except where data-protection law does not allow that limitation.
  • We may update this DPA to reflect changes in law or in the Service. Material changes will be announced in the console at least 3 business days before they take effect.