This agreement applies automatically when you accept the Terms & Conditions: nothing needs signing. If your procurement process needs a signed copy, or you need to add your own details, email support@zestco.uk and we'll send one. The sub-processor list is in Annex 3.
1. Parties
This agreement is between ZestCo Ltd, a company registered in England and Wales, company number 16694401, registered office Ingles Manor, Castle Hill Avenue, Folkestone, England, CT20 2RD (“Zest”, “we”), and the business or organisation that uses Freshservice Import under our Terms & Conditions (the “Customer”, “you”).
It forms part of the Terms & Conditions (the “Terms”) under which you use Freshservice Import (the “Service”). It is accepted when you accept the Terms, or when both parties sign it. If this agreement and the Terms conflict on the processing of personal data, this agreement wins.
2. Definitions
- Data Protection Law: the UK GDPR, the Data Protection Act 2018, the Privacy and Electronic Communications Regulations 2003 and, where it applies to you, the EU GDPR.
- Customer Personal Data: personal data that Zest processes on your behalf in providing the Service, as described in Annex 1.
- Sub-processor: a third party Zest engages to process Customer Personal Data.
- Personal Data Breach: a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, Customer Personal Data.
- Restricted Transfer: a transfer of Customer Personal Data outside the UK that isn't covered by UK adequacy regulations.
- IDTA and Addendum: the International Data Transfer Agreement and the International Data Transfer Addendum to the EU Standard Contractual Clauses, issued by the ICO under section 119A of the Data Protection Act 2018.
- Controller, processor, data subject, personal data, processing and supervisory authority have the meanings in Data Protection Law.
3. Roles and scope
- You are the controller and Zest is the processor of Customer Personal Data.
- Annex 1 sets out the subject matter, duration, nature and purpose of the processing, the types of personal data and the categories of data subjects.
- This agreement doesn't cover personal data Zest processes as a controller for its own purposes: user accounts and sign-in details, licensing and anti-abuse records, and support correspondence. Our privacy policy covers that data.
- The Service is sold through a merchant of record, Onelink (part of Stripe). Onelink and Stripe are separate controllers for payment data and aren't Zest's Sub-processors.
4. Zest's obligations
4.1 Instructions
- Zest processes Customer Personal Data only on your documented instructions, including on transfers outside the UK, unless UK law requires otherwise. If it does, Zest tells you first unless the law prohibits it.
- Your instructions are this agreement, the Terms, and your use and configuration of the Service. Further instructions must be in writing and consistent with the Service.
- Zest tells you promptly if it believes an instruction infringes Data Protection Law.
- Zest doesn't sell Customer Personal Data, use it to train AI models, or use it for its own purposes.
4.2 Confidentiality
Zest ensures that everyone authorised to process Customer Personal Data is bound by confidentiality and only accesses it where needed to provide or support the Service.
4.3 Security
- Zest implements the technical and organisational measures in Annex 2, appropriate to the risk, as required by Article 32 UK GDPR.
- Zest may update Annex 2 provided the overall level of protection doesn't fall.
4.4 Sub-processors
- You give general authorisation for Zest to use the Sub-processors listed in Annex 3.
- Zest gives at least 30 days' notice of any new or replacement Sub-processor, by email to your account's administrators and by updating Annex 3 on this page with a new version number and date.
- You may object on reasonable data protection grounds within those 30 days. If we can't resolve the objection, you may end the Service and Zest refunds any prepaid fees for the unused period.
- Zest imposes data protection terms on each Sub-processor that give the same protection as this agreement, and remains liable for its Sub-processors' performance.
4.5 Data subject rights
Taking into account the nature of the processing, Zest assists you by appropriate technical and organisational measures to respond to requests from data subjects. If Zest receives a request directly, it passes it to you within 5 working days and doesn't respond itself unless you instruct it to.
4.6 Assistance
Zest assists you with your obligations under Articles 32 to 36 UK GDPR (security, breach notification, data protection impact assessments and prior consultation), taking into account the nature of the processing and the information available to Zest. This includes providing the Service's data protection impact assessment on request.
4.7 Personal Data Breaches
- Zest notifies you without undue delay, and in any event within 24 hours, after becoming aware of a Personal Data Breach.
- The notice includes, as far as 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, and a contact point. Zest provides further information as it becomes available.
- Zest takes reasonable steps to contain and investigate the breach and to reduce its effects.
- Notifying you isn't an admission of fault.
Our breach process is described on the Privacy & security page.
4.8 Deletion and return
- You can export the send log and delete your account, with all Customer Personal Data Zest stores, in the Service at any time (Your data in the tool).
- When the Service ends, Zest deletes Customer Personal Data within 30 days, unless UK law requires Zest to keep it. Zest confirms deletion in writing on request.
4.9 Information and audits
- Zest makes available the information needed to demonstrate compliance with this agreement, including the Service's data protection impact assessment, its security documentation and its Privacy & security page and Trust Centre.
- If that information isn't enough to demonstrate compliance, you may audit Zest once a year, on 30 days' written notice, during UK business hours, at your cost, subject to reasonable confidentiality terms. An additional audit is allowed after a Personal Data Breach or at a supervisory authority's request.
4.10 International transfers
Zest makes a Restricted Transfer, or allows a Sub-processor to make one, only with an appropriate safeguard: the UK–US data bridge (the UK Extension to the EU–US Data Privacy Framework) where the recipient's certification is current and covers the data, the IDTA, or the Addendum. Where the EU GDPR applies to your data, the corresponding safeguard is the EU Standard Contractual Clauses or the EU–US Data Privacy Framework. Annex 3 records the safeguard for each Sub-processor and each transfer.
Pending legal confirmation: whether the EU GDPR applies to the Service, and so whether an EU representative and EU transfer safeguards are needed, is being confirmed with our legal adviser. Until then the UK safeguards in Annex 3 apply, and this clause and Annex 3 may be updated under clause 8.
5. Your obligations
You:
- have a lawful basis for the processing and give data subjects any information Data Protection Law requires;
- ensure your instructions comply with Data Protection Law;
- put in your import files only the personal data needed for your purpose, and don't include special category or criminal offence data unless you've assessed and documented that it's necessary;
- secure your own accounts and systems, including the Freshservice API key you give the Service, and limit its permissions to what the Service needs; and
- are responsible for the actions your own systems take on records the Service creates or updates, for example notifications and workflow automations in your Freshservice.
6. Liability
Each party's liability under this agreement is subject to the limitations and exclusions in the Terms. Nothing in this agreement limits a party's liability to data subjects or to a supervisory authority where Data Protection Law doesn't allow it.
7. Term
This agreement lasts as long as Zest processes Customer Personal Data. Clauses 4.7 to 4.9 and 6 survive its end.
8. Changes, law and jurisdiction
- We may update this agreement. We'll change the version and date at the top and, for material changes, tell your account's administrators by email at least 30 days before they apply. Sub-processor changes follow clause 4.4.
- This agreement is governed by the law of England and Wales. The courts of England and Wales have exclusive jurisdiction.
Annex 1. Processing details
| Item | Detail |
|---|---|
| Subject matter | Creating and updating tickets, service requests and replies in your own Freshservice from spreadsheet files you prepare. |
| Duration | Your subscription or trial, plus the retention periods below. |
| Nature | Rows are checked in the user's browser and sent one at a time through Zest's server functions to your Freshservice. Row content and your API key pass through in memory and aren't stored. A send log records the outcome of each send. |
| Purpose | Running the imports you instruct, and giving you a record of what was sent. |
| Data subjects | People named in your import files (for example staff, contractors, students, customers); your users who run imports. |
| Personal data in transit (not stored) | Whatever you put in your import files: typically names, email addresses, staff or student IDs, ticket subjects and descriptions, field values, replies, and CC and BCC addresses. Also your Freshservice API key. |
| Personal data stored | The send log: user ID, Freshservice subdomain, ticket number, action, outcome, HTTP status and Freshservice error codes, and whether mandatory-field checks were skipped. No row content and no error messages. |
| Special category data | Only if you include it in import files (clause 5.3). It's never stored by Zest. |
| Retention | In-transit data: none. Send log: 90 days by default, adjustable per account on request; deleted when the account is deleted. |
| Export and deletion | Account administrators can export the send log and delete the account in the Service (Your data). |
| Location | Server functions and database in Frankfurt (EU). |
Annex 2. Technical and organisational measures
Data minimisation
- Import content and API keys are never written to Zest's database, server logs or the browser console.
- The send log holds identifiers and outcomes only.
- No analytics, advertising or AI processing of Customer Personal Data.
Access control
- Sign-in through WorkOS. Every Freshservice function requires a valid session, a current account membership and an active plan or trial.
- A Freshservice subdomain is bound to the email domain of the account that first proves access to it; other accounts are refused. A deployment can also be restricted to a list of allowed subdomains.
- Account deletion requires the account owner or an organisation administrator, a recent sign-in and an explicit confirmation.
- Zest staff don't access your Freshservice unless you grant access for support. Any such access is read-only and time-limited.
Application and network security
- All traffic over HTTPS with HSTS. Calls go only to your
<subdomain>.freshservice.com, with a fixed path and method per function, numeric-only IDs, no redirects followed, and a 1 MB request limit. - Strict Content Security Policy; third-party scripts loaded with Subresource Integrity or self-hosted.
- Session cookies signed, HttpOnly, Secure and SameSite=Lax, expiring after 12 hours.
- Database row-level security on, with access only through server functions.
- Automated tests and OWASP ZAP security scanning in the build pipeline; code review before changes reach production.
Integrity
- Templates are signed and rejected if the Freshservice form has changed.
- Every row is validated against the live form before sending, and the user confirms a summary first.
- The server never retries a create after a lost response; such rows are marked Uncertain for the user to check.
Retention and deletion
- Send log purged automatically after its retention period; accounts with no plan deleted automatically 30 days after the trial or last paid period ends.
- Self-service export and deletion.
Organisational
- Secrets held only in the hosting provider's encrypted environment settings, scoped per environment, and rotated after access changes or suspected leaks.
- A written Personal Data Breach process with customer notification within 24 hours (clause 4.7).
- Staff bound by confidentiality; access removed when people leave.
- Compliance monitored through Vanta; Trust Centre available to customers from the Privacy & security page.
Annex 3. Sub-processors
Sub-processor list version 1.0, 28 October 2026. New or replacement Sub-processors are announced at least 30 days in advance by email to account administrators and by a new version of this list (clause 4.4). To be told by email about changes, make sure your account has an administrator with a monitored address.
Pending legal confirmation: the safeguards below are the contractual ones in each provider's data processing agreement. Where a provider's certification under the UK Extension to the EU–US Data Privacy Framework is verified as current and covering this data, the row will say so in a new version of this list. No provider is described as certified until that's verified.
| Sub-processor | Purpose | Customer Personal Data | Location | Transfer and safeguard |
|---|---|---|---|---|
| Netlify, Inc. (US) | Hosting and server functions | Import content and API keys, in transit only | Server functions in Frankfurt (EU); static files on a global CDN | UK to EU: no Restricted Transfer; the EU is covered by UK adequacy regulations. Any access from the US (support and operations): the UK Addendum to the EU Standard Contractual Clauses, under Netlify's data processing agreement. Where the EU GDPR applies: the EU Standard Contractual Clauses in the same agreement. |
| Supabase, Inc. (US) | Database | The send log | Frankfurt (EU) | UK to EU: no Restricted Transfer; the EU is covered by UK adequacy regulations. Any access from the US (support and operations): the UK Addendum to the EU Standard Contractual Clauses, under Supabase's data processing agreement. Where the EU GDPR applies: the EU Standard Contractual Clauses in the same agreement. |
For information: not Sub-processors of Customer Personal Data
- WorkOS, Inc. (US): sign-in and single sign-on for your users. This is data Zest holds as a controller, covered by our privacy policy. It is a UK-to-US Restricted Transfer, made under the UK Addendum to the EU Standard Contractual Clauses in WorkOS's data processing agreement.
- Onelink and Stripe (UK, EU, US): merchant of record and payment processing, as separate controllers under their own privacy policy.
- Freshworks: your own Freshservice, provided to you under your agreement with Freshworks. Zest sends data to it only on your instruction.
Change history
- 28 October 2026: version 1.0, first published.
