Last updated: August 20, 2026
Subprocessor List
Providers RevenueUI uses to host, secure, authenticate, and bill for the service.
RevenueUI uses the following providers to operate the service. A provider is a subprocessor only to the extent it processes Customer Personal Data on RevenueUI’s behalf. Some providers may also act as independent controllers for their direct relationship with a user.
| Provider | Purpose | Data involved | Processing location and transfer basis |
|---|---|---|---|
| Cloudflare | Web delivery, Worker execution, analytics-event collection, rate limiting, Queue delivery, caching, and operational logs | Request metadata, transient IP address, event payloads, public website configuration | Global network. Provider DPA; adequacy or Standard Contractual Clauses as applicable |
| Laravel Cloud and its infrastructure providers | Laravel API, database, queue jobs, storage, backups, and application operations | Account data, website configuration, analytics events, connected revenue records, encrypted provider credentials, support feedback | Configured and provider-operated regions. Provider terms; adequacy or Standard Contractual Clauses as applicable |
| Stripe | RevenueUI subscription billing and retrieval of payment and subscription data connected by Customer | Billing account and subscription data; connected payment, refund, customer, invoice, Checkout Session, Payment Intent, subscription, trial, and RevenueUI identifier metadata | Provider-operated global infrastructure. Provider DPA and lawful transfer mechanism as applicable |
| Google sign-in authentication | Name, verified email address, provider account ID, and profile image URL | Provider-operated global infrastructure. Google’s applicable privacy and data-transfer terms |
Changes and objections
RevenueUI will update this page before a new provider begins processing Customer Personal Data where reasonably practicable. A Customer with a reasonable data-protection objection may contact palty.support@gmail.com before the change takes effect. RevenueUI will review available alternatives, recognizing that an essential-provider objection may require suspension or termination of the affected service.
Customers should review a provider’s current terms and configured region because location and downstream subprocessors can change independently of RevenueUI.