Legal · Transparency
Subprocessors
Last updated: November 11, 2026
Onplana engages the third-party service providers below to operate the platform. This list satisfies the transparency requirement of GDPR Art. 28(2). For the full data-processing terms applicable to your organisation, refer to the Onplana Data Processing Agreement, which is part of your Master Services Agreement and authorises the list below.
The browser extension and the desktop and mobile apps are clients for the same platform. They talk only to Onplana's own services, so customer content reaches exactly the processors named below and no others. The one processor the phone app adds is push delivery: when you allow notifications, Apple Push Notification service (iPhone) or Firebase Cloud Messaging (Android) carries each notification to your device, and both are listed under optional subprocessors below with the data they receive. Apple, Google, Microsoft and Mozilla also distribute those apps and collect their own install and crash telemetry as independent controllers under their own terms. Those apps do hold a cached copy of your own tasks on your own device, which is described in the Privacy Policy.
Two categories: Core subprocessors are always engaged whenever Onplana operates; customer content flows through them by default. Optional / integration subprocessors are engaged only when a customer organisation explicitly enables that integration (e.g. installing the Microsoft Teams app), or, for push delivery, only when a person allows notifications on the phone app. No data flows to those vendors absent that step. Services a customer connects with its own account, such as Google Drive, Box, Dropbox, GitHub, Jira, QuickBooks Online and Xero, are not subprocessors and are listed under Services you connect.
Material changes to this list, adding, removing, or changing the region of a subprocessor, will be notified in advance per the DPA. Subscribe to changes by emailing privacy@onplana.com with the subject subprocessor-notify.
Core subprocessors
| Subprocessor | Purpose | Data category | Region | DPA |
|---|---|---|---|---|
| Microsoft Azure | Application hosting (Container Apps), database (Postgres Flexible Server), cache (Redis), object storage (Blob), Key Vault, networking. | All customer content + account data | Azure West US (United States). Daily encrypted backups + 7-day point-in-time restore retained by Azure Postgres Flexible Server; no cross-region replica today. | DPA → |
| Stripe, Inc. | Billing, subscription management, payment processing. | Billing email, billing address, payment-method token (full card data never touches Onplana, collected directly by Stripe Elements). | United States (Stripe is the controller for payment-card data). | DPA → |
| Anthropic, PBC | Claude API, AI features (risk detection, plan generation, status reports, in-app chat). | Project text, task descriptions, and any free-text passed to AI tools. Per Anthropic policy, API inputs are not used for training and are not stored after the request completes. | United States. | DPA → |
| Microsoft Azure OpenAI Service | Azure OpenAI models, same AI features as Anthropic above. Onplana operates both providers and decides which serves requests, with the other on standby. | Same as Anthropic. Processed in Onplana's Azure OpenAI environment; no data is shared with OpenAI Inc. nor used for training. | Azure East US 2 (United States). | DPA → |
| Sentry (Functional Software, Inc.) | Error monitoring (stack traces + request metadata on uncaught backend exceptions). | Stack traces, request method + path, IP address. Personal data is scrubbed via Sentry data-scrubber rules; payload bodies are not sent. | United States (default Sentry SaaS region). | DPA → |
| Azure Communication Services | Transactional email (invitations, password resets, notification digests, billing receipts). | Recipient email address + email content composed by Onplana on behalf of the customer. | Same Azure region as the hosting tenant. | DPA → |
| hCaptcha (Intuition Machines, Inc.) | Anti-bot challenge on sign-up + freebie marketing tool gates. | Browser fingerprint, IP address, challenge-solve token. Not linked to a user account. | Global edge. | DPA → |
| ipwho.is (IP geolocation API) | Country of a free-tool upload, admin owner location. | The visitor's IP address only. One lookup per address; the answer is cached in memory for 7 days. Onplana stores the two-letter country, never the IP address. | Provider's public HTTPS API. | None on file |
Optional / integration subprocessors
Engaged only when a customer organisation has explicitly connected the corresponding integration via Settings → Integrations, or, for the two push delivery rows, when a person installs the phone app and allows notifications.
| Subprocessor | Purpose | Data category | Region | DPA |
|---|---|---|---|---|
| Google LLC | Google OAuth (consumer sign-in). Google Drive file attach is a service you connect, listed below. | OAuth identity (email + verified flag + sub) at sign-in. | Global (Google Cloud). | DPA → |
| Microsoft Corporation (consumer + Microsoft 365 / Teams) | Microsoft OAuth sign-in + Microsoft Teams notification integration (when an org installs the Teams app). | OAuth identity (email, verified flag, sub). Teams: channel + message content for connected channels. | Microsoft Cloud (region depends on tenant). | DPA → |
| Microsoft Clarity (Microsoft Corporation) | Product session analytics (heatmaps + masked session replay) inside the app on the FREE plan only, and only for users who opt in. Helps us see where the product trips people up and improve the free experience. | De-identified, masked interaction data: clicks, scrolls, navigation, and page layout. Text, form input values, people’s names, and file contents are masked and never captured. No personal-data identifier (email / name) is sent. | Global (Microsoft). | DPA → |
| Apple Inc. (Apple Push Notification service) | Push notification delivery to the Onplana Tasks iPhone app (only when a person installs the app and allows notifications). | Notification text: task titles, project names, the name of the person who acted, and comment excerpts of up to about 120 characters. Record ids (task, issue, expense, project) so a tap opens the right item. The device token Apple issues. | Global (Apple). Apple's terms name no processing location for push delivery; the reference is Attachment 1 of the Apple Developer Program License Agreement. | DPA → |
| Google LLC (Firebase Cloud Messaging) | Push notification delivery to the Onplana Tasks Android app (only when a person installs the app and allows notifications). | Notification text: task titles, project names, the name of the person who acted, and comment excerpts of up to about 120 characters. Record ids (task, issue, expense, project) so a tap opens the right item. The device registration token. | Global (Google Cloud and Google data center locations). Firebase Cloud Messaging offers no region choice. | DPA → |
Services you connect
The providers below are not Onplana subprocessors. They are services a customer chooses and connects with its own account. Nothing passes between Onplana and a provider unless someone in the customer's organisation connects the customer's own account: an organisation administrator for GitHub, Jira and the accounting export, or each person for their own Google Drive, Box or Dropbox. Onplana then sends or reads only what a person asks for: a file they pick to attach, an issue created from a task, a Jira issue imported as a task, or an accounting export. What the provider holds stays in the customer's own account, under the customer's own agreement with that provider, not on Onplana's behalf. A file copied into Onplana from one of these services is held like any other upload, by the core subprocessors above.
- Google Drive (Google LLC), for attaching a file a person picks from their own Drive to an Onplana task or project. Google privacy policy
- Box (Box, Inc.), for attaching a file a person picks from their own Box account. Box privacy notice
- Dropbox (Dropbox, Inc.), for attaching a file a person picks from their own Dropbox account. Dropbox privacy policy
- GitHub (GitHub, Inc.), for creating an issue from an Onplana task in the customer's own repository. GitHub privacy statement
- Jira Cloud (Atlassian), for creating a Jira issue from an Onplana task in the customer's own Jira site, and importing a Jira issue as a task. Atlassian privacy policy
- QuickBooks Online (Intuit Inc.), for the accounting export of invoices into the customer's own QuickBooks company. Intuit privacy statement
- Xero (Xero Limited), for the accounting export of draft invoices into the customer's own Xero organisation. Xero privacy notice
What the accounting export sends and the access it asks for are described in section 4.3 of the Privacy Policy. The Google Drive access is described in section 4.1 of the same policy.
Questions
See also Privacy Policy and Security. For data-residency, transfer mechanism (Standard Contractual Clauses), or DPIA questions, email privacy@onplana.com.