Sub- processors
The third parties OllieSafe engages to deliver the Services. We notify customers at least 30 days in advance of any addition or replacement, and customers may object on reasonable data-protection grounds per the DPA.
As of: May 2026. This list is maintained as the authoritative public sub-processor register and changes only with a corresponding code update plus customer notification per the OllieSafe Data Processing Addendum Section 7.
Notice of change. OllieSafe will provide at least thirty (30) days' advance notice before adding or replacing a sub-processor. Customers who have subscribed to sub-processor change notifications via security@olliesafe.com will receive the notice by email. Customers may object on reasonable data-protection grounds within the notice window; if the parties cannot reach a commercially reasonable resolution, the customer may terminate the affected Services without penalty (DPA Section 7).
Active sub-processors
| Vendor | Service provided | Categories of data Processed | Processing location |
|---|---|---|---|
| Google Cloud Platform (Google LLC) | Primary cloud infrastructure: compute (Cloud Run), managed PostgreSQL (Cloud SQL), object storage (Cloud Storage), networking (VPC, Load Balancer, Cloud Armor WAF), observability (Cloud Logging, Cloud Monitoring), secret storage (Secret Manager), and managed container registry (Artifact Registry). | All Customer Personal Data at rest and in transit within the OllieSafe platform. | us-west1 (United States) |
| Firebase / Google Identity Platform (Google LLC) | User authentication, multi-factor authentication, password reset, session token issuance, and pre-/post-authentication blocking functions. | Authentication identifiers (email, tenant association), MFA factor metadata, session tokens, login event records. | United States (Google-managed regions) |
| Stripe, Inc. | Payment processing for subscription billing, including card tokenization, payment-method storage, invoicing, and subscription lifecycle management. | Billing contact name and email, payment-method tokens (card data is tokenized by Stripe and never reaches OllieSafe), invoice and subscription metadata. | United States |
| Sentry (Functional Software, Inc.) | Application error monitoring, performance telemetry, and release-health tracking for OllieSafe services. Personally identifiable information is redacted at the SDK layer; only operational metadata reaches Sentry. | Stack traces, request metadata (path, status, timing), redacted user/tenant identifiers for error attribution. | United States (us-east region) |
| Resend (Resend, Inc.) | Transactional email delivery, including account verification, password reset, billing notifications, and incident/training notifications generated by the platform. | Recipient email address, sender identity, message subject and body, delivery and bounce status. | United States |
| Cloudflare, Inc. | Authoritative DNS, edge caching for marketing assets, and WAF/bot mitigation for public-facing endpoints. OllieSafe does not use Cloudflare Workers for Customer Personal Data Processing. | Request metadata (IP address, user agent, request path, response status) for the marketing site and public endpoints. | Global edge network with cache and log retention controls set to the United States region where supported |
Affiliates and intra-group processing
OllieSafe Inc. has no subsidiaries that Process Customer Personal Data at this time. If that changes, the affiliate will be added to this list with the same 30-day advance notice discipline as any third-party sub-processor.
Transfer mechanisms
All listed sub-processors Process Customer Personal Data in the United States. Where Customer Personal Data originates in the European Economic Area, the United Kingdom, or Switzerland, the transfer relies on the EU Standard Contractual Clauses (Module 2: controller-to-processor) and the United Kingdom International Data Transfer Addendum as incorporated by the OllieSafe DPA Section 13. Each sub-processor relationship is governed by a written agreement imposing data-protection obligations no less protective than the OllieSafe DPA.
Sub-processors retired since the prior version
None. The next time a sub-processor is removed, the retired vendor and the retirement effective date will appear here for the subsequent six months as a change-record trail.
Subscribe to change notifications
To receive at least 30 days' advance email notice of any sub-processor change, email security@olliesafe.com with subject Subprocessor change notifications. We will add the requested address to the notification distribution.
Contact
Questions about a listed sub-processor, redline requests, or data-protection objections: legal@olliesafe.com.
Last updated
May 2026.