Data Processing Agreement
Version 2.0 · Last updated 23 September 2026
This Data Processing Agreement ("DPA") forms part of the Terms of Service between Jara Technologies Ltd ("Tidehawk", the "Processor") and the customer that holds the workspace (the "Customer", the "Controller"). It applies whenever Tidehawk processes personal data on the Customer's behalf in providing the service. It is accepted electronically when the workspace is created; the version accepted and the time of acceptance are recorded against the workspace, and the Customer may download a copy at any time.
Terms defined in the Terms of Service have the same meaning here. "Data Protection Law" means UK GDPR and the Data Protection Act 2018, and, where the Customer is established in the European Economic Area, EU GDPR. "Personal Data", "processing", "data subject", "personal data breach" and "supervisory authority" have the meanings given in Data Protection Law.
1. Roles and scope
1.1 The Customer is the controller, and Tidehawk is the processor, of the Customer Personal Data described in Annex 1. Where the Customer is itself a processor for its own clients, the Customer warrants that it has the authority of the relevant controller to appoint Tidehawk as a sub-processor on these terms, and Tidehawk is a sub-processor.
1.2 Tidehawk is an independent controller of the account, billing and security data described in the Privacy Policy. This DPA does not apply to that data.
1.3 If this DPA conflicts with any other part of the Agreement in relation to Personal Data, this DPA prevails.
2. Duration
This DPA applies for as long as Tidehawk processes Customer Personal Data, which is the term of the Agreement plus the 30-day retention period after it ends and any period needed to complete deletion under section 10.
3. The Customer's instructions
3.1 Tidehawk will process Customer Personal Data only on the Customer's documented instructions, which are: to provide the service as described in the Agreement and the documentation; to act on the settings and actions the Customer's users choose in the service; and any further written instruction the Customer gives that is consistent with the Agreement. Tidehawk will inform the Customer if, in its opinion, an instruction infringes Data Protection Law.
3.2 Tidehawk may process Customer Personal Data where required by a law to which it is subject. In that case it will tell the Customer of the requirement before processing, unless the law prohibits it on important grounds of public interest.
3.3 The Customer warrants that it has a lawful basis for the processing it instructs, that it has provided any notices and obtained any consents Data Protection Law requires, and that it is entitled to monitor every domain it adds to the service, as the Terms require.
4. Confidentiality
Tidehawk will ensure that every person it authorises to process Customer Personal Data is bound by a contractual or statutory duty of confidentiality, has received appropriate training, and has access only to the extent needed for their role.
5. Security
5.1 Tidehawk will implement and maintain the technical and organisational measures described in Annex 2, and will not reduce the overall level of protection they provide during the term of the Agreement.
5.2 Taking into account the state of the art, the costs of implementation and the nature, scope, context and purposes of the processing, those measures are intended to ensure a level of security appropriate to the risk, including protection against unauthorised or unlawful processing and against accidental loss, destruction or damage.
5.3 The Customer is responsible for the security of its own systems and credentials, for the access rights it grants to its users, and for the systems it connects to the service.
6. Sub-processors
6.1 The Customer gives general authorisation for Tidehawk to engage the sub-processors listed in the sub-processor register, which forms Annex 3 of this DPA, for the functions described there.
6.2 Tidehawk will give the Customer at least 30 days' notice by email to the workspace owner before it adds or replaces a sub-processor. The Customer may object in writing within that period on reasonable grounds relating to data protection. If the parties cannot resolve the objection in good faith, the Customer may terminate the Agreement on notice and receive a pro rata refund of any Fees paid in advance for the period after termination. This is the Customer's sole remedy for such an objection.
6.3 Tidehawk will impose on each sub-processor, by written contract, obligations that protect Customer Personal Data to a standard no lower than this DPA, and remains fully liable to the Customer for the sub-processor's performance.
7. Where data is processed
7.1 Tidehawk will store and process Customer Personal Data in the United Kingdom, and will not transfer it outside the United Kingdom except as described in this section and in Annex 3.
7.2 The following transfers are inherent in the service and are authorised by the Customer: sending a domain name, and nothing else, to the public Certificate Transparency sources named in Annex 3 in order to discover certificates; and querying the public RDAP or WHOIS service of the registry responsible for a domain in order to read its expiry date.
7.3 For any transfer of Customer Personal Data to a country outside the United Kingdom that does not benefit from UK adequacy regulations, Tidehawk will ensure an appropriate safeguard under Chapter V of UK GDPR is in place, such as the UK Extension to the EU–US Data Privacy Framework for a certified recipient, or the International Data Transfer Agreement or Addendum issued by the Information Commissioner, and will identify the safeguard relied on in Annex 3.
8. Assistance to the Customer
8.1 Tidehawk will assist the Customer, by appropriate technical and organisational measures and taking into account the nature of the processing, in responding to requests from data subjects to exercise their rights. The service provides the workspace owner with tools to export and erase Personal Data. If Tidehawk receives a request directly from a data subject about Customer Personal Data it will, where lawful, refer the request to the Customer within five working days and will not respond to the data subject other than to confirm the referral.
8.2 Tidehawk will assist the Customer in meeting its obligations under Articles 32 to 36 of UK GDPR, on security, breach notification, data protection impact assessments and prior consultation, taking into account the nature of the processing and the information available to Tidehawk. Assistance that goes materially beyond what the service itself provides may be charged at Tidehawk's then-current reasonable rates, which will be agreed in advance.
9. Personal data breach
9.1 Tidehawk will notify the Customer without undue delay, and in any event within 48 hours, after becoming aware of a personal data breach affecting Customer Personal Data. The notification will be sent to the email address of the workspace owner and will describe, so far as known, the nature of the breach, the categories and approximate number of data subjects and records concerned, the likely consequences, the measures taken or proposed, and a contact point. Information that is not available at first will follow without undue delay as it becomes known.
9.2 Tidehawk will co-operate with the Customer and take reasonable steps to contain, investigate and remedy the breach. Tidehawk's notification is not an admission of fault or liability.
10. Return and deletion
10.1 The Customer may export Customer Personal Data from the service at any time during the Agreement and during the 30 days after it ends.
10.2 At the end of the 30-day period after the Agreement ends, or earlier on the Customer's written instruction, Tidehawk will permanently delete Customer Personal Data from its live systems using a verified erasure process and will provide a signed record of the deletion on request. Data held in backups is deleted by the normal rotation of those backups within 35 days. Tidehawk may retain Personal Data where, and for as long as, a law to which it is subject requires it to, and will continue to protect it under this DPA.
11. Audit and information
11.1 Tidehawk will make available to the Customer the information reasonably necessary to demonstrate compliance with this DPA, including the security page, this DPA and its annexes, the sub-processor register, the results of any independent security assessment Tidehawk has obtained, and answers to a reasonable written security questionnaire not more than once in any twelve months.
11.2 Where that information is not sufficient to demonstrate compliance, the Customer, or an independent auditor it appoints who is bound by confidentiality and is not a competitor of Tidehawk, may audit Tidehawk's compliance with this DPA, not more than once in any twelve months unless required by a supervisory authority or following a personal data breach. The Customer will give at least 30 days' written notice, the audit will take place during working hours and in a way that does not unreasonably disrupt Tidehawk's business or compromise the security or confidentiality of other customers, and each party bears its own costs. Tidehawk will co-operate and provide reasonable assistance.
12. Liability
The limitations and exclusions of liability in the Terms of Service apply to this DPA, except that nothing in this DPA limits either party's liability to a data subject or supervisory authority under Data Protection Law.
13. Changes
Tidehawk may update this DPA to reflect a change in Data Protection Law, a change in the service, or guidance from a supervisory authority, provided the update does not reduce the protection given to Customer Personal Data. Tidehawk will give workspace owners at least 30 days' notice of a material change, and the version in force at any time is recorded against the workspace.
Annex 1: Description of the processing
Subject matter. Monitoring of SSL/TLS certificates and domain registrations across the Customer's clients, alerting on approaching expiry, and creating and updating tickets in the Customer's PSA.
Nature and purpose. Collection of the data the Customer enters; discovery of certificate and domain records from public sources and from the servers behind the Customer's domains; storage; analysis of expiry dates; transmission of alerts by email and to the Customer's PSA; reporting; and deletion at the end of the Agreement. The purpose is to provide the service the Customer has subscribed to.
Duration. The term of the Agreement plus 30 days.
Categories of data subjects. The Customer's employees and contractors who use the service; the Customer's clients' staff whose contact details are entered as alert recipients or are held in the Customer's PSA; individuals who own domains monitored by the Customer, where a domain or registry record identifies a person.
Categories of Personal Data. Names, work email addresses and roles; IP addresses and sign-in records of users; domain names and hostnames; registry contact details where a registry publishes them; the account name attached to PSA credentials; the content of alert emails and PSA tickets, which describe certificates and domains rather than people.
Special category data. None is required by the service, and the Customer must not place any in it.
Annex 2: Technical and organisational measures
Hosting and residency. Application servers, the database and backups run on DigitalOcean in London (LON1). Transactional email is sent from Amazon Web Services in London (eu-west-2).
Encryption. TLS 1.2 or later for every connection, including between the application and the database, with the database's certificate authority pinned. PSA credentials, two-factor secrets and other sensitive values are encrypted at rest with AES-256-GCM using keys held outside the database. Key rotation is supported and recorded.
Tenant separation. Every customer table carries the workspace identifier, and PostgreSQL row-level security is enforced inside the database so that the application role can read only the workspace it is acting for. An automated test suite exercises this separation and must pass before any change is released.
Access control. Users sign in with a password held as a salted hash, with two-factor authentication available to all and enforceable by the workspace owner. Roles limit what each user may do. Tidehawk staff access the administration console with mandatory two-factor authentication; every access to a customer's data by a member of staff is recorded in a hash-chained audit log that cannot be altered without detection, and sensitive operations such as acting as a customer require the approval of a second member of staff.
Least privilege. The application connects to the database with a role that has only the permissions each table requires and cannot alter the schema. Administrative operations use a separate role.
Logging and monitoring. Sign-ins, configuration changes and administrative actions are logged with actor, time and IP address. Security-relevant events are reviewed. Logs are retained for the periods stated in the Privacy Policy.
Change control. Code changes are reviewed and pass automated type checking, linting and test suites, including the tenant-separation suite, before release. Production secrets are generated on the server and never stored in source control.
Backups and resilience. The managed database is backed up daily with point-in-time recovery, held in the same region. Application containers restart automatically on failure and are health-checked.
Incident response. A documented process assigns an owner to each incident, tracks the 72-hour regulatory deadline from the time of awareness, and records the decisions taken and the notifications made.
Deletion. Erasure runs through a verified pipeline that removes data from live systems and produces a signed certificate of erasure. Backups rotate within 35 days.
Personnel. Staff with access to customer data are bound by confidentiality obligations and receive data protection and security training.
Annex 3: Authorised sub-processors
The current list, with each provider's function, the data it receives, its location and the transfer safeguard relied on, is maintained at /subprocessors and is incorporated into this DPA. The register carries its own version number and date, and changes to it are notified under section 6.