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.

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.

5. Subprocessors and Third-Party Sharing

We share personal data only with the following subprocessors, solely as needed to operate the Service:

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

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.