Data Processing Agreement
Version 17 April 2026 · Pursuant to Art. 28 GDPR · Integral part of the Terms & Conditions
This Data Processing Agreement (“Agreement”) is entered into between the customer (“Controller”) and Triad B.V., trading under the name LeadGrid.io (“Processor”), with its registered office at Parallel Boulevard 17 A, 2202 HK Noordwijk, the Netherlands, registered with the Netherlands Chamber of Commerce under number 42034623. It is deemed agreed when Controller takes out a Subscription to the Service.
1. Definitions
Terms used in this Agreement have the meaning given in the GDPR. In addition, the definitions of the Terms & Conditions apply. In case of conflict, this Agreement prevails in respect of the processing of personal data.
2. Subject, nature and purpose
Processor processes personal data exclusively on the instructions and for the account of Controller, in the context of providing the LeadGrid.io Service: recruitment and sales pipeline management, tracking of candidates and leads, AI-assisted CV summaries, rejection-email drafts, contact extraction, inbound and outbound email, and integrations via the public REST API.
Categories of data subjects and personal data are described in Annex 1.
3. Duration
This Agreement takes effect when the Subscription is concluded and runs for as long as Processor processes personal data for Controller. After termination, the provisions on confidentiality, liability and governing law remain in force to the extent necessary.
4. Instructions
Processor processes personal data only on the written instructions of Controller. The Terms & Conditions, this Agreement and Controller’s configuration of the Service constitute such instructions. Processor will inform Controller without delay if, in its opinion, an instruction infringes the GDPR or other data-protection legislation.
5. Confidentiality
Processor ensures that all persons processing personal data under its authority are bound by an obligation of confidentiality, either by statute or by contract.
6. Security measures
Processor implements appropriate technical and organisational measures to secure personal data against loss, unauthorised access and other unlawful processing, as described in Annex 2. Processor reviews these measures periodically and updates them where appropriate, taking into account the state of the art and the risk to data subjects.
7. Sub-processors
Controller grants Processor general authorisation to engage the sub-processors listed in Annex 3. Processor imposes on each sub-processor, by written agreement, the same obligations as arise from this Agreement, to the extent applicable.
Processor will inform Controller in advance of intended changes to the sub-processor list (additions or replacements). Controller may object, with reasons, within thirty (30) days of notification. If the parties cannot reach a solution, Controller may terminate the Subscription as of the effective date of the change.
8. Data-subject rights
Processor assists Controller by appropriate technical and organisational measures, insofar as reasonably possible, to fulfil Controller’s obligation to respond to requests from data subjects (access, rectification, erasure, restriction, portability and objection). Processor forwards any requests it receives directly to Controller.
9. Personal-data breaches
Processor notifies Controller without undue delay, and in any event within 48 hours of discovery, of any personal-data breach. Processor provides all information reasonably available that Controller needs to fulfil its own legal notification and documentation obligations, including:
- the nature of the breach and the categories of data involved
- the (estimated) scale and possible consequences
- the measures already taken and proposed
- contact details for further information
Processor will not notify the Dutch Data Protection Authority (Autoriteit Persoonsgegevens) or data subjects on behalf of Controller unless expressly instructed to do so.
10. Assistance with DPIAs and prior consultation
Processor assists Controller, upon reasonable request, with any data-protection impact assessment (DPIA) and any subsequent prior consultation of the supervisory authority, taking into account the nature of the processing and the information available to Processor.
11. Return and deletion of data
After termination of the Subscription, Processor allows Controller a period of 30 days to export personal data (via the REST API or dashboard). Thereafter, Processor deletes all personal data, unless storage is legally required (e.g. tax retention obligations for billing records). Processor confirms deletion in writing on request.
12. Audit
Processor makes available to Controller, upon request, all information necessary to demonstrate compliance with this Agreement. Controller may, once per year — or more often in case of a reasonable suspicion of non-compliance — conduct (or have conducted) an audit. The audit takes place on business days, during office hours, after timely announcement, and in a manner that does not unreasonably disrupt the Service. The costs of the audit are borne by Controller, unless material deficiencies are established.
Processor may instead provide a recent independent audit report or an ISO 27001 / SOC 2 attestation from its (sub-)processors, which Controller will generally accept.
13. International transfers
Where processing takes place outside the European Economic Area, it is based on appropriate safeguards as referred to in Art. 46 GDPR, including the European Commission’s Standard Contractual Clauses (2021/914) or the EU–US Data Privacy Framework, supplemented by technical additional measures where appropriate.
14. Liability
The liability of the parties under this Agreement is governed by the liability clause of the Terms & Conditions. Each party is liable under Art. 82 GDPR towards data subjects for damage caused by that party’s failure to comply with its GDPR obligations.
15. Miscellaneous
In case of conflict between this Agreement and other documents between the parties, this Agreement prevails in respect of the processing of personal data. Changes are valid if announced through the Service or by email, subject to a reasonable period to object or terminate the Subscription. This Agreement is governed by Dutch law; disputes are submitted to the District Court of The Hague (Rechtbank Den Haag).
Annex 1 — Data and categories of data subjects
Categories of data subjects
- Users of Controller (employees, administrators)
- Candidates tracked in recruitment pipelines
- Leads and prospects tracked in sales pipelines
- Contact persons at leads’ or candidates’ organisations
Categories of personal data
- Identification and contact data: name, email, phone, company, role/title, LinkedIn or external profile URL
- CV and application content: uploaded résumés (PDF), work history, education, skills, attachments
- Commercial pipeline data: deal size, currency, stage, notes, meeting history, assigned owner
- Communication content: emails forwarded into LeadGrid via inbound email, outbound messages sent from LeadGrid, notes attached to dossiers
- AI-generated derivative data: candidate summaries, extracted contact details, rejection-email drafts, stage-fit scores
- Connected-system data: data pushed/pulled via the public REST API and any third-party integrations activated by Controller
- Technical data: IP address, session and log data for security and support purposes
Nature of processing
Collection, storage, consultation, structuring, modification, combination, transmission (including via AI services for classification and text generation), disclosure to connected systems, and erasure.
Annex 2 — Security measures
Processor has implemented, among others, the following measures:
- TLS 1.2+ for all data in transit
- Supabase Row-Level Security (RLS) on every table with mandatory organisation-id scoping as defence-in-depth
- Role-based access control (owner / admin / member) with least-privilege enforcement server-side
- Password hashing (bcrypt) managed by Supabase Auth; session cookies marked
HttpOnly+Secure - Public REST API secured with hashed API keys, per-key rate limits (60 req/min free, 600 req/min growth), scope validation
- Stripe webhooks verified with HMAC signature; idempotent event processing via
processed_stripe_eventstable - Inbound-email endpoint secured with shared secret and constant-time comparison; file-size and content-type limits on CV uploads
- Secret management via environment variables; no hardcoded secrets
- CSP, HSTS, X-Frame-Options
DENY, Referrer-Policy, Permissions-Policy hardening on all responses - Audit logging of sensitive actions and AI requests
- Sandboxed, version-controlled deployments on Vercel with automated build and type checks
- Daily encrypted database backups managed by Supabase; periodic restore tests
- Production-data access restricted to a small number of personnel under strict authorisation and confidentiality
- Incident-response process with a 48-hour notification obligation for personal-data breaches
Annex 3 — Sub-processors
| Sub-processor | Processing | Location |
|---|---|---|
| Supabase Inc. | Database, authentication, file storage | EU (Ireland) |
| Vercel Inc. | Application hosting and edge network | EU / US (SCCs) |
| OpenAI, L.L.C. | AI classification and text generation (no training on customer input) | US (SCCs) |
| Stripe Payments Europe, Ltd. | Subscription billing and payment processing | EU (Ireland) / US (SCCs) |
| Resend, Inc. | Outbound transactional email and inbound-email parsing | US (SCCs) |

