Last updated: February 19, 2026
This Data Processing Agreement ("DPA") forms part of the Terms of Service or other master agreement ("Agreement") between Hyperping SAS ("Hyperping", "we", "us", or "our") and the Customer ("Customer", "you", or "your"). It reflects the parties' agreement regarding the processing of Personal Data in accordance with applicable data protection laws.
In the event of any conflict between this DPA and the Agreement, the terms of this DPA shall prevail with respect to the processing of Personal Data.
Unless otherwise defined in this DPA, capitalized terms have the meaning given in the Agreement.
The terms "Controller", "Processor", "Data Subject", "Processing" (and "Process"), "Business", "Service Provider", and "Supervisory Authority" have the meanings given under the relevant Data Protection Laws.
2.1 The Customer acts as the Data Controller (or "Business" under CCPA), and Hyperping acts as the Data Processor (or "Service Provider" under CCPA). The Customer determines the purposes and means of processing; Hyperping processes data on the Customer's behalf.
2.2 If the Customer is itself a Processor for a third-party Controller, Hyperping acts as a Sub-processor. The obligations in this DPA remain the same.
2.3 In certain limited cases (e.g., Hyperping processing its own account/contact data as a Controller), each party acts as an independent Controller and will comply with Data Protection Laws accordingly. This DPA primarily governs Hyperping's role as a Processor.
The Customer shall:
Hyperping shall:
3.3 The subject matter, nature, purpose, and duration of processing, as well as types of Personal Data and categories of Data Subjects, are described in Annex A.
4.1 General Authorization. The Customer authorizes Hyperping to engage Sub-processors listed in Annex B. The current list is also available at hyperping.com/subprocessors.
4.2 Sub-processor Obligations. Hyperping ensures Sub-processors are bound by data protection obligations no less protective than this DPA. Hyperping remains liable for its Sub-processors' performance.
4.3 Notice and Objection. Hyperping will provide at least 14 days' advance notice of changes to the Sub-processor list. The Customer may object in writing within 7 days on reasonable data protection grounds. The parties will discuss in good faith. If no resolution is reached, Customer may terminate the affected services as its sole remedy. If no objection is made within 7 days, the new Sub-processor is deemed accepted.
4.4 Essential Sub-processors. Certain Sub-processors (e.g., cloud hosting) are essential to the Services. Objecting to an essential Sub-processor may require suspension or termination of the service, with a pro-rata refund of prepaid fees.
4.5 Emergency Replacement. If Hyperping urgently needs to replace a Sub-processor (e.g., for security or continuity), it will notify the Customer as soon as practicable. The Customer retains the right to object after the fact.
5.1 If Hyperping receives a Data Subject request, it will redirect the individual to the Customer or forward the request. Hyperping will not independently respond to Data Subject requests.
5.2 The Customer is responsible for responding to Data Subject requests. Hyperping provides tools (dashboard features for data export and deletion) to assist.
5.3 Hyperping will assist the Customer in fulfilling Data Subject requests through appropriate technical and organizational measures.
5.4 If Hyperping receives a legally binding request from a public authority for Customer Personal Data, it will inform the Customer (unless prohibited by law) before responding, and will disclose only the minimum necessary.
Hyperping ensures that personnel with access to Personal Data are subject to confidentiality obligations, have access on a need-to-know basis, and are trained on data protection responsibilities. These obligations survive termination of this DPA.
7.1 Hyperping maintains appropriate technical and organizational security measures, including:
Hyperping may update security measures provided they do not materially reduce protection levels. Details are available at hyperping.com/security.
7.2 The Customer is responsible for securing their own account credentials, API keys, and configurations, and for using available security features (SSO, access roles, etc.).
8.1 Hyperping will notify the Customer without undue delay upon becoming aware of a Personal Data Breach, providing sufficient information for the Customer to meet regulatory notification obligations. Information may be provided in phases as it becomes available.
8.2 Hyperping will promptly contain, investigate, and mitigate any breach, and cooperate with the Customer on remediation and notifications. Notification is not an acknowledgment of fault.
8.3 The Customer determines whether notifications to Data Subjects or authorities are required. Hyperping will assist with available information and reasonable remedial measures.
9.1 The Customer may audit Hyperping's compliance with this DPA. Hyperping will provide information reasonably necessary to demonstrate compliance.
9.2 Audits require at least 14 days' written notice, must be conducted during business hours without unreasonable disruption, and are limited to once per 12-month period (unless required by a supervisory authority or following a significant breach).
9.3 Third-party auditors must be mutually agreed, execute confidentiality agreements, and may not be direct competitors of Hyperping.
9.4 Hyperping may provide third-party certifications, audit reports, or penetration test summaries to satisfy audit requests.
9.5 The Customer bears its own audit costs plus reasonable costs incurred by Hyperping. If an audit reveals material non-compliance, Hyperping will remediate at its own expense.
10.1 Upon termination of the Agreement, Hyperping will, at Customer's choice, return or delete all Customer Personal Data within 30 days, except where retention is required by law.
10.2 If no request is received, Hyperping will delete Customer Personal Data from active systems within 30 days following termination.
10.3 During the term, Customer can delete data via the dashboard at any time (monitors, incidents, subscribers, etc.).
10.4 Backup copies are purged according to Hyperping's retention schedule (30-day daily, 12-week weekly, 12-month monthly). Residual data in backups is protected from processing until deleted.
10.5 Upon request, Hyperping will confirm in writing that deletion has been completed.
11.1 Customer Personal Data is primarily stored in the EU (Frankfurt, Germany). Transient monitoring data may be processed globally at probe servers, but primary storage remains in the EU.
11.2 The Customer authorizes Hyperping and its Sub-processors to transfer Personal Data internationally as needed, subject to the safeguards below.
11.3 For transfers from the EEA, UK, or Switzerland to countries without an adequacy decision, the parties rely on: (a) EU Standard Contractual Clauses (SCCs); (b) the EU-US Data Privacy Framework where applicable; or (c) other legally recognized mechanisms. A copy of applicable transfer mechanisms is available upon request.
11.4 If a transfer mechanism becomes insufficient, the parties will cooperate in good faith to implement additional measures or alternative solutions.
11.5 Hyperping will not grant third parties (including government agencies) direct access to Customer Personal Data unless required by law. If compelled, Hyperping will provide the minimum necessary and inform the Customer where legally permitted.
12.1 Confidentiality. Both parties keep this DPA and related information confidential per the Agreement.
12.2 Notices. All notices must be in writing. Email delivery has the same legal effect as paper.
12.3 Liability. Liability under this DPA is subject to the limitations in the Agreement. Claims under this DPA are subject to the aggregate liability cap in the Agreement.
12.4 Governing Law. This DPA is governed by the laws of France. Disputes are subject to the exclusive jurisdiction of the courts of Paris, France.
12.5 Precedence. In case of conflict, this DPA prevails over the Agreement solely regarding Personal Data processing.
12.6 Term. This DPA remains in effect as long as Hyperping processes Personal Data under the Agreement. Sections that by nature should survive termination will survive.
12.7 Changes. Hyperping may update this DPA with notice to the Customer. Material changes provide an opportunity to object or terminate. Continued use constitutes acceptance.
12.8 Entire Agreement. This DPA and the Agreement represent the parties' entire understanding regarding Personal Data processing.
Hyperping processes Customer Personal Data to provide uptime monitoring, alerting, status page management, incident management, on-call scheduling, and related services. This includes monitoring availability and performance, sending notifications, managing status page subscriptions, and providing customer support and account administration.
For the duration of the Agreement, plus any retention period required by law or specified in the DPA.
Hyperping does not require or intend to collect special categories of personal data (health, race, political opinions, etc.) or data about children under 16. The Customer should not submit such data unless explicitly agreed.
The current list of Sub-processors is maintained at hyperping.com/subprocessors.
| Sub-processor | Description | Location |
|---|---|---|
| DigitalOcean, LLC | Primary cloud hosting, databases, and object storage | EU (Frankfurt, Germany) |
| Amazon Web Services, Inc. | Monitoring infrastructure, S3 storage, compute | Global (primary EU and US) |
| Scaleway SAS | EU-based monitoring infrastructure | EU (Paris/Amsterdam) |
| Vercel, Inc. | Status page hosting and marketing website | Global (primary US and EU) |
| Cloudflare, Inc. | CDN, DDoS protection, SSL/TLS management | Global |
| Stripe, Inc. | Payment processing and subscription billing | United States (PCI-DSS Level 1) |
| Twilio, Inc. | SMS and phone call alert delivery | United States (global routing) |
| Twilio SendGrid | Email delivery for alerts and notifications | United States (global delivery) |
| Google LLC | Single Sign-On (OAuth) authentication | United States (global) |
| WorkOS, Inc. | Enterprise SSO (SAML, Okta, Azure AD) | United States |
| Segment (Twilio Segment) | Product analytics and event tracking | United States |
| Sentry (Functional Software, Inc.) | Error tracking and performance monitoring | United States |
Hyperping will update this list as needed on its website and via notice to Customer, in accordance with Section 4 of this DPA.
Hyperping SAS
50 Avenue des Champs-Élysées, 75008 Paris, France
hello@hyperping.io