Legal

Sub-processors

Last updated October 25, 2026

Frosty, operated by FROST THE BRAND LLC, uses the third-party service providers below to operate the Service. Each processes personal data only on our behalf, to provide, secure, and support the Service, under a data-processing agreement. We never sell your data and never use your conversations, files, or connected-app content for advertising.

Current sub-processors

  • Anthropic. AI processing (generating responses, reports, and actions, and short summaries and outlines of a workspace's own docs, files, skills, notes and quiet chats, which an admin can turn off). Processes the prompt and context for your requests; does not train its models on this data. United States.
  • OpenRouter. Model routing for the open models a member chooses (such as GLM, DeepSeek and Kimi), used only for that one run and only when someone picks one; Claude runs never go through it. Processes the prompt and context for that run. Requests are sent only to a fixed, vetted list of third-party inference hosts that keep no copy of the data (zero data retention), with data collection denied; no China-based host is ever used. The hosts on that list are headquartered in the United States, and OpenRouter and the hosts may process the data in more than one country, so a request is not pinned to a single location. The current host list is available on request.
  • Pipedream. Third-party app integrations, the main way apps are connected. Holds the OAuth tokens for apps connected through it and runs the actions you authorize; processes those tokens and the content of the API calls you route through those apps. United States.
  • Composio. Third-party app integrations for apps Pipedream does not support, and for apps already connected through it. Holds the OAuth tokens for those apps (vaulted, AES-256) and runs the actions you authorize. United States.
  • Clerk. Authentication and identity (sign-in, account and workspace identifiers, email). United States.
  • Stripe. Payments and billing (billing contact and transaction metadata; full card details are handled by Stripe, not stored by us). United States.
  • E2B. Secure sandboxed compute, where Frosty builds and runs work, including browser automation and the code Frosty writes to build your Apps. For an App build it sees the build brief, the names of your Table columns and the code it writes; it never receives your Table rows. United States.
  • ElevenLabs. Speech to text and live voice: turns the audio in recordings, videos and voice dictation that members attach, upload or link into a written transcript with speaker labels, and runs live voice conversations with Frosty (the member's microphone audio, the words, and the conversation text it passes to its language model). For live voice Frosty asks ElevenLabs not to keep voice recordings and to delete the call record (the text and length of the call) after one day, or the shortest period ElevenLabs accepts for our plan, kept that long so Frosty can bill the call by its real length; that is a request we make through its settings, not a guarantee, and ElevenLabs' own terms govern what it keeps. Processes that audio (sent as the file or as a signed, short-lived link to it, or streamed live) and returns the words or Frosty's spoken reply. A United States company; processing is not pinned to one country, and transfers rely on the EU-US Data Privacy Framework and Standard Contractual Clauses.
  • LiveKit. Real-time audio and screen routing for meetings: carries each participant's microphone audio and any screen they choose to share between the people on the call, and holds the room while it lasts. It does not record audio or video, and Frosty turns recording off in its LiveKit project. What people say is turned into text elsewhere (ElevenLabs, listed here) and saved as chat messages under their names; shared screens are not watched, stored or read by Frosty. A United States company; transfers rely on the EU-US Data Privacy Framework and Standard Contractual Clauses.
  • Resend. Transactional and account-status email (magic links, approvals, notifications, low-credit/account-status alerts, and re-engagement reminders): recipient address and message content. United States.
  • Apple (Push Notification service) and Google (Firebase Cloud Messaging). Delivery of phone notifications to the Frosty iPhone and Android apps, once enabled: an anonymous device token and a short fixed notice (for example, that an approval is waiting). No names, workspace content or secrets are sent. United States.
  • Cloudflare. CDN, DNS, edge security, and private off-site storage (R2) for database backups and for the files and screen recordings customers upload to their Docs: network metadata, request logs, backups, and those files. Files are kept in a private bucket with no public address and are reachable only through signed, short-lived links. Bucket location: to be stated here when it is chosen. United States / global edge.
  • Railway. Application hosting and database storage (the application, logs, and stored workspace data). United States.
  • Slack. The Slack integration, only if you connect it: messages and metadata in channels and DMs where Frosty is used. United States.

Changes and notice

We keep this list current. Before we add or replace a sub-processor that handles personal data, we notify customers with an active data-processing agreement so they can review or object on reasonable data-protection grounds. To be notified of changes, or to request our DPA or sub-processor agreements, email support@heyfrosty.ai.

Apps you connect yourself (such as Google, Microsoft, a CRM, or an ad platform) are accessed only under the authorization you grant and are governed by each provider's own terms; they are not Frosty sub-processors. See our Privacy Policy for the full detail.

Frosty is an AI coworker, not a person. It can make mistakes, so review its work before relying on it.

Sub-processors | Frosty