Data Processing Agreement (Business Customers)
Last updated 16 November 2026 · Version 1.1
Contents
About this DPA
This Data Processing Agreement ("DPA") forms part of the Kalsenti Terms of Service (the "Terms") between Kalsenti Limited ("Kalsenti") and the business that accepts the Terms ("Customer"). It sets out how Kalsenti handles personal data on Customer's behalf when Customer uses the Service.
Customer accepts this DPA by accepting the Terms or by using the Service for business purposes. No signature is needed. A Customer that wants a signed copy can use the optional signature block at the end.
This DPA does not apply to individuals using the Service for their own personal purposes. Kalsenti's Privacy Policy covers them.
| Item | Detail |
|---|---|
| Kalsenti | Kalsenti Limited, a company registered in England and Wales (company number 17555690), whose registered office is at 82a James Carter Road, Mildenhall, Bury St Edmunds, England, IP28 7DE |
| Privacy contact | privacy@kalsenti.ai |
| Customer | The business named in the account or order form that accepts the Terms |
| Effective date | The date Customer accepts the Terms or, for an updated version, the date it takes effect under clause 15.3 |
| Service | Kalsenti's unified AI model API, dashboard, tools and support, as described in the Terms |
| Governing law | England and Wales |
1. Definitions
1.1 In this DPA:
- Account Data means personal data about Customer's personnel that Kalsenti needs to run Customer's account, such as names, email addresses, billing contacts and payment records.
- Customer Personal Data means personal data that Kalsenti processes on Customer's behalf in providing the Service, including personal data in Inputs and Outputs. It does not include Account Data or Usage Data.
- Data Protection Laws means all laws on privacy and personal data that apply to the processing of Customer Personal Data under the Terms, including the UK GDPR, the Data Protection Act 2018, the EU GDPR and US state privacy laws, each where it applies.
- EU GDPR means Regulation (EU) 2016/679.
- EU SCCs means the standard contractual clauses approved by Commission Implementing Decision (EU) 2021/914, as amended or replaced.
- Inputs means prompts, messages, files and other content that Customer or its end users send to the Service.
- Model Provider means a third party that hosts or runs an AI model made available through the Service.
- Outputs means content the Service returns in response to Inputs.
- Restricted Transfer means a transfer of personal data that needs a transfer mechanism under Data Protection Laws.
- Security Incident means a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, Customer Personal Data held by Kalsenti or its Subprocessors.
- Subprocessor means a third party that Kalsenti engages to process Customer Personal Data, including Model Providers.
- UK GDPR means the UK General Data Protection Regulation as defined in the Data Protection Act 2018.
- Usage Data means information about how the Service is used, such as timestamps, the model selected, token counts, latency, cost, error codes, API key identifiers and IP addresses. It does not include the content of Inputs or Outputs.
1.2 "Controller", "processor", "personal data", "processing", "data subject" and "supervisory authority" have the meanings given in Data Protection Laws. Where a law uses equivalent terms, such as "business" and "service provider", these terms are read accordingly.
1.3 Words defined in the Terms have the same meaning in this DPA unless this DPA defines them differently.
2. Roles and scope
2.1 Customer as controller. Where Customer is a controller of Customer Personal Data, Kalsenti is its processor.
2.2 Customer as processor. Where Customer processes Customer Personal Data for its own clients, Kalsenti is Customer's subprocessor. Customer confirms that its clients have authorised Customer's instructions, Kalsenti's appointment and Kalsenti's use of Subprocessors under this DPA. Customer is the single point of contact for its clients, and Kalsenti has no direct obligations to them unless Data Protection Laws require it.
2.3 Affiliates. Where Customer's affiliates use the Service under Customer's account, Customer enters into this DPA for itself and on their behalf. Only Customer may enforce this DPA against Kalsenti.
2.4 Details. Annex 1 sets out the subject matter, nature, purpose and duration of the processing, and the types of personal data and data subjects.
3. Kalsenti's own data
3.1 Kalsenti is an independent controller of Account Data and Usage Data. It processes them under its Privacy Policy to run and bill accounts, keep the Service secure, prevent fraud and abuse, comply with the law, and operate and improve the Service.
3.2 Kalsenti may create aggregated or de-identified statistics from Usage Data that do not identify Customer or any individual, and may use them for any purpose.
3.3 Customer should not put personal data into request metadata, such as user identifiers or tags, other than pseudonymous identifiers.
3.4 The rest of this DPA does not apply to Account Data or Usage Data, except that Kalsenti also protects them with the measures in clause 6.
4. Processing instructions
4.1 Kalsenti will process Customer Personal Data only on Customer's documented instructions, unless the law requires otherwise. Customer instructs Kalsenti to process Customer Personal Data to:
(a) provide, maintain, secure and support the Service, including sending Inputs to the Model Provider that serves the model Customer selects and returning Outputs;
(b) route a request to another provider of the same or a similar model where Customer has enabled fallback or automatic routing;
(c) store chat history and, for models that require it, safety logs, as set out in Annex 1;
(d) detect, prevent and report abuse, fraud, security threats and breaches of the Terms or the law, including by checking images against known child sexual abuse material, filtering keywords, checking samples of requests with automated safety tools, and reporting suspected child sexual abuse material to the authorities;
(e) transfer Customer Personal Data as clause 8 allows;
(f) follow Customer's settings and use of the Service, the Terms and this DPA; and
(g) follow other reasonable written instructions that Kalsenti agrees to. Kalsenti may charge for instructions that go beyond the Service's standard features.
4.2 Where the law requires Kalsenti to process Customer Personal Data in another way, Kalsenti will tell Customer before doing so, unless the law prohibits this.
4.3 Kalsenti will tell Customer if, in its opinion, an instruction infringes Data Protection Laws. Kalsenti may suspend the affected processing until Customer confirms or changes the instruction.
4.4 No training and no sale. Kalsenti will not use Customer Personal Data, Inputs or Outputs to train, fine-tune or improve AI models. Kalsenti will not sell Customer Personal Data or use it for advertising.
5. Customer responsibilities
5.1 Customer is responsible for:
(a) having a lawful basis for the processing, and giving any notices and obtaining any consents that Data Protection Laws require;
(b) the content of Inputs, and making sure its instructions comply with Data Protection Laws;
(c) choosing models, providers, routing and retention settings that suit its data; and
(d) keeping its API keys and account credentials secure.
5.2 Sensitive data. The Service is not designed for special category data, criminal offence data or children's data. Customer may submit such data only where it has a lawful basis and has decided that the Service's safeguards are appropriate. Kalsenti will protect any such data under this DPA in the same way as other Customer Personal Data.
5.3 Regulated data. Customer must not submit data that needs extra contract terms under sector-specific rules, such as protected health information under HIPAA, unless Kalsenti has agreed those terms in writing.
6. Confidentiality and security
6.1 Kalsenti will make sure that anyone it authorises to process Customer Personal Data is bound by a duty of confidentiality.
6.2 Kalsenti will maintain technical and organisational measures appropriate to the risk, including those in Annex 2. Kalsenti may update these measures, provided the overall level of protection does not materially decrease.
7. Subprocessors
7.1 General authorisation. Customer gives Kalsenti general written authorisation to engage Subprocessors, including Model Providers, on the terms of this clause.
7.2 Subprocessor list. Kalsenti will give Customer its current list of Subprocessors on request to privacy@kalsenti.ai. The list shows each Subprocessor's name, location and processing task. The list is Kalsenti's confidential information. Customer may share it only with its professional advisers, regulators and, where they need it to meet their own data protection obligations, its own clients, in each case under a duty of confidentiality.
7.3 Models Customer selects. When Customer selects a model, or enables a provider or routing option, Customer authorises the Model Providers that serve it. On request, Kalsenti will tell Customer which Model Providers serve a model, where they process data and how long they keep Inputs and Outputs. Kalsenti's model list shows each model's processing region and whether a zero data retention agreement applies.
7.4 Notice of changes. Kalsenti will give at least 10 days' notice before a new or replacement Subprocessor, other than one authorised under clause 7.3, processes Customer Personal Data. Kalsenti will give notice by email to customers who ask for notices at privacy@kalsenti.ai, or by a notice in the dashboard. The notice will state the Subprocessor's processing task and country, and Kalsenti will give its name on request.
7.5 Urgent changes. Where Kalsenti must replace a Subprocessor urgently for security, legal or service continuity reasons, it may do so straight away and will give notice as soon as it reasonably can.
7.6 Objections. Customer may object to a new Subprocessor on reasonable data protection grounds within the notice period. The parties will discuss the objection in good faith. If they cannot resolve it, Kalsenti may stop using that Subprocessor for Customer, or Customer may stop using the affected part of the Service. If neither is practical, Customer may terminate the affected Service and receive a refund of any prepaid fees for the unused period. This is Customer's only remedy for an objection.
7.7 Subprocessor terms. Kalsenti will have a written contract with each Subprocessor that imposes data protection obligations no less protective than those in this DPA, to the extent relevant to the Subprocessor's service. Kalsenti remains liable to Customer for each Subprocessor's performance of those obligations, subject to clause 13.
8. International transfers
8.1 Where data goes. Kalsenti is based in the United Kingdom. Kalsenti and its Subprocessors may process Customer Personal Data in the UK, the European Economic Area (EEA), the United States and any other country where they operate. Customer authorises these transfers.
8.2 Kalsenti's onward transfers. For each Restricted Transfer to a Subprocessor, Kalsenti will put in place a transfer mechanism recognised by Data Protection Laws. Examples are UK adequacy regulations, the UK-US Data Bridge, the ICO's International Data Transfer Agreement or UK Addendum, and the EU SCCs. Kalsenti will carry out any transfer risk assessment the law requires.
8.3 Transfers from the UK. A transfer from a Customer in the UK to Kalsenti is not a Restricted Transfer.
8.4 Transfers from the EEA. Transfers from the EEA to Kalsenti rely on the European Commission's adequacy decision for the UK. If that decision stops applying, the EU SCCs apply as set out in Annex 3.
8.5 Transfers from Switzerland. Transfers from Switzerland rely on Switzerland's recognition of the UK as providing adequate protection. If that recognition stops applying, the EU SCCs apply with the Swiss changes in Annex 3.
8.6 Other countries. If the law of another country requires a transfer mechanism for Customer's transfer to Kalsenti, the parties will use the EU SCCs as adapted for that law, or another mechanism that Kalsenti reasonably agrees to.
8.7 Changes in law. If a transfer mechanism stops being valid, Kalsenti may switch to another lawful mechanism. Customer will sign any documents reasonably needed for this.
9. Security incidents
9.1 Kalsenti will notify Customer without undue delay, and in any event within 72 hours, after becoming aware of a Security Incident. Kalsenti will send the notice to the email address on Customer's account.
9.2 The notice will describe, as far as then known, what happened, the data and data subjects affected, the likely consequences and the steps taken or proposed. Kalsenti will give further information in stages as it becomes available.
9.3 Kalsenti will take reasonable steps to contain, investigate and fix the Security Incident.
9.4 Customer is responsible for any notice it must give to supervisory authorities or data subjects. Kalsenti will not notify them about Customer Personal Data on Customer's behalf unless the law requires it.
9.5 A Security Incident does not include unsuccessful attempts or activities that do not compromise security, such as pings, port scans or failed log-in attempts.
9.6 Notice of a Security Incident is not an admission of fault or liability.
10. Assistance and requests
10.1 Data subject requests. If a data subject contacts Kalsenti about Customer Personal Data, Kalsenti will refer them to Customer and will not respond itself, unless the law requires it. Taking into account the nature of the processing, Kalsenti will help Customer respond to data subject requests and complaints, through the Service's features or other reasonable means.
10.2 Impact assessments. Taking into account the nature of the processing and the information available to it, Kalsenti will give Customer reasonable help with security, data protection impact assessments and prior consultation with supervisory authorities.
10.3 Requests from authorities. If a public authority or other third party asks Kalsenti for Customer Personal Data, Kalsenti will refer it to Customer where possible. Kalsenti will tell Customer about the request unless the law prohibits this, and will disclose only what the law requires.
10.4 Costs. Kalsenti may charge reasonable costs for help under this clause that goes beyond the Service's standard features, unless the help is needed because Kalsenti breached this DPA.
11. Audits and information
11.1 Kalsenti will give Customer the information reasonably needed to show that Kalsenti complies with this DPA. This includes answering a written security questionnaire once a year and sharing existing security documentation and any third-party reports or certifications Kalsenti holds.
11.2 Customer may audit Kalsenti, including by inspection, where:
(a) the information under clause 11.1 is not enough to show compliance;
(b) a supervisory authority requires it; or
(c) a Security Incident has occurred.
11.3 An audit must be on at least 30 days' written notice, within a scope agreed in advance, during business hours and under a duty of confidentiality. It may take place no more than once in any 12 months, unless clause 11.2(b) or (c) applies. It may be carried out by Customer or by an independent auditor that is not a competitor of Kalsenti. Customer bears its own costs and pays Kalsenti's reasonable costs, unless the audit finds a material breach of this DPA by Kalsenti.
11.4 An audit does not give access to other customers' data or to Subprocessors' facilities. For Subprocessors, Kalsenti may rely on their own audit reports and certifications.
12. Deletion and return
12.1 During the term, Customer can delete Customer Personal Data through the Service where the Service allows.
12.2 When the Service ends, Customer may export Customer Personal Data available through the Service, or ask Kalsenti to return it within 30 days of the end date. After that, Kalsenti will delete Customer Personal Data within 30 days, unless the law requires Kalsenti to keep it.
12.3 Copies in backups will be deleted under Kalsenti's normal backup rotation. Data that Kalsenti must keep by law, or that is in backups awaiting deletion, stays protected under this DPA and is not otherwise processed.
12.4 Kalsenti will confirm deletion in writing if Customer asks.
13. Liability
13.1 Each party's liability under this DPA is subject to the limits and exclusions of liability in the Terms. Liability under this DPA and the Terms counts towards one combined limit.
13.2 Nothing in this DPA limits liability that cannot be limited by law, or either party's liability to data subjects under Data Protection Laws or under the EU SCCs where they apply.
13.3 Only Customer, as the party to the Terms, may bring claims against Kalsenti under this DPA.
14. US state privacy laws
14.1 Where the California Consumer Privacy Act or a similar US state law applies, Kalsenti acts as Customer's service provider or processor. Customer discloses Customer Personal Data to Kalsenti only for the limited and specified purpose of providing the Service.
14.2 Kalsenti will not:
(a) sell or share Customer Personal Data, as those terms are defined in those laws;
(b) retain, use or disclose Customer Personal Data for any purpose other than providing the Service, or outside its direct business relationship with Customer, except as those laws allow; or
(c) combine Customer Personal Data with personal data it receives from others, except as those laws allow.
14.3 Kalsenti will comply with those laws as they apply to it and will tell Customer if it can no longer meet its obligations under them. Customer may then take reasonable steps to stop and remedy unauthorised use of Customer Personal Data. Kalsenti certifies that it understands and will comply with this clause 14.
15. General
15.1 Order of precedence. If there is a conflict, the EU SCCs (where they apply) take priority, then this DPA, then the Terms.
15.2 Term. This DPA continues for as long as Kalsenti processes Customer Personal Data under the Terms.
15.3 Updates. Kalsenti may update this DPA, for example to reflect changes in the law, transfer mechanisms or the Service. Kalsenti will give at least 30 days' notice, by email or in the dashboard, of any update that has a material adverse effect on Customer. An update will not reduce the overall protection of Customer Personal Data unless the law requires it. If Customer objects to an update, it may terminate the Service before the update takes effect. Otherwise, continued use of the Service after that date means Customer accepts the update.
15.4 Governing law. This DPA is governed by the laws of England and Wales, and the courts of England and Wales have exclusive jurisdiction, except where the EU SCCs require otherwise.
15.5 Severability. If any part of this DPA is found invalid, the rest continues in effect.
Annex 1: Processing details
| Item | Detail |
|---|---|
| Data exporter | Customer, as named in its account or order form. Contact: the account owner, or the contact Customer gives in writing. Role: controller, or processor for its own clients |
| Data importer | Kalsenti Limited (company number 17555690), 82a James Carter Road, Mildenhall, Bury St Edmunds, England, IP28 7DE. Contact: privacy@kalsenti.ai. Role: processor or subprocessor |
| Subject matter | Providing the Service to Customer under the Terms |
| Nature of processing | Receiving Inputs, routing and transmitting them to Model Providers, returning Outputs, storing chat history and safety logs as described below, securing data, and deleting it |
| Purpose | Providing the Service in line with Customer's instructions in clause 4 |
| Data subjects | Customer's personnel, end users and clients, and any other individuals whose personal data Customer includes in Inputs |
| Personal data | Any personal data in Inputs and Outputs, such as names, contact details, identifiers and other content Customer chooses to send |
| Special category data | Not intended. Customer decides whether to submit it under clause 5.2. If submitted, the measures in Annex 2 apply to it |
| Frequency | Continuous, as Customer sends requests |
| Duration | The term of the Terms, plus the deletion period in clause 12 |
| Retention by Kalsenti | API requests are processed in memory and not stored. Chat history is stored encrypted, in a way Kalsenti can't read, until Customer deletes it. Requests to abliterated models are logged for 30 days. When safety checks block a request, Kalsenti records the reason, not the content |
| Retention by Model Providers | Depends on each Model Provider's terms with Kalsenti. Available on request under clause 7.3 |
| Subprocessors | As described in clause 7 |
| Competent supervisory authority | The Information Commissioner's Office (UK). For the EU SCCs, the authority determined under their Clause 13 |
Annex 2: Security measures
Kalsenti maintains at least the following measures.
| Area | Measure |
|---|---|
| Encryption in transit | TLS 1.2 or higher for traffic to and from the Service, and between the Service and Model Providers |
| Encryption at rest | Stored Customer Personal Data, including chat history and safety logs, is encrypted at rest |
| Access control | Access to production systems is limited to authorised personnel who need it, using unique accounts and multi-factor authentication, and is removed promptly when no longer needed |
| API authentication | API access uses Customer-managed API keys, which Customer can rotate or revoke |
| Credentials | Credentials are not stored in source code and are rotated if compromise is suspected |
| Logging | Request metadata and access to systems are logged for billing, security and support |
| Separation | Each customer's data is logically separated from other customers' data |
| Data minimisation | Inputs and Outputs are processed only to provide the Service and are not used for model training |
| Retention | Inputs and Outputs are kept only as set out in Annex 1 |
| Vulnerability management | Systems and dependencies are patched on a risk-prioritised basis |
| Incident response | A documented process to detect, contain, investigate and notify Security Incidents |
| Backups | Where backups are kept, they are encrypted and deleted on a regular rotation |
| Subprocessor checks | Each Subprocessor's security and data protection terms are reviewed before use |
| Personnel | Everyone with access to Customer Personal Data is bound by confidentiality obligations |
Annex 3: Transfer terms
This Annex applies only where clause 8.4, 8.5 or 8.6 says the EU SCCs apply. In that case the EU SCCs are incorporated into this DPA by reference and completed as follows.
| EU SCCs term | How it is completed |
|---|---|
| Modules | Module Two (controller to processor) where Customer is a controller. Module Three (processor to processor) where Customer is a processor |
| Clause 7 (docking clause) | Does not apply |
| Clause 8.9 (audits) | Customer exercises its audit rights as set out in clause 11 of this DPA |
| Clause 9(a) (subprocessors) | Option 2, general written authorisation. The notice period is the one in clause 7.4 of this DPA |
| Clause 11(a) (redress) | The optional wording does not apply |
| Clause 13 (supervision) | The competent supervisory authority is the one determined under Clause 13 according to Customer's situation |
| Clause 17 (governing law) | Option 1. The law of Ireland |
| Clause 18(b) (courts) | The courts of Ireland |
| Annex I | Completed by Annex 1 of this DPA |
| Annex II | Completed by Annex 2 of this DPA |
| Annex III | Completed by the Subprocessor list under clause 7.2 |
| Certification of deletion | Given on Customer's request |
Switzerland. For transfers subject to the Swiss Federal Act on Data Protection (FADP): references to the EU GDPR are read as references to the FADP; the Swiss Federal Data Protection and Information Commissioner is the competent supervisory authority; and the term "member state" does not prevent data subjects in Switzerland from bringing claims where they habitually reside.
Optional signature
Customer does not need to sign this DPA; it applies when Customer accepts the Terms. A Customer that wants a signed copy can complete this block and send it to privacy@kalsenti.ai, and Kalsenti will countersign and return it.
For and on behalf of Customer
| Field | Entry |
|---|---|
| Company name | |
| Signature | |
| Name | |
| Title | |
| Date |
For and on behalf of Kalsenti Limited
| Field | Director | Director |
|---|---|---|
| Signature | ||
| Name | ||
| Date |