This Data Processing Agreement (“DPA”) forms part of GlitchTip’s Terms of Service and applies automatically in the circumstances described in the Data Processing section of those Terms. No signature or separate acceptance is required.
Version 1.0 — Last Updated July 22, 2026
Superseded by the current version: immediately for new accounts, and for existing accounts on November 21, 2026.
This DPA has 2 parts: (1) the Key Terms on this page and (2) the Common Paper DPA Standard Terms Version 1.1 posted at commonpaper.com/standards/data-processing-agreement/1.1 (“DPA Standard Terms”), which is incorporated by reference. If there is any inconsistency between the parts of the DPA, the Key Terms on this page will control over the DPA Standard Terms. The Key Terms below have the meanings given on this page. However, if this page omits or does not define a Key Term, the default meaning will be “none” or “not applicable” and the correlating clause, sentence, or section does not apply to this DPA. All other capitalized words have the meanings given in the DPA Standard Terms or the Agreement.
This page is the Cover Page for purposes of the DPA Standard Terms. Every reference in the DPA Standard Terms to the “Cover Page” means this page, including its Key Terms and Annexes. Customer electronically accepts this Cover Page by accepting the Agreement, and the parties are deemed to have agreed to a Cover Page for purposes of Section 10.1 of the DPA Standard Terms at that time.
The GlitchTip Terms of Service, as accepted by Customer.
https://glitchtip.com/documentation/hosted-architecture#core-infrastructure-third-party-processors
The technical and organizational security measures described in Annex II below, together with the controls published at Hosted GlitchTip: Architecture & Security Compliance.
Provider: david@burkesoftware.com
Customer: the email address registered to Customer’s GlitchTip account.
The Provider’s total cumulative liability arising out of the related DPA Covered Claims will not be more than the greater of $3,000.00 or 1 times the fees payable by Customer to Provider in the 12 month period immediately before the claim.
To the extent California Consumer Privacy Act, Cal. Civ. Code § 1798.100 et seq (“CCPA”) applies, the parties acknowledge and agree that Provider is a service provider and is receiving Personal Data from Customer to provide the Service as agreed in the Agreement and detailed below (see Nature and Purpose of Processing), which constitutes a limited and specified business purpose. Provider will not sell or share any Personal Data provided by Customer under the Agreement. In addition, Provider will not retain, use, or disclose any Personal Data provided by Customer under the Agreement except as necessary for providing the Service for Customer, as stated in the Agreement, or as permitted by Applicable Data Protection Laws. Provider certifies that it understands the restrictions of this paragraph and will comply with all Applicable Data Protection Laws. Provider will notify Customer if it can no longer meet its obligations under the CCPA.
EEA Transfers: Ireland
UK Transfers: England and Wales
Name: the Customer, as identified by the account registered for the Services
Address: USA
Activities relevant to transfer: See Annex I(B)
Role: Controller
Name: Burke Software and Consulting LLC
Contact person: Burke Software and Consulting LLC — Privacy & Security Contact, Data Protection Contact
Address: New York, New York USA
Activities relevant to transfer: See Annex I(B)
Role: Processor
The Service is: GlitchTip, a hosted error tracking and application monitoring platform
Is special category data (as defined in Article 9 of the GDPR) Processed? Not intentionally. Customer determines what data its error reporting configuration transmits and is responsible for excluding special category data. Because payloads include unstructured content, such data may be transmitted incidentally. Where Customer has executed a Business Associate Agreement with Provider, protected health information may be Processed subject to that agreement.
Continuous
Provider will process Customer Personal Data as long as required (i) to conduct the Processing activities instructed in Section 2.2(a)-(d) of the Standard Terms; or (ii) by Applicable Laws.
The supervisory authority will be the supervisory authority of the data exporter, as determined in accordance with Clause 13 of the EEA SCCs or the relevant provision of the UK Addendum.
The measures below, together with the controls published at Hosted GlitchTip: Architecture & Security Compliance, are the Security Policy.
User identification and authorization process and protection:
Production environment access is restricted to Principal Engineers at Burke Software and requires Single Sign-On (SSO) backed by hardware-based multi-factor authentication (FIDO2/YubiKey). Environment variables and API keys are stored as Kubernetes Secrets and are never committed to source control.
Protecting Customer Personal Data during transmission (in transit):
All data in transit is encrypted using TLS 1.2 or higher (HTTPS).
Protecting Customer Personal Data during storage (at rest):
Data at rest is stored on DigitalOcean Block Storage with native encryption. Core databases run on managed Kubernetes (DOKS) PostgreSQL clusters via CloudNativePG, isolated within a private VPC and restricted to a trusted-source allowlist; they are not reachable from the public internet.
Physical security where Customer Personal Data is processed:
Physical security and environmental controls are provided by DigitalOcean at its EU (Frankfurt, DE) and US (New York, US) data centers.
Internal IT and IT security governance and management:
Infrastructure is defined as code using OpenTofu, version-controlled, audited, and deployed via GitLab CI/CD. Developer workstations use full-disk encryption (LUKS), automatic inactivity locks, and host firewalls, and receive monthly security patching.
Ensuring limited data retention:
Captured event data and associated Telemetry Data are retained for 90 days by default and are then automatically deleted.
Modification to Standard Terms Section 5.2 (Security Reports) and the defined term “Report.” Provider is a small organization that performs internal security self-assessments and does not undergo audits by independent third-party auditors. Accordingly, the references in Section 5.2 to audits by independent third-party auditors and to a “Report” do not apply to Provider. In their place, upon Customer’s written request to the Provider Security Contact (no more than once per calendar year), Provider will provide a summary of its then-current internal security documentation and self-assessment records sufficient for Customer to verify Provider’s compliance with the technical and organizational security measures described in Annex II. This modification does not affect Customer’s rights under Section 5.1 (Audit Rights) or Section 5.3 (Security Due Diligence).
Provider and Customer have not changed the Standard Terms, except for the details on this page. Customer accepts this DPA by accepting the Agreement, and this DPA takes effect on the later of (a) the date Customer accepted the Agreement and (b) the Last Updated date of this page. It continues for as long as Provider Processes Customer Personal Data.
If a PDF or other rendering of this DPA differs from this page, this page controls.
Customers on a paid plan whose procurement process requires a signed artifact can request a copy of this DPA executed by Burke Software by emailing support@glitchtip.com. It restates these published terms without modification and does not alter the DPA already in effect. The terms are provided as published and are not negotiable.
The Common Paper DPA Standard Terms Version 1.1 are published by Common Paper and are incorporated into this DPA by reference.