Data processing agreement
Last updated:
This data processing agreement applies to hosted endpoint subscriptions. It is part of our Terms and conditions, and you accept it together with them when you buy a hosted endpoint subscription. It sets out how we process personal data on your behalf, as Article 28 of the EU General Data Protection Regulation (GDPR) requires.
Parties
- The customer: the business that holds a hosted endpoint subscription, as controller ("you").
- Envoyant Research, Strawinskylaan 4117, 1077 ZX Amsterdam, The Netherlands, Company nr. 27339412, VAT NL820561733B01, info@envoyant.net, as processor ("we").
1. Scope and roles
1.1 This agreement applies to personal data that we process on your behalf when we provide your hosted endpoint: the enquiries, quote requests and questions that AI agents send to it, the records of how agents use it, the hashes we derive from IP addresses to protect it, the addresses of the people you choose to receive enquiry emails, and, after you claim your business, the preparation of draft answers from the public pages of your website. Annex 1 describes the processing.
1.2 You are the controller of that data. We are your processor. We process it only to provide the endpoint to you.
1.3 This agreement does not cover data for which we are the controller ourselves, as our privacy policy describes: your account and sign-in data, our communications with you, our own website and free scan, billing records, security logs of our providers, and the aggregated, anonymised statistics described in clause 3.3.
1.4 Our payment provider handles the subscription payment as merchant of record (it charges you and issues the invoice in its own name) and processes your payment data under its own terms and privacy policy. It is not our sub-processor for that data, and it receives no data about the people who use your endpoint.
1.5 AI assistants and agents that call your endpoint (for example the assistant a person uses to send you an enquiry) are not our sub-processors. They act for their own users. The data they send us becomes subject to this agreement when it reaches your endpoint.
2. Duration
This agreement starts when you accept it and lasts for as long as we process personal data for your endpoint, including the 90 days after your subscription ends (clause 12). Clauses that by their nature continue (for example confidentiality and clause 12) survive its end.
3. Nature and purpose; your instructions
3.1 We process the data to: answer questions with the texts you approved; take in enquiries and quote requests and deliver them to you; prepare draft answers for your approval; show you enquiries, unanswered questions and statistics in your dashboard; limit abuse and protect the service; and keep the records these purposes need for the periods in Annex 1.
3.2 Your instructions are: the Terms, this agreement, and the settings you choose in your dashboard (for example which tools are on, which fields an enquiry form has, and who receives enquiry emails). We follow no other instructions unless you give them to us in writing (email is enough) and we agree that they are part of the service. We will tell you if we believe an instruction breaks the GDPR or other EU or Member State data protection law.
3.3 You instruct us to produce, from the call records in Annex 1, aggregated statistics that are anonymised so that they identify no person and not your business (for example how many calls hosted endpoints received from which assistant products), and to use them to run and improve our services. We use only fields that are not personal data for this, never the text of questions or enquiries.
3.4 If EU or Member State law requires us to process the data in another way, we tell you first, unless that law forbids it.
4. Your obligations
4.1 You make sure that you have a legal basis for the processing, and that the people who send you enquiries through your endpoint are informed as Articles 13 and 14 GDPR require. To help with this, your endpoint gives agents the address of the privacy policy on your own website with every enquiry receipt, and an enquiry is accepted only when the agent confirms that its user has agreed to share the details with you so that you can contact them.
4.2 You do not configure enquiry forms that ask for special categories of personal data, data about criminal convictions, payment card details, passwords or identity-document numbers, and you do not approve answers that contain personal data of other people beyond business contact details you are allowed to publish.
4.3 You keep the recipients of enquiry emails up to date, and you are responsible for the security of the mailboxes and the copies you download.
5. Confidentiality
We make sure that everyone who can access the data under our authority is bound by confidentiality, by contract or by law, and accesses it only as far as needed to provide or support the service. Today that is the founder and the engineers acting for us; access to production data is limited to named team members.
6. Security (Article 32 GDPR)
6.1 We take the technical and organisational measures in Annex 2. They take into account the state of the art, the cost, the nature and purpose of the processing, and the risks to people.
6.2 We may change the measures over time, as long as the overall level of protection does not go down.
7. Sub-processors
7.1 You give us a general authorisation to use sub-processors. The sub-processors at the date of this agreement are described in Annex 3.
7.2 We tell you about any intended addition or replacement of a sub-processor at least 30 days in advance, by email to the account address. You may object on reasonable grounds relating to data protection within 14 days of our notice. We will then try to find a solution with you. If we cannot, you may cancel the affected subscription with effect from the change, and we refund the prepaid fees for the period after it, through our payment provider.
7.3 In an emergency (for example a sub-processor’s security failure or insolvency) we may replace a sub-processor at shorter notice. We tell you as soon as we can, and the right to object and cancel in clause 7.2 applies.
7.4 We impose on each sub-processor, by contract, data protection obligations that give at least the protection of this agreement, in particular on security. We remain responsible to you for our sub-processors’ performance.
8. International transfers
8.1 Our database, where enquiries, unanswered questions and statistics are stored, is in the EU. Some sub-processors are established outside the EEA (in the United States and Singapore) or run global networks, so data may be processed outside the EEA. In particular: requests to your endpoint are handled in the data centre of our network provider that is closest to the calling agent, which can be outside the EEA; questions sent for AI matching are processed by our AI provider in the United States; and our email provider keeps logs and metadata of the enquiry emails in the United States. Enquiries are stored by us only in the EU database.
8.2 We transfer data outside the EEA only where Chapter V GDPR is met: an adequacy decision (including the EU-US Data Privacy Framework for certified recipients) or the standard contractual clauses approved by the European Commission (Decision (EU) 2021/914), with additional measures where needed. Annex 3 states the mechanism for each sub-processor. You can ask us for a copy of the relevant clauses.
9. Help with the rights of data subjects
9.1 If a person asks us directly to exercise their rights about data we process for you, we do not answer the request ourselves (except to tell them that we passed it on), and we forward it to you within 5 business days.
9.2 Your dashboard lets you view and export the enquiries your endpoint received. For a request we cannot meet through the dashboard, for example erasure of one person’s enquiries, we help you on request within 10 business days, by finding the records by the person’s email address and deleting or exporting them.
10. Help with security, impact assessments and consultation
We help you, taking into account the nature of the processing and the information we have, to meet your obligations under Articles 32 to 36 GDPR, in particular by giving you the information in this agreement and its annexes, and reasonable further information on request for a data protection impact assessment. Help beyond that, or beyond 2 hours a year, may be charged at reasonable rates agreed in advance.
11. Personal data breaches
11.1 We tell you without undue delay, and in any case within 48 hours, after we become aware of a personal data breach that affects data we process for you.
11.2 The notice goes to the account email address. It describes, as far as we know at the time: what happened; the categories and approximate number of people and records concerned; the likely consequences; what we have done or propose to do; and a contact. We add information as we learn it.
11.3 We take reasonable steps to contain the breach and limit its effects, and we keep a record of it.
11.4 A notice is not an admission of fault or liability.
12. Deletion and return at the end
12.1 While your subscription runs, we delete data on the schedule in Annex 1 (for example enquiries 12 months after receipt, unanswered questions after 30 days).
12.2 When your subscription ends, your endpoint is paused. During the following 90 days you can download your enquiries from the dashboard and see your approved answers there; on request we send you a copy of your approved answers. This is how we return the data to you. If you want us to delete everything sooner, tell us and we will.
12.3 90 days after the subscription ended, unless you subscribed again, we delete automatically the endpoint, its published versions, its approved and draft answers and their approval records, the enquiries it received, the unanswered questions, its statistics, your domain verification and its signing key. The deletion cannot be undone.
12.4 Copies in backups are deleted when the backups expire, within the backup retention period of our database provider. Until then they are kept secure and are not used. Emails with enquiries that we delivered to your recipients are in their mailboxes and outside our control; copies of those emails held by our email provider are deleted under its retention periods (Annex 3).
12.5 We keep data after that only where EU or Member State law requires it.
13. Information and audits
13.1 We make available to you the information needed to show that we meet Article 28 GDPR: this agreement, its annexes, and on request a written answer to a reasonable security questionnaire once every 12 months.
13.2 Where our sub-processors publish audit reports or certifications (for example ISO 27001 or SOC 2), we rely on them for the parts of the service they run, and tell you how to obtain them.
13.3 If that information is not enough to show compliance, or a supervisory authority requires it, you may audit us, or have an independent auditor bound by confidentiality audit us, on at least 30 days’ written notice, at most once every 12 months, during business hours, without access to other customers’ data, and at your own cost. We may charge reasonable costs for our time.
14. Liability
Each party’s liability under this agreement is subject to the limitations and exclusions in the Terms (the sections "Limitation of liability", "Liability for hosted endpoints" and "Our liability cap for hosted endpoints"). The cap there applies to all claims under the Terms and this agreement together. Nothing in this clause limits the rights of data subjects under Article 82 GDPR.
15. Order of precedence; law
15.1 If this agreement and the Terms conflict on the protection of personal data, this agreement applies.
15.2 This agreement is governed by Dutch law. The competent court in Amsterdam, the Netherlands, has exclusive jurisdiction, unless mandatory law says otherwise.
15.3 We may update this agreement when the law, a supervisory authority or a change in the service requires it. We give at least 30 days’ notice of a material change, and you may cancel before it takes effect, as the Terms say.
Annex 1: Description of the processing
- Controller: the customer (the business that holds the subscription).
- Processor: we, as named under "Parties".
- Subject matter: hosting an AI-agent endpoint, at the business’s own address on our endpoint domain, that answers with texts the customer approved, takes in enquiries and quote requests, and reports on its use; and preparing draft answers for the customer’s approval.
- Duration: the subscription, plus 90 days after it ends (clause 12).
- Frequency: continuous, whenever an agent calls the endpoint.
- Data subjects: (a) people on whose behalf an AI agent asks the endpoint a question or sends an enquiry (prospects and customers of the business); (b) people named in those questions or enquiries; (c) the customer’s staff named as recipients of enquiry emails or on the public pages of the customer’s website.
- Special categories: none intended. Enquiry forms must not ask for them (clause 4.2). Free-text fields can still contain them if a person types them in.
Annex 1: What we process, why, and for how long
- Enquiry or quote request: the fields the customer configured, such as name, email address, phone number, company, message, quote details, preferred dates and time zone; the user’s confirmation to be contacted; which tool was used; time; delivery status and attempts. Purpose: deliver the enquiry to the customer, show it in the dashboard, prevent duplicates and abuse. Where: our EU database, the fields encrypted in the application before storage. Kept: 12 months from receipt (fixed in Starter), or until the deletion 90 days after the subscription ends, if that comes first.
- Enquiry email: the same fields, in plain text. Purpose: notify the customer’s chosen recipients; if delivery fails, we try again several times. Where: our email provider, then the recipients’ mailboxes. Kept: by the email provider under its log retention, in the United States (Annex 3); in the mailboxes, under the customer’s responsibility.
- Duplicate check and data subject requests: a keyed one-way hash (HMAC-SHA-256) of the email address in an enquiry. Purpose: refuse the same enquiry twice within 24 hours, and find a person’s enquiries for a request under clause 9. Where: our EU database. Kept: with the enquiry.
- Recipients of enquiry emails: the email addresses the customer chooses (at most five). Purpose: deliver enquiries. Where: our EU database. Kept: until the customer changes them, or until the endpoint is deleted.
- Unanswered question: where recorded, the text of a question no approved answer matched, with email addresses and phone numbers replaced before storage (other details in a question, such as names, are not removed); time; language. Purpose: show the customer which questions to answer next. Where: our EU database. Kept: 30 days.
- Question being matched: the text of each question, held in memory only. Purpose: pick the approved answer that fits. When word matching is unsure and AI matching is switched on, the question (at most 500 characters) and the customer’s approved questions are sent to our AI provider, which returns only which approved answer fits, or none. Where: our network provider’s edge; the AI provider (Annex 3). Kept: not stored by us beyond the request, except as an unanswered question above. The AI provider deletes the inputs and outputs within 30 days and may not train its models on them (Annex 3).
- Call record (statistics): time; tool; outcome; protocol version; the name and version of the calling assistant software; response time; whether the answer was signed; which approved answer was given; how it was matched; the IP hash below. No question text and no enquiry content. Purpose: statistics in the dashboard, abuse and error analysis. Where: our EU database. Kept: 13 months.
- IP hash: a keyed hash (HMAC with a secret, salted per day) of the caller’s IP address (for IPv6, of its /64 network). The IP address itself is used in memory for short burst limits and is not stored. Purpose: rate limits and abuse prevention. Where: our EU database, with the call record and the enquiry. Kept: removed from a call record after 2 days and from an enquiry after 2 hours.
- Request in transit: IP address, request headers and body, as needed to deliver the request. Purpose: delivering and protecting the endpoint. Where: our network provider’s edge. Kept: under the network provider’s log policy (Annex 3).
- Draft answers: the facts and quotes from the public pages of the customer’s website that our scan found, which can name staff, and the drafts made from them. Purpose: prepare draft answers for the customer’s approval. Where: our EU database; the AI provider (Annex 3) while a draft is written. Kept: until the endpoint is deleted.
Annex 1: What is not processed for the customer
Approved answers themselves are the customer’s approved business content; any personal data in them is business contact data the customer chose to publish. The customer’s account data is processed by us as controller (clause 1.3).
Annex 2: Technical and organisational measures
Encryption and pseudonymisation:
- TLS for all traffic to the website, the dashboard and the endpoints, and between our services and providers.
- Enquiry fields encrypted in the application with AES-256-GCM before they are stored, with the record id and the business bound in as additional data. The key is a secret held only in our hosting providers’ secret stores, never in the database. Enquiries are decrypted only on our servers, for the dashboard and the enquiry email.
- Signing keys: one Ed25519 key per business, wrapped (P-256 ECDH, HKDF-SHA-256, AES-256-GCM, bound to the business and key id) so that only the endpoint service can unwrap it; the plain key exists only in that service’s memory; rotation and revocation.
- IP addresses stored only as keyed, day-salted hashes; email addresses for duplicate checks only as keyed hashes.
- Unanswered questions stored with email addresses and phone numbers replaced.
Annex 2: Confidentiality and access control
- Row-level security on every database table: a customer can read only the data of its own business, customers have no direct write access, and every change goes through server functions that check the user’s role. Automated tests check that two businesses cannot see each other’s data.
- The public endpoint service holds no database credentials: it reads a published, validated copy of the approved answers and writes enquiries and statistics only through an internal call that is not reachable from the internet.
- Each request is bound to one business by its host name; the published copy must match that host, and the signing key cannot be unwrapped for another business.
- Sign-in by one-time email link only, with bot protection, limits per address and no self sign-up; customer accounts cannot reach the team area, which needs a listed team member.
- Secrets kept only in our hosting providers’ secret stores, never in code; secret scanning and dependency audits in our build pipeline.
- Administrative actions on endpoints (for example a suspension) recorded in an audit log.
Annex 2: Integrity
- Every input checked against strict schemas at each boundary; requests to an endpoint limited to 64 KiB.
- Answers are served only from the approved, published version; an approval covers the exact text, and any edit needs a new approval.
- Answers signed so that agents can detect changes after signing.
- Text from crawled pages and from agents is treated as untrusted data, checked by a sanitiser, and shown only as plain text.
Annex 2: Availability and resilience
- Managed database with backups by the provider.
- Endpoints run on a global edge network; the published copy is checked against the database and rewritten every hour.
- Rate limits per caller and per business; strict limits on enquiries in the database (5 per IP hash per hour, 50 per business per 24 hours, duplicates refused for 24 hours).
- If enquiry delivery by email fails, the enquiry is kept, retried and shown in the dashboard with its delivery status.
- Per-business and global kill switches, effective within a few minutes.
Annex 2: Minimisation, retention and testing
- Enquiry receipts never echo the submitted personal data back to the agent.
- Application logs contain events and error codes only: no IP addresses, form contents or tokens.
- Automatic hourly deletion jobs for each retention period in Annex 1, and for the deletion 90 days after a subscription ends.
- Automated tests for tenant isolation, row-level security and access rights, and conformance tests for the endpoint, in our build pipeline.
- Security review of every change to authentication, signing, the endpoint, billing webhooks or database access rules.
- Confidentiality of everyone with access (clause 5).
Annex 3: Sub-processors
These are the categories of sub-processors we use for the data in Annex 1, where they process it and the safeguards for transfers outside the EEA. The current list with each provider’s name and address is available on request at info@envoyant.net. We tell you about changes by email to your account address (clause 7.2).
- Database and customer sign-in provider: stores enquiries (encrypted by us), unanswered questions, statistics and approval records, and runs customer sign-in. Location: a data centre in the EU. The contracting company is established in Singapore, so remote access is covered by the standard contractual clauses (Modules 2 and 3).
- Network, edge computing and bot-protection provider: runs the endpoints, stores the published copy of approved answers and the wrapped signing keys (no data of the people who use the endpoint is stored there), and handles requests (IP address, question text, enquiry fields) in transit. Location: a global network; a request is handled in the data centre closest to the caller, which can be outside the EEA. US company: EU-US Data Privacy Framework where the provider is certified, otherwise the standard contractual clauses.
- Website and dashboard hosting provider: hosts the dashboard and its server functions, which decrypt enquiries for display and export. Location: server functions in the EU (Frankfurt); the provider’s main processing facilities, including request logs, are in the United States. US company: EU-US Data Privacy Framework where the provider is certified, otherwise the standard contractual clauses.
- Email delivery provider: sends enquiry emails to the business’s recipients and sign-in emails. Location: email logs and metadata are stored in the United States. US company: EU-US Data Privacy Framework where the provider is certified, otherwise the standard contractual clauses.
- AI provider: writes draft answers from the business’s website before publication and, when AI matching is switched on, chooses which approved answer fits a question when word matching is unsure. It never writes the answers the endpoint gives. It receives page text for drafting, and the question text and the approved questions for matching; never enquiry data. Location: processing in the United States, with no EU-only option. Contracting company in the EU (Ireland); standard contractual clauses (Modules 2 and 3). Under its terms it may not train its models on our data, and it deletes inputs and outputs within 30 days, except where it must keep them to enforce its usage policies or by law.
Annex 3: Not a sub-processor
Our payment provider acts as merchant of record for the subscription payment: it charges the customer, issues tax invoices and receipts in its own name and handles VAT. It processes payment and tax data of the customer, not data of the people who use the endpoint, under its own privacy policy, as a controller in its own right.
Who runs Envoyant
- Operator
- Envoyant Research
- Address
- Strawinskylaan 4117
1077 ZX Amsterdam
The Netherlands - Registration number
- Company nr. 27339412
- VAT number
- NL820561733B01
- info@envoyant.net