Data Processing Agreement
Version: 2026-10-29
This Data Processing Agreement ("DPA") is part of the agreement between the customer ("Customer") and FYAI B.V. ("FYAI") under the Terms of Service (the "Agreement"). It applies to the personal data FYAI processes on behalf of the Customer and is accepted together with the Terms of Service (art. 9.1); no separate signature is needed. A signed copy is available on request.
1. Roles
1.1 The Customer is the controller of the personal data of its website visitors and leads; FYAI is the processor. Where an agency uses FYAI for its own clients, the agency is the Customer and ensures it may give these instructions on its clients' behalf.
1.2 For the data of the Customer's own users of FYAI (account holders and team members), FYAI is the controller; the Privacy Policy applies to that data.
2. Subject matter and duration
2.1 FYAI processes personal data to record leads from the Customer's lead sources, to let the Customer qualify and enrich them, and to send the outcome as conversions and customer lists to the platforms the Customer connects. Annex 1 describes the processing.
2.2 This DPA runs for as long as FYAI processes personal data under the Agreement.
3. Documented instructions
3.1 FYAI processes personal data only on the Customer's documented instructions (art. 28(3)(a) GDPR). These are the Agreement, this DPA and the instructions the Customer gives in FYAI, which FYAI records with the exact text, the user, the time, the IP address and the browser:
- activating a form or changing its field mapping, with the legal basis for the fields it stores;
- the declaration per lead source that its leads may be used for advertising: for the website, and with every API key and file import;
- connecting, disconnecting or changing the settings of an advertising platform or CRM;
- the instruction per platform to upload and maintain customer lists;
- downloading leads, and deleting a lead or the workspace.
3.2 FYAI informs the Customer without delay if, in its opinion, an instruction infringes the GDPR or other data protection law.
4. The Customer's responsibilities
4.1 The Customer ensures it has a lawful basis for every field it lets FYAI store, informs the data subjects in its privacy statement, and obtains the consent its lead sources declare: the website only loads the FYAI script, and the Customer's systems only send leads, after the visitor consented to the use of their data for advertising and personalised advertising. Everything FYAI receives counts as approved for processing.
4.2 The Customer does not let FYAI process special categories of personal data (art. 9 GDPR) or data of children.
5. Confidentiality
5.1 FYAI ensures that everyone it authorises to process the personal data is bound to confidentiality.
6. Security
6.1 FYAI takes the technical and organisational measures in Annex 2 (art. 32 GDPR) and keeps them appropriate to the risk. FYAI may change a measure, provided the level of protection does not go down.
7. Sub-processors
7.1 The Customer gives FYAI general authorisation to engage sub-processors. Annex 3 lists them.
7.2 FYAI informs the Customer of a new or replaced sub-processor at least 30 days before it processes personal data. The Customer may object within that period on reasonable grounds; if the parties do not resolve the objection, the Customer may terminate the Agreement for the affected service.
7.3 FYAI imposes the same data protection obligations on each sub-processor as this DPA imposes on FYAI, and remains liable to the Customer for them.
8. Platforms the Customer connects
8.1 Advertising platforms and CRM systems the Customer connects are not sub-processors of FYAI. The Customer connects them, has its own agreement with each, and FYAI sends personal data to, or reads it from, the Customer's own account there on the Customer's instruction. FYAI is not responsible for what the platform does with that data.
8.2 FYAI sends a lead only to the platform that brought it in, and sends email addresses and phone numbers only as SHA-256 hashes.
8.3 Customer lists FYAI maintained stay in the Customer's ad accounts when a connection, the workspace or the Agreement ends; they are the Customer's. They are no longer kept up to date from then on. When deleting a workspace the Customer can have FYAI take everybody it put on them off first.
9. International transfers
9.1 FYAI stores and processes the personal data in the Netherlands. A sub-processor that processes personal data outside the EEA does so under the EU Standard Contractual Clauses (2021/914). Transfers to the platforms the Customer connects fall under the Customer's own agreement with each platform.
10. Requests from data subjects
10.1 FYAI assists the Customer in answering requests from data subjects (art. 12 to 22 GDPR). In FYAI the Customer can find a lead, download it and delete it from the lead panel. A request FYAI receives directly is passed on to the Customer without delay and not answered by FYAI itself.
11. Personal data breaches
11.1 FYAI notifies the Customer of a personal data breach without undue delay, and at the latest within 48 hours after becoming aware of it, with the information art. 33(3) GDPR asks for as far as available, so the Customer can meet its own 72-hour deadline. FYAI keeps the Customer informed and takes the measures needed to limit the consequences.
12. Assistance
12.1 FYAI assists the Customer, as far as can reasonably be asked, with data protection impact assessments and prior consultations of the supervisory authority (art. 35 and 36 GDPR).
13. End of the processing
13.1 When the Customer deletes a workspace or the Agreement ends, the workspace stops at once and stays readable for 30 days, so the Customer can download its leads; the Customer can undo a deletion within that period. After the 30 days the workspace and its leads are deleted, and the leads are removed for good 90 days later.
13.2 A lead the Customer deletes is removed for good after 90 days.
13.3 FYAI keeps the audit log of the Customer's instructions as evidence that it processed on instruction; the IP address and browser in an entry are removed 24 months after the instruction ended. Invoices are kept for the statutory retention period.
14. Audits
14.1 FYAI makes available the information needed to demonstrate compliance with art. 28 GDPR, in the first place in writing. The Customer may have an audit carried out at most once a year, with 30 days' notice, during office hours, by an auditor bound to confidentiality, at the Customer's expense.
15. Liability, precedence and law
15.1 Liability under this DPA follows the Agreement.
15.2 For the processing of personal data this DPA prevails over the Terms of Service.
15.3 Dutch law applies; disputes are brought before the court the Terms of Service name.
Annex 1: Description of the processing
Data subjects. Visitors and leads of the Customer; contacts in files the Customer imports and in the Customer's CRM; the Customer's users of FYAI.
Personal data. Contact details (name, email address, phone number, company); the form fields the Customer maps; click IDs, UTM parameters, landing page and referrer; IP address and browser at submission; the qualification, status and amounts of a lead; deal and invoice amounts from the Customer's CRM. No special categories.
Processing. Collecting leads from the Customer's lead sources; storing, displaying and enriching them; matching them with CRM data; sending conversions and customer lists, with email addresses and phone numbers hashed, to the platforms the Customer connects; reporting.
Retention. Lead data for as long as the workspace is active, or shorter on the Customer's instruction; deleted leads 90 days; API logs 90 days; export files 30 days; import files 7 days; the audit log as in 13.3.
Annex 2: Technical and organisational measures
- Hosting, application servers and databases in the Netherlands (Iron Mountain data centre, Haarlem); the application is only served over HTTPS.
- Values of a website form are only stored once the Customer activated it, and only the mapped fields; password and file fields are never read.
- Email addresses and phone numbers go to advertising platforms only as SHA-256 hashes, and a lead only to the platform that brought it in.
- Access tokens of platforms and CRMs are stored encrypted; API keys only as a hash; passwords hashed.
- Data, connections and access are separated per workspace; team roles and access per workspace; email addresses are verified; repeated login attempts are blocked; changing a password ends other sessions.
- Every outgoing API call is logged for 90 days with its request and response, with tokens and other secrets removed; the Customer's instructions are kept in an audit log.
- Rate limits on the tracking endpoint, the Inbound API and the CSV feed.
- Payments run through Stripe Checkout; card details never reach FYAI.
- Connections to CRM systems only read; FYAI writes nothing into the Customer's CRM.
Annex 3: Sub-processors and connected platforms
| Sub-processor | Function | Location |
|---|---|---|
| CONSTRUKT B.V. | Hosting, application servers and databases (Iron Mountain data centre, Haarlem) | Netherlands (EU) |
| Mailgun Technologies, Inc. | Transactional email | European Union (EU region only) |
| Functional Software, Inc. (Sentry) | Error monitoring | EU/US, under SCC |
| Stripe Payments Europe, Ltd. | Billing and payment processing | Ireland (EU), with transfers under SCC |
Not sub-processors (article 8): the platforms the Customer connects.
| Platform | What FYAI does there |
|---|---|
| Google LLC (Google Ads, Google Tag Manager) | Offline conversions and enhanced conversions for leads to the customer's Google Ads account, Customer Match lists, the customer's Tag Manager container, lead form submissions Google sends to the customer's webhook in FYAI |
| Typeform | Form submissions Typeform sends to the customer's webhook in FYAI, from forms the customer activated |
| Tally | Form submissions Tally sends to the customer's webhook in FYAI, from forms the customer activated |
| Meta Platforms Ireland Ltd. | Conversions API, Custom Audiences, Lead Ads |
| LinkedIn Ireland Unlimited Company | Conversions API, Matched Audiences, Lead Gen Forms |
| OpenAI Ireland Ltd. | Conversions API (ChatGPT Ads) |
| Pinterest Europe Ltd. | Conversions API |
| Snap Group Limited (Snap Inc.) | Conversions API, Lead Generation forms |
| TikTok Technology Limited | Events API, Instant Forms |
| Calendly LLC | Bookings of the customer's selected event types, received as leads; click ids passed through booking links |
| Microsoft Ireland Operations Limited (Microsoft Advertising) | Offline conversions with enhanced conversions |
| CRM and invoicing systems: HubSpot, Salesforce, Pipedrive, Teamleader Focus, monday.com, ClickUp, Odoo, Moneybird | Read only: deal and invoice amounts proposed for the customer's leads |