Data Processing Agreement
Last updated 12 October 2026
This Data Processing Agreement ("DPA") forms part of the Terms of Service between Pez Solutions Ltd, which runs Updawg ("Updawg", the processor), and the organization that uses Updawg (the "customer", the controller). It applies where Updawg processes personal data on the customer's behalf, and is intended to meet Article 28 of the UK GDPR and of the EU GDPR.
Personal data about the people who use Updawg — their accounts, sign-ins and billing — is processed by Updawg as a controller, as described in the Privacy Policy, and is not covered by this DPA.
1. What is processed
| Subject matter | Providing the Updawg service: inventorying the customer's hosts, proposing updates according to the customer's policies, and applying the ones the customer or its policies approve. |
|---|---|
| Duration | For as long as the customer uses the service, then until deletion under section 8. |
| Data subjects | The customer's staff and contractors who use Updawg, and people whose names appear in host data the customer chooses to have reported (for example in hostnames or repository URLs). |
| Personal data | Names and email addresses of the customer's members and invitees, as they appear in its organization; IP addresses in its audit log; hostnames and the other host details listed at docs.updawg.net; the output of jobs run on its hosts. No special category data is intended to be processed. |
| Processing | Storage, display, comparison against published advisories, sending signed jobs to the customer's hosts, and notifications to channels the customer configures. |
| Location | The region the customer chose when it created the organization: Germany (Frankfurt) for the EU region, the United States (Iowa) for the US region. See section 9. |
2. Updawg's obligations
Updawg will:
- Process personal data only on the customer's documented instructions, which are the Terms of Service, this DPA and the customer's use and configuration of the service, unless the law requires otherwise — in which case Updawg will tell the customer first unless the law forbids it. Updawg will tell the customer if it believes an instruction breaks data protection law.
- Ensure everyone authorised to process the data is bound by confidentiality.
- Implement the security measures in section 5.
- Use sub-processors only as set out in section 6.
- Help the customer, taking account of the nature of the processing, to answer requests from data subjects and to meet its obligations on security, breach notification, impact assessments and prior consultation.
- Delete personal data at the end of the service, as in section 8, and let the customer export it beforehand.
- Make available the information needed to show compliance with this DPA, and allow for and contribute to audits, as in section 7.
3. The customer's obligations
The customer is responsible for having a lawful basis for the processing, for the instructions it gives, for choosing its organization's region, and for what its hosts are configured to report.
4. Personal data breaches
Updawg will notify the customer's owners without undue delay, and in any case within 48 hours, after becoming aware of a personal data breach affecting the customer's data, with the information the customer reasonably needs to meet its own obligations, and will keep it informed as more becomes known.
5. Security
Updawg maintains at least the following measures. More detail is in the security whitepaper.
- Encryption in transit (TLS) everywhere; agents authenticate with mutual TLS and a certificate per host.
- Each organization's data isolated in the database by row-level security on every customer table.
- Jobs signed with a per-organization key held in Google Cloud's key management service, or with a key the customer holds itself; agents verify every job and refuse kinds their local configuration does not allow.
- Secrets such as notification credentials encrypted at rest under envelope encryption, and all stored data encrypted at rest.
- An append-only audit log of administrative and change actions.
- Least-privilege access for staff, with access to production limited and logged.
- Encrypted daily backups with point-in-time recovery, and a restore tested at least every three months.
6. Sub-processors
The customer authorises the sub-processors below. Updawg will give the customer's owners at least 30 days' notice by email, and update this list, before adding or replacing one; the customer may object on reasonable data protection grounds, and if the objection cannot be resolved may terminate the affected service. Updawg imposes data protection obligations on each sub-processor no less protective than this DPA and remains liable for their performance.
| Sub-processor | Purpose | Location |
|---|---|---|
| Google Cloud EMEA Ltd | Hosting, database, key management, storage | Germany (Frankfurt) for the EU region; United States (Iowa) for the US region |
| Hetzner Online GmbH | Our mail server: sign-in links, invitations and email notifications, for both regions | Germany |
| Atlassian Pty Ltd | Our support helpdesk: what the customer's people send to help@updawg.net | May be outside the UK and EEA |
| Stripe Payments Europe Ltd | Payments and invoicing for paid plans | Ireland; may transfer to the United States |
Some services are the customer's or its people's own choice of recipient, not Updawg's sub-processors: notification channels the customer configures (Slack, Microsoft Teams, ntfy, PagerDuty, webhooks), the customer's own identity provider for single sign-on and SCIM, and GitHub, Google or Microsoft when a person chooses to sign in with them.
7. Audits
Updawg will answer a reasonable written security questionnaire once a year. Where that and the security whitepaper are not enough to show compliance, the customer may carry out an audit, at its own cost, on 30 days' notice, during business hours, and under confidentiality.
8. Deletion
An owner can delete the customer's organization at any time. It becomes inaccessible at once and its data is permanently deleted seven days later. If the service ends any other way, Updawg deletes the customer's data within 30 days of the end. Either way, backups containing it expire within a further 14 days, and nothing is kept except where the law requires it. The customer can export its audit log, compliance reports and host data through the portal and the API at any time before then.
9. Data location and international transfers
The customer's organization data is kept in the region it chose. Whatever the region, the accounts of its members, their sign-in sessions and their memberships are kept in the EU region (Frankfurt), and email is sent through Updawg's mail server in Germany. Where personal data is transferred outside the UK or EEA — to the US region at the customer's choice, or by a sub-processor — the transfer is made under the EU Standard Contractual Clauses and the UK International Data Transfer Addendum, which are incorporated by reference, or under an adequacy decision where one applies.
10. Liability and precedence
Each party's liability under this DPA is subject to the limits in the Terms of Service. If this DPA and the Terms of Service conflict on the processing of personal data, this DPA prevails.
Contact
Pez Solutions Ltd, registered in England and Wales, company number 17515727. Registered office: 167-169 Great Portland Street, 5th Floor, London W1W 5PF. privacy@updawg.net