Data Processing Agreement

Last updated: October 19, 2026

This Data Processing Agreement (the "Agreement") is entered into under Article 28 of Regulation (EU) 2016/679 (GDPR) and Article 33 of Spanish Organic Law 3/2018 (LOPDGDD), and forms part of the Pixhook.io Terms of Service. The user accepts it by using the Service.

1. Parties

  • Data controller: the Pixhook.io user who generates tracking pixels, with or without an account (the "Controller").
  • Data processor: Masalia, tax ID (NIF) 50199893R, with address at Calle Ciudad de Toledo 1, 05004 Ávila (Spain), owner of Pixhook.io (the "Processor").

2. Subject matter

The Processor processes, on behalf of the Controller, the personal data collected when a person opens an email, document or page containing one of the Controller's pixels, for the sole purpose of providing the Service described in the Terms.

3. Description of the processing

AspectDetails
NatureCollection, recording, storage, consultation, disclosure to the Controller (dashboard, emails, webhooks and exports) and erasure
PurposeInforming the Controller of opens of their emails or documents and providing the subscribed features
Categories of data subjectsRecipients of the Controller's emails, documents or pages containing the pixel
Types of dataDate and time of the open, IP address, browser and operating system (user agent), device type, approximate country, referring page (referer) and campaign parameters (UTM)
Special categories of dataNone. The Controller must not use the Service to process special categories of data
DurationFor as long as the Controller uses the Service. Each open is kept for the retention period of the Controller's plan (30 days without an account) and then deleted automatically

4. Processor's obligations

The Processor undertakes to:

  1. Process the data only on the documented instructions of the Controller, which are those arising from the Terms and from the Controller's configuration of the Service. If it considers that an instruction infringes the law, it will inform the Controller immediately.
  2. Not use the data for its own purposes or disclose it to third parties, except to the sub-processors in section 6 or where required by law.
  3. Ensure that persons authorized to process the data have committed to confidentiality.
  4. Apply the security measures in the Annex, appropriate to the risk under Article 32 GDPR.
  5. Assist the Controller, as far as reasonable and taking into account the nature of the processing, in responding to data subjects' requests. If a data subject contacts the Processor, it will forward the request to the Controller without undue delay.
  6. Notify the Controller without undue delay and within 48 hours at the latest of becoming aware of any personal data breach affecting their data, with the information available so that the Controller can meet its own notification obligations.
  7. Assist the Controller, where necessary, with data protection impact assessments and prior consultations with the supervisory authority.
  8. Make available to the Controller the information necessary to demonstrate compliance with this Agreement and allow reasonable audits, on request with sufficient notice and at the Controller's expense.
  9. Delete the data at the end of the provision of the Service, in accordance with section 8.

5. Controller's obligations

The Controller undertakes to:

  1. Have a valid legal basis for the processing and, where required by law (ePrivacy Directive, Article 22.2 of the LSSI-CE), the prior consent of recipients.
  2. Inform recipients about the use of tracking pixels in accordance with Articles 13 and 14 GDPR.
  3. Respond to data subjects' rights requests.
  4. Not use the Service with minor recipients or to process special categories of data.
  5. Oversee the processing and its own compliance with the law.

6. Sub-processors

The Controller grants the Processor a general authorization to engage the following sub-processors:

Sub-processorServiceLocation
Nominalia Internet, S.L.U.Hosting of the Service and database, email deliverySpain (EU)
Cloudflare, Inc.Content delivery, security and approximate country detectionUnited States and EU

The Processor imposes on each sub-processor the same data protection obligations it assumes under this Agreement.

If it adds or replaces a sub-processor, it will update this list at least 15 days in advance and notify registered users by email. The Controller may object on reasonable data protection grounds. If no solution is found, the Controller may cancel their subscription and delete their account.

7. International transfers

Cloudflare, Inc. may process data in the United States. The transfer relies on its self-certification under the EU-U.S. Data Privacy Framework and on the Standard Contractual Clauses approved by the European Commission, incorporated in its data processing agreement.

8. End of processing

When the account is deleted, the Processor immediately deletes the data on opens of the Controller's pixels. Beforehand, the Controller may export it from the dashboard according to their plan, or request it by email.

Data from pixels created without an account is deleted automatically after 30 days.

Backups that may contain data are overwritten in their ordinary cycles.

9. Liability

Each party is liable for its own breaches under Article 82 GDPR. If the Processor uses the data for other purposes, discloses it or uses it in breach of this Agreement, it will be considered a controller in respect of that processing. The limitations of liability in the Terms apply to the extent permitted by law.

10. Term and governing law

This Agreement remains in force for as long as the Controller uses the Service and, thereafter, for as long as the Processor holds any of the Controller's data. It is governed by Spanish law and subject to the Courts of Ávila (Spain). In case of discrepancy between language versions, the Spanish version prevails.

Annex. Security measures

  • Encrypted communications over HTTPS/TLS.
  • User passwords hashed with bcrypt.
  • Access to each Controller's data restricted to their account, through authentication with signed tokens.
  • Protection against attacks and abuse through Cloudflare, blocking of internal files and attempt limits.
  • Validation of webhook and redirect URLs, and escaping of data shown in the dashboard.
  • Data minimization: the IP is not sent to external geolocation services. Only the approximate country is recorded, and the IP is masked outside the Controller's dashboard.
  • Automatic deletion of data at the end of the retention period.
  • Administrative access restricted to authorized personnel, with action logging.
  • Regular hosting backups.