Data Processing Agreement
Last updated: 29 July 2026
This Data Processing Agreement ("DPA") forms part of, and is incorporated by reference into, the Privytics Terms of Service (the "Agreement") between the customer identified in the Agreement (the "Customer") and Sergi Arguimbau Guarinos (NIF ES43221590J), a sole trader (autónomo) established in Spain with registered address at Carrer Isaac Newton, Edifici Disset, 3a planta, D-1, Parc Bit, 07120 Palma de Mallorca, Spain ("Privytics"). Where the Agreement and this DPA conflict on the subject matter of the Processing of Personal Data, this DPA prevails.
This DPA reflects the parties' agreement on the terms governing the Processing of Personal Data under the Agreement in accordance with the requirements of applicable data protection law, including Article 28 of Regulation (EU) 2016/679 (the "GDPR").
Privytics operates an independent, managed, EU-hosted product-analytics service at privytics.com, built on the open-source OpenPanel analytics engine (AGPL-3.0). Privytics is not affiliated with, endorsed by, or sponsored by OpenPanel.
1. Roles of the Parties
1.1. This DPA governs the Processing by Privytics of Personal Data relating to the Customer's own end-users that is collected, transmitted, or otherwise made available to the Privytics service by or on behalf of the Customer (the "Customer Personal Data").
1.2. With respect to Customer Personal Data, the Customer acts as the Controller and Privytics acts as the Processor. Where the Customer is itself acting as a processor on behalf of a third-party controller, the Customer warrants that it is authorised to instruct Privytics as a sub-processor and that its instructions and obligations under this DPA are consistent with those of the relevant controller.
1.3. This DPA does not apply to Personal Data for which Privytics acts as an independent controller, including Personal Data relating to visitors to privytics.com and Personal Data relating to the Customer's own account, billing, and support interactions. Privytics' Processing of that data as a controller is described in the Privytics Privacy Policy.
2. Definitions
Capitalised terms not defined in this DPA have the meaning given to them in the Agreement or the GDPR. In this DPA:
- "Applicable Data Protection Law" means all laws and regulations applicable to the Processing of Personal Data under the Agreement, including the GDPR, the GDPR as retained in the law of the United Kingdom, and any implementing or supplementing national laws.
- "Controller" means the natural or legal person which, alone or jointly with others, determines the purposes and means of the Processing of Personal Data.
- "Processor" means the natural or legal person which Processes Personal Data on behalf of the Controller.
- "Personal Data" means any information relating to an identified or identifiable natural person that is Processed by Privytics on behalf of the Customer under the Agreement.
- "Processing" (and "Process") means any operation performed on Personal Data, whether or not by automated means, such as collection, recording, storage, use, disclosure, or erasure.
- "Data Subject" means the identified or identifiable natural person to whom Personal Data relates.
- "Sub-processor" means any third party engaged by Privytics to Process Customer Personal Data.
- "Personal Data Breach" means a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, Customer Personal Data.
- "Standard Contractual Clauses" or "SCCs" means the standard contractual clauses for the transfer of personal data to third countries adopted by the European Commission under Implementing Decision (EU) 2021/914, and, where relevant, the UK International Data Transfer Addendum.
- "EEA" means the European Economic Area.
- "Supervisory Authority" means an independent public authority established under the GDPR.
3. Subject Matter and Details of Processing
3.1. The subject matter, duration, nature and purpose of the Processing, the categories of Data Subjects, and the categories of Personal Data are set out in Annex I and are incorporated into this DPA by reference.
3.2. Privytics shall Process Customer Personal Data only for the purpose of providing and supporting the service under the Agreement and in accordance with the Customer's documented instructions.
4. Processor Obligations
Privytics shall comply with the obligations of a processor under Article 28(3) of the GDPR. In particular, Privytics shall:
4.1. Documented Instructions
(a) Process Customer Personal Data only on the documented instructions of the Customer, including with regard to transfers of Personal Data to a third country, unless required to do otherwise by EU or Member State law to which Privytics is subject; in that case Privytics shall inform the Customer of that legal requirement before Processing, unless the law prohibits such information on important grounds of public interest.
(b) Treat the Agreement, this DPA (including its Annexes), and the ordinary use and configuration of the service by the Customer as the Customer's complete and final documented instructions. Additional or alternative instructions must be agreed in writing.
(c) Inform the Customer without undue delay if, in Privytics' opinion, an instruction infringes Applicable Data Protection Law. Privytics is not obliged to carry out a legal review of the lawfulness of the Customer's instructions.
4.2. Confidentiality
Privytics shall ensure that persons authorised to Process Customer Personal Data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality, and that access is limited to personnel who need it to perform the Agreement.
4.3. Security
Privytics shall implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk, in accordance with Article 32 of the GDPR. A description of those measures is set out in Annex II. The Customer acknowledges that security measures are subject to technical progress and that Privytics may update them provided that the updates do not materially reduce the overall level of security.
4.4. Sub-processing
(a) The Customer grants Privytics a general authorisation to engage Sub-processors to Process Customer Personal Data. The Sub-processors engaged as at the date of this DPA are listed in Annex III.
(b) Where Privytics engages a Sub-processor, it shall impose on that Sub-processor, by way of a written contract, data protection obligations that are no less protective than those set out in this DPA, in particular providing sufficient guarantees to implement appropriate technical and organisational measures in accordance with Article 28(4) of the GDPR ("back-to-back terms").
(c) Privytics shall give the Customer advance notice of any intended addition or replacement of a Sub-processor, giving the Customer the opportunity to object on reasonable, data-protection-related grounds within fourteen (14) days of the notice. Notice may be given by email or by updating a subscribable Sub-processor page. If the Customer objects and the parties cannot reach a resolution, the Customer may, as its sole remedy, terminate the affected part of the service by written notice.
(d) Privytics remains fully liable to the Customer for the performance of each Sub-processor's data protection obligations.
4.5. Assistance to the Controller
Taking into account the nature of the Processing and the information available to Privytics, Privytics shall:
(a) assist the Customer, by appropriate technical and organisational measures and insofar as possible, in fulfilling the Customer's obligation to respond to requests from Data Subjects exercising their rights under Chapter III of the GDPR (access, rectification, erasure, restriction, portability, and objection). Where a Data Subject request is made directly to Privytics, Privytics shall, unless legally prohibited, promptly notify the Customer and shall not respond to the request itself except on the Customer's documented instructions; and
(b) assist the Customer in ensuring compliance with its obligations under Articles 32 to 36 of the GDPR (security of Processing, breach notification to the Supervisory Authority and to Data Subjects, data protection impact assessments, and prior consultation), taking into account the nature of Processing and the information available to Privytics.
4.6. Personal Data Breach Notification
(a) Privytics shall notify the Customer without undue delay after becoming aware of a Personal Data Breach affecting Customer Personal Data.
(b) The notification shall, to the extent known and as it becomes available, describe: the nature of the breach, including where possible the categories and approximate number of Data Subjects and records concerned; the likely consequences of the breach; the measures taken or proposed to address it and to mitigate its adverse effects; and the name and contact details of a single point of contact from whom more information can be obtained.
(c) Privytics' notification is not an acknowledgement of fault or liability. The Customer is responsible for any notifications it is required to make to a Supervisory Authority or to affected Data Subjects.
4.7. Deletion or Return of Personal Data
At the Customer's choice, Privytics shall delete or return all Customer Personal Data after the end of the provision of the service, and delete existing copies, unless EU or Member State law requires storage of the Personal Data. Privytics shall make Customer Personal Data available for export for a period of thirty (30) days following termination or expiry of the Agreement (the "export window"), after which Privytics shall delete the data within a reasonable period, save for data retained in routine encrypted backups which shall be deleted in accordance with Privytics' backup rotation cycle.
4.8. Audits and Information
(a) Privytics shall make available to the Customer all information necessary to demonstrate compliance with the obligations set out in Article 28 of the GDPR and this DPA.
(b) Privytics shall allow for and contribute to audits, including inspections, conducted by the Customer or an auditor mandated by the Customer. To satisfy audit requests, Privytics may first make available relevant documentation, such as security summaries, subprocessor lists, and third-party certifications or reports where available. Where such documentation is insufficient to demonstrate compliance, the Customer may, on reasonable prior written notice of at least thirty (30) days, no more than once per calendar year (unless required by a Supervisory Authority or following a Personal Data Breach), conduct an inspection during normal business hours, subject to confidentiality obligations and in a manner that does not compromise the security or availability of the service or the data of other customers.
5. International Transfers
5.1. Privytics stores analytics event data on infrastructure located in the EU (Germany). Certain operational Sub-processors listed in Annex III are established outside the EEA. Privytics does not represent that no Customer Personal Data is ever Processed outside the EEA.
5.2. For any transfer of Customer Personal Data to a Sub-processor located outside the EEA in a country that is not the subject of an adequacy decision, the parties rely on the Standard Contractual Clauses, which are incorporated by reference and completed with the details set out in this DPA and its Annexes. Where required, the parties shall carry out a transfer impact assessment and implement any necessary supplementary measures.
5.3. The Customer mandates and authorises Privytics to conclude the Standard Contractual Clauses (and any relevant transfer mechanism) with such Sub-processors in the name of and on behalf of the Customer. Privytics shall make available, on request, information about the transfer mechanisms in place.
6. Liability, Precedence, Term, and Governing Law
6.1. Precedence. In the event of a conflict between this DPA and the Agreement, this DPA prevails with respect to the Processing of Customer Personal Data. In the event of a conflict between this DPA and the Standard Contractual Clauses, the Standard Contractual Clauses prevail.
6.2. Liability. Each party's liability arising out of or related to this DPA is subject to the limitations and exclusions of liability set out in the Agreement. Any reference to the liability of a party means the aggregate liability of that party under the Agreement and this DPA together.
6.3. Term and Termination. This DPA takes effect on the date the Agreement becomes effective and remains in force for as long as Privytics Processes Customer Personal Data on behalf of the Customer. The obligations in Sections 4.7 and 4.8 survive termination.
6.4. Governing Law. This DPA is governed by the laws of Spain, without prejudice to the mandatory data protection laws applicable to the Processing, and to any governing law specified within the Standard Contractual Clauses.
Annex I — Details of the Processing
Subject matter. The provision of the Privytics managed product-analytics service to the Customer under the Agreement, including ingestion, storage, aggregation, and presentation of analytics data.
Duration of the Processing. For the term of the Agreement, plus the export and deletion periods described in Section 4.7.
Nature and purpose of the Processing. Collection and receipt of analytics events transmitted by the Customer's applications or websites via the Privytics SDKs and ingestion endpoint (api.privytics.com); computation of anonymous, daily-rotating device identifiers; storage of event and, where enabled, session-replay data; aggregation and querying to produce analytics dashboards, reports, and insights presented in the Privytics app (app.privytics.com); and related support.
Categories of Data Subjects. The end-users of the Customer's websites, applications, or products whose interactions are measured by the Privytics service.
Categories of Personal Data.
| Category | Description |
|---|---|
| Derived device identifier | A daily-rotating, salted hash of IP address, user agent, and project id. The salt rotates at midnight UTC, so identifiers reset daily. Privytics does not store raw IP addresses as part of anonymous analytics beyond the transient Processing needed to compute the hash. |
| Technical / device data | User agent string and information derived from it (e.g., browser, operating system, device type), and coarse geolocation derived from IP address (e.g., country/region). |
| Usage / event data | Page views, custom events, event properties, referrer, and page/screen paths transmitted by the Customer's applications. |
| Customer-supplied identifiers and traits | A user id and optional traits (such as name and email) sent by the Customer via the identify() method. This is Personal Data determined and controlled by the Customer. |
| Session-replay recordings (optional) | Where session replay is enabled by the Customer for a project, rrweb-based recordings of user interactions. All text and input fields are masked by default. |
Special categories of Personal Data. None are intended or required. The Customer must not transmit special-category data (Article 9 GDPR) to the service except where it has a lawful basis and has configured masking and consent appropriately.
Frequency of the Processing. Continuous, for the duration of the Agreement.
Annex II — Technical and Organisational Measures
Privytics implements and maintains the following technical and organisational measures pursuant to Article 32 of the GDPR:
- Encryption in transit. All data transmitted to and from the service is protected using TLS.
- Encryption at rest. Stored analytics data and backups are encrypted at rest.
- Access control and least privilege. Access to production systems and Customer Personal Data is restricted to authorised personnel on a need-to-know basis, subject to authentication and role-based authorisation.
- Tenant isolation. Customer data is logically segregated by project and organisation so that one customer cannot access another customer's data.
- Pseudonymisation. Anonymous analytics rely on daily-rotating, salted hashes of IP address, user agent, and project id rather than persistent identifiers, minimising and pseudonymising the Personal Data Processed.
- Data-store hardening. The analytics data store (ClickHouse) is network-isolated and not directly exposed to the public internet.
- Network controls. Firewalling, restricted network ingress, and bot-protection controls (including Cloudflare Turnstile) protect the ingestion and application layers.
- Backups and restore. Regular encrypted, off-site backups are taken, with restore procedures tested periodically.
- Logging and monitoring. Application error monitoring and uptime monitoring are in place to detect and respond to anomalies and incidents.
- Breach response. Documented procedures for detecting, investigating, escalating, and notifying Personal Data Breaches, including a single point of contact.
- Vendor management. Sub-processors are assessed for data protection and security, and bound by written contracts with appropriate safeguards, including the Standard Contractual Clauses where relevant.
- Consent gating. The service provides built-in consent gating (initialising with
disabled: trueand starting collection only afterready()), enabling the Customer to withhold Processing until a lawful basis is established.
Annex III — Approved Sub-processors
The following Sub-processors are engaged by Privytics to Process Customer Personal Data. For each Sub-processor located outside the EEA, transfers are covered by the Standard Contractual Clauses.
| Sub-processor | Purpose | Location |
|---|---|---|
| EU data-centre provider | Hosting of analytics event data and encrypted backups | Germany / EU |
| Neon Inc. | Managed PostgreSQL for account, organisation, and project data | Germany / EU (AWS eu-central-1); United States company |
| Polar Software Inc. | Payments and merchant of record (uses Stripe as its processor) | United States |
| Resend | Transactional email delivery | United States (AWS us-east-1) |
| Sentry | Application error monitoring | United States or EU region |
| Better Stack | Uptime monitoring and status page | EU / United States |
| Cloudflare | Website and dashboard hosting, delivery of the op1.js tracking script, bot protection (Turnstile), and R2 backup storage | United States / global |
Privytics will update this Annex and notify the Customer in advance of any intended change in accordance with Section 4.4.
Contact
For any questions about this DPA or to exercise rights and obligations under it, contact Privytics at hello@privytics.com.
This document is provided for general information and should be reviewed by qualified legal counsel for the applicable jurisdiction before being relied upon.