Progense engages the third-party sub-processors listed below to help provide the Progense platform and related services (the "Service"). Each sub-processor processes personal data only as necessary to perform the services it provides to Progense, and is bound by contractual obligations consistent with our Data Processing Agreement.
We maintain this list to provide transparency to our customers. We may update it from time to time as our infrastructure evolves. Where required, we will provide a mechanism for customers to be notified of additions or replacements and to object on reasonable data-protection grounds.
Infrastructure and Hosting
| Sub-Processor |
Purpose |
Data processed |
Location |
| Laravel Cloud |
Application hosting, compute, and managed database hosting for the backend |
Account data, Customer Data |
United States |
| Vercel |
Hosting and delivery of the web application and marketing site |
Limited technical and usage data; serves the application that processes Customer Data |
United States |
| Laravel Cloud Object Storage |
Storage of files and uploads |
Files and attachments uploaded as Customer Data |
United States |
| Laravel Reverb (hosted on Laravel Cloud) |
Real-time delivery of in-app events and messages |
Message metadata and identifiers transmitted in real time |
United States |
Payments
| Sub-Processor |
Purpose |
Data processed |
Location |
| Paddle |
Merchant of Record; payment processing, subscription billing, and tax collection and remittance |
Billing and transaction information, limited customer identifiers; full card details are handled by Paddle and not stored by Progense |
International |
Authentication
| Sub-Processor |
Purpose |
Data processed |
Location |
| Google (Sign-in with Google) |
Optional third-party authentication |
Name, email address, and a unique account identifier provided by Google when a user chooses Google sign-in |
Global |
Email Delivery
| Sub-Processor |
Purpose |
Data processed |
Location |
| Postmark |
Delivery of transactional and notification emails |
Recipient name and email address, and the content of transactional and notification messages |
United States |
Bot and Abuse Prevention
| Sub-Processor |
Purpose |
Data processed |
Location |
| Cloudflare Turnstile |
CAPTCHA challenge and automated-abuse prevention on sign-up and public forms |
IP address and challenge-interaction signals at the time of submission |
Global |
Artificial Intelligence
| Sub-Processor |
Purpose |
Data processed |
Location |
| Anthropic |
Processing of requests for optional artificial-intelligence features |
The portions of Customer Data necessary to fulfill an AI request, sent at the user's direction and identified using internal opaque identifiers where feasible |
United States |
Notes
- Merchant of Record: Because Paddle acts as our Merchant of Record, Paddle is the seller of record for transactions and independently determines certain processing necessary to fulfill its legal and financial obligations. Paddle's own terms and privacy notice also apply to the payment relationship.
- Artificial-intelligence data use: Our agreement with our AI sub-processor restricts the use of Customer Data submitted through AI features, including with respect to model training, other than as permitted under that agreement.
- Optional services: Some sub-processors (such as the authentication and AI providers) process data only when a customer or user chooses to use the corresponding optional feature.
For questions about our sub-processors, contact us at progense@gmail.com.