Legal
Data Processing Agreement
How Future Visuals B.V. (Tlntly) processes candidate data for its customers under Article 28 of the GDPR.
Effective October 29, 2026
Future Visuals B.V. took over the business of the eenmanszaak Future Visuals on 25 September 2026. It is now the provider of Tlntly.
Roles
Future Visuals B.V. is a Dutch besloten vennootschap (private limited company), KvK 42176504, VAT NL870047577B01, Franz Lisztlaan 16, 2253 HL Voorschoten, the Netherlands. Its director is Holding Opus B.V. (KvK 42175360), represented by Rick van den Broek. Future Visuals B.V. took over the business of the eenmanszaak Future Visuals on 25 September 2026.
This Data Processing Agreement (DPA) covers the candidate data you upload to Tlntly. You are the controller: you decide why the data is processed. Future Visuals B.V. (“we”) processes it on your behalf as processor (GDPR Article 28). If you process the data for your own client, you are their processor, we are your subprocessor, and this DPA applies down that chain.
This DPA is part of our Terms of Service or of a signed agreement. A signed agreement keeps the DPA version it refers to until it ends. Terms such as “personal data” and “processing” have their GDPR meaning.
What we process
- Purpose: providing Tlntly: parsing CVs and vacancies, scoring and matching, tailoring, translating, writing letters, anonymizing, exporting PDFs and storing your data. AI runs on Google Gemini through Vertex AI in the EU.
- Duration: as long as you use Tlntly, plus the periods in Deletion.
- Whose data: candidates and anyone else whose data you upload.
- Which data: names, contact details, photos and LinkedIn URLs; work history, education, skills, languages and other CV content; scores, rationales and generated texts.
- Sensitive data: Tlntly is not designed for special categories of data (such as health or religion) or criminal records. CVs may still contain them, or reveal them through a photo, date of birth or nationality. Upload such data only when you need it and have a legal basis. You can remove it, or anonymize a profile, at any time. Our scoring is instructed not to use or infer protected traits.
- We use the data only for you, never for our own purposes, and never to train AI.
Our duties
We:
- process the data only on your documented instructions, including for transfers outside the EEA, unless EU or Dutch law requires otherwise. Your instructions are the Terms, this DPA and how you use Tlntly's settings;
- tell you straight away if we think an instruction breaks data protection law;
- make sure everyone with access to the data is bound to confidentiality;
- help you answer requests from people who exercise their GDPR rights;
- help you with security, data breaches, data protection impact assessments and consulting a supervisory authority (GDPR Articles 32 to 36);
- give you the information you need to show compliance, and allow audits as described below.
Your duties
You make sure you have a legal basis for the data you upload, inform candidates about the processing (including the AI), answer their requests, and meet your duties as deployer under the EU AI Act, as set out in the Terms.
Security
We take the measures below (GDPR Article 32). We may improve them, but never lower the overall level of protection.
- Encryption in transit (HTTPS/TLS) and at rest, including backups.
- Sign-in through Google or LinkedIn. Access is limited to the members of each organization, by role, and each organization's data is kept separate.
- Only our authorized staff can reach production systems, when needed, with multi-factor authentication on our provider accounts. We look at your content only for support you ask for, to handle an incident, or when the law requires it.
- The database and files are stored in the EU, and AI runs in the EU. Background job records hold identifiers, not CV content. AI telemetry doesn't record prompts or outputs.
- Continuous backups with point-in-time recovery, kept for at most 35 days.
- Uploads are checked for unsafe content, and scoring instructions forbid made-up facts and protected traits.
- Technical logs to detect and investigate incidents.
- Every code change is reviewed by a person and type-checked before release.
Subprocessors
You give general permission to use the subprocessors below. Each is bound by contract to protection at least as strong as this DPA, and we remain fully liable for them (GDPR Article 28(4)).
| Subprocessor | Purpose | Data | Location | Transfer safeguard |
|---|---|---|---|---|
| Google Cloud (Vertex AI) Google Cloud EMEA Limited (Ireland) | AI processing: parsing, scoring, tailoring, translation, letters, anonymization | CV and vacancy content, candidate data, AI prompts and outputs | EU (Vertex AI, EU multi-region) | Not needed |
| Neon (Databricks) Databricks, Inc. (USA) | Database hosting and backups | All customer data | EU (AWS Frankfurt, Germany) | Data stays in the EU; SCCs and EU-US Data Privacy Framework for support access |
| Amazon Web Services (S3) Amazon Web Services EMEA SARL (Luxembourg) | File storage | Logos, branding images and member work photos | EU (Ireland, eu-west-1) | Not needed |
| Vercel Vercel Inc. (USA) | Application hosting | Requests and responses passing through the app, technical logs | EU and USA | EU-US Data Privacy Framework and SCCs |
| Trigger.dev API Hero Ltd (United Kingdom) | Background job processing | Job identifiers, statuses and technical logs. Its workers process CV content in memory to run AI tasks; job records don't store it. | USA (AWS, us-east-1) | UK adequacy decision; SCCs for onward transfers |
| Resend Resend, Inc. (USA) | Product and service emails | Names and email addresses of users and invitees, email content | EU (sending, Ireland) and USA | EU-US Data Privacy Framework and SCCs |
| Stripe Stripe Payments Europe, Limited (Ireland) | Payments, invoices and tax | Billing contact, company and payment details (no candidate data) | EU and USA | EU-US Data Privacy Framework and SCCs |
We email you at least 30 days before we add or replace a subprocessor. You can object on reasonable data protection grounds within that time. If we can't resolve it, you can end the affected service before the change takes effect. In an emergency, such as a security incident at a subprocessor, we may act sooner and tell you as soon as possible.
Outside the EU
We store personal data in the EU (database in Germany, files in Ireland) and run AI in the EU. Some subprocessors are US companies or process data in the USA, as the table above shows. For those transfers we rely on the EU-US Data Privacy Framework where the provider is certified, and otherwise on the EU's Standard Contractual Clauses, together with encryption and access controls.
Data breaches
We tell you without undue delay, and within 48 hours, after we become aware of a personal data breach. We include what we know: what happened, which data and roughly how many people are affected, the likely consequences, and what we are doing about it. We help you investigate, limit the damage, and notify the authority and the people affected (GDPR Articles 33 and 34).
Audits
We first answer your written questions. We don't hold security certifications or audit reports of our own; our subprocessors publish their own security information. If you still need an audit or inspection, you or an independent auditor you hire may do one at most once a year (more often after a personal data breach or when a supervisory authority requires it), with 30 days' notice, during office hours and at your own cost.
Deletion
- You can export or delete candidates, CVs and vacancies at any time.
- When a paid subscription ends, we keep the data for 12 months so you can export it or subscribe again, and email the owner 30 days before deletion. Then we delete all personal data we process for you.
- After the subscription ends, the owner can ask for earlier deletion in Settings (done 7 days later) or by email (done within 30 days). We confirm deletion by email.
- Deleted data leaves our backups within 35 days. We restore a backup only to recover from an incident, and then delete again what was deleted before.
- Background job records at Trigger.dev hold identifiers and logs, not CV content. Records from before 28 October 2026 may contain CV content; we have asked Trigger.dev to delete them.
- We keep no copies after deletion, unless EU or Dutch law requires it.
Liability, duration and changes
- Liability under this DPA follows the limits in the Terms or the signed agreement. This doesn't limit candidates' rights under GDPR Article 82.
- This DPA applies as long as we process personal data for you, and ends when we have deleted or returned it. Confidentiality and breach duties continue after that.
- We email you about material changes to this DPA at least 30 days before they take effect, unless the law requires a change sooner. If you keep using Tlntly, you accept the change. If you object, you can cancel before it takes effect; the current version then applies until your paid period ends.
Contact
For DPA questions or to request a signed copy:
Future Visuals B.V., Franz Lisztlaan 16, 2253 HL Voorschoten, the Netherlands. KvK 42176504. VAT NL870047577B01. hello@tlntly.com