Last updated: September 20, 2026
A sub-processor is a third party we engage to process data on our behalf in order to deliver ForthWrite. Every sub-processor below is bound by its own security and confidentiality commitments, receives only the data it needs to perform its function, and is never permitted to use your data for its own purposes (such as training its own general-purpose models on your content). See our Privacy Policy for the full detail on what we collect and why.
| Name | Purpose | Data processed | Location |
|---|---|---|---|
| Vercel Inc. | Application hosting, edge network, and scheduled (cron) jobs | Application requests and server logs; no message content is persisted at this layer | United States (global edge network) |
| Supabase, Inc. (infrastructure hosted on AWS) | Primary database and authentication | Account data, encrypted OAuth/API tokens, and voice-matching snippets. Those snippets hold real message text: the inbound message you replied to, the draft we wrote, each revision with the instruction behind it, and the version you sent. Capture is on by default. On an individual plan you can turn it off. On a Teams plan the owner or admin can turn the requirement off; the seat holder cannot. | United States (AWS) |
| Stripe, Inc. | Payment processing and billing | Payment method and billing information; never touches our own servers | United States |
| Anthropic, PBC | AI draft generation (primary model) | Thread or message content sent transiently at draft time; not retained by us after the response returns | United States |
| OpenAI, L.L.C. | AI draft generation (Free and grandfathered Standard proxy default) and voice-dictation transcription (Whisper) | Thread or message content, and/or microphone audio, both transient | United States |
| Other BYOK AI providers you connect (e.g. Google, xAI, Mistral) | AI draft generation, only when you configure your own API key for that provider | Thread or message content, transient, subject to that provider's own policies | Varies by provider |
| Sentry (Functional Software, Inc.) | Error monitoring and observability | Scrubbed error and crash diagnostics; message and thread content is never sent to Sentry | United States |
| PostHog, Inc. | Product analytics | Usage events (page views, feature flags, sign-in). No message or thread content. The connected mailbox address is sent on an inbox-disconnect event | United States |
| Upstash, Inc. | Shared rate-limit store | Rate-limit keys that may be an email address or an IP address; no message content | United States |
| HeyCatch, Inc. | Growth-plan product analytics | Page views, clicks, signup and payment events, and account identifiers; no message or thread content | United States |
| Resend | Transactional email delivery | Your account email address and the content of transactional notifications we send you (e.g. billing, product updates); never your drafts or message content | United States |
| LeadConnector (HighLevel) | Consulting SMS delivery | Mobile number and message content for people who opt in to the Consulting SMS Program; not used for the email product | United States |
| Twilio, Inc. | Carrier partner that may send Consulting SMS on LeadConnector's behalf | Mobile number and message content needed to deliver those texts | United States |
Gmail, Outlook, Slack, and LinkedIn are the source platforms you explicitly authorize ForthWrite to read from, you already have your own direct relationship and agreement with each of them, so we do not list them as sub-processors above. When you connect one of these platforms, ForthWrite reads only the specific thread, message, or channel history needed to draft a reply, on demand, using your own authorization. If you opt in to voice-matching capture (on by default, and revocable at any time), a snippet of what you send is retained on the same rolling window described in our Privacy Policy, regardless of which platform it came from.
On a Teams plan, the owner and any administrator of your team can read the captured message text for every accepted member of that team, through the review record in the dashboard. That includes the inbound message, the draft ForthWritewrote, any revisions with the instruction behind them, and the version that was sent. Team members cannot see each other's records, and nothing crosses a team boundary. Full detail is in Section 6a of our Privacy Policy.
If we add a new sub-processor with access to your message content, we will update this page and bump the “Last updated” date above. For material changes, we will also note it in our product update channels. Contact us at support@forthwrite.ai with any questions about a specific sub-processor.