Plain-language summary (this does not replace the agreement):
- Your customers' data is yours: you decide how it is used and LinkLider processes it on your behalf.
- We only use it to provide the service and according to what you set up in your dashboard; never to sell it or for our own marketing.
- We use subprocessors (hosting, email, messaging, AI) that are listed, and we notify you before adding new ones.
- If there is a security incident, we notify you without undue delay (target: 72 hours) so you can notify your customers.
- You must have your own privacy notice and get express consent for sensitive data, such as health data.
- Export your data before closing your account; after you request closure you have 11 days to change your mind, and then we delete it, except what the law requires us to keep.
1. Parties and acceptance
This Data Processing Agreement (the "DPA") is entered into between the Merchant, as controller (or "business"), and LINKLIDER LLC or LinkLider S.A.S. depending on the currency in which it contracts (the "Contracting Entity"), as processor (or "service provider"). It is accepted when a business is created on LinkLider and is part of the Terms and the Merchant Terms, and it prevails over them regarding the Merchant's customer data. For LINKLIDER LLC this English version governs; for LinkLider S.A.S. the Spanish version governs.
2. Purpose, duration and business purpose
The processor will process the personal data that the Merchant and its customers enter on the platform only to provide the LinkLider Services (store, payments, bookings, events, forms, email, messaging, loyalty, CRM, point of sale and other features). This is the "business purpose" of the processing. It lasts as long as the service relationship, plus the period in section 13.
3. Data and data subjects
| Data subjects | Types of data |
|---|---|
| Buyers and customers | Name, email, phone, shipping address, purchase history, payments (limited card data), bookings, loyalty, subscriptions, visit source |
| Patients, students, attendees | The above plus form responses, which may include health or other sensitive data, and uploaded files |
| Subscribers and prospects | Email, name, email opens, survey responses |
| Applicants (the Merchant's job openings or programs) | Form data and uploaded documents |
| CRM contacts and Team Members | Contact details, notes, activity |
4. Merchant's instructions
The processor processes the data according to the Merchant's instructions, which are: these documents, the configuration the Merchant sets in its dashboard (what it collects, who it messages, what it automates, what it connects) and written instructions sent to legal@linklider.com. If an instruction appears to violate the law, the processor will tell the Merchant and may decline to carry it out.
5. Processor obligations
- Process the data only on the Merchant's instructions and for the business purpose. Not sell it or share it for cross-context behavioral advertising; not retain, use or disclose it outside the direct business relationship with the Merchant; and not combine it with other data except as permitted by law (for example, to provide the service or prevent fraud).
- Comply with the privacy laws that apply to it as a service provider or processor, provide the same level of protection they require, and notify the Merchant if it can no longer meet these obligations. The Merchant may take reasonable steps to stop and remediate unauthorized use. (for example, Cal. Civ. Code §§1798.100(d) and 1798.140(ag) and Cal. Code Regs. tit. 11, §7051).
- Keep the data confidential; staff with access are bound by confidentiality.
- Apply the security measures in section 8.
- Not transfer the data except to subprocessors (section 7), to authorities when the law requires it, or on the Merchant's instructions.
- Help the Merchant respond to data subject requests (section 10).
- Delete or return the data at the end (section 13).
- If it ever processes data of people in the European Union, the EEA or the United Kingdom, meet the requirements of Article 28 of the GDPR (and of the UK GDPR).
6. Use of artificial intelligence
The processor's AI features are designed not to send contact details of the Merchant's customers: they receive the content they need (business texts, products, questions). In free text, such as a chat history, emails, phone numbers, CURP and RFC are removed automatically before sending, but that filter may not catch everything. If the Merchant connects its own AI account or another external tool (for example, through the API or MCP), what it sends there is its own decision and outside this DPA.
7. Subprocessors
The Merchant authorizes the processor to use the subprocessors listed in the Privacy Policy (hosting, Cloudflare, email, Twilio and WhatsApp, Firebase and AI providers, among others, with the role shown there). The processor:
- Imposes on them data protection obligations equivalent to those in this DPA and is responsible for them to the Merchant.
- Will post changes to that list and email the Merchant at least 30 days before adding a subprocessor that processes its customers' data, except in a security emergency.
- If the Merchant objects on reasonable grounds, the parties will look for an alternative; if there is none, the Merchant may terminate the affected service without penalty.
The integrations the Merchant connects with its own account (Stripe, Mercado Pago, PayPal, Skydropx, Shippo, Factura.com, Clarity, Hotjar, pixels) are third parties engaged by the Merchant, not LinkLider subprocessors. Payment processors also process payment data as independent businesses under their contracts with the Merchant.
8. Security
The processor maintains reasonable administrative, technical and physical measures: encryption in transit, role-based access control, support access with one-time codes and a log of every access, separation of data by business, backups and monitoring. No measure eliminates all risk.
9. Security incidents
If the processor discovers an incident affecting the Merchant's data, it will notify the Merchant without undue delay, aiming to do so within 72 hours after confirming it, with what is known: what happened, which data and data subjects are affected, what measures were taken and what is recommended. It will help the Merchant notify its customers and the authorities when required. Notifying data subjects is the Merchant's obligation as controller unless the parties agree otherwise.
10. Data subject requests
The Merchant handles its customers' requests (access, correction, deletion, opt-out and equivalents). To help, the dashboard lets the Merchant view, correct, export to CSV and delete data. If a data subject writes directly to LinkLider, the request will be forwarded to the Merchant without answering on its behalf, unless the law requires otherwise.
11. Merchant obligations
- Have its own privacy notice (or use the default template, see Merchant Terms) and disclose that it uses LinkLider as a service provider.
- Have a legal basis or consent for each processing, including marketing messages.
- Obtain express written consent for sensitive data (health, ethnic origin, beliefs, sex life, biometric data, among others).
- Not request or upload data it does not need (for example, full card numbers, passwords or IDs if not required).
- If it keeps medical records, comply with the health rules that apply to it; LinkLider is not a certified electronic health record system.
- No HIPAA data. LinkLider is not offered for protected health information (PHI or ePHI) under the U.S. Health Insurance Portability and Accountability Act (HIPAA), does not act as a business associate and does not sign Business Associate Agreements. A Merchant that is a HIPAA covered entity or business associate must not collect, upload, store or send PHI or ePHI through LinkLider (forms, bookings, files, messages, notes or any other feature). A patient's consent does not replace a Business Associate Agreement where the law requires one. This exclusion does not change what the law requires if PHI is in fact processed: if the Merchant learns that it has, it must tell us right away at legal@linklider.com so the data can be removed.
- For minors, obtain the consent of the parent or guardian.
- Be responsible for its Team Members and the integrations it connects.
12. International transfers
Data is hosted in the United States and some subprocessors are in other countries. The Merchant accepts this and must disclose it in its privacy notice. The processor requires appropriate safeguards from its subprocessors.
13. Termination and deletion
The Merchant can export its data from the dashboard at any time and should do so before requesting closure. When it requests closure, its businesses go offline and it has 11 days to change its mind; after that, the processor deletes the data from the platform, and from backups in their normal cycle, except what the law requires it to keep (for example, tax or payment records), which it will keep restricted and only for that purpose.
14. Compliance review
Once a year, or after an incident, the Merchant may ask for reasonable information about security measures (questionnaire, description of controls or subprocessors' certifications). On-site audits must be agreed in writing, with prior notice, confidentiality and at the Merchant's expense.
15. Liability
Each party is responsible for its own breaches of data protection law. The limitation of liability and indemnification in the Terms apply, except for what the law does not allow to be limited.
Last updated: November 3, 2026.