Data Processing Agreement

Draft. Applies from the public launch of EverHook. Version 2026-11-16.

This Data Processing Agreement ("DPA") forms part of the EverHook Terms of Service and governs the processing of personal data that EverHook carries for the Customer. It implements Article 28(3) of Regulation (EU) 2016/679 ("GDPR").

1. Parties, roles and scope

1.1 Parties. "Processor" means Goran Nikolic, a natural person residing in Novi Sad, Serbia, who operates EverHook. Contact: privacy@everhook.dev. "Customer" means the entity that holds an EverHook Account and accepts the Terms of Service.

1.2 Roles. For Customer Personal Data the Customer is the controller and the Processor is its processor. The Customer is also the controller for data already delivered to its Destinations, for the WooCommerce plugin's local fallback queue on the Customer's own server, and for data held by the sending platform.

1.3 Out of scope. The Processor is an independent controller for Account-holder data: users' email addresses, login and Google sign-in data, invitations, billing records and audit trails. The EverHook Privacy Policy governs that data, not this DPA.

1.4 Definitions. Terms defined in the GDPR have the same meaning here.

2. Processor obligations

2.1 Documented instructions. The Processor processes Customer Personal Data only to receive, store, deliver, retry, replay and display the Customer's webhooks, as configured by the Customer in its Account. The Terms of Service, this DPA and the Customer's configuration are the Customer's complete instructions. The Processor informs the Customer if it believes an instruction breaches the GDPR.

2.2 Payload opacity. The Processor treats payloads as opaque bytes. It does not parse, index, profile or analyse them, does not use them to train or prompt any AI or machine-learning model, and routes, filters and de-duplicates on headers only. Exactly three functions read payload content, each listed in Annex II, section 2.

2.3 Confidentiality. Every person authorised to process Customer Personal Data is bound by a confidentiality obligation.

2.4 Support access. EverHook support staff see delivery metadata only: status codes, timings, attempt counts and error classes. They may read payload content only inside an elevation window that the Account Owner grants from the dashboard (default 4 hours, maximum 24 hours, revocable at any time). Support cannot grant or extend a window itself. The grant, every access inside it, and its expiry or revocation are written to the Account's audit log, which the Customer can read.

2.5 Security. The Processor implements the technical and organisational measures in Annex II and may update them, provided the overall level of protection does not decrease.

2.6 Assistance. Taking into account the nature of the processing, the Processor assists the Customer with data subject requests (section 4), security, breach notification, data protection impact assessments and prior consultation under Articles 32 to 36 GDPR.

2.7 Personal data breach. The Processor notifies the Customer without undue delay, and in any case within 48 hours, after becoming aware of a personal data breach affecting Customer Personal Data. The notice describes the nature of the breach, the categories and approximate number of records concerned, the likely consequences and the measures taken or proposed. The Processor sends it to the Account Owner's email address and updates it as facts become available.

3. Sub-processors and transfers

3.1 General authorisation. The Customer authorises the Sub-processors in Annex III. Each is bound by written terms that give at least the protection of this DPA. The Processor remains liable for their performance.

3.2 Changes. The Processor gives at least 30 days' notice of a new or replaced Sub-processor by email to the Account Owner and on the sub-processor page. The Customer may object on reasonable data protection grounds within that period. If the parties cannot resolve the objection, the Customer may terminate the affected service and receive a pro-rata refund of prepaid fees.

3.3 Location. Customer Personal Data (payloads, delivery logs, dead letters and backups) is stored in the European Union only: Hetzner data centres in Falkenstein and Nuremberg, Germany. The service is operated from Serbia: the Processor accesses those servers remotely from Serbia to run and support the service. Serbia has no EU adequacy decision, so that access is a transfer under Chapter V GDPR, covered by section 8.

3.4 Paddle. Paddle.com Market Limited (United Kingdom) is engaged only once paid plans are introduced; during the free beta no payment data is collected. It receives payment and tax data only, never payload content. Paddle acts as Merchant of Record: it sells to the Customer as principal and is an independent controller for that transaction. Transfers to it rely on the UK adequacy decision, with standard contractual clauses as fallback.

4. Data subject requests and erasure

4.1 Self-service. The Customer answers data subject requests through the Account's Privacy section or the API: export (export:read scope) and erasure (privacy:erase scope). The Processor forwards to the Customer any request it receives directly and does not answer it itself.

4.2 Erasure. Erasure is two-phase. A preview returns the number of matching events before anything is destroyed, then a commit starts a job. Matching is exact-string and case-insensitive, over identifiers of at least 6 characters. The job completes within 7 days and nulls the payload, the order reference and the Destination response snippet in every copy the Processor holds, across the full Retention Window. An erased dead letter can no longer be replayed.

4.3 In-flight copies. The Processor also cancels copies of erased events still queued for delivery in its own message broker. They are acknowledged without being delivered.

4.4 Boundary. The Processor does not reach data already delivered to the Customer's Destinations, the WooCommerce plugin's local fallback queue on the Customer's server, or the sending platform. The Customer is the controller for all three and erases there itself.

4.5 Export. An export contains the Account's configuration and event metadata for the Retention Window, as JSON or CSV, through a time-limited signed link. It does not contain payload content or secrets; the export names both as present but withheld.

5. Retention, deletion and backups

5.1 Retention. Customer Personal Data is deleted automatically at the end of the Retention Window in Annex I, section 6.

5.2 Account closure. When the Customer closes its Account, a 30-day grace period starts, during which closure can be reversed. Ingestion stops immediately; deliveries already in flight complete. At the end of the grace period all Customer Personal Data is hard-deleted. The Customer should request an export before closing.

5.3 Backups. Backups are not rewritten. They persist erased or deleted data for at most 30 days, after which it is gone. Every erasure request is recorded and re-applied automatically after any restore from a backup older than the request.

6. Audits

6.1 Information. On request, the Processor makes available the information necessary to demonstrate compliance with Article 28 GDPR, including this DPA, Annex II and the certifications of its Sub-processors (Hetzner Online GmbH holds ISO/IEC 27001).

6.2 Audits. The Customer may audit the Processor once a year, on 30 days' written notice, during business hours, through an independent auditor bound by confidentiality, at the Customer's cost. A supervisory authority may audit at any time. Answers to a security questionnaire satisfy this right where they are sufficient.

7. Liability, term and precedence

7.1 Liability. Each party's liability under this DPA is subject to the limitations in the Terms of Service, except where the GDPR does not permit a limitation.

7.2 Term. This DPA lasts as long as the Processor processes Customer Personal Data.

7.3 Precedence. If this DPA conflicts with the Terms of Service on the processing of personal data, this DPA prevails.

7.4 Governing law. This DPA is governed by the law of the Republic of Serbia, and the courts of Novi Sad have jurisdiction, except where section 8 and the Standard Contractual Clauses provide otherwise.

8. Standard Contractual Clauses

8.1 Incorporation. The standard contractual clauses annexed to Commission Implementing Decision (EU) 2021/914, Module Two (controller to processor) (the "SCCs"), are incorporated into this DPA by reference, unchanged. The Customer is the data exporter and the Processor is the data importer. By accepting the Terms of Service the parties enter into the SCCs.

8.2 Options.

8.3 Annexes of the SCCs.

8.4 Onward transfers. Every Sub-processor in Annex III that processes Customer Personal Data does so in the European Union. Clauses 8.7 and 9 of the SCCs govern any onward transfer.

8.5 Precedence. If this DPA or the Terms of Service conflict with the SCCs, the SCCs prevail.

Annex I: Description of processing

  1. Subject matter and purpose: receiving webhooks from the Customer's e-commerce platforms, durably queuing them, delivering them with retries to the Customer's Destinations, and keeping a delivery log, dead-letter queue and replay facility.
  2. Nature: storage, transmission, retry, replay, display in a redacted view, export of metadata, erasure. No profiling, no automated decision-making, no AI processing.
  3. Data subjects: the Customer's end customers and other persons whose data appears in order, customer, fulfilment or similar events the Customer chooses to route through the service.
  4. Categories of personal data: whatever the sending platform puts in the webhook body, typically name, email address, phone number, postal address, order contents and platform customer id. The Processor does not inspect the payload and cannot exclude other categories; the Customer should not route special-category data (Article 9 GDPR) through the service.
  5. Duration: for the term of the Terms of Service, subject to the Retention Window.
  6. Retention Window:
DataWhere it livesRetained
Webhook events (payload, order reference)Event log60 days, then dropped daily
Delivery attempts (Destination response snippet)Attempt log60 days, then dropped daily
Dead letters (payload of failed deliveries)Dead-letter store90 days, then dropped daily
Messages in deliveryMessage brokerAt most 72 hours
Events held while the Account is suspended for non-payment or over its unverified capEvent log, not queued for delivery7 days, then discarded
BackupsHetzner Object Storage, Nuremberg30 days
Rejected ingest requests (source IP, no body)Rejection log30 days

Audit logs and usage records contain no consumer personal data and no payload content; they are kept 7 years for legal and tax purposes.

Annex II: Technical and organisational measures

1. Hosting and resilience

2. Data minimisation and payload access

3. Encryption

4. Access control

5. Logging and audit

6. Outbound delivery

Annex III: Sub-processors

The current list, with each sub-processor's role, data and location, is on the sub-processor page. It forms part of this DPA.