Privacy Policy

1. Introduction

FROST THE BRAND LLC (“Frosty,” “we,” “us,” or “our”) operates Frosty, an autonomous AI coworker service (the “Service”) available as a web app and a Slack integration that connects to the business tools you authorize. This Privacy Policy explains how we collect, use, disclose, and safeguard personal data when you use the Service, and your rights and choices. By using the Service, you agree to the practices described here.

“Customer Data” means data submitted to or processed by the Service on your behalf, including connection credentials (such as OAuth tokens), account and workspace identifiers and settings, files and Apps created in Frosty, conversations and outputs, automations and approval decisions, and service logs.

2. Information We Collect

We collect only what we need to provide, maintain, and secure the Service.

• Account and workspace information: your name and email (through our authentication provider) when you create an account or join a workspace, your workspace/organization identifiers, and the identifiers of users who interact with Frosty.
• Connection credentials: access tokens and scopes for the integrations you enable (including Slack and any apps connected through our integration provider). Integrations are workspace-shared, so related credentials and settings may be used by authorized members of your workspace through Frosty. We never send your account passwords or raw credentials to the AI model.
• Content and records inside Frosty: the messages, instructions, and files you give Frosty; the work it produces (reports, dashboards, hosted Apps); conversation threads and tool calls; automation configurations; and approval or rejection decisions.
• Files you upload to Docs: the files and images you add to a document (PDF, images, text, spreadsheet and presentation files), with their name, type, size and who added them. They are kept in a private storage bucket with no public address, opened only through short-lived signed links by people who can already open that document, and deleted when you remove them, when the document is permanently deleted, or when the account or workspace is erased.
• Slack message content (if you connect Slack): message content from channels where Frosty is invited, direct messages to Frosty, and thread replies, used to process your requests and maintain context.
• Service logs and usage data: operational and security logs (timestamps, errors, request metadata) and usage events (tasks run, credits used, features used) needed to operate, secure, and improve reliability.
• Security access log: when someone opens a file stored in Docs, or a workspace export is made, we record the person's identifier, the document and file identifiers and the time, for 90 days, so we can investigate a suspected leak. It is security logging only: it is not shown in the product and is never used to monitor, rank or evaluate people.
• Communications with us: information you provide when you contact support.
• Website, analytics, and advertising data: when you visit our site, use our product, or begin signup or checkout, we and the third-party tools we use may collect cookies, pixels, and similar online identifiers, device and browser metadata, IP address, pages viewed, interaction events, and referral or campaign identifiers, used for analytics, advertising measurement, and referral attribution.

Sensitive data: we do not knowingly collect sensitive personal data (such as financial account numbers, health data, or children's data) unless necessary for the Service and provided by you.

3. How We Use Your Information

• Provide and operate the Service: authenticate users and workspaces, maintain the integrations you enable, run tasks, generate outputs, and maintain context.
• AI processing: relevant portions of Customer Data may be processed by AI systems to produce responses and outputs at your direction. We do NOT use Customer Data for advertising, and we do NOT train our own or any third-party foundation models on Customer Data.
• Security and integrity: detect and prevent fraud, abuse, and unauthorized access, investigate incidents, and maintain audit trails.
• Service improvement: using aggregated or de-identified data that cannot reasonably identify you.
• Shared how-to knowledge: when Frosty works out how to do something in a connected app, it may keep the how-to (which kind of request worked, with every name, number, address and value removed) to work better for everyone. It never keeps your data, and it is erased from our library if the workspace that taught it is deleted.
• Communications: service-related messages (product, security, billing, and administrative) and customer support.
• Analytics, advertising, and attribution: measure product and website usage and campaign performance, run and measure advertising, attribute signups and subscriptions (including to our affiliate program and ad campaigns), and prevent abuse of our marketing and referral programs.
• Compliance and protection: comply with law, enforce our Terms, and protect the rights, safety, and property of our users and Frosty.

4. How We Disclose or Share Information

We never use your Customer Data (your conversations, files, and connected-app content) for advertising, and we do not sell your Customer Data. We do use third-party analytics, advertising, and attribution tools that collect online identifiers and usage data about your visits to our website and product, as described below. Otherwise, we share information only as needed to provide and support the Service, with appropriate safeguards.

A. Service providers (subprocessors). We use vendors to host and operate the Service. They may process Customer Data on our behalf solely to provide, secure, and support the Service. Our current, maintained list (with each provider's purpose, the data it processes, and its location) is published at /sub-processors:

• Anthropic: AI processing (generating responses, reports, and actions from the prompt and context for your requests).
• OpenRouter: model routing for the open models a member chooses (such as GLM, DeepSeek and Kimi), used only for that run; requests go only to a fixed, vetted list of zero-data-retention inference hosts with data collection denied and no China-based hosts, and their processing locations can vary.
• Clerk: authentication and identity (sign-in, account and workspace identifiers).
• Pipedream: third-party app integrations, the main way apps are connected (OAuth tokens and the content of API calls for the apps you connect through it).
• Composio: third-party app integrations for apps Pipedream does not support, and for apps already connected through it (OAuth tokens and actions for those apps).
• E2B: secure sandboxed compute, where Frosty builds and runs work, including browser automation and the code Frosty writes to build your Apps (it sees the build brief, the names of your Table columns and the code, never your Table rows).
• ElevenLabs: speech to text and live voice (the audio in recordings, videos and voice dictation you attach, upload or link, turned into a transcript; and the audio and words of a live voice conversation with Frosty. For live conversations 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: ElevenLabs' own terms and settings decide what it keeps, and the words of the conversation are saved in your chat by Frosty).
• LiveKit: real-time audio and screen routing for meetings. Meeting audio and any screen you choose to share are carried by LiveKit to connect the call, and the words are turned into text in real time by ElevenLabs. Frosty does not record audio or video. What people say is saved as chat messages under their names.
• Stripe: payments and billing (billing contact and transaction metadata; full card details are handled by Stripe, not stored by us).
• Resend: transactional and account-status email (magic links, approvals, notifications, low-credit/account-status alerts, and re-engagement reminders).
• Cloudflare: CDN, DNS, and edge security (network metadata and request logs).
• Railway: hosting and storage (the application, logs, and stored workspace data).
• Slack: the Slack integration (messages and metadata where Frosty is used), if you connect it.

Apps you connect (such as Google, Microsoft, a CRM, or an ad platform) are accessed only under the authorization you grant, through our integration provider, and are governed by each provider's own terms.

B. AI provider details. When you use AI features, the prompt and context needed to generate an output are sent to our AI provider (Anthropic). Anthropic processes data in the United States, may briefly retain it per its API policy for security and abuse monitoring, processes each request in isolation (not visible to other customers), and does not use it to train its models. Anthropic is our default. If a member picks one of the open models offered in the model menu, the prompt and context for that one run go instead to OpenRouter, which routes the request only to hosts that keep no copy of the data (zero data retention), with data collection denied and no China-based hosts. Those runs happen only in a person's own chat and their own automations. Open models are never used for conversations in Slack or for client-facing replies, and an automation that reads Slack channels never uses one; an automation can deliver its result to Slack.

C. Analytics, advertising, and attribution. We use third-party analytics, advertising, and attribution tools, which may include Google Analytics, Hyros, and advertising platforms such as Google and Meta, to measure usage, run and measure advertising campaigns, and attribute signups and subscriptions. These tools may receive online identifiers, device and event metadata, and referral or campaign data. Depending on where you live, some of this may be considered a “sale,” “sharing,” or “targeted advertising” under applicable law, and you may have the right to opt out (see Your Rights and Choices). You can manage cookies in your browser, and where required we provide a cookie-consent control. We never use your Customer Data (conversations, files, or connected-app content) for advertising.

D. Slack platform. The Service integrates with Slack via Slack OAuth 2.0 and Slack APIs, subject to Slack's terms and privacy policy. We access Slack data only after you grant permission, and you can revoke access at any time in Slack App Management. Slack APIs are not used to develop, improve, or train generalized AI or ML models.

E. Legal compliance and protection. We may disclose information if required by law or valid legal process, or to protect the rights and safety of users and the public, prevent fraud, or enforce our Terms.

F. Business transfers. If Frosty is involved in a merger, acquisition, financing, restructuring, or sale of assets, information may be disclosed to advisors and successors, subject to appropriate confidentiality protections.

G. Third-party links. The Service may link to third-party websites or services; we are not responsible for their privacy practices.

H. Chats you share inside your workspace. Chats you share are readable by the people you share them with, including earlier messages. Replies in a shared chat can include things drawn from your personal notes or private channels, so check before you share. You choose who can read a chat and whether they can also post in it, only people in your workspace can be added, and you can stop sharing at any time from the chat's Share control. When a person you shared a chat with posts in it, Frosty answers them using their own account and permissions, not yours. We record who shared a chat with whom and when. If a workspace admin turns on sharing with the Frosty team, our team (and the AI tools it uses to review runs) can read everything in that workspace to fix problems: chats, runs and the inputs and results of the steps Frosty takes (kept 30 days), automations, settings, members and when they last signed in, connections and their health, approvals, files, tables, docs, memory, skills, spaces and the people invited to them, and voice calls. We never see the passwords or tokens your apps connect with, and keys we find are hidden. It is off by default, revocable, and every read is logged.

I. Summaries of your workspace content. In the background, Frosty uses an AI model from our AI provider (Anthropic, the same sub-processor listed above) to write a short summary and outline of your longer docs, files, skills and saved notes, and a small card (date, who took part, topics, decisions) for chats that have gone quiet, so it can find things faster. Text is scrubbed of obvious secrets and contact details before it is sent. Each summary is stored with the item it describes, is visible only to people who can already open that item, and is deleted when the item is deleted, when the person it belongs to erases their account, or when the workspace is deleted. A workspace admin can turn this off in Settings, which also deletes the summaries already written. We do not use summaries for advertising or to train models.

5. Data Storage and Security

Customer Data is stored in the United States with reputable cloud providers, using access controls appropriate to the data. We maintain these safeguards:

• Encryption in transit (TLS 1.2+ / 1.3) for data moving between you, the Service, and the systems we connect to.
• Connected-account tokens (for example Slack) are encrypted at rest by us, using AES-256-GCM.
• Other Customer Data is held on managed infrastructure and in private, access-controlled storage, and relies on our infrastructure providers' storage-level protections rather than encryption applied by us. Applying our own encryption at rest across the whole data store is an active priority; until that is done we state the position plainly here rather than imply more than we do.
• Access controls: least-privilege access and multi-factor authentication on administrative systems.
• Isolation between workspaces (tenants) so one customer's data is not exposed to another.
• Audit logging, monitoring, and an incident-response process, including notification to affected customers or authorities where required by law.

You are responsible for maintaining appropriate security in your own Slack workspace and connected accounts (for example, channel access and admin permissions). No method of transmission or storage is completely secure, but we work continuously to protect your data.

6. Data Retention

We retain Customer Data only as long as needed to provide the Service, meet our obligations, and comply with law.

Content reports. When someone reports a message from a shared chat, we keep the report and a short excerpt of the message so we can review it. A report is deleted 12 months after we resolve it. A report still open is kept until we resolve it.

• Active systems: when an account is closed or we receive a verified deletion request, we delete Customer Data from active production systems, typically within about 30 days.
• Backups: we keep backups for business continuity in private, access-controlled cloud storage, and they are purged as they age out on their normal rotation. Like the main store, they rely on our storage provider's protections rather than encryption applied by us.
• Exports: where legally permitted, you may request an export before deletion.
• Derived data: derived data (such as indexes or embeddings) is deleted or disassociated when the underlying Customer Data is deleted, subject to backup rotation and legal obligations.

6A. Screen Recordings and How Long Docs Keeps Things

Screen recordings. When you record your screen with Frosty, the video is saved to your Files; a video uploaded with Upload a video in Docs, or recorded in Docs before October 20, 2026, stays in its doc. Either way it is stored in a private storage bucket with no public address. A video holds everything visible in the screen, window or tab you pick and the sound from your microphone, which can include other people's names, messages, faces or voices. It never includes your computer's own sound. A recording starts only when you click, through your browser's own picker and indicator; we do not record in the background, on a schedule or remotely.

• Who can see it: only you, until you share it, and only you can share it or keep it. Only you can delete the video; if you share the doc with the team, a workspace administrator can move the doc to Recently deleted, and its video is deleted with it after 30 days. No workspace administrator or Frosty staff member opens a private recording in the ordinary course, and we never use a recording to monitor, rank or evaluate anyone or for any employment decision.
• Public links and view counts: a public link is off for every video until the owner, or someone with Read and write on it, turns it on. With it on, anyone who has the link can watch the video, signed in or not, and read its transcript, summary, chapters, links, comments and reactions, and the page shows the maker's first name and last initial and the date. A signed-in person who has the link can also comment and react; their comments and reactions, with their name as first name and last initial, are visible to everyone who has the link, and they are deleted with that person's account or with the video. A signed-out visitor can read but not write. The link is signed with a secret key only Frosty's servers hold, so a copy of our database alone cannot open a video; the owner can copy the same link whenever they open the share sheet, resetting the link makes a new one and stops the old one, and turning the link off stops new plays at once, while a play that has already started may run on for about a minute. Frosty makes a short animated preview of the first seconds of the video so the link looks right when you paste it in a chat or an email; that preview is public while the link is on and is deleted with the video. Each video counts its views. The owner, and people with Read and write on the video, see how many times it was watched, and see which teammates watched and when; watching your own video is not counted. A person who watches through a public link is counted without a name: Frosty records a random number your browser makes, never your address, and uses it only to count one view in half an hour. These numbers are shown to no one else, are deleted with the video, and a teammate's own views are deleted when their account is deleted and included in their data export. We do not use them to rank or evaluate anyone.
• AI: a recording saved to Files is transcribed automatically so you can search it and jump to any moment, the same as any audio or video in Files (section 6B). Its sound goes to our speech-to-text provider (listed in section 3) and the transcript is kept with the file. Transcription uses your workspace's credits. Right after, a summary and chapters are written from the transcript by our AI model provider (listed in section 3); this also uses your workspace's credits, and you can edit or replace both.
• Comments and reactions: comments and emoji reactions on a video, with the name of the person who left them and the moment they point to, are visible to everyone who can watch that video, and are deleted with the video or with the person's account.
• Other people: if anyone else can be seen or heard, tell them you are recording. On a call, use headphones or tell everyone on it. The notice you read before recording says so, and an uploaded video asks you to confirm the people in it agreed to be recorded.
• Your computer: while you record, pieces of the recording are kept in your own browser for up to 24 hours so a crash does not lose it. They are deleted when the upload finishes, when you discard it, when you sign out, and after 24 hours.
• For teams that record: Frosty is the processor of your team's recordings and your organisation is the controller. A recording can show special-category data and other people's personal data, so a data protection impact assessment is likely advisable where staff record routinely, and in some countries (Germany, for example) a works council may have a say over recording tools. Staff must be told. Suggested wording for your team: "This workspace uses Frosty to record screens. A recording is saved to the Files of the person who made it, is visible only to that person unless they share it, and is never used to monitor staff."

How long Docs keeps things:

• A recording saved to Files: kept until you delete it, like any file (section 6B), with its transcript.
• A recording's video in a doc (uploaded in Docs, or recorded before October 20, 2026): 90 days from upload, unless its owner chooses Keep. The owner gets a reminder in Updates 7 days before. The text, notes and any other parts of the doc stay.
• Deleted docs: 30 days in Recently deleted, then permanently deleted with their files and recordings.
• Earlier versions of a doc: the newest 20 are always kept; older ones for 12 months.
• Activity history of a doc (who shared, edited or restored it): 180 days.
• The security access log: 90 days.
• Usage counts used to show how often a doc is opened or read by Frosty: 13 months.
• Uploads that never finish and files with no doc: 24 hours.
• A removed member's Just me docs and recordings: kept by the workspace and shown to no one, until a workspace administrator hands them to a teammate or deletes them (see section 6C). A deleted doc stays in Recently deleted for 30 days. Docs that were shared stay shared.

6B. Files and How Long Files Keeps Things

Files is the page where you find the files in your workspace: files added to a chat, files in Docs and Design, files you upload to Files, and files Frosty makes for you. A file can be opened only by the people who can open the place it came from. A file you upload to Files is private to you until you share it. We do not use a guessable link for any file.

• What we store: the file's name, type, size, who added it and when, a short history of what was done to it (ids only, never the file's text), and, for text-like files (PDF, Word, Excel, plain text, Markdown, CSV and JSON), the text taken from inside the file so you can search it and Frosty can read it when you ask. That text is held behind the same access as the file, is capped in size, and is never written to logs. A small preview picture of an image may also be kept.
• Who can see it: exactly the people who can open the file. The text and the preview follow the file.
• AI: Frosty reads a file only when you ask it to, when you send it in a chat, or when an automation you set up names it. Files you upload are never sent to an AI model on their own, with one exception: the sound of audio and video files is transcribed automatically by our speech-to-text provider (section 3) so you can search it, and that uses your workspace's credits. We do not use files to train models.

How long Files keeps things:

• Files you upload: until you remove them. A removed file stays in Recently deleted for 30 days, then the file and its text are permanently deleted.
• Files Frosty made for you: 90 days, unless you click Keep or move the file into a folder. You get a reminder in Updates 7 days before. The text and preview are deleted with the file.
• Files that belong to a chat, a doc or a design: as long as that chat, doc or design. When the source is deleted its files are deleted with it.
• Extracted text and preview pictures: for as long as their file, and no longer.
• The history of what was done to a file (who shared, renamed or removed it): 90 days.
• A removed member's Just me files: kept by the workspace and shown to no one, until a workspace administrator hands them to a teammate or deletes them (see section 6C). A deleted file stays in Recently deleted for 30 days. Shared files stay shared; 30 days after their owner leaves they go to an Ownerless list an administrator can claim.
• When the workspace or account is erased, every file, its text and its previews are deleted.

6C. When Someone Leaves a Workspace or Deletes Their Account

In a team workspace, the workspace (your organisation) is the controller of the work its members create, and Frosty is its processor. So when a member leaves or deletes their account, the work stays with the workspace and the member’s personal data is erased. In plain words, with the Help page “What happens to your work when someone leaves” at heyfrosty.ai/help/when-someone-leaves:

• Work shared with other people stays shared, and everyone who had it keeps it. It becomes owned by the workspace, administrators manage who has access, and the former member is shown as “former member”. No one is picked as the new owner automatically.
• Work the member kept to themselves (docs, designs, tables, files, folders, skills, Apps, custom modes and memory notes they wrote) is kept and shown to no one. It waits in a “Left by” list on the Hand over page, which shows administrators how many items of each kind wait, never their titles or contents, until an administrator hands them to a teammate or deletes them. Deleted work can be put back in the list by an administrator for 30 days, then it is permanently deleted.
• While it waits, an item keeps the internal account identifier of the person who left (never a name), so it can be handed over, and so the person gets back what is still waiting if they are added back to the workspace with the same account. When the person deletes their account, that identifier is replaced with a placeholder that points to no one, and nothing comes back to a new account.
• Chats the member kept to themselves are kept by the workspace and are not shown in the app to anyone, administrators included. Only the workspace owner can download them, and every download is logged. Chats that were shared stay shared. Anything a chat made, such as a doc or a file, follows the rules for that kind of item.
• Every automation the member owned gets a new owner when they leave: the person they added first at Read and write, with a workspace administrator added at Read and write, or, when nobody had Read and write, a workspace administrator (the one who removed the member when we know who that was, otherwise the administrator who joined first). People at Read only keep Read only, and the member is taken off it. The automation stops running and becomes a Draft that needs setup; its new owner is told, with the names of the apps its past runs used, and it runs again only once the new owner has connected each of those apps and turns it back on. The apps the member signed in to with their own account are disconnected when they leave, including ones shared with the team; apps connected with a company key rather than the member’s own sign-in stay connected and stay shared as they were, and an app whose kind we cannot tell is treated as the member’s own sign-in and disconnected. A shared app kept this way is then managed by the workspace’s administrators. An automation that starts on an event in an app is set up again on the new owner’s own account when they turn it on.
• Erased on account deletion: the member’s profile, settings, devices, notification choices, connected accounts and what Frosty learned about them. Run history keeps only the cost and the time of each run, without the name or the content.
• A personal workspace that only the person uses is deleted with the account, with everything in it.
• A workspace can ask us to delete work it holds, at any time, by emailing support@heyfrosty.ai from an administrator’s address. Work is also deleted when the workspace is deleted.

6D. Deleted Chats, Notes, Tables, Skills, Apps and Modes

When you delete a chat, a memory note, a table, a skill, an App or a model mode, it is not erased at once. It moves to Recently deleted on that page, where it is hidden from everyone, Frosty stops using it, and the person who made it or a workspace administrator can restore it or delete it forever.

• How long: 30 days in Recently deleted, then it is permanently deleted with everything that belongs to it (a chat's messages and files, a table's rows, a skill's versions, an App's members and data).
• Who can see it there: only people who could manage it before it was deleted, meaning its owner, or a workspace administrator for a team item (an administrator sees a chat there only if it was shared with them).
• Delete forever: the owner or an administrator can delete it at once from Recently deleted; this cannot be undone.
• Exports: the workspace export does not include items in Recently deleted. Download my data includes your own, because we still hold them.
• Deleting your account: erases your personal items at once, including anything of yours in Recently deleted; it does not wait for the 30 days. What stays with the workspace after you leave is described at heyfrosty.ai/delete-account.

7. Your Rights and Choices

Depending on where you live, you may have rights to access, correct, delete, or export your personal data, and to object to or restrict certain processing.

• Access and correction: request a copy of, or correction to, the personal data we hold about you.
• Deletion: delete your account and its data from the Profile page in Settings at any time; the steps, and what is deleted and kept, are at heyfrosty.ai/delete-account. For workspace-level data, we may require the request to come from an authorized workspace administrator or account owner.
• Withdraw consent / disconnect: uninstall the Slack app or disconnect an integration to stop new collection from that source. This does not by itself delete previously stored data, which we remove per Section 6.
• Marketing preferences: opt out of marketing messages at any time; you will still receive essential service communications.
• Opt out of sale, sharing, or targeted advertising: where applicable, you may opt out of the “sale” or “sharing” of your personal information and of targeted advertising, using our cookie controls and any “Do Not Sell or Share My Personal Information” option we provide. We honor recognized browser opt-out signals (such as Global Privacy Control) where required by law.
• Data portability: where required by law (such as GDPR), request a copy of your data in a machine-readable format.
• Authorized agents and U.S. state rights: where permitted, you may use an authorized agent, and residents of certain U.S. states may have rights to know, access, delete, correct, and opt out of certain uses. We will not discriminate against you for exercising your rights.
• EEA / UK rights: you may also object to or request restriction of certain processing and lodge a complaint with your local supervisory authority.

To exercise any of these, email support@heyfrosty.ai. After a verifiable request we will respond within the timeframe required by law (typically within 45 days, with a permitted extension where allowed). If we deny a request, you may appeal by emailing support@heyfrosty.ai with “Privacy Appeal” in the subject line.

8. Children's Privacy

The Service is intended for business use by adults and is not directed to children. We do not knowingly collect personal data from anyone under 18 (or the age of majority in their jurisdiction, if higher). If we learn we have, we will delete it promptly. Contact support@heyfrosty.ai if you believe a child has provided personal data.

9. International Users and GDPR / UK GDPR

FROST THE BRAND LLC is based in the United States and may process personal data in the U.S. If you are in the EEA or UK, we process personal data under one or more legal bases, including performance of a contract (providing the Service you request), consent (such as connecting Slack via OAuth and certain non-essential cookies where required), and legitimate interests (security, fraud prevention, and improving reliability), balanced against your rights. Where required for cross-border transfers, we use appropriate safeguards such as Standard Contractual Clauses, and we will appoint an EU/UK representative and update this Policy if required by law.

10. Slack Marketplace Compliance

If you connect Slack, Frosty accesses the following Slack data for the purposes shown:

• Messages in channels where Frosty is invited: process requests and provide AI assistance.
• Direct messages to Frosty: respond to direct interactions.
• Thread replies: maintain context for requested actions.
• User profile information: identify users and personalize responses.
• Channel information: understand context and permissions.
• Files and file metadata (when you request): process attachments and uploads or downloads.

Our commitments: we use Slack data only to provide and operate the Service; we do not sell Slack data; we do not use Slack data for advertising; we affirm Slack APIs are not used to develop, improve, or train generalized AI or ML models; and we do not train our own or any third-party foundation models on Customer Data. You can uninstall Frosty or revoke access at any time in Slack App Management; after revocation we stop collecting new Slack data immediately, and previously stored data is deleted per Section 6.

11. Changes to this Privacy Policy

We may update this Privacy Policy from time to time. For material changes, we will notify you by appropriate means (such as notifying workspace administrators or emailing the address associated with the account). The “Last updated” date reflects the most recent revision, and your continued use of the Service after changes take effect indicates acceptance.

12. Contact

Questions or requests about this Privacy Policy or our data practices: email support@heyfrosty.ai.

FROST THE BRAND LLC, 7150 E Camelback Rd, Unit 444, Scottsdale, AZ 85251, USA.