On this page
- The short version
- 1. About this DPA
- 2. Definitions
- 3. Roles and instructions
- 4. Confidentiality
- 5. Security
- 6. Sub-processors
- 7. International transfers
- 8. Helping you meet your obligations
- 9. Personal data breaches
- 10. Audits and information
- 11. Deletion and return
- 12. Aggregated and anonymised data
- 13. General
- Annex 1: Details of processing
- Annex 2: Security measures
- Annex 3: Sub-processors
The short version
- You're the controller of the personal data in your Fymo workspace. We're your processor and act only on your instructions.
- We keep it secure and confidential, and use other providers only under contracts with the same protections.
- We tell you about a personal data breach without undue delay.
- We help you answer requests from individuals and meet your other obligations.
- When your subscription ends, we delete your personal data within 30 days, and from backups 14 days after that.
- Transfers outside the UK and the EEA are protected by approved safeguards, such as the Standard Contractual Clauses.
This summary is for convenience. The full DPA below is what applies.
1. About this DPA
This data processing agreement ("DPA") is between Fymo Ltd ("Fymo", "we") and the business that uses Fymo ("you"). It forms part of your agreement with us for the Fymo service and applies whenever we process personal data on your behalf to provide that service.
This DPA applies automatically as part of your agreement with us, so you don't need to sign it separately. We can provide a signed copy on request at privacy@fymo.ai.
If you've signed a separate DPA with us, the signed DPA takes precedence over this one.
This DPA covers processing subject to the UK GDPR, the EU GDPR and the Swiss Federal Act on Data Protection.
2. Definitions
- "Agreement" means your order form and the signed terms under which we provide the Fymo service to you.
- "Customer Personal Data" means personal data we process on your behalf under the Agreement.
- "Data Protection Laws" means the UK GDPR, the Data Protection Act 2018, the EU GDPR, the Swiss Federal Act on Data Protection, and any other data protection law that applies to the processing.
- "Sub-processor" means a third party we engage to process Customer Personal Data.
- "SCCs" means the standard contractual clauses approved by the European Commission in Decision 2021/914.
- "UK Addendum" means the International Data Transfer Addendum to the SCCs issued by the UK Information Commissioner.
"Controller", "processor", "data subject", "personal data", "personal data breach" and "processing" have the meanings given in the GDPR.
3. Roles and instructions
3.1 You're the controller of Customer Personal Data, or a processor acting for your own client. We're your processor, or your sub-processor where you act for a client.
3.2 We process Customer Personal Data only on your documented instructions. Your instructions are the Agreement, this DPA, and the way you set up and use the service. You can give further instructions in writing if they're consistent with the Agreement.
3.3 If the law requires us to process Customer Personal Data in another way, we'll tell you before we do, unless the law forbids it.
3.4 We'll tell you straight away if we think an instruction breaks Data Protection Laws.
3.5 You're responsible for having a lawful basis for the processing, for giving data subjects the information the law requires, and for the data you connect to Fymo.
3.6 We don't sell Customer Personal Data, use it for advertising or use it to train AI models.
3.7 As part of the service, we record how your users use Fymo, including session replays, to support your users and to operate, secure and fix the service. We do this only for users who agree to it, and we ask for that agreement on your behalf in Fymo. We use this data to improve Fymo only in aggregated or anonymised form, as section 12 describes.
3.8 We're a controller only for the personal data we use to manage our relationship with you, such as contact details for your account, contracts and billing. Our privacy policy covers that processing, and this DPA doesn't.
4. Confidentiality
We give our staff and contractors access to Customer Personal Data only where they need it to provide, secure or support the service. Everyone with access is bound by a written duty of confidentiality and is trained in handling personal data.
5. Security
5.1 We protect Customer Personal Data with technical and organisational measures appropriate to the risk, as Article 32 of the GDPR requires. Annex 2 describes them.
5.2 We keep your data separate from other customers' data.
5.3 We review our measures regularly and may update them, but we won't reduce the overall level of protection.
6. Sub-processors
6.1 You give us general written authorisation to use sub-processors. Our current sub-processors are listed in our Trust Center at trust.fymo.ai (Annex 3).
6.2 Except as section 6.5 allows, we'll tell you at least 10 days before we add or replace a sub-processor, by updating the list in our Trust Center and emailing your account contact.
6.3 You can object to a new sub-processor in writing within 10 days of our notice, on reasonable grounds relating to data protection. We'll work with you in good faith to resolve it. If we can't, you can end the affected part of the service by written notice.
6.4 Each sub-processor is bound by a written contract that protects Customer Personal Data at least as well as this DPA. We remain responsible to you for our sub-processors' performance of those obligations.
6.5 We may replace an existing sub-processor without advance notice if the replacement is urgent and the reason is outside our control, such as a security problem or the provider stopping or failing to provide its service. The replacement will protect Customer Personal Data at least as well as the one it replaces. We'll tell you without undue delay, and you can still object under section 6.3.
7. International transfers
7.1 By default, we host Customer Personal Data in the UK and the EU. If we agree with you to host it in another region, such as the US, we'll host it there instead. Some sub-processors process it in other countries, as the list in our Trust Center shows.
7.2 Transfers to us from the EEA and Switzerland rely on the adequacy decisions for the UK. Where a transfer needs another safeguard, including if an adequacy decision stops applying:
- From the EEA: the SCCs apply, Module 2 where you're a controller and Module 3 where you're a processor. The optional docking clause (Clause 7) doesn't apply. Under Clause 9, option 2 applies, with the notice period in section 6. The optional wording in Clause 11 doesn't apply. Clauses 17 and 18 choose the law and courts of Ireland. Annexes 1 to 3 of this DPA complete the SCCs' annexes.
- From the UK: the SCCs apply as amended by the UK Addendum. Its tables are completed with the details in this DPA, and neither party may end it under its Table 4.
- From Switzerland: the SCCs apply with references to the GDPR read as references to the Swiss Federal Act on Data Protection, and the Swiss Federal Data Protection and Information Commissioner as a supervisory authority.
7.3 Where our sub-processors process Customer Personal Data outside the UK and the EEA, we protect it with the SCCs and the UK Addendum, or rely on the sub-processor's certification under the EU-US Data Privacy Framework and its UK Extension.
7.4 If a public authority asks us for Customer Personal Data, we'll ask it to go to you directly. If we're legally required to disclose the data, we'll tell you first where the law allows, and disclose only what we must.
8. Helping you meet your obligations
8.1 If a data subject contacts us directly about Customer Personal Data, we'll pass the request to you without undue delay. We won't respond to it ourselves, except to tell them we've passed it on.
8.2 We'll help you respond to data subjects' requests to exercise their rights, as far as the service's features don't already let you.
8.3 We'll give you reasonable help with data protection impact assessments and with consulting a supervisory authority, where they relate to our processing.
8.4 If help under this section takes significant work beyond the normal service, we may charge reasonable costs, which we'll agree with you before we start.
9. Personal data breaches
9.1 We'll tell you without undue delay after becoming aware of a personal data breach affecting Customer Personal Data.
9.2 We'll tell you what we know about the breach, as it becomes available:
- what happened, including the categories and approximate number of data subjects and records affected
- its likely consequences
- what we've done or plan to do about it, including to limit its effects
- who to contact for more information
9.3 We'll take reasonable steps to contain the breach, and help you meet your duties to notify supervisory authorities and data subjects.
9.4 Telling you about a breach isn't an admission of fault or liability.
10. Audits and information
10.1 We'll give you the information you reasonably need to check that we meet this DPA. We'll start with our most recent independent reports, such as penetration test summaries, shared under a duty of confidentiality.
10.2 If those reports aren't enough to show compliance, or a supervisory authority requires it, you or an independent auditor bound by confidentiality may audit our processing of Customer Personal Data. You'll give us at least 30 days' written notice, and audits take place during business hours, no more than once a year unless a breach or a supervisory authority makes another necessary. You pay the costs of the audit.
10.3 Audits under Clause 8.9 of the SCCs follow this section.
11. Deletion and return
11.1 You can ask us for an export of Customer Personal Data before your subscription ends.
11.2 We delete Customer Personal Data within 30 days after the Agreement ends, including from our sub-processors. Backups expire after 14 days, so copies in backups are gone within 14 days of that deletion.
11.3 Where the law requires us to keep some Customer Personal Data, we'll keep protecting it under this DPA, use it only for that legal requirement, and delete it once the requirement ends.
11.4 We'll confirm deletion in writing if you ask.
12. Aggregated and anonymised data
12.1 You authorise us to aggregate or anonymise Customer Personal Data so that it can't identify you, your users or anyone else, and to use the result to operate and improve Fymo. We never sell it or use it to train AI models.
12.2 Once data is in that form, it's no longer Customer Personal Data and this DPA doesn't apply to it.
13. General
13.1 Precedence. If documents conflict on the processing of Customer Personal Data, the SCCs and the UK Addendum come first, then this DPA, then the rest of the Agreement.
13.2 Liability. Each party's liability under this DPA is subject to the limits in the Agreement, except where the SCCs or Data Protection Laws don't allow liability to be limited.
13.3 Duration. This DPA applies for as long as we process Customer Personal Data, including after the Agreement ends.
13.4 Changes. We may update this DPA to reflect changes in law or in the service. We won't reduce the protection it gives Customer Personal Data, and we'll tell you at least 30 days before a significant change takes effect.
13.5 Law and courts. This DPA is governed by the law of England and Wales, and the courts of England and Wales have exclusive jurisdiction, except where the SCCs say otherwise.
Annex 1: Details of processing
This annex also completes Annex I of the SCCs and Tables 1 and 3 of the UK Addendum.
| Item | Details |
|---|---|
| Data exporter | You, as named in your order form. Controller, or processor for your own client. |
| Data importer | Fymo Ltd, 124 City Road, London, EC1V 2NX, United Kingdom. privacy@fymo.ai. Processor. |
| Subject matter | Providing the Fymo service under the Agreement. |
| Nature of processing | Connecting to your sources and copying data from them; storing, transforming, testing and modelling it; running queries; producing insights, dashboards and alerts; supporting your users; with each user's consent, recording how they use the service, including session replays; securing and backing up the service; deleting data. |
| Purpose | To provide, secure and support the service for you, and to create aggregated or anonymised data as section 12 describes. |
| Duration | The term of the Agreement, plus up to 30 days for deletion and a further 14 days for backups to expire. |
| Data subjects | Your users (your employees and contractors), and the people whose data is in your connected sources, such as your customers, prospects, suppliers and staff. |
| Personal data | Users: name, work email address, role, sign-in and activity records, and, with their consent, product usage events and session replays. Session replays can show connected-source data that's on screen at the time. Connected sources: whatever you connect, typically contact details, company and job information, CRM and billing records, product usage and support history. |
| Sensitive data | None. The Agreement doesn't allow sensitive data. |
| Frequency of transfer | Continuous, while the service runs. |
| Retention | As set out in section 11. Session replays are deleted after 30 days. |
| Supervisory authority | For EEA transfers, as set by Clause 13 of the SCCs. For UK transfers, the Information Commissioner's Office. |
Annex 2: Security measures
This annex also completes Annex II of the SCCs and the UK Addendum.
| Area | What we do |
|---|---|
| Encryption | Data is encrypted in transit with TLS 1.2 or higher, and at rest with AES-256. Encryption keys are managed in our cloud providers' key management services. |
| Customer separation | Each customer's data is kept separate from other customers' data. |
| Access control | Staff get the least access their role needs. Access to production systems requires multi-factor authentication, is reviewed at least once a year, and is removed when someone leaves. |
| Logging and monitoring | We log access to production systems and customer data, and monitor for unusual activity. |
| Testing | The platform is independently penetration tested at least once a year, and we scan our code and dependencies for vulnerabilities. |
| Changes | Changes to production go through code review and automated tests. |
| Resilience | Data is backed up daily, and we test restoring from backups at least once a year. The service runs on Google Cloud and Amazon Web Services in the EU and the UK by default, or in another region we agree with you. |
| Incidents | We have a documented incident response plan, which we test at least once a year. |
| People | Staff sign confidentiality agreements and complete security training when they join and every year after. |
| Suppliers | We review sub-processors' security before using them, and bind them by contract to protections at least as strong as this DPA's. |
| Data minimisation | You choose which sources and data to connect. AI model providers don't have access to the data in your connected sources unless you ask us to turn on a feature that needs it. We'll tell you what data the feature would share with them, and only turn it on once you've explicitly agreed. |
Annex 3: Sub-processors
This annex also completes Annex III of the SCCs. Our current sub-processors, with what each does and where it processes data, are listed in our Trust Center at trust.fymo.ai.