Data Processing Agreement

1. Parties, scope and precedence

This Data Processing Agreement (“DPA”) forms part of the Terms of Service between the customer (“Controller”) and Maximilian Barabas, autónomo, NIE Z1807197T, Calle Polca Majorera 1, apartamento 78, Nuevo Horizonte, 35610 Antigua, Las Palmas, Spain, info@maxhoriz.com (“Processor”).

  1. This DPA applies to personal data the Processor processes on the Controller’s behalf when providing the MaxHoriz service, as required by Article 28 of Regulation (EU) 2016/679 (“GDPR”).
  2. It does not apply to data the Processor handles as a controller in its own right (for example account, billing and website data), which the Privacy Policy covers.
  3. The Controller accepts this DPA by accepting the Terms. No separate signature is needed.
  4. If this DPA and the Terms conflict on the protection of personal data, this DPA prevails.

Version 1.0, effective 02.11.2026

2. Definitions

Terms such as “personal data”, “processing”, “controller”, “processor”, “data subject”, “personal data breach” and “supervisory authority” have the meaning given in the GDPR. In addition:

  • Customer Personal Data: personal data the Controller or its users upload to, create in or receive through the service, as described in Annex I.
  • Service: the MaxHoriz lead management, CRM and email outreach software provided under the Terms.
  • Sub-processor: a third party the Processor engages to process Customer Personal Data, listed in Annex III.
  • Data Protection Law: the GDPR, the Spanish Organic Law 3/2018 (LOPDGDD) and any other data protection law that applies to the processing.

3. Roles and the Controller’s instructions

The Controller is the controller of Customer Personal Data and the Processor is its processor.

  1. The Processor processes Customer Personal Data only on the Controller’s documented instructions. These are given by the Terms, this DPA and the Controller’s use and configuration of the Service (for example importing leads, launching campaigns or approving AI-drafted lines).
  2. If EU or Member State law requires other processing, the Processor informs the Controller before processing, unless that law prohibits it.
  3. The Processor tells the Controller without undue delay if it believes an instruction breaks Data Protection Law, and may suspend that instruction until it is confirmed or changed.
  4. The Controller is responsible for the lawfulness of the processing, including having a legal basis for contacting its leads, giving them the information required by Articles 13 and 14 GDPR, and honouring their objections and unsubscribe requests.
  5. The Controller must not upload special categories of personal data (Article 9 GDPR) or data about criminal convictions (Article 10 GDPR).

4. Obligations of the Processor

The Processor meets the obligations of Article 28(3) GDPR as follows.

  1. Confidentiality. Everyone the Processor authorises to process Customer Personal Data is bound by confidentiality, by contract or by law.
  2. Security. The Processor implements the technical and organisational measures in Annex II, appropriate to the risk under Article 32 GDPR. It may update them as long as the overall level of protection does not decrease.
  3. Purpose limitation. The Processor does not use Customer Personal Data for its own purposes, does not sell it, and does not use it to train AI models.
  4. Isolation. Each Controller’s data is separated from other customers’ data at database level.
  5. Staff and operator access. The Processor accesses Customer Personal Data only where needed to run, support or secure the Service, or at the Controller’s request.

5. Sub-processors

The Controller gives general written authorisation to use the Sub-processors listed in Annex III.

  1. The Processor announces any new or replaced Sub-processor by email to the account owner at least 30 days in advance, and updates Annex III.
  2. The Controller may object on reasonable data-protection grounds within that period. If no solution is found, the Controller may terminate the affected part of the Service, and the Processor refunds any prepaid fees for the remaining term.
  3. Each Sub-processor is bound by written data-protection terms at least as protective as this DPA.
  4. The Processor remains responsible to the Controller for its Sub-processors’ performance of those obligations.
  5. The Controller’s own mailbox provider, connected to the Service to send and receive the Controller’s emails, is chosen by the Controller and is not a Sub-processor.

6. International transfers

Customer Personal Data is stored in the EU: the database in Ireland and the application in Dublin.

  1. Where a Sub-processor processes Customer Personal Data outside the European Economic Area, the transfer relies on an adequacy decision, including the EU–US Data Privacy Framework where the recipient is certified, or on the European Commission’s Standard Contractual Clauses (Decision (EU) 2021/914), with supplementary measures where needed.
  2. For AI processing, only the data listed for Anthropic in Annex III leaves the EEA. Lead names and email addresses are not sent to the AI provider.
  3. On request, the Processor tells the Controller which transfer mechanism applies to each Sub-processor.

7. Personal data breaches

The Processor notifies the Controller without undue delay, and in any case within 48 hours of becoming aware of a personal data breach affecting Customer Personal Data.

  1. The notice goes to the account owner’s email address and includes, as far as known at the time: the nature of the breach, the categories and approximate number of data subjects and records concerned, the likely consequences, and the measures taken or proposed.
  2. Information not available at first is provided in stages, without further undue delay.
  3. The Processor takes reasonable steps to contain the breach and limit its effects, and keeps a record of every breach.
  4. The Controller remains responsible for notifying the supervisory authority and data subjects under Articles 33 and 34 GDPR. The Processor supports it with the information it holds.
  5. Notifying a breach is not an admission of fault or liability.

8. Assistance, audits and records

Data subject requests. The Service lets the Controller view, export, correct and delete leads and stop contacting them. Beyond that, the Processor helps the Controller, as far as possible, to answer requests for access, rectification, erasure, restriction, portability and objection.

  • Requests the Processor receives directly from a data subject are forwarded to the Controller within 3 working days. The Processor does not answer them itself unless the Controller instructs it to.

Other assistance. The Processor helps the Controller, taking into account the information available to it, with security under Article 32, breach notifications under Articles 33–34, data protection impact assessments and prior consultations under Articles 35–36 GDPR. Assistance beyond the normal Service may be charged at reasonable cost.

Audits.

  1. The Processor makes available, on request, the information needed to show compliance with this DPA and Article 28 GDPR.
  2. The Controller, or an independent auditor bound by confidentiality, may audit once a year at its own cost, with 30 days’ written notice, during business hours, and without access to other customers’ data or to the Processor’s or Sub-processors’ security secrets.
  3. Further audits are allowed after a personal data breach affecting the Controller or when a supervisory authority requires one.
  4. For Sub-processors, the Processor may meet audit requests with their current third-party certifications or audit reports.

Records. The Processor keeps a record of processing activities carried out on behalf of controllers, as required by Article 30(2) GDPR.

9. Return and deletion, term, liability and law

Return and deletion.

  1. The Controller can export its data at any time during the term.
  2. Within 30 days after the Service ends, the Processor deletes all Customer Personal Data, including the Controller’s users’ accounts, unless EU or Member State law requires it to be kept. The Processor confirms the deletion in writing on request.
  3. Backups containing Customer Personal Data are deleted or overwritten within a further 30 days. If a backup has to be restored in that period, the Processor repeats every recorded deletion before the restored data is used again.
  4. The Controller can ask for earlier deletion of its account and data at info@maxhoriz.com.

Term. This DPA applies for as long as the Processor processes Customer Personal Data for the Controller, and its deletion and confidentiality obligations survive the end of the Terms.

Liability. Each party’s liability under this DPA is subject to the limitations in the Terms, except where Data Protection Law does not allow limitation. Article 82 GDPR governs liability towards data subjects.

Changes. The Processor may update this DPA to reflect changes in law, in the Service or in Sub-processors, with at least 30 days’ notice by email. Changes do not reduce the protection of Customer Personal Data.

Law and courts. This DPA is governed by Spanish law. The courts of Las Palmas de Gran Canaria have jurisdiction, without affecting data subjects’ rights or the competence of the Spanish Data Protection Agency (AEPD) or any other supervisory authority.

Annex I – Description of processing

ItemDescription
Subject matterProviding the MaxHoriz Service under the Terms
DurationThe term of the Terms, plus the deletion periods in section 9
Nature and purposeStoring and organising lead data; sending emails from the Controller’s own mailbox; reading and matching replies, bounces and unsubscribes; researching leads’ public company websites and drafting email lines with AI; reporting
Data subjectsThe Controller’s leads and business contacts; the Controller’s users
Categories of dataNames, business email addresses, phone numbers, company names and websites, notes, email content, delivery and unsubscribe status, facts quoted from public company websites, AI-generated text; for users: name, email address, login and usage data
Special categoriesNone. The Controller must not upload them
FrequencyContinuous, while the Controller uses the Service

Annex II – Technical and organisational measures

AreaMeasures
EncryptionTLS for all connections; mailbox credentials encrypted at rest with AES-256-GCM, with the key held outside the database
Tenant isolationEach customer’s data separated at database level with row-level security
Access controlLeast-privilege access for the operator; secrets kept out of source code; credentials never shown in the browser or in logs
HostingDatabase and application hosted in the EU (Ireland)
Error reportsEmail addresses and tokens removed before error events leave the application
Abuse protectionRate limiting on public endpoints; bot protection on sign-in pages
Sending safeguardsEmails sent only from the Controller’s own connected mailbox; automatic hold on sending when reply tracking or the mailbox fails; unsubscribe and bounce handling; per-company sending limits
Change managementProduction changes reviewed, tested in CI and backed up before release; database migrations checked before and verified after
BackupsDatabase backups encrypted on a full-disk-encrypted device with owner-only access, deleted automatically after 30 days
DeletionA documented erasure procedure with a pre-check, a dry run by default and verification afterwards; each erasure recorded so it can be repeated after a backup restore
MonitoringDaily automated health report on scheduled jobs, sending, AI usage and errors; alerts to the operator
Incident responseBreach notification to the Controller within 48 hours (section 7); a record of every incident

Annex III – Sub-processors

Sub-processorServicePersonal dataLocationTransfer mechanism
Supabase Inc.Database, authenticationAll Customer Personal DataEU (Ireland)Stored in the EU
Vercel Inc.Application hostingAll data passing through the applicationEU (Dublin)Stored in the EU
ResendInbound replies, system emailsReply emails, bounce and complaint events, users’ email addressesEU
Anthropic Ireland, LimitedAI website research and email linesCompany website text, extracted facts, company name, the Controller’s offer. Not lead names or email addressesUSASCC in Anthropic’s DPA, part of its Commercial Terms
Functional Software Inc. (Sentry)Error trackingError events with email addresses and tokens removedEU (Germany)Stored in the EU
Cloudflare Inc.Bot protection on sign-in pagesUsers’ browser signals and IP addressGlobal

Providers used without access to Customer Personal Data: cron-job.org (scheduling), healthchecks.io (uptime pings), GitHub (source code) and Telegram (internal operator alerts with no personal data).

Last updated: 02.11.2026