LTFI Tech, LLC (operator of the OpsPing service) engages the following third-party subprocessors to provide the on-call paging and alerting Service. Each processes customer data only as needed to perform its function, as described in our Privacy Policy and Data Processing Agreement.
Meeting Assistant is pending Zoom Marketplace approval and coming soon; it is not generally available yet. The listed processors may process its data only if the feature is approved and enabled.
| Service | Purpose | Data processed | Location | SOC 2 status |
|---|---|---|---|---|
| Amazon Web Services (AWS) | Hosting, compute, and database (PostgreSQL on Amazon EC2); Meeting Assistant bot tasks (Fargate) and transcript storage (S3); Amazon SES for transactional email delivery | All Service data: account information, channel PII, push tokens, alert logs, operational data, and Meeting Assistant transcripts and summaries; email addresses and email content for transactional email | United States (us-east-2, Ohio — core application, database, and backups; us-east-1, N. Virginia — Meeting Assistant bot tasks and transcript S3 bucket, plus encrypted recovery copies) | SOC 2 compliant (per AWS compliance programs) |
| Google — Firebase Cloud Messaging (FCM) | Direct push notification delivery to Android devices | Push tokens, device identifiers, notification content, and delivery metadata | United States account; delivery over Google's global edge network | Covered under Google Cloud compliance programs (SOC 2) |
| Apple — Push Notification service (APNs) | Direct push notification delivery to iOS devices | Push tokens, device identifiers, notification content, and delivery metadata | United States account; delivery over Apple's global edge network | Covered under Apple platform security programs |
| Twilio | Optional voice alert delivery and legacy SMS delivery (only if enabled) | Phone numbers and alert content (only when voice or a legacy SMS channel is enabled) | United States | SOC 2 Type II compliant (per Twilio trust center) |
| Cloudflare — edge network | DNS, edge security, and Cloudflare Pages hosting for opsping.com domains | DNS records, connection metadata, and HTTP request metadata for our public marketing, blog, and status sites | Global network (United States-based account) | SOC 2 Type II compliant (per Cloudflare trust center) |
| 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; the opsping-email-ingress Worker parses the full message transiently and forwards only the listed fields to the OpsPing API) |
Sender and recipient addresses, subject, body text, and Message-ID of inbound alert email; the full message (including attachments, other headers, and raw body) is parsed transiently by the Worker, and only these fields are forwarded to OpsPing | Global network | SOC 2 Type II compliant (per Cloudflare trust center) |
| Cloudflare — Workers AI | AI inference for OpsPing Meeting Assistant transcription (/transcribe) and summarization (/summarize) through the opsping-meeting-summary Worker at ai.opsping.com; summary requests occur in default and both mode. Also the opsping.com documentation assistant (a separate Cloudflare Pages Function in the opsping-www project) |
Meeting audio segments (16 kHz mono WAV, base64-encoded, ephemeral) on /transcribe; participant display names and speaker labels, transcript text with the meeting ID prepended (sent in chunks with partial summaries on rolling/combine steps), prompts and instructions (including glossary entries — canonical term, definition, aliases — and organization summary instructions), draft and partial summary context, and linked incident record fields used for terminology correction (title, description, responders, impacted services, timeline, and postmortem action items; assistant-posted timeline entries excluded; capped at 20,000 characters) on /summarize; and documentation-assistant questions |
Global network (Cloudflare-hosted models; no regional or jurisdictional pin configured, so inference may run outside the United States and outside the us-east-1 region where the meeting bot runs) | SOC 2 Type II compliant (per Cloudflare trust center) |
| Stripe | Billing and subscription management: hosted Checkout, Customer Portal, invoicing, and payment lifecycle webhooks | Billing contact name and email, Stripe customer and subscription identifiers, plan/tier, seat count, subscription state, tax identifiers entered during checkout, and invoice/payment metadata. Card and bank details are entered in Stripe-hosted Checkout or the Customer Portal and never enter OpsPing systems | Stripe, LLC (United States) with global onward transfers under Stripe's DPA/SCCs | SOC 2 report available; PCI Service Provider Level 1 (per Stripe security documentation) |
| Proton AG — Proton Mail | Human mailboxes for support, legal, security, sales, general inquiries, migration, SMS compliance, and recruiting/applicant correspondence | Correspondence email addresses, message content, and metadata; applicant name, email, note, CV/application materials for careers@ | Switzerland (Proton AG); global access by authorized staff | ISO 27001 certified; SOC 2 Type II verified (per Proton trust center; reviewed 2026-10-26 — OpsPing has not independently reviewed the certificate or SOC 2 report) |
Proton AG review record (2026-10-26). Proton AG is listed on the basis of its published Data Processing Agreement (last modified 2026-02-10; Proton AG as processor, with subprocessing in Section 5, deletion or return in Section 9, audit rights in Section 10, and transfer safeguards in Section 11), its Trust Center (vendor-stated ISO 27001 certification and SOC 2 Type II verification), and its GDPR page. Switzerland hosting is covered by the European Commission's adequacy decision for Switzerland; Section 11 of Proton's DPA covers onward transfers. These certifications and attestations are Proton's own published claims: OpsPing has not obtained or independently reviewed the SOC 2 report or ISO 27001 certificate. Proton AG hosts human mailboxes and correspondence only and is not a Meeting Assistant processor.
AI Processing and Retention
OpsPing Meeting Assistant sends each speaker's audio segment over TLS to the /transcribe route of the opsping-meeting-summary Worker at ai.opsping.com, which calls Cloudflare Workers AI (whisper-large-v3-turbo). In default or both summary mode it sends audio-derived transcript chunks with the meeting ID prepended, prompts/instructions (including glossary entries — canonical term, definition, aliases — and organization summary instructions), partial and draft summary context, and linked incident record fields used for terminology correction (title, description, responders, impacted services, timeline, postmortem action items; assistant-posted timeline entries excluded; capped at 20,000 characters) to the same Worker's /summarize route; audio is not sent to /summarize. In customer mode no summary request goes to Workers AI, but audio is still transcribed there; both sends summary requests to Workers AI and the organization's own endpoint. That Worker runs on Cloudflare's global network with no regional or jurisdictional pin configured and may process data outside the United States, including outside the AWS us-east-1 region where the bot task and transcript bucket run. The opsping.com documentation assistant is a separate Cloudflare Pages Function in the opsping-www project, not the meeting Worker. Meeting audio is held only in the bot task's ephemeral storage and is deleted when the transcription pipeline finishes and the task is destroyed; it is never written to durable storage.
Per Cloudflare's Workers AI Data usage documentation, for standard inference requests Cloudflare does not retain inputs or outputs after they are no longer needed to process the request and deliver the response, and Cloudflare does not use Customer Content processed by Workers AI to train AI models. Those commitments are subject to the exceptions described there: stateful features that store content (OpsPing does not enable AI Gateway, Batch, or observability for the meeting Worker), operational metadata (such as account and model identifiers, timestamps, request and response sizes, token counts, latency, and status codes), and safety, security, or legal exceptions. OpsPing does not write audio, transcripts, or summaries to Cloudflare telemetry.
Transcripts are stored in OpsPing's private S3 bucket in AWS us-east-1; the Go summary pipeline that assembles prompts and stores results, and the summaries/meeting-metadata database, run in the core AWS us-east-2 deployment; summarization inference runs on Cloudflare Workers AI. Transcripts, summaries, saved corrections, and correction suggestions are deleted by the daily retention job when the organization'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. Copies of summaries already posted to Slack channels 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. For every delivered summary OpsPing records the provider (default or customer_endpoint) on the summary record and writes a meetingbot.summarized audit entry listing the provider(s) whose summaries were delivered. Per Cloudflare's data-usage terms, meeting content is not used to train AI models on the default Cloudflare path; where an organization configures its own AI endpoint, that endpoint's retention and training terms are set by the organization and its provider, and it is not an OpsPing subprocessor.
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 no 365/400-day maximum is asserted until release verification proves the live lifecycle rules. Receipts and backups are pseudonymous, not anonymous, and may remain linkable while the HMAC key or backups exist; access is key-restricted.
Tenant deletion/restoration security receipts are 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). They contain only a format version, delete/restore action, pseudonymous tenant identifier, timestamp, and HMAC — no names, email, Slack/Zoom identifiers, meeting content, or user identifiers. Retention is planned at 400 days (399 + 1 noncurrent); backups/PostgreSQL are planned to be capped at 365 days (364 + 1); Object Lock is not configured. 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 or longer rules block publication. These minimum security records survive tenant-content deletion and are pseudonymous, not anonymized.
For customers subject to EU or UK data protection law, Cloudflare's data processing terms incorporate the EU Standard Contractual Clauses for that onward transfer, and its terms govern its processing as our subprocessor; Stripe, LLC's own data processing terms and Standard Contractual Clauses govern billing data, including its global onward transfers. Transfers to OpsPing itself are covered by the Module Two Standard Contractual Clauses in our Data Processing Agreement. Cloudflare's edge network also processes DNS and HTTP request metadata globally while serving our public marketing, blog, and status sites. The core API at api.opsping.com is DNS-only and is not proxied through Cloudflare; the Meeting Assistant inference endpoint ai.opsping.com is a Cloudflare Worker (Workers AI), the documentation assistant is a Cloudflare Pages Function, and inbound email-to-alert traffic transits Cloudflare Email Routing and the opsping-email-ingress Worker.
Changes to This List
We may add or replace subprocessors from time to time. Customers are notified at least thirty (30) days in advance of any subprocessor change, and may object on reasonable data-protection grounds within fourteen (14) days of that notice, as described in our Data Processing Agreement. If an objection cannot be resolved, you may terminate the affected Service.
Questions about our subprocessors: [email protected].