Legal
This document is provided as-is and is not legal advice. Consult counsel before relying on it.
Last updated 2026-10-14. This is the list of third-party subprocessors Pocket-CFO uses to operate the service, what each one receives, and its current status.
Purpose: database, authentication, and file storage for the entire product. Data received: all customer data Pocket-CFO stores, including account and authentication information, company profile data, normalized accounting records, mappings, scenarios, and encrypted OAuth connection tokens. Status: active for every customer.
Purpose: hosts the Pocket-CFO website and web app, and passes every request the app makes on to the application server. Data received: everything you send to or receive from Pocket-CFO passes through Vercel in transit, including sign-in session tokens and your company's financial data; Vercel does not store it. Status: active for every customer.
Purpose: runs the Pocket-CFO application server, its background jobs and scheduled tasks, and the job queue and cache they use. Data received: all customer data while it is being processed, and job payloads that can include calculated financial figures while they wait in the queue. Status: active for every customer.
Purpose: sends Pocket-CFO email from rippre.com addresses, including account-confirmation and password-reset messages, invitations, report deliveries, and feedback confirmations, and receives the email you send to our addresses. Data received: recipient email addresses and the content of each message. Status: active for every customer.
Purpose: turns figures Pocket-CFO has already calculated into plain English: your KPI briefings and CFO diary entries, and the answers you get from Ask Pocket-CFO. Data received: a sanitized, derived fact packet only: company name, period dates, the already-computed figures, and drafting instructions. OpenAI does not receive raw accounting records, transaction detail, or account numbers, and never calculates a figure. Status: active when you use KPI briefings or Ask Pocket-CFO.
Purpose: web subscription billing and payment processing for purchases made on the Pocket-CFO website. Data received: payment and billing details you enter directly into Paddle's own checkout; Pocket-CFO does not handle your card data. Our stored copy of Paddle's webhook events has customer, billing, address, and business fields redacted before it is saved. Status: active for all web subscriptions.
Purpose: manages mobile in-app-purchase subscription entitlements for the iOS and Android apps. Data received, when enabled: purchase and entitlement events relayed from Apple and Google, keyed to your organization. Status: set up, but not yet in use. The iOS and Android apps are not yet available, so no purchase data reaches RevenueCat until they are.
Purpose: accounting connector you choose to connect so Pocket-CFO can sync your books. Data received: your authorized chart of accounts, transactions, and related financial data by OAuth; connection tokens are encrypted at rest. Status: active. Xero supports live backend OAuth and server-side sync once you connect it.
Purpose: accounting connector you choose to connect so Pocket-CFO can sync your books. Data received, when enabled: your authorized chart of accounts, transactions, and related financial data by OAuth; connection tokens are encrypted at rest. Status: not yet available. Live QuickBooks connections are waiting on Intuit's production approval, so no customer QuickBooks data is received today.
Purpose: additional accounting connectors you may choose to connect. Data received, when enabled: your authorized chart of accounts, transactions, and related financial data by OAuth. Status: not currently enabled. These connectors run on deterministic mock fixtures in this build, and live API authorization is intentionally not wired yet, so no real customer data reaches these vendors today.
Purpose: product usage analytics. Data received, when enabled: usage, device, and interaction data, and only if you accept analytics cookies. Status: not currently enabled. No tracking ID is configured in this build; the consent-gated code exists but stays inert without one.
Purpose: product analytics. Data received, when enabled: usage and interaction data, and only if you accept analytics cookies; page content is masked and session recording stays disabled even when active. Status: not currently enabled. No API key is configured in this build; the consent-gated code exists but stays inert without one.
Purpose: privacy-preserving page-view and traffic analytics for the Pocket-CFO website. Data received, when enabled: page path, referrer, and coarse device and country information, and only if you accept analytics cookies. Vercel Web Analytics is cookieless and does not build a cross-site profile; the page URL is stripped of its query string and fragment before any event is sent, so no token or search term reaches the vendor. Status: active on the website for visitors who accept analytics cookies. Unlike the other analytics vendors it needs no account key, so it works as soon as it is deployed. It is not used in the iOS or Android apps.
Purpose: session-replay analytics. Data received, when enabled: session and interaction data, and only if you accept session-replay cookies. Status: not currently enabled. No site ID is configured in this build; the consent-gated code exists but stays inert without one.
Purpose: session-replay and behavioural analytics. Contentsquare is the same company as Hotjar. Data received, when enabled: session recordings and interaction data, and only if you accept session-replay cookies. Status: not currently enabled. No tag ID is configured in this build; the consent-gated code exists but stays inert without one.
Purpose: mobile app distribution and, when used, in-app payment processing for the iOS and Android apps. Data received, when enabled: whatever device, distribution, and purchase data the App Store or Play Store ordinarily collects for an installed app. Status: not currently enabled. The mobile apps are not yet available in the App Store or Google Play.
