Privacy policy

Last updated: 2026-07-29

This Privacy Policy describes how FYAI B.V. ("we", "us", "FYAI") processes personal data in connection with the FYAI platform.

FYAI acts in two distinct roles under the GDPR:

  1. Controller for the data of our own customers and their team members, the account holders who use FYAI.
  2. Processor for the lead data our customers collect through FYAI on their own websites. Our Data Processing Agreement applies additionally to that role.

1. Who we are

Company
FYAI B.V.
Chamber of Commerce
42118728
Registered address
Gaspeldoorn 8, 4814 NP Breda
Email
privacy@fuelyour.ai
Privacy contact
Lauren Fortes
Data Protection Officer
FYAI is not of the scale at which the GDPR requires a formal Data Protection Officer.

2. What personal data we process

2.1 As controller (customer accounts)

When you create an FYAI account or are invited as a team member, we process:

  • Identification data: name, email address
  • Authentication data: hashed passwords, API tokens, session data
  • Team context: team and workspace roles, invitation history
  • Communication: emails about your account (transactional only, no marketing unless you opted in)
  • Logs: IP address, user agent and timestamps for logins, critical actions such as form activation, downloads of leads and connecting platforms, and audit events

2.2 As processor (lead data)

When a customer deploys FYAI on their website, we process, on the instruction of that customer, data about visitors to that website:

  • Attribution data: gclid, fbclid, li_fat_id, oppref, epik, ScCid, ttclid, msclkid, source URL, timestamps, IP address and user agent
  • Form data: only after explicit activation by the customer and only for the fields the customer has mapped: name, email address, phone number, company name, address details and any designated custom fields
  • Consent snapshot: where the customer sends one
  • Lead qualification: labels, quote value and realised revenue entered by the customer

Until a form is activated, its leads hold the names of its fields, never their values.

Leads also reach FYAI from the lead forms of advertising platforms the customer connects (Meta, LinkedIn, TikTok, Snapchat, and Google Ads lead form assets, which Google sends to a webhook of the customer's workspace in FYAI), from forms the customer builds with Typeform or Tally (FYAI registers a webhook on a form only once the customer has activated it, and asks the tool to remove it when the form is switched off or the tool disconnected; a click id or campaign value arrives only through a hidden field the customer adds to the form), from the customer's own systems through the Inbound API and from files the customer imports. Answers to a platform lead form are stored on the lead only once the customer has activated that form; a Google Ads lead form lead received before that keeps only its click id and campaign. Every call to the Inbound API or to a lead webhook, its content included, is kept in a call log for 90 days for troubleshooting.

When the customer connects Calendly, every booking of an event type the customer selected becomes a lead: the invitee's name, email address, phone number where the event type asks for one, the answers to the booking questions, the appointment time, the UTM values of the booking link and, when the booking is cancelled, when, by whom and why. On pages where the customer runs the FYAI script, the script adds the stored click ids to the Calendly link in its salesforce_uuid parameter, so that they return to FYAI with the booking; nothing else is sent to Calendly. Bookings of event types the customer did not select are not stored: their call is logged with its outcome and without the invitee's data, as is every Calendly call. A cancellation that arrives before its booking is kept as the booking's Calendly reference, the time and whether host or invitee cancelled, without name or reason, for at most seven days.

3. Purposes and legal bases

Processing Legal basis (GDPR)
Creating and managing accounts Performance of a contract (Art. 6(1)(b))
Tracking and logging leads Processor on behalf of the customer (Art. 28)
Security, fraud and abuse detection Legitimate interest (Art. 6(1)(f))
Billing and accounting Legal obligation (Art. 6(1)(c))
Product improvement on aggregated, non-identifiable data Legitimate interest (Art. 6(1)(f))
Service and account communication Performance of a contract (Art. 6(1)(b))

We do not use lead data for our own marketing purposes, and we do not share it with any third party other than the advertising platforms designated by the customer.

4. Sharing with third parties (sub-processors)

We engage the sub-processors listed below. The Data Processing Agreement lists them too.

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

Platforms the customer connects. The advertising platforms and CRM systems below are not sub-processors of FYAI. The customer connects them per workspace, has its own agreement with each, and FYAI sends data to (or reads data from) the customer's own account there, on the customer's instruction. Lead data only goes to platforms the customer has connected, and only to the platform that brought the lead in.

Platform What FYAI does there Location
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 EU/US
Typeform Form submissions Typeform sends to the customer's webhook in FYAI, from forms the customer activated EU/US
Tally Form submissions Tally sends to the customer's webhook in FYAI, from forms the customer activated Belgium (EU)
Meta Platforms Ireland Ltd. Conversions API, Custom Audiences, Lead Ads EU/US
LinkedIn Ireland Unlimited Company Conversions API, Matched Audiences, Lead Gen Forms EU/US
OpenAI Ireland Ltd. Conversions API (ChatGPT Ads) EU/US
Pinterest Europe Ltd. Conversions API EU/US
Snap Group Limited (Snap Inc.) Conversions API, Lead Generation forms EU/US
TikTok Technology Limited Events API, Instant Forms EU/US
Calendly LLC Bookings of the customer's selected event types, received as leads; click ids passed through booking links US
Microsoft Ireland Operations Limited (Microsoft Advertising) Offline conversions with enhanced conversions EU/US
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 Depends on the system and the customer's account

5. International transfers

Our hosting, application servers and databases are located in the Netherlands. Where a sub-processor processes data outside the EEA, that transfer takes place under the EU Standard Contractual Clauses (2021/914). Several platforms the customer connects, such as Google and Meta, are established in the United States; those transfers fall under the customer's own agreement with the platform. FYAI sends email addresses and phone numbers to them only as SHA-256 hashes.

6. Retention periods

Category Retention
Account data Until account termination, plus 12 months
Audit log (form activations and mapping changes, imports, downloads of leads, connected platforms and CRMs) Kept as proof of the customer's instructions. The IP address and user agent in an entry are removed 24 months after the instruction ended.
CSV export files Maximum 30 days on disk
Customer lead data Per customer instruction; by default for as long as the workspace is active. Soft-deleted records are permanently removed after 90 days.
A deleted workspace Read-only for 30 days, then deleted with its leads; the leads are permanently removed 90 days later. Customer lists in the customer's own ad accounts stay there unless the customer asks FYAI to empty them first.
Billing data 7 years, statutory tax retention

7. Security

We take appropriate technical and organisational measures, including:

  • TLS encryption on all connections
  • Password hashing, and encryption at rest of third-party access tokens
  • Hashing of email addresses and phone numbers (SHA-256 over the value normalised as each platform prescribes: for email lowercased and trimmed, and for Microsoft Advertising also without the dots and any +alias before the @; for phone numbers the platform's international format) where the conversion matching protocol requires it. The plaintext values never leave our infrastructure, only the hashes are forwarded.
  • Role-based access control, with multi-tenant isolation per team and per workspace
  • Rate limiting on the tracking and export endpoints
  • Audit logging of privacy-sensitive actions
  • Backups and tested recovery procedures
  • Limited internal access on a need-to-know basis

8. Cookies and similar technologies

The FYAI platform itself uses strictly necessary cookies only, session and CSRF. We place no tracking or marketing cookies on our own platform.

On our customers' websites, FYAI may be deployed as a tracking pixel. Placing that pixel and obtaining any required cookie consent is the responsibility of that customer, who is the controller for it.

9. Your rights

Under the GDPR you have the right to:

  • Access your data (Art. 15)
  • Rectification (Art. 16)
  • Erasure (Art. 17)
  • Restriction of processing (Art. 18)
  • Object to processing (Art. 21)
  • Data portability (Art. 20)
  • Withdraw consent you previously gave

Are you a visitor to a customer's website? Address your request to that customer first: they are the controller. We support them in fulfilling it.

Requests can be sent to privacy@fuelyour.ai. You also have the right to lodge a complaint with the Dutch Data Protection Authority (Autoriteit Persoonsgegevens).

10. Deleting data connected through Meta

If you connected a Meta advertising account to FYAI using Facebook Login, you can ask us to delete the data associated with that connection. Send a request to privacy@fuelyour.ai, or remove FYAI from your Facebook account settings, in which case Meta notifies us automatically.

On receiving such a request we delete the stored access tokens and the account connection. You receive a confirmation code with which you can check the status of your request at any time.

11. Data breaches

We comply with the personal data breach notification duty under Art. 33 GDPR. Affected customers are informed without undue delay, in accordance with the Data Processing Agreement.

12. Changes to this policy

We may update this Privacy Policy. Material changes are communicated to account holders at least 30 days in advance, by email or in the application.

13. Contact

FYAI B.V., Gaspeldoorn 8, 4814 NP Breda
privacy@fuelyour.ai