This Data Processing Agreement ("DPA") is entered into between LTFI Tech, LLC, a Massachusetts limited liability company and operator of the OpsPing service ("Processor") and ______________________________ ("Controller"), each a "Party," and supplements the Terms of Service or other master agreement between the Parties governing the OpsPing on-call paging and alerting service (the "Service").
1. Roles and Scope
The Parties acknowledge and agree that, with respect to the processing of personal data submitted to the Service by or on behalf of the Controller ("Customer Personal Data"): the Controller is the data controller, and LTFI Tech, LLC is the data processor, as those terms are defined under the EU General Data Protection Regulation ("GDPR") and equivalent laws. The Processor processes Customer Personal Data only on the Controller's documented instructions, as represented by the Controller's use and configuration of the Service, unless required by law.
2. Subject Matter, Duration, Nature, and Purpose
Meeting Assistant is pending Zoom Marketplace approval and is coming soon; it is not generally available yet. The processing descriptions below apply only if and when the Controller enables the feature.
- Subject matter: Provision of the on-call paging and alerting Service, including billing and the hosted Meeting Assistant transcription and summarization feature where enabled by the Controller.
- Duration: The term of the underlying agreement, subject to the deletion provisions in Section 8.
- Nature and purpose: Storage and processing of account information, channel PII (on-call phone numbers and email addresses), push tokens and device identifiers, alert and incident content (including inbound alert email content processed by Cloudflare Email Routing and the Email Worker), operational activity, support, legal, security, sales, general-inquiry, migration, and SMS-compliance correspondence held in Proton-hosted mailboxes listed in Section 4 (human mailbox and correspondence hosting only), user-initiated support diagnostics, billing contact details, Stripe customer and subscription identifiers, plan/seat and invoice metadata, and — where the Controller enables Meeting Assistant — meeting audio (held only in the task's ephemeral storage and deleted when the transcription pipeline finishes), participant display names and speaker labels, audio-derived transcripts (sent to Workers AI in chunks for summarization), prompts/instructions and organization summary instructions, partial and draft summary context, AI-generated summaries and corrections, meeting metadata, linked incident record fields used for the terminology-correction pass (title, description, responders, impacted services, timeline, and postmortem action items; assistant-posted timeline entries excluded; capped at 20,000 characters), organization glossary configuration (canonical term, definition, aliases; which may include admin-approved short excerpts from corrections), and encrypted Zoom OAuth tokens, solely to deliver alerts, process billing, provide meeting transcripts and summaries, provide support, and operate the Service.
- Categories of data subjects: The Controller's employees, contractors, on-call personnel, billing contacts, and other users whose details are submitted to the Service, and — where Meeting Assistant is enabled — the meeting participants whose audio and display names are captured.
3. Controller Obligations
The Controller warrants that it has a lawful basis for processing, has provided all required notices to and obtained all required consents from data subjects (including on-call team members whose phone numbers and email addresses are submitted), and will not submit special categories of personal data to the Service.
4. Subprocessors
The Controller authorizes the Processor to engage the following subprocessors:
| Subprocessor | Function |
|---|---|
| Amazon Web Services (AWS) | Hosting, compute, and database (PostgreSQL on Amazon EC2); Amazon SES for email delivery |
| Google — Firebase Cloud Messaging (FCM) | Direct push delivery to Android devices |
| Apple — Push Notification service (APNs) | Direct push delivery to iOS devices |
| Twilio | Optional voice delivery and legacy SMS delivery (only if enabled by Controller) |
| Cloudflare — edge network | DNS, edge security, and Cloudflare Pages hosting for opsping.com domains |
| Cloudflare — Email Routing and Email Worker | Inbound email-to-alert ingestion (Email Routing catch-all for alerts.opsping.com; legacy alerts.ops-ping.com alias; Worker parses the full message transiently and forwards only sender/recipient, subject, body text, Message-ID to the OpsPing API) |
| Cloudflare — Workers AI | AI inference for Meeting Assistant transcription (/transcribe) and summarization (/summarize) through the opsping-meeting-summary Worker at ai.opsping.com — summarization requests occur only when the Controller selects the default or both summary mode — and for the opsping.com documentation assistant (a separate Cloudflare Pages Function in the opsping-www project) |
| Stripe | Billing and subscription management (hosted Checkout, Customer Portal, invoicing, and payment lifecycle webhooks) |
| Proton AG — Proton Mail | Human mailboxes for support, legal, security, sales, general inquiries, migration, and SMS compliance correspondence (Switzerland; controller-side recruiting is outside this DPA) |
Subprocessor review record — Proton AG, reviewed 2026-10-26. Before listing Proton AG, OpsPing reviewed Proton's publicly published terms and security materials on 2026-10-26: the Proton Data Processing Agreement (last modified 2026-02-10), which applies to any business or organization using the services and designates Proton AG as processor, with subprocessing in Section 5, deletion or return in Section 9, audit rights in Section 10, and data-transfer safeguards in Section 11; the Proton Trust Center, where Proton states that it is ISO 27001 certified and SOC 2 Type II verified; and the Proton GDPR page. Proton AG is therefore an authorized subprocessor under this DPA for the human mailbox and correspondence hosting described above. Limitation: this review covers published vendor terms and statements only. OpsPing has not obtained or independently reviewed Proton's SOC 2 report, ISO 27001 certificate, or underlying audit evidence, and the certification and attestation qualifications above are Proton's own published claims, not findings by OpsPing.
The Processor will provide at least thirty (30) days' prior written notice before engaging a new or replacement subprocessor. The Controller may object on reasonable data-protection grounds within fourteen (14) days of such notice; if the objection cannot be resolved, the Controller may terminate the affected Service. See the full subprocessor list for details.
5. Security Measures
OpsPing implements the following technical and organizational measures:
- Hosting: Core Service infrastructure (application, database, backups, and transcript storage) is hosted on Amazon Web Services. Cloudflare provides DNS, edge security, Pages hosting for public sites, and Workers AI inference; Stripe processes billing.
- Access control: IAM-based access control with least-privilege principles; access to production systems is restricted to authorized personnel.
- Encryption in transit: TLS 1.2 or higher for all connections to the Service.
- Encryption at rest: Data is stored in PostgreSQL on AWS EC2 instance storage, with automated daily database backups. Sensitive fields — channel values (on-call phone numbers and email addresses) and MFA secrets — are additionally encrypted at the application layer using AES-256-GCM.
- Meeting Assistant: meeting audio is held only in the bot task's ephemeral storage, sent over TLS to the OpsPing
opsping-meeting-summaryWorker atai.opsping.com/transcribe(which calls Cloudflare Workers AI), and deleted when the transcription pipeline finishes; transcripts are stored in a private Amazon S3 bucket in AWS us-east-1 encrypted with AWS KMS (SSE-KMS); Zoom OAuth tokens are encrypted at rest with AES-256-GCM; bot tasks are single-use, deny all inbound network access, and receive only their per-session HMAC-signed token, the short-lived Meeting SDK JWT and On-Behalf-Of join token, the meeting passcode, and a shared, static, route-scoped bearer token for the transcription endpoint — no long-lived Zoom OAuth tokens and no general cloud credentials. For summarization indefaultorbothmode, transcript chunks, prompts/instructions, partial or draft summary context, and the linked-incident record used for terminology correction are sent over TLS to the same Worker's/summarizeroute, which calls Cloudflare Workers AI. The Worker is configured without AI Gateway, the Batch API, a content-storing feature, or observability. On the default Cloudflare path, Cloudflare's Workers AI data-usage terms state zero data retention and no training for standard inference requests, subject to the stated exceptions; a Controller-configured AI endpoint follows the Controller's and its provider's terms. For every delivered summary OpsPing records the provider on the summary record and writes ameetingbot.summarizedaudit entry listing the provider(s) whose summaries were delivered.
Channel PII encryption: on-call phone numbers and email addresses are encrypted at the application layer (AES-256-GCM) in addition to infrastructure-level protections. MFA secrets receive the same treatment.
6. Data Breach Notification
OpsPing will notify the Controller without undue delay, and in any event within seventy-two (72) hours, after becoming aware of a personal data breach affecting Customer Personal Data. Notification will include, to the extent known: the nature of the breach, categories and approximate number of data subjects affected, likely consequences, and measures taken or proposed. OpsPing will provide reasonable cooperation in the Controller's breach investigation and any required notifications to authorities or data subjects.
7. Assistance and Data Subject Rights
OpsPing will provide reasonable assistance, taking into account the nature of the processing, to enable the Controller to respond to data subject requests (access, rectification, deletion, portability) and to demonstrate compliance with GDPR Articles 32–36. OpsPing will refer data subjects who contact OpsPing directly to the Controller. Deletion requests are honored within thirty (30) days of a verified request.
8. Return and Deletion on Termination
Upon termination or expiry of the underlying agreement, OpsPing will, at the Controller's election, return or delete Customer Personal Data within ninety (90) days of termination, unless retention is required by law. Note that closed alerts and operational data are in any event automatically purged after ninety (90) days of retention during the subscription term; open alerts are retained until closed. Meeting Assistant audio is held only in the task's ephemeral storage and deleted when the transcription pipeline finishes. Transcripts, summaries, saved corrections, correction suggestions, and their operational metadata are deleted by the daily retention job when the Controller's configured retention window (1–365 days; default 30) elapses. The daily job deletes each expired transcript object from S3 before deleting its row; when that object deletion fails, the row is kept and retried on the next daily sweep. The transcript bucket's separate S3 lifecycle rule expires objects after its configured period (fixed 400-day fail-safe: 365-day maximum tenant retention + 35-day margin) as a backstop. Zoom deauthorization, console disconnect, and organization deletion delete the database records and attempt the stored transcript-object deletions; object-deletion failures are logged (with the object key when available) and the bucket lifecycle backstop above removes any object left behind. Organization glossary entries and summary instructions may include admin-approved short excerpts from corrections and are Controller configuration retained until the Controller deletes them or the organization is deleted, outside the meeting-content retention window. Ordinary Customer Personal Data in human mailbox and support correspondence is returned or deleted within ninety (90) days after termination. Only controller-side business or legal records that are required by law or needed to establish, exercise, or defend legal claims may be retained for the disclosed period (up to three years), access-restricted, and then deleted; this is not a blanket retention exception. Applicant/candidate correspondence is controller-side recruiting data outside this customer DPA and remains governed by the Privacy Policy and ROPA. Copies of summaries already posted to Slack or internal incident timelines are not recalled by Meeting Assistant retention or deletion paths: Slack copies follow the workspace's retention, and internal incident-timeline copies follow the incident record's and organization's lifecycle.
Backups and recovery copies. Encrypted backup and recovery copies may contain pseudonymous or customer identifiers; live erasure cannot rewrite already-created versioned backups. Those copies are access-restricted to recovery operations. Backup/recovery-copy expiry at or before 365 days and the separate 400-day tenant-lifecycle security-record retention are deployment-gated commitments, not verified current behavior: the canonical offsite lifecycle stack is not yet applied and verified live, and release verification requires its live rules to match before those maxima are asserted. No 365/400-day maximum is claimed until that verification passes. Receipts and backups are pseudonymous, not anonymous, and may remain linkable while the HMAC key or backups exist; access is key-restricted.
Tenant lifecycle security-record exception. On tenant deletion or restoration OpsPing records only a format version, the action (delete or restore), a pseudonymous tenant identifier, a timestamp, and an HMAC. It contains no names, email addresses, Slack or Zoom identifiers, meeting content, or user identifiers, and exists to keep deletion effective across database restore and for security accountability. It is stored in AWS S3 opsping-offsite-970817257986 (us-east-2) and replicated to the KMS-encrypted opsping-recovery-us-east-1-970817257986 (us-east-1), versioned with no Object Lock. Retention is planned at 400 days (399 current + 1 noncurrent); backups/PostgreSQL are planned to be capped at 365 days (364 + 1). Those maxima are not verified live: the canonical offsite lifecycle stack has not been applied, and both buckets' live lifecycle rules must match before release; missing/longer rules block publication. These minimum records survive tenant-content deletion and are pseudonymous, not anonymized.
9. International Transfers — Standard Contractual Clauses
To the extent Customer Personal Data subject to GDPR is transferred to a country without an adequacy decision, such transfers are governed by the EU Commission Standard Contractual Clauses (2021/914), Module Two (controller-to-processor), which are incorporated by reference. The core Service, the Go Meeting Assistant summary pipeline that assembles prompts and stores results, and the database holding meeting metadata and summaries run in AWS us-east-2 (Ohio), with encrypted recovery copies of backups, database archive logs, attachments, and configuration in AWS us-east-1 (N. Virginia); the single-use Meeting Assistant Fargate bot task and transcript S3 bucket run in AWS us-east-1 (N. Virginia), both in the United States; Meeting Assistant inference runs on Cloudflare Workers AI, and public-site delivery (including public-site DNS and HTTP request metadata) uses Cloudflare's global network; the meeting Worker is not configured with a regional or jurisdictional restriction, so Cloudflare may process data outside the United States; and billing data is processed by Stripe, LLC in the United States and may be processed globally by Stripe affiliates under Stripe's Data Processing Agreement and Standard Contractual Clauses. Cloudflare's and Stripe's own data processing terms and Standard Contractual Clauses govern their onward processing as OpsPing subprocessors; push notifications are delivered from United States provider accounts over Google's and Apple's global edge networks under their data processing terms and Standard Contractual Clauses; human mailbox correspondence is hosted by Proton AG in Switzerland, a country covered by a European Commission adequacy decision (Commission Decision 2000/518/EC, as listed on the European Commission adequacy page), so no further transfer safeguard is required for that hosting; for any onward transfer by Proton AG from Switzerland, the EU, or another adequacy country to a country outside that scope, Section 11 of Proton's Data Processing Agreement (last modified 2026-02-10) provides that the parties rely on Switzerland-, EU-, or UK-approved then-current standard contractual clauses or another lawful transfer mechanism under Data Protection Laws; the SCCs in this DPA govern transfers to OpsPing.
SCC attachment: ______________________________ (completed per customer at execution).
10. Audits
Upon reasonable prior written notice, and not more than once annually unless required by a supervisory authority or following a breach, the Controller may audit OpsPing's compliance with this DPA through questionnaires and review of available third-party reports and documentation. On-site audits may be arranged where questionnaires and documentation are insufficient, at the Controller's reasonable cost.
11. Liability
Each Party's liability under this DPA is subject to the limitation-of-liability provisions of the underlying agreement, except where such limitation is prohibited by applicable data protection law.
12. Precedence and Changes
In the event of conflict between this DPA and the underlying agreement regarding data protection, this DPA prevails. OpsPing may update this DPA to reflect changes in law or subprocessors, with notice as required by Section 4.
13. Governing Law
This DPA is governed by the laws of the Commonwealth of Massachusetts, except that provisions implementing GDPR obligations are governed by the law specified in the applicable Standard Contractual Clauses where mandatory. Effective date: ______________________________ (per agreement, completed at execution).
Signature Block
IN WITNESS WHEREOF, the Parties have executed this Data Processing Agreement as of the effective date above.
| Controller | Processor | |
|---|---|---|
| Party | ______________________________ | OpsPing |
| Name | ______________________________ | ______________________________ |
| Title | ______________________________ | ______________________________ |
| Signature | ______________________________ | ______________________________ |
| Date | ______________________________ | ______________________________ |
Questions about this DPA: [email protected].