Infrastructure Security

Meeting Assistant is pending Zoom Marketplace approval and coming soon; it is not generally available yet. The technical descriptions below describe controls for use if approved and enabled.

The managed OpsPing cloud runs as one active production deployment in AWS us-east-2 (Ohio), backed by PostgreSQL on the application host. A stopped, pre-provisioned recovery environment in us-east-1 (N. Virginia) can be promoted by an operator; there is no automatic failover. Email is delivered via AWS SES. The hosted Meeting Assistant runs single-use Fargate bot tasks and stores transcripts in a private S3 bucket in AWS us-east-1; summary generation, summaries, and meeting metadata run in the core PostgreSQL deployment in us-east-2, with inference on Cloudflare Workers AI's global network. Public marketing, blog, and status sites are hosted on Cloudflare Pages; billing runs through Stripe. Private single-tenant deployments run the same application on infrastructure you or we manage.

Data Encryption

Network Security

Access Control

Application Security

Authentication

Input Validation & Output Encoding

Dependency Management

Zero Standing Access

OpsPing support has no application-level access to your data. Support can see your alerts only when you invite the support account into your organization, and everything it does is recorded in your own audit log. Infrastructure administrators retain technical access to production systems for operations and recovery; that access is limited to documented break-glass procedures.

Tenant Isolation

Support Access by Invitation

Break-Glass Accountability

Compliance & Certifications

SOC 2

OpsPing is not pursuing SOC 2 certification — no independent audit has been conducted and none is planned. Our practices are mapped to the SOC 2 Trust Services Criteria, in depth, on our SOC 2 page.

GDPR

OpsPing acts as a processor for customer data and offers a Data Processing Agreement (DPA) with the 2021 EU Standard Contractual Clauses (Module Two) for customers who need one. The core application, primary database, backups, the Go summary pipeline, summaries, and meeting metadata are stored/run in AWS us-east-2 (Ohio, USA), with encrypted recovery copies in AWS us-east-1; Meeting Assistant bot tasks and the transcript S3 bucket run in AWS us-east-1 (N. Virginia, USA); summarization inference runs on Cloudflare Workers AI. Cloudflare's global network handles DNS, edge/Pages hosting, Email Routing and the Email Worker for inbound alert email, and Workers AI inference (including public-site request metadata; the meeting Worker has no regional or jurisdictional pin configured); Stripe, LLC processes billing in the United States with global onward transfers under its DPA/SCCs; human mailbox correspondence is hosted by Proton AG in Switzerland, which is covered by the European Commission's adequacy decision for Switzerland, so no further transfer safeguard applies to that hosting. Transfers to OpsPing are covered by the DPA's SCCs; Cloudflare's, Stripe's, Google's, and Apple's own data processing terms and SCCs govern their onward processing (push delivery uses United States provider accounts and their global edge networks); any onward transfer by Proton outside Switzerland, the EU, or another adequacy country relies on Switzerland-, EU-, or UK-approved standard contractual clauses or another lawful transfer mechanism under Section 11 of Proton's Data Processing Agreement. See our Privacy Policy for details on data handling, retention, and deletion.

Data Retention

Vulnerability Disclosure

If you discover a security vulnerability in OpsPing, please report it to security@opsping.com. We investigate all reports and respond within 48 hours. We don't run a public bug bounty yet, but we credit researchers in our engineering blog (with permission).

Do not attempt to access, modify, or delete other users' data when testing. Use your own account and test alerts only.

Questions?

Contact security@opsping.com for security questions, DPA requests, or penetration testing coordination. We're happy to provide additional documentation for your security review.

Enterprise Security Questionnaire

Evaluating OpsPing for your organization? This section answers the questions we most commonly receive in vendor security assessments. OpsPing is generally available. Some controls described here are still maturing; we disclose limitations plainly so your team can make an informed risk decision.

Product Overview

OpsPing is a SaaS on-call paging and alerting product for DevOps and operations teams, consisting of a React Native (Expo) mobile application and an AWS-hosted backend. Alerts are delivered via direct push notifications, optional voice calls (Twilio), and email (Amazon SES). SMS is not offered in new channel setup; legacy SMS channels remain deliverable only if already enabled.

Data Handling

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.

Subprocessors

We share personal data only with the subprocessors needed to operate the Service — AWS (hosting, database, transcript storage, and email via Amazon SES), Apple and Google (direct push delivery), Twilio (optional voice delivery and legacy SMS where already enabled), Cloudflare (DNS, edge/Pages hosting for the public sites, Email Routing/Email Worker for inbound alert email, and Workers AI inference for Meeting Assistant transcription (/transcribe) and summarization (/summarize) and the docs assistant; core api.opsping.com traffic is DNS-only and not proxied, ai.opsping.com is a Cloudflare Worker that calls Workers AI, and the docs assistant is a Pages Function), Stripe (billing), and Proton AG (human mailboxes for support, legal, security, sales, general inquiries, migration, SMS compliance, and recruiting/applicant correspondence). Organizations may select default (Workers AI summaries only), customer (their own HTTPS AI endpoint for summaries; transcription remains on Workers AI), or both; for each delivered summary OpsPing records the provider on the summary record and writes a meetingbot.summarized audit entry listing the provider(s) whose summaries were delivered. See the full subprocessor list for purposes, data processed, locations, and SOC 2 status. Customers are notified at least 30 days in advance of subprocessor changes, with a 14-day objection window (see our DPA).

Security Measures

Compliance Status

Incident Response

Business Continuity & Disaster Recovery

Security questions not covered here: security@opsping.com. This questionnaire reflects the current state of the product and will be updated as controls mature.