1. Introduction
This Privacy Policy explains how LTFI Tech, LLC, a Massachusetts limited liability company and maker of the OpsPing service ("LTFI Tech," "OpsPing," "we," "us") collects, uses, stores, and shares information when you use the OpsPing on-call paging and alerting service, including the OpsPing mobile application and the website at opsping.com (collectively, the "Service"). This policy is effective as of August 2026.
2. Information We Collect
Meeting Assistant is pending Zoom Marketplace approval and coming soon; it is not generally available yet. The descriptions below document its processing and controls if enabled.
- Account information. Name (if provided), email address, and authentication credentials used to create and manage your account.
- Channel PII. On-call phone numbers and email addresses you provide for yourself or your team members so we can deliver alerts to them.
- Push tokens and device identifiers. Native mobile push tokens and a per-installation identifier used to register and monitor direct push delivery through Google Firebase Cloud Messaging (FCM) or Apple Push Notification service (APNs).
- Alert content and operational activity. Records of alerts, incidents, maintenance windows, notes, schedules, delivery attempts, acknowledgements, escalations, and other actions taken in the Service.
- Meeting Assistant content. Where an organization enables the hosted OpsPing Meeting Assistant, we process meeting audio captured only after the meeting host grants recording permission; participant display names; the resulting transcript; the AI-generated summary, saved summary corrections, and correction suggestions; meeting metadata (meeting ID, timestamps, and session status); linked incident record fields (title, description, responders, impacted services, timeline, and postmortem action items); organization vocabulary glossary entries (canonical term, definition, and aliases), where canonical terms are transcription hotwords and the term, definition, and aliases feed summary correction; entries may include admin-approved short excerpts from summary corrections; and summary instructions, and encrypted Zoom OAuth tokens where a user connects their Zoom account. The Meeting Assistant Privacy Policy describes this processing in detail, including the authorizing Zoom user's user ID (we request only
user:read:tokenand do not read Zoom profile, name, or email) and bot-task CloudWatch logs (participant display names and IDs, meeting timings). - Billing and subscription data. If you purchase a paid plan, we process billing contact name and email, plan/tier, seat count, subscription state, Stripe customer and subscription identifiers, tax identifiers you enter during checkout, and invoice and payment metadata. Card and bank details are entered in Stripe-hosted Checkout or the Customer Portal and never enter OpsPing systems.
- IP address and technical data. IP address, device type, and basic log data collected automatically when you access the Service.
- Support communications and diagnostics. Information you choose to provide in a support request or in-app bug report. An in-app bug report also includes the device model, operating-system and app versions, locale, current screen, and a recent metadata-only activity trail; it excludes message contents, credentials, and push tokens.
- Inbound alert email. Where email-to-alert is enabled, Cloudflare Email Routing receives the full inbound message on
alerts.opsping.com(the legacyalerts.ops-ping.comdomain remains an inbound alias) and theopsping-email-ingressWorker parses it — including attachments, other headers, and the raw body — transiently. Only the sender and recipient addresses, subject, body text (including HTML converted to text), and Message-ID are forwarded to OpsPing, where the message becomes alert content. - Business correspondence. Messages sent to our support, legal, security, sales, general-inquiry (
hello@), migration, SMS-compliance, or careers addresses are hosted in Proton Mail mailboxes operated by Proton AG (Switzerland), including sender and recipient addresses, message content, and delivery metadata. Careers correspondence may include applicant name, email, note, CV/application materials, and metadata, and is used only to evaluate interest and contact candidates.
3. How We Use Information
We use the information above to: provide and operate the Service (including delivering alerts through direct push, email, optional voice calls, and any legacy SMS channel already enabled); manage accounts and authentication; diagnose user-reported problems; maintain and improve the Service; communicate with you about the Service; and comply with legal obligations. We do not sell your personal information.
4. SMS and Text Messaging
OpsPing does not offer SMS in new channel setup. If you or your team's administrator previously registered a phone number for legacy SMS alert delivery, we use it solely to send operational incident alerts and on-call notifications for the OpsPing service. How opt-in worked: a number was registered only inside the OpsPing console by you or your team's administrator, received a one-time verification code by SMS, and did not receive alert messages until that code was confirmed.
- No sharing of mobile information or consent: mobile phone numbers collected for SMS alerts are never sold or rented. Mobile information will not be shared with third parties or affiliates for marketing or promotional purposes. Information sharing with subcontractors in support services, such as customer service, is permitted. All other use case categories exclude text messaging originator opt-in data and consent; this information will not be shared with any third parties. Numbers are passed only to our messaging provider (Twilio), solely as needed to deliver the messages.
- Message frequency: message frequency varies with your team's on-call activity — typically fewer than 10 messages per month.
- Message and data rates may apply to messages sent and received, depending on your mobile plan.
- Opt-out and help: reply STOP to any OpsPing text message to unsubscribe from further SMS alerts at any time. Reply HELP for help, or contact smscompliance@opsping.com.
5. Subprocessors and Third-Party Sharing
We share personal data only with the following subprocessors, solely as needed to operate the Service:
| Subprocessor | Function | Data shared |
|---|---|---|
| Amazon Web Services (AWS) | Hosting, compute, and database (PostgreSQL on Amazon EC2); Amazon SES for email | All Service data; email addresses for email delivery |
| Google — Firebase Cloud Messaging (FCM) | Direct push notification delivery to Android devices | Push tokens, device identifiers, notification content, and delivery metadata |
| Apple — Push Notification service (APNs) | Direct push notification delivery to iOS devices | Push tokens, device identifiers, notification content, and delivery metadata |
| Twilio | Optional voice delivery and legacy SMS delivery | Phone numbers and alert content (only if you enable voice or retain a legacy SMS channel) |
| 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 sites |
| 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; opsping-email-ingress Worker parses the full message transiently and forwards only sender/recipient, subject, body text, Message-ID 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 |
| 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 |
| 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 |
| 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@ |
AI processing for the Meeting Assistant runs on Cloudflare Workers AI; the opsping.com documentation assistant is a separate Cloudflare Pages Function in the opsping-www project, not the meeting Worker. Per Cloudflare's Workers AI Data usage documentation, for standard inference requests Cloudflare does not retain inputs or outputs after they are needed to deliver the response, and Cloudflare does not use Customer Content to train AI models. Those commitments are subject to the exceptions described there: stateful features that store content (which OpsPing does not enable for the meeting Worker), operational metadata such as account/model identifiers, timestamps, request sizes, and token counts, and safety, security, or legal exceptions. OpsPing disables Cloudflare observability for the meeting Worker and does not use AI Gateway logging or the Batch API. If an organization configures its own AI endpoint for summaries, that endpoint's retention and training terms are set by the organization and its provider.
Meeting Assistant provider modes and provider record. Organization admins choose how summaries are generated: default sends summary requests only to Cloudflare Workers AI; customer sends them only to the organization's own HTTPS AI endpoint (meeting audio is still transcribed by Cloudflare Workers AI); both sends them to both. The Cloudflare Worker has two routes: /transcribe receives audio segments and returns transcript text, and /summarize receives audio-derived transcript chunks, prompts/instructions, partial or draft summary context, and the linked-incident record used for terminology correction — audio is not sent to /summarize. The meeting Worker is stateless for this use: it has no storage binding, cache, AI Gateway, Batch API, or Cloudflare observability configured, and returns the response without writing meeting content to durable storage. 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.
We may also disclose information if required by law or to protect our rights and the safety of users. See the full subprocessor list for details.
6. Cookies and Analytics
Our website uses essential cookies or local storage for session management, security, and saved preferences. No advertising or analytics cookies currently load. If we introduce non-essential analytics, they will load only after consent and may be declined without affecting core functionality. The mobile application does not use advertising cookies or trackers.
7. Data Retention and Deletion
- Closed alerts, the audit trail, and other operational data are retained for ninety (90) days and then automatically and permanently purged. Alerts are retained while they remain open.
- Account and channel data is retained while your account is active.
- Meeting Assistant data. Meeting audio is held only in the task's ephemeral storage and is deleted when the transcription pipeline finishes and the task is destroyed; it is never written to durable storage. Transcripts, summaries, saved summary 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. 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. 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.
- Tenant lifecycle security receipts. When a workspace/tenant is deleted or restored, OpsPing writes an append-only, signed security record containing 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. Purpose: prevent a database restore from silently reactivating a deleted tenant and maintain security accountability; legal basis is legitimate interests in security and integrity (Art. 6(1)(f)), and for Customer Personal Data the DPA. Storage: AWS S3
opsping-offsite-970817257986(us-east-2), replicated to the KMS-encryptedopsping-recovery-us-east-1-970817257986(us-east-1); versioning is enabled and Object Lock is not configured. Retention is planned at 400 days (current 399 + noncurrent 1); backups and PostgreSQL objects 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 or longer rules block publication. These minimum security records are excluded from the tenant-content deletion promise. The tenant identifier is pseudonymous, not anonymized, and may be linkable while mappings or backups exist. - 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.
- Organization configuration. Vocabulary glossary entries (canonical term, definition, and aliases) and summary instructions are organization configuration that may include admin-approved short excerpts from corrections. They are kept until an organization admin deletes them and are purged when the organization is deleted, outside the meeting-content retention window.
- Billing and subscription data. Billing and subscription records are retained while the account is active and as needed for tax and accounting; Stripe retains its own invoice and payment records under its terms.
- Inbound alert email becomes alert content and follows the alert-retention rules above; Cloudflare Email Routing and the Email Worker process it transiently.
- Support, legal, security, sales, general-inquiry, migration, SMS-compliance, and careers correspondence held in Proton Mail mailboxes is retained for up to three years only where needed to respond, comply with law, or establish, exercise, or defend legal claims. On termination of a customer agreement, ordinary Customer Personal Data in mailbox/support correspondence is deleted or returned within ninety (90) days; only controller-side business/legal records lawfully required or needed for claims may be retained for that disclosed period, access-restricted, and then deleted. Applicant/candidate recruiting records follow the same retention and deletion-request process.
- Deletion requests. You may request access to or deletion of your personal data by contacting legal@opsping.com. Deletion requests are honored within thirty (30) days of a verified request, subject to legal retention requirements.
- How erasure works. When your account is deleted, your identity (profile, contact channels, device tokens, and every denormalized copy of your name) is removed or replaced with a non-identifying "Deleted user" placeholder in live systems, while your organization's incident history, timelines, and metrics stay intact. An append-only erasure ledger lets restores re-scrub erased identities. This is pseudonymization, not irreversible anonymization: encrypted backup/recovery copies may retain personal data or identifiers and are not rewritten by live erasure; the tenant-lifecycle receipts above are a separate pseudonymous security record. Their 365/400-day maxima are deployment-gated and not verified live; both remain linkable while the HMAC key or backups exist, are key-restricted, and expire under the applicable retention once verified. Access to backups is limited to recovery operations.
8. Data Security
We host the core Service (application, database, backups, and transcript storage) on AWS and use industry-standard safeguards, including TLS 1.2+ encryption in transit, IAM-based access controls, and automated daily database backups. Cloudflare provides DNS, edge security, Pages hosting for our public sites, and Workers AI inference; Stripe processes billing.
Channel PII encryption: the on-call phone numbers and email addresses you provide are encrypted at the application layer using AES-256-GCM, in addition to infrastructure-level protections. MFA secrets receive the same treatment.
Meeting Assistant controls: meeting audio is held only in the bot task's ephemeral storage and is sent only over TLS to the /transcribe route of the opsping-meeting-summary Worker, which calls Cloudflare Workers AI; transcripts are stored in a private Amazon S3 bucket in us-east-1 encrypted with AWS KMS (SSE-KMS); Zoom OAuth tokens are encrypted at rest with AES-256-GCM. A bot task receives only its 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; it holds no long-lived Zoom OAuth tokens and no general cloud credentials. Cloudflare observability and AI Gateway logging are disabled for the meeting Worker; the documentation assistant is a separate opsping-www Pages Function whose request logs are transient operational logs, not a content store. Per Cloudflare's Workers AI data-usage terms, meeting content is not used to train AI models on the default Cloudflare path, subject to the stated exceptions; an organization-configured AI endpoint follows that organization's and provider's terms.
9. International Transfers
The core Service (application, primary database, and backups), the Go Meeting Assistant summary pipeline that assembles prompts and stores results, and meeting metadata and summaries in PostgreSQL run in AWS us-east-2 (Ohio); summarization inference itself runs on Cloudflare Workers AI. Encrypted recovery copies of backups, database archive logs, attachments, and configuration are kept in AWS us-east-1 (N. Virginia). The single-use Fargate bot task and transcript S3 bucket run in AWS us-east-1 (N. Virginia). Cloudflare's global network handles DNS, edge security, Pages hosting, and Workers AI inference; the meeting Worker is not configured with a regional or jurisdictional restriction, so meeting audio, transcripts, summaries, and public-site request metadata may be processed outside the United States, including outside us-east-1. 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. If you access the Service from outside the United States, your information will be transferred to and processed in the United States and on Cloudflare's global network. For customers subject to EU/UK data protection law, transfers to OpsPing can be covered by Standard Contractual Clauses under a Data Processing Agreement; Cloudflare's and Stripe's own data processing terms and Standard Contractual Clauses govern their onward processing as our subprocessors. Push notifications are delivered from United States provider accounts over Google's and Apple's global edge networks, governed by their data processing terms and Standard Contractual Clauses. Human mailbox correspondence is hosted by Proton AG in Switzerland, which is covered by the European Commission's adequacy decision for Switzerland; 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.
10. Children's Privacy
The Service is not directed to, and may not be used by, anyone under the age of 18. We do not knowingly collect personal information from minors. If you believe a minor has provided us personal information, contact us and we will delete it.
11. Your Rights and Contact
Depending on your jurisdiction, you may have rights to access, correct, delete, or port your personal data, and to object to or restrict certain processing. To exercise any of these rights, or for questions about this policy, contact us at legal@opsping.com.
We may update this policy from time to time; material changes will be communicated through the Service or by email, and the updated policy will note a new effective date. Current effective date: August 2026.