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.
| Service | Purpose | Data processed | Location | SOC 2 status |
|---|---|---|---|---|
| Amazon Web Services (AWS) | Hosting, compute, and database (DynamoDB) | All Service data: account information, channel PII, push tokens, alert logs, and operational data | United States (us-east-2, Ohio) | SOC 2 compliant (per AWS compliance programs) |
| Amazon SES | Transactional email delivery (alert and account emails) | Email addresses and email content | United States | Covered under AWS compliance programs |
| Expo | Push notification relay to iOS and Android devices (delivers downstream via Apple Push Notification service and Google Firebase Cloud Messaging) | Push tokens and notification content | United States | SOC 2 Type II compliant (Security criterion, per Expo security page) |
| Google — Firebase Cloud Messaging (FCM) | Push notification delivery to Android devices (downstream of the Expo push relay) | Push tokens, device identifiers, and delivery metadata | United States (Google global infrastructure) | Covered under Google Cloud compliance programs (SOC 2) |
| Twilio | Optional SMS and voice alert delivery (only if you enable it) | Phone numbers and message content (only when SMS/voice is enabled) | United States | SOC 2 Type II compliant (per Twilio trust center) |
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: legal@ops-ping.com.