- Product: InProQu SaaS
- Last reviewed: 27 July 2026
- Operator: InProQu · Notice: [email protected]
This list identifies platform sub-processors InProQu may use to deliver the hosted Service. See the Data Processing Addendum.
1. Infrastructure and operations
| Subprocessor | Role | Data (typical) | Region note |
|---|---|---|---|
| Application hosting (VPS) | Runs the InProQu application | All Service data at rest on the host | Asia / Pacific (primary operations) |
| PostgreSQL (managed with the application host) | Primary database | Account data and Customer Content | Same as hosting |
| Cloudflare, Inc. (when CDN / DNS / WAF is enabled) | CDN, DNS, WAF | IP addresses, request metadata, cached assets | Global edge |
Cloudflare Turnstile (marketing site inproqu.com) |
Bot / spam protection on public forms | IP address, browser/device signals for challenge verification | Global edge |
| Platform transactional email (SMTP provider configured for InProQu) | Auth and system email | Email addresses and message content | Per provider |
| Polar | Merchant of Record — SaaS subscriptions, tax, invoices | Account email, billing details, payment metadata | Per Polar |
| Lemon Squeezy (legacy / optional) | Alternate checkout if configured | Account email, billing details | Per Lemon Squeezy |
| Paddle (optional) | Alternate Merchant of Record if configured | Account email, billing details | Per Paddle |
| Error / log tooling (if enabled) | Diagnostics | Logs that may include IDs or IPs | Disclosed when added |
| Backup storage (if separate from the primary host) | Backups | Encrypted backups | Same region when possible |
2. Optional platform features
| Subprocessor | When used | Data |
|---|---|---|
| Playwright / Chromium on server | Only if server-side PDF export is enabled | Document HTML rendered to PDF |
| Shared platform AI key | Only if InProQu operates a shared AI key (not customer BYOK) | Disclosed separately if ever used |
3. Not platform subprocessors — Customer BYOK integrations
When Customer connects their own accounts, Customer instructs transfer to (examples):
Google (Gmail, Drive, Sheets, Contacts, Calendar, Analytics), Microsoft (Outlook, OneDrive, Entra login, Teams), Slack, Dropbox, Dropbox Sign, Notion, pCloud, Zoho, HubSpot, Salesforce, Pipedrive, Stripe, PayPal, PayMongo, Maya Business, OpenAI, Anthropic, Twilio, and other catalog integrations.
Those providers process under Customer’s contracts and settings. InProQu is not their merchant or controller for that data.
OAuth login to InProQu via Google or Microsoft uses those IdPs as identity providers for authentication; see Privacy Policy.
4. Updates
Material additions of platform sub-processors will be reflected here and noticed per the DPA. Contact [email protected] for notice preferences if offered.