Skip to content

GDPR · Art. 28

Data processing agreement

This data processing agreement (“DPA”) forms part of the agreement under which Devhook S.r.l. (“Devhook”) provides Devhook Pulse (the “Service”) to its customers. It applies whenever Devhook processes personal data on a customer’s behalf through the Service, as required by Article 28 of Regulation (EU) 2016/679 (“GDPR”).

The customer that holds a workspace is the controller (the “Customer”) and Devhook is its processor. Where this DPA and the agreement conflict on the protection of personal data, this DPA prevails.

Parties

  • Controller: the Customer, as identified by its workspace and billing details.
  • Processor: Devhook S.r.l., registered office Via Andrea Dell'Isola 12, 06083 Bastia Umbra (PG), VAT IT04018180549.Certified email (PEC): [email protected]

1. Subject matter, duration and purpose

Devhook processes personal data only to provide the Service as the Customer configures it: uptime and synthetic monitoring, alert notifications, incident management and public status pages. Processing consists of collecting, storing, organising, transmitting (for example, delivering alerts to the channels the Customer sets up) and deleting data.

Processing lasts for as long as the Customer uses the Service and ends with the deletion described in section 9. Annex A lists the categories of data subjects and of personal data.

2. Documented instructions

Devhook processes personal data only on the Customer’s documented instructions, including with regard to transfers to third countries. This DPA, the agreement and the Customer’s configuration of the Service are those instructions. Devhook departs from them only where EU or Member State law requires it, and then informs the Customer first unless that law forbids it.

Devhook informs the Customer immediately if, in its opinion, an instruction infringes the GDPR or other data protection law.

3. Confidentiality

Devhook ensures that the persons it authorises to process personal data are bound by confidentiality, by contract or by law, and access the data only as far as needed to operate, support and secure the Service.

4. Security of processing

Devhook implements the technical and organisational measures described in Annex B, which take into account the state of the art, the costs of implementation and the risks of the processing, as required by Article 32 GDPR. Devhook may update them as technology evolves, provided the overall level of protection is not reduced.

5. Sub-processors

The Customer gives Devhook general written authorisation to engage the sub-processors listed in Annex C. Devhook informs the Customer in advance of any intended addition or replacement of a sub-processor, giving the Customer the opportunity to object. If an objection cannot be resolved, the Customer may terminate the affected Service.

Devhook imposes on every sub-processor, by contract, data protection obligations equivalent to those of this DPA, and remains fully liable to the Customer for their performance.

6. Transfers outside the EEA

The Service is hosted in the European Economic Area (EEA). Personal data is transferred outside the EEA, by Devhook or by a sub-processor, only under the conditions of Chapter V GDPR, for example on the basis of an adequacy decision or of the standard contractual clauses adopted by the European Commission.

7. Assistance to the Customer

Taking into account the nature of the processing, Devhook assists the Customer with appropriate technical and organisational measures in responding to requests from data subjects exercising their rights under Chapter III GDPR, and forwards to the Customer any such request it receives directly.

Devhook also assists the Customer, with the information available to it, in ensuring compliance with Articles 32 to 36 GDPR: security of processing, notification of personal data breaches, data protection impact assessments and prior consultation.

8. Personal data breaches

Devhook notifies the Customer without undue delay after becoming aware of a personal data breach affecting the Customer’s personal data. The notification gives, as far as known at the time, the information listed in Article 33(3) GDPR, and is supplemented as further information becomes available. Devhook takes reasonable measures to contain the breach and to mitigate its possible adverse effects.

9. Deletion and return

Data the Customer deletes in the Service is removed from the live database. Check results and audit entries are deleted automatically when the retention period of the Customer’s plan expires.

The Customer can export all the data of its workspace at any time, as a machine-readable JSON archive with a SHA-256 checksum, from the workspace settings (Settings → Data & privacy); the archive can be downloaded for 24 hours. The workspace owner can delete the workspace there too, once an export has been downloaded: the workspace is frozen at once (no checks, alerts or public status pages, every API key revoked) and deleted with all the personal data it contains 14 days later, unless the owner cancels before. A record of the deletion, with no personal data, is kept as evidence.

When the Service ends, or earlier on the Customer’s written request, Devhook deletes the Customer’s workspace and the personal data it contains, unless EU or Member State law requires their storage. On the Customer’s request, Devhook first returns the data in a commonly used, machine-readable format. Encrypted backups expire on their own schedule (Annex B).

Copies held in the encrypted backups are erased as the backups rotate out, within 6 months.

10. Information and audits

Devhook makes available to the Customer all information necessary to demonstrate compliance with Article 28 GDPR, and allows for and contributes to audits, including inspections, conducted by the Customer or by an auditor it mandates. Audits are agreed with reasonable notice, are carried out so as neither to disrupt the Service nor to compromise the security of other customers’ data, and are subject to confidentiality.

11. Final provisions

This DPA remains in force for as long as Devhook processes personal data on the Customer’s behalf. It is governed by the law that governs the agreement, and disputes fall under the jurisdiction agreed there. Notices under this DPA are given in writing, to Devhook at its registered office or certified email (PEC).

Annex A · Details of the processing

Categories of data subjects

  • The Customer’s users and the members it invites to its workspace.
  • Recipients of the alert notifications the Customer configures.
  • The Customer’s billing contacts.
  • Individuals whose personal data appears in content the Customer monitors or enters in the Service, such as monitored URLs, check responses and incident notes.

Categories of personal data

  • Account data: name, email address, Google account identifier, password hash.
  • Workspace data: roles, invitations and an audit trail of administrative actions, in which the client IP address is stored only as a keyed hash.
  • Configuration data: alert destinations (email addresses and webhook, Slack, Discord or Telegram endpoints), monitored URLs and custom request headers.
  • Operational data: check results, incidents and incident notes.
  • Billing data: name, billing address, tax identifiers, SDI recipient code and PEC, and subscription status. Payment card data is entered on Stripe and never reaches Devhook.
  • Technical data: IP addresses and request metadata, used for rate limiting and present in service logs.

The Service is not designed to process special categories of personal data (Article 9 GDPR) or data relating to criminal convictions and offences (Article 10 GDPR), and the Customer does not enter them.

Annex B · Technical and organisational measures

Encryption in transit
Every public endpoint is served only over HTTPS, with TLS 1.2 or 1.3, automatically renewed certificates and HTTP Strict Transport Security. Requests reach the Service through Cloudflare’s network, which terminates TLS and forwards them to the Service over HTTPS. Remote probe nodes talk to the central service only over HTTPS, and every message is signed (HMAC-SHA256).
Encryption of stored credentials
Secrets the Customer stores in the Service (alert channel configurations and custom monitor request headers) and authentication secrets are encrypted at the application layer with AES-256-GCM. Each value is bound to its workspace and field, and the encryption key can be rotated.
Password and token hashing
Passwords are stored only as salted scrypt hashes. Password reset tokens, sign-up codes and API keys are stored only as hashes, never in clear text.
Encrypted off-site backups
Every day the database is backed up, encrypted on the server (restic, AES-256) before it leaves it, and copied to separate object storage over HTTPS. Daily, weekly and monthly snapshots rotate out automatically: the oldest is at most 6 months old.
Network isolation
The database and the cache run on an internal network with no published ports and no internet access, and only the reverse proxy accepts connections from the internet. Every service runs in a container with a read-only file system, no Linux capabilities, no privilege escalation and resource limits.
Access control and tenant isolation
Every request is authenticated and authorised by the user’s role in the workspace, and every database query is restricted to the Customer’s workspace. The database enforces the same restriction itself (row-level security): the application’s database role cannot read or change another customer’s rows even if a query omits the restriction, and it is neither a superuser nor the owner of the tables. Session cookies are HttpOnly, Secure and SameSite=Strict, and sign-in, registration and password reset are rate-limited.
Protection of outbound requests
Checks and webhooks to Customer-supplied addresses go through a guard that blocks private, loopback and internal network addresses.
Logging and audit trail
Service logs are structured and redact secrets. Administrative actions in a workspace are recorded in an audit log the Customer can consult.
Secure development
Every change passes automated tests, static security analysis, secret scanning and a dependency vulnerability audit before it is deployed. Deployments are automated, from versioned container images.
Organisational measures
Access to production systems is limited to authorised Devhook personnel bound by confidentiality, on a need-to-know basis.

Annex C · Sub-processors

Devhook engages the following sub-processors. Changes are notified in advance as set out in section 5.

Annex C · Sub-processors
Sub-processorServiceLocation of processing
Hetzner Online GmbHHosting of the Service: servers, database and monitoring probesGermany and Finland (Falkenstein, Nuremberg, Helsinki)
Cloudflare, Inc.Network edge: TLS termination, protection against attacks and forwarding of requests to the ServiceUnited StatesOutside the EEA: Chapter V GDPR safeguards apply
Stripe Payments Europe, LimitedPayment processing and subscription billingIreland and United StatesOutside the EEA: Chapter V GDPR safeguards apply
Resend, Inc.Delivery of transactional and alert emailsUnited StatesOutside the EEA: Chapter V GDPR safeguards apply
Hetzner Online GmbHStorage of encrypted backupsGermany

Sign-in with Google is offered at the user’s choice: for it, Google acts as an independent controller and is not a sub-processor of Devhook.