Subprocessors
Subprocessors
Plain-English version: by default, your financial data stays on your machine, and each service below touches only the narrow slice a specific feature needs. The optional AI categorization feature you can switch on sends limited transaction details to Anthropic if you enable it; we spell that out below. This page lists each service, what it does, what data passes through it, and where to read their privacy commitments.
Written in plain English, and in effect today.
Last updated: October 23, 2026
Who’s on this list and why
A “subprocessor” is a vendor we use to help run GlidePath Money. Each one is scoped narrowly: payment goes through Stripe, outbound transactional email through Resend, our support mailboxes and bank-diagnostic alerts through Zoho Mail, an operator mailbox that holds earlier bank-diagnostic alerts through Microsoft 365, hosting through Cloudflare, the AI helper through Anthropic, and stock-price refreshes through a proxied call to Yahoo Finance. By default your financial data stays on your machine, so by default none of them see it. The exception is opt-in: if you turn on AI categorization, we send a transaction’s payee, amount, date and account type (plus your own category names) to Anthropic. Even then, none of them see your account names, balances, holding quantities, or who owns what. If you refresh prices, the ticker symbols you track go to Yahoo Finance through our Worker (see its row below). If you turn on detailed weekly digest emails, the digest Resend sends you can include amounts, balances and account names. See the Privacy Policy for the full picture of what we do and don’t collect.
Not on this list: Google Ads. Our marketing site uses Google Ads to measure the page visits, downloads, and license purchases its ads lead to. It isn’t a vendor that runs the app or your license, but it does receive data from us. For visitors outside the EU, EEA, UK, and Switzerland, Google’s tag on every page reads and sets Google’s cookies and sends Google each page’s address; on the post-checkout page, that address includes Stripe’s ID for your checkout. When a license purchase follows a Google ad click, in any region, we can also report it to Google: the click ID, amount, currency, time, and Stripe’s checkout ID. We don’t send Google your name, email, license key, or anything from the desktop app. The details are under Cookies + analytics in the Privacy Policy.
| Subprocessor | Function | Data they see | Location | Their privacy policy |
|---|---|---|---|---|
| Stripe | Payment processing + Stripe Tax (automated US sales tax + Canadian GST). QuickTech LLC is the seller of record; Stripe is the card processor. | Your name, email, billing address, payment method, transaction history (held by Stripe as our payment processor); for a purchase that follows a Google ad click, the ad’s click ID, and for a maintenance renewal or an upgrade, our license reference (and, for an upgrade, your license key), each carried in the checkout’s details | US (Stripe Inc.) with global infrastructure | stripe.com/privacy |
| Resend | Outbound transactional email — license keys, welcome notes, renewal reminders, a reminder about a checkout you didn’t finish, the weekly digest if you turn it on, feedback confirmations and follow-ups, report notifications to our support mailbox, refund-request emails to you, refund-request and purchase alerts to our support mailbox, operational replies | The content and recipient of each email we send, kept in Resend’s send log under its own retention policy. That includes the confirmation and follow-up emails about in-app feedback, sent to the reply email you gave; the refund-request alerts, which carry the email address and any note you entered on the refund form; and the purchase alerts, which carry your email address, our license reference, the amount and Stripe’s ID for the checkout, as each alert has them, plus the details listed for Zoho Mail below; and the bank-support diagnostic alerts we send ourselves (the bank’s domain from our list, counts when supplied and valid, and other fixed details, with no text from your file, not linked to you; alerts we sent before our server changed held the text the Privacy Policy describes, and stay in this log under its retention policy; until October 23, 2026, copies went to our Microsoft 365 operator mailbox, and they now go to our Zoho Mail support host). | US | resend.com/legal/privacy-policy |
| Zoho Mail | Support-email hosting — the mailboxes behind hi@ and [email protected], where we receive your messages and from which we reply and may write to you about an in-app feedback report you sent; our report notifications, refund-request alerts and purchase alerts also arrive there, and bank-support diagnostic alerts arrive at [email protected] on the same host | The content of your support correspondence and the sender/recipient email addresses, including any email we write to you about a feedback report you sent, addressed to the reply email you gave with it; a notification of each in-app feedback report and crash report you send, carrying only the report’s reference, type, and app version; an alert of each refund request you submit, carrying the email address you entered (also as the reply-to address), the refund kind, any note you added, and, as the request moves along, our license reference and the refund’s amount and Stripe’s IDs for the charge and the refund; and an alert of each purchase, maintenance renewal and upgrade you pay for, and of any payment we couldn’t apply, carrying your email address, our license reference, the amount and Stripe’s ID for the checkout, as each alert has them (a new-purchase alert also names the tier, says whether your license email went out (and the error, if it didn’t), and says whether you arrived from one of our Google ads, yes or no; a renewal alert adds your new maintenance end date; an alert about a payment we couldn’t apply says why; and if a license email fails at first, a second alert follows when it is delivered); and each bank-support diagnostic alert since October 23, 2026 (the bank’s domain from our list, fixed fields, and counts when supplied and valid; no text from your file, not linked to you). All of it stays in the mailbox until we delete it. | US (data region) | zoho.com/privacy |
| Microsoft 365 | Operator mailbox that received bank-support diagnostic alerts until October 23, 2026, and still receives site-deployment drift alerts (commit details only); customer support, refund, purchase and current diagnostic alerts use the Zoho mailbox above | The bank-support alerts it received before October 23, 2026, kept until we delete them. Those alerts contain a listed bank domain, fixed fields and valid counts only when supplied. Version 1.2.0 supplies no counts. Before our server changed, these alerts could contain the first line of a bank file, its download address and full site name, as the Privacy Policy describes. We deleted old-format alerts already held in the mailbox and use a rule for delayed arrivals. The mailbox provider may keep deleted copies recoverable for a period under its own retention policy. | Microsoft cloud; mailbox data location depends on our tenant configuration | microsoft.com/privacy |
| Cloudflare | Marketing-site hosting (Pages), Worker API endpoints, DNS, D1 customer database | Traffic in transit, DNS lookups, request metadata (timestamps, URLs, status codes; for a price refresh, the URL includes the ticker symbols, and our Worker’s request log keeps it for up to 7 days), customer record (email, license key), the feedback reports and refund requests you send us, our replies to your feedback, the opt-in bank-support diagnostics (the bank’s domain from our list, counts when supplied and valid, and other fixed details, with no text from your file, not linked to you), the ad-click record, and the other records the Privacy Policy’s storage table lists under Cloudflare D1 (such as unfinished checkouts, crash reports, device records and the legal-acceptance log). We don’t store your data folder anywhere; it stays on your computer. | Global edge network | cloudflare.com/privacypolicy |
| Anthropic (optional AI features) | Two opt-in features, all powered by Claude through our Worker proxy: the Glide AI helper (conceptual Q&A) and AI transaction categorization | Glide AI: only the question you type plus page context (page name, section). AI categorization (opt-in): a transaction’s payee, amount, date and account type, plus your category names — never account names, balances, holdings, or owner. Anthropic processes commercial API traffic per their privacy commitments and does not train on it. | US | anthropic.com/legal/privacy |
| Yahoo Finance (via our Worker proxy) | Holdings price refresh — we proxy the lookup so Yahoo never sees your IP | The list of ticker symbols you hold (just symbols — never quantities, account names, or your identity) | US | legal.yahoo.com/us/en/yahoo/privacy |
What about Anthropic and my data?
Glide AI is an optional explainer feature. When you ask Glide a question like “what is a Roth conversion?” or “why does this Monte Carlo run show a wide range?”, we send Anthropic your question text and minimal page-context (the page name, the feature you’re on). We do not send your transactions, balances, holdings, or any data from your DataFolder. Glide AI is sandboxed from your data by design. See the security page for the architecture.
How we choose subprocessors
We pick vendors who: (a) charge per usage rather than per seat, so you don’t pay for someone else’s business model; (b) commit to not training on or selling customer data; (c) operate at a scale that gives us reasonable security guarantees without requiring us to lock you in.
Changes to this list
If we add or replace a subprocessor, we’ll update this page and email everyone with an active license at least 30 days before the change takes effect. The most recent version is dated at the top.
Contact
Questions about subprocessors or data flows: [email protected].