Data Processing Agreement (SDR Agent)

Last updated: October 18, 2026

1. Parties and purpose

This Agreement is entered into between the Clonio user who turns on the SDR Agent (the "Controller") and ZIPGENIAL LLC, a Florida (United States) company with address at 655 S Le Jeune Rd, Ste 905, Coral Gables, FL 33134 and email contact@clonio.es, owner of Clonio (the "Processor"). It governs the processing of third parties' personal data that the Processor carries out on the Controller's behalf when providing it with the SDR Agent, under Article 28 of Regulation (EU) 2016/679 ("GDPR"). It forms part of Clonio's Legal Notice, and the Controller expressly accepts it when turning on the SDR Agent. If the Controller turns it on acting for a company, it declares that it is authorised to accept this Agreement on that company's behalf, and that company is the Controller. The Processor's representative in the Union (Article 27 GDPR) is GRUPO TINFORCE S.L.U., Spanish tax ID (NIF) B22930978, Rúa Dinán, 21, entreplanta, puerta B, 27002 Lugo (Spain), info@zipgenial.com.

2. Description and duration

The subject matter, nature and purpose of the processing, the types of data, the categories of data subjects and the retention periods are described in Annex I. This Agreement lasts while the SDR Agent is turned on and until the deletion provided for in clause 11.

3. Instructions

The Processor processes the data only on the Controller's documented instructions, including with regard to international transfers. Documented instructions are this Agreement and its Annexes, the settings the Controller chooses in the app (activation, ideal customers, stages, notes, discards, deletions, exclusions and deactivation) and any additional written instructions it sends to contact@clonio.es and the Processor accepts. By accepting this Agreement, the Controller approves as its own instruction the operation of the service described in Annex I. The Processor will notify the Controller at least thirty (30) days in advance, by email or in the app, of any change to the data captured, the purpose, the retention periods or the sub-processors; will inform it immediately if it considers that an instruction infringes data protection law; and, if Union or Member State law requires it to process the data otherwise, will inform it beforehand, unless that law prohibits it.

4. No own purposes

The Processor does not process the data for its own purposes or those of third parties: it does not sell or disclose it, combine it across Controllers, or use it for advertising or to train or fine-tune artificial intelligence models, and it does not allow its sub-processors to do so. As the sole exception, it may derive from the data aggregated, anonymous statistics on how the service works (for example, counts by interaction type or the accuracy rate of the assessment), from which no one can be identified, in order to maintain and improve the SDR Agent; for that operation it acts as controller, on the basis of its legitimate interest.

5. Confidentiality

The Processor ensures that persons authorised to process the data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality, and that they only access it when the Controller asks for help with an issue, to investigate a security problem or to comply with the law.

6. Security

The Processor implements the technical and organisational measures in Annex II, which ensure a level of security appropriate to the risk under Article 32 GDPR, and may replace them with others offering an equal or higher level of protection.

7. Sub-processors

The Controller gives the Processor a general authorisation to engage the sub-processors listed in Annex III. The Processor will inform the Controller at least thirty (30) days in advance, by email and by updating Annex III, of any addition or replacement of sub-processors; the Controller may object on reasonable data protection grounds and, if no solution is found, turn off the SDR Agent. The Processor imposes on each sub-processor, by contract, data protection obligations equivalent to those in this Agreement and remains fully liable to the Controller for their performance.

8. International transfers

The Processor is established in the United States. The disclosure of the Controller's data to the Processor is governed by the standard contractual clauses adopted by Commission Implementing Decision (EU) 2021/914, Module Two (controller to processor), which the parties incorporate by reference into this Agreement, with the Controller as data exporter and the Processor as data importer, and with these options: clause 7 (docking clause) is included; in clause 9(a), option 2 (general prior authorisation) applies, with the notice period in clause 7 of this Agreement; the option in clause 11(a) is not included; under clause 13, the competent supervisory authority is the one determined by its paragraph (a) and, for Controllers established in Spain, the Spanish Data Protection Agency; the clauses are governed by Spanish law (clause 17) and disputes are submitted to the courts of Madrid (clause 18). Their Annexes I, II and III are those of this Agreement. In case of conflict, the standard contractual clauses prevail.

Some sub-processors in Annex III process the data in the United States or may access it from there. The Processor only transfers data to sub-processors established outside the Union with a safeguard under Chapter V GDPR (their certification under the EU-U.S. Data Privacy Framework or the standard contractual clauses, Module Three), shown in Annex III.

9. Data subject rights

Taking into account the nature of the processing, the Processor assists the Controller in responding to requests to exercise the rights under Articles 15 to 22 GDPR: in the app, the Controller can view all data about each person, delete them and tick "Don't track this person again". If a data subject contacts the Processor directly, the Processor will forward the request to the Controller without undue delay and will not answer it on the merits unless instructed by the Controller.

Standing instruction: when the Controller deletes a person ticking "Don't track this person again", the Processor will delete their data and keep only a pseudonymised code, computed with a secret key from their LinkedIn identifiers and different for each Controller, solely so as not to record them again while the Controller's account exists. If the person objects or requests erasure directly to the Processor, the Processor will forward the request to the Controller without undue delay, as set out in the previous paragraph, and will only delete them or stop recording them on the Controller's instructions.

10. Assistance and personal data breaches

The Processor assists the Controller in complying with Articles 32 to 36 GDPR with the information available to it about the processing. It will notify the Controller without undue delay, and in any event within forty-eight (48) hours of becoming aware of it, of any personal data breach affecting its data, with the information under Article 33(3) GDPR available to it, supplemented in phases. It will not notify the breach to the supervisory authority or to data subjects on the Controller's behalf unless instructed by the Controller.

11. End of the processing

If the Controller turns off the SDR Agent or no longer has a plan that includes it, the Processor deletes all of its data after thirty (30) days, or immediately if the Controller asks when turning it off, unless the Controller turns it back on or gets that plan back before then. Until deletion, the Controller may ask contact@clonio.es for a copy of its data in a structured format. The database provider's backups are overwritten in their ordinary cycle. The exclusion codes in clause 9 are deleted together with the Controller's account.

12. Information and audits

The Processor makes available to the Controller the information necessary to demonstrate compliance with this Agreement and Article 28 GDPR, and allows for and contributes to audits, including inspections, conducted by the Controller or an independent auditor bound by confidentiality appointed by it, with thirty (30) days' prior notice, at most once a year unless there is a personal data breach or a supervisory authority requires it, first in documentary form and at the Controller's expense.

13. Controller's obligations

The Controller warrants that the processing it entrusts is lawful and, in particular, undertakes to: (a) have a valid legal basis; (b) inform the people it contacts under Article 14 GDPR; (c) respect their right to object, using "Don't track this person again" where appropriate; (d) comply with the rules on commercial communications by electronic means, in particular Article 21 of Spanish Law 34/2002 (LSSI) or the equivalent applicable rule; and (e) give only instructions that comply with data protection law.

14. Liability, precedence, governing law and jurisdiction

Each party's liability towards data subjects is governed by Article 82 GDPR; between the parties, the limitation of liability clause of the Legal Notice applies, except in cases of wilful misconduct or gross negligence and except as mandatorily provided by the standard contractual clauses. On data protection matters, this Agreement prevails over the Legal Notice. It is governed by the GDPR and Spanish law, and disputes concerning it are submitted to the courts of Madrid (Spain), without prejudice to data subjects' right to bring proceedings in the courts of their habitual residence.

Annex I. Description of the processing

  • Data subjects: people who interact with the Controller's LinkedIn content or profile and whom LinkedIn shows the Controller: they react to, comment on or share its posts, send it or accept invitations, start following it or view its profile; and the people on its sales board with whom they converse on LinkedIn.
  • Data: name; professional headline; link to the profile photo; public address and internal identifiers of the LinkedIn profile; connection degree; interactions (type, date, post, reaction type, comment and invitation note text, and whether a repost included text); from the LinkedIn conversations with the people on the board: dates, the conversation thread identifier, who wrote and the class of the reply, and the text of recent messages, processed transitorily to classify it and suggest a reply, without being kept; for some people, current job title, company and location; generated assessments (fit level, reason, quote and confidence, interest level, comment class, reply class and proposed meetings); data entered by the Controller (stage, notes, reminders, meetings, discards and resource deliveries) and suggested messages; pseudonymised exclusion codes. No email addresses or phone numbers are collected and special categories of data are not sought; if a comment reveals them incidentally, it is not used to assess fit and its text is deleted after 90 days.
  • Operations: collection by the Controller's extension from its own LinkedIn session, read-only and with rate limits; recording, structuring, storage and consultation; automated assessment of fit (rules and a language model) and of interest (points, without artificial intelligence); classification of comments; reading of the conversations with the people on the board, without storing their text; classification of replies and detection of agreed meetings; drafting of message and reply suggestions that the Controller decides whether to send; deletion.
  • Purpose: the Controller's assisted business prospecting: identifying the people who interact with it and may fit its ideal customer, suggesting messages and keeping track of its business relationships. The Processor sends no communications.
  • Frequency: continuous while the SDR Agent is on, with periodic reads (roughly every six hours while the browser is in use).
  • Retention: people who do not fit and are not in the pipeline, and people the Controller has done nothing with, 90 days from their last interaction; all others, 12 months without interactions or Controller activity on them; discarded people, 90 days from the discard; comment and invitation note text, 90 days; the text of conversation messages is not kept; everything, 30 days after deactivation (or immediately, if the Controller asks); exclusion codes, while the Controller's account exists.
  • Transfers: to the United States, to the Processor and to the sub-processors in Annex III, with the safeguards in clause 8.

Annex II. Technical and organisational measures

  • Encryption in transit (TLS) between the extension, the app, the database and the providers, and encryption at rest of the database by its provider.
  • Isolation per Controller: every query filters by its identifier, composite foreign keys prevent mixing data across accounts, row-level security only lets it read its own data and only the server writes.
  • Minimisation: no emails or phone numbers; the name and photo are not sent to the artificial intelligence to assess fit; automatic daily deletion according to Annex I; individual deletion and exclusion.
  • The LinkedIn session cookie never leaves the Controller's browser; the extension's credentials are short-lived and revocable.
  • Product analytics and server logs without data subjects' data; the Sales section is excluded from session recording and automatic click capture.
  • Access to production limited to authorised staff, on a least-privilege basis; daily usage caps and request limits against abuse.
  • Sub-processors under data processing agreements and transfer safeguards; data hosted in the European Union (Ireland).

Annex III. Sub-processors

  • Supabase, Inc.. Location: United States; servers in Ireland. Service: database. Data: all data in Annex I. Transfer safeguard: standard contractual clauses.
  • Vercel Inc.. Location: United States; functions in Dublin (Ireland). Service: running the app. Data: all, in transit. Transfer safeguard: EU-U.S. Data Privacy Framework.
  • OpenAI, OpCo, LLC. Location: United States. Service: fit assessment (also in the preview when defining the ideal customer), class of comments, invitation notes and replies, detection of agreed meetings and drafting fallback. Data: headline, job title, company and location, without name or photo, for fit; comment or invitation note text and post excerpt for its class; recent messages of the conversation (transitorily) to classify the reply and detect agreed meetings; in the drafting fallback, the same data as Anthropic. Transfer safeguard: standard contractual clauses.
  • Anthropic, PBC. Location: United States. Service: drafting message and reply suggestions. Data: name, headline, fit reason, interaction type, comment text and excerpt of the Controller's post; to suggest a reply, recent messages of the conversation (transitorily). Transfer safeguard: standard contractual clauses.

Upstash (request limits and task coordination) and PostHog (product analytics) receive no data subjects' data and are therefore not listed in this Annex.