Skip to content
Foxl
Download for macOS

Privacy Policy

Last updated: October 21, 2026

This policy describes how Foxl AI ("Foxl", "we") handles your information across Foxl Agent, Foxl Code and Foxl Notes, on desktop, web and mobile. It is written to describe what the software actually does. Where a product differs from the others, it says so per product rather than generalising.

1. What we collect

Account

  • Email address. Required - it is your account identity and how sign-in links reach you.
  • Display name and avatar. Optional. If you sign in with Google, Apple or GitHub we store the name and avatar that provider returns, refreshed on each sign-in unless you have set your own. A picture you set from an image link is fetched once when you save it and stored with your account, so other people's apps load it from Foxl rather than from the site you linked.
  • Provider identity. For Google, Apple and GitHub sign-in we store the provider's immutable user id, so an account cannot be taken over by someone who later controls the same email address.
  • Password. Only if you choose to set one. Stored as a PBKDF2-SHA256 hash with a per-account salt; we never store or log the password itself.

Usage and billing

  • Token counts and request counts per model. Used to meter credits and enforce rate limits. These are the same records you can see on your own usage screen.
  • Subscription tier and credit balance. Card details are handled by our payment provider; we never see or store them.

Devices and notifications

  • Push token. If you enable notifications, the token Apple or Google issues for that device, so a notification can be addressed to it. Removed when you disable notifications or delete the account, and pruned automatically when the platform reports it as no longer valid.
  • Session records. One row per signed-in device holding a coarse device description from your browser or app user agent, so you can see and revoke your own sessions.

Google account data

  • Sign in with Google. Your name, email address, profile picture and Google account ID, used only for the account fields above. Foxl keeps no Google access or refresh token from signing in.
  • Gmail, if you connect it in the desktop app. Permission to send email on your behalf, and your email address so the app can show which account is connected. Foxl uses it only to send the emails you ask it to send. It cannot read, search or delete your mail. The access tokens are stored encrypted on your computer. Foxl Relay passes the sign-in and each token refresh through to Google, because Google requires a credential we keep off your computer, and stores neither. Disconnecting asks Google to revoke the access; you can also remove it at myaccount.google.com/connections.

Foxl's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We do not use Google user data for advertising, we do not sell it, and we do not use it to train AI models.

Content, per product

  • Foxl Agent. On the desktop app, conversations are stored locally on your machine. Web and mobile can use your paired desktop or Foxl Relay. Relay model requests pass through Foxl to Amazon Bedrock, and we record usage totals. If a reply finishes while the mobile app is in the background, the relay can temporarily keep an encrypted copy so your device can retrieve it when you return.
  • Remote chat, only if you turn it on. When your computer is offline, Foxl can answer from the cloud instead. Those conversations, their attachments and the notes Foxl keeps for itself there (what you asked it to remember) are stored on our servers: in Foxl's own Amazon Web Services account, in Amazon S3 in the US West (Oregon) region, encrypted at rest with Amazon S3 managed keys (SSE-S3). Model requests go to Amazon Bedrock, as for Relay, and we record usage totals. Your computer imports these conversations when Foxl is next open on it. When you delete one of them in the Foxl app on your phone or at app.foxl.ai while your computer is away, its stored copy is deleted. A delete made on your computer, or one that reaches it because it is online, moves the conversation to its trash, which keeps the stored copy (you can restore it there). Deleting it for good (Delete permanently, Empty trash, or the trash's 7-day cleanup) deletes its stored copy too, the next time your computer is online and signed in to the account that imported it, and so does deleting for good a conversation you continued on your computer. The notes Foxl keeps for itself belong to your account, not to one conversation, and stay until they are deleted or you delete your account. Turning remote chat off stops new cloud replies and keeps what is already stored. If you delete your account, everything stored for remote chat, including the notes Foxl keeps for itself, is deleted within a few days of the account being deleted.
  • Foxl Code. Conversations, task plans and task event history are stored on our servers, because a coding task runs for minutes or hours across several invocations and has to survive you closing the app. A cloud task clones your repository onto the disk of that task's own virtual machine on Amazon Web Services, and that copy is erased when the machine shuts down: after 15 idle minutes, and at most 8 hours after it started. While a Claude Code terminal session on a private GitHub repository is open, its uncommitted changes are also saved every two minutes to that repository, as a ref (not a branch) that anyone who can read the repository can fetch, so that reconnecting can put them back; on a public repository they are not saved this way. The ref is deleted when the session ends and its work is pushed to the task's branch. If the session ends any other way (its machine is recycled and you never reconnect, a reconnect cannot put the changes back, or the final push fails), the ref stays in your repository until a later reconnect restores it and that session ends with its work pushed, or until you delete it. We keep no copy of it, and deleting the task or your account does not delete it. The coding agent's own files for the task are kept longer, in that task's AWS session storage. They include Claude Code's conversation, which contains the parts of your repository it read and the output of the commands it ran, so a reconnected task can pick up where it left off. AWS deletes that storage at the latest 14 days after the task's session was last used; reconnecting to the task or opening its files uses it again. When the Foxl Code assistant you chat with runs in our cloud, it has its own AWS session storage for your account, and the files it creates there, which can include a copy of your repository, are kept for up to 14 days after the assistant last ran, including runs it makes on its own for schedules and the autonomous loop. Deleting a task or your account does not delete either of these sooner. A task you run on your own computer clones the repository and keeps the agent's files on that computer instead.
  • Channels, DMs and shared folders. What you post in a team channel or a direct message - the text, your reactions and your mentions - is stored in our database on Cloudflare, and the other members of that channel can read it. Files you attach to a message or add to a shared folder are stored in Amazon S3 in the AWS US West (Oregon) region, and the text of a shared document is stored in our database. Members of the space or folder you shared into can read them.
  • Foxl Notes and voice input. Notes and transcripts are stored on your device. When you use Foxl Relay transcription, microphone audio or audio you import is sent directly to Amazon Transcribe to produce text. This includes voices and any personal information spoken in the recording. Foxl Relay receives session settings and usage data to authorize and meter transcription. If you save a recording, its audio remains on your device until you delete it. AI summaries send the relevant transcript text to the model service you have selected.

Foxl Relay AI services on iOS

Before first using a Foxl Relay model or speech-to-text on iOS, we ask for one permission covering both services. The dialog identifies the data sent to Foxl AI and Amazon Web Services: your message, relevant conversation history, included files and images, and note or transcript text needed for your request go to Amazon Bedrock to generate the answer, summary or translation you request. Microphone or imported audio goes directly to Amazon Transcribe to produce text. These inputs may contain personal information.

The app waits for approval before sending model content or opening an audio connection to Amazon Transcribe. Approval covers both services on all iOS devices signed in to the same account, so using the other service or another device does not ask again. Declining prevents either service from receiving your content or audio. This permission applies to Foxl-provided Relay services on iOS. It does not change the desktop app or requests handled through your own provider account.

Foxl Relay stores your account's permission, including the disclosure version, approval and update times, and a change number. The permission record contains no conversation text or audio. Signing out does not withdraw this account permission. You can withdraw it in Settings > Data controls > Foxl Relay data sharing. The app checks the account's permission before each use, so withdrawal applies before the next use on each device. If permission cannot be checked or saved, the app does not send the content or audio.

Logs

Our infrastructure provider processes request metadata, including IP address, in the course of serving and protecting the service. We keep a short-lived audit record of remote-access tunnel connections for abuse investigation.

Issue reports

When you send a report with Report an issue in the app, we receive what you wrote, the email address you give for a reply, your app version, platform and language, and, if you are signed in, your Foxl account's email address and id. The open conversation's messages are included only if you tick that box. On the desktop a diagnostic report (system information, connection state, recent logs and errors) is included unless you untick it. Keys, tokens and your account name in file paths are removed first, but please do not type passwords or keys into a report. The whole report, with everything above, is filed as an issue in Foxl's private GitHub repository so we can track the fix, and emailed to the Foxl support inbox; only the Foxl team can read either. It is not posted to Discord or anywhere public. If a bug is confirmed, a member of the Foxl team may describe it in a public issue on github.com/foxl-ai/foxl, where anyone can read it, in their own words and never with your email address, your account, the conversation or the diagnostic report. Nothing is posted there automatically. The same team member may also file a bug you post in the Foxl Discord server as a public issue there, with your message and without your Discord name.

2. What we do not do

  • We do not advertise to you. There is no advertising SDK and no advertising identifier in Foxl. We do not combine your data with data from other companies, and we do not build advertising profiles.
  • We do not put analytics in the apps. The Foxl desktop app and the Foxl apps for iOS and Android contain no analytics SDK and send no usage data. Our websites - foxl.ai, docs.foxl.ai, app.foxl.ai and code.foxl.ai - use Google Analytics to count page views, and only if you accept analytics cookies. docs.foxl.ai also counts page views with Cloudflare Web Analytics, which uses no cookies and does not identify you. See sections 3 and 4.
  • We do not sell your personal information.
  • We do not train models on your content. Foxl builds no models and trains nothing on what you write. Our hosted models run on Amazon Bedrock. Depending on the model, AWS may retain prompts and responses for safety and abuse review, including up to 30 days for models requiring human review. Bedrock does not share this content with the model publisher, including under its legacy provider_data_share setting. See Amazon Bedrock data retention.
  • Speech-to-text provider use. Amazon Transcribe may retain voice inputs to provide, maintain and improve its AI services under the Amazon Transcribe terms described in its data privacy FAQ. We do not promise zero retention by the transcription provider. Your own provider account is governed by your agreement and settings with that provider.
  • We do not store your own provider API keys. If you bring your own key, it is held on your device. When a request is made through the relay the key transits our servers in order to reach the provider, and is not written to storage or logs.

3. Cookies and similar technologies

Foxl uses cookies and browser storage for two purposes.

  • Strictly necessary. Sign-in and session storage, your preferences, and a device identifier that binds your session to this device. Foxl does not work without these, and they are not used for analytics. Your answer to the analytics question below is itself stored this way, because we need it in order to honour it.
  • Analytics, only with your consent. On foxl.ai, docs.foxl.ai, app.foxl.ai and code.foxl.ai we use Google Analytics 4, which sets first-party cookies to count page views and returning visitors. We do not load Google Analytics and we do not set those cookies until you accept them. If you decline, nothing is loaded and nothing is sent.
  • Page-view counts on docs.foxl.ai, without cookies. docs.foxl.ai also uses Cloudflare Web Analytics to count page views and page load times. It sets no cookie, stores nothing in your browser and does not identify or fingerprint you, so it does not depend on the analytics choice below.

You can change your answer at any time from the Cookie settings link in the footer of foxl.ai. One choice covers all four websites, and withdrawing it stops collection immediately.

We use no advertising cookies, and we allow no third party to advertise on our sites. The Foxl desktop, iOS and Android apps set no analytics cookie and load no analytics code.

4. Who processes your data

These are the third parties involved in running the service:

  • Cloudflare - hosting, the database, and request routing for every surface, and cookie-free page-view counts (Web Analytics) on docs.foxl.ai.
  • Amazon Web Services - Bedrock for models, Transcribe for live meeting transcription, storage for Foxl Code task workspaces, and Amazon S3 for files in channels and shared folders.
  • Model providers you choose - Anthropic, OpenAI, Google, xAI, DeepSeek and Groq. A request only reaches a provider you have selected, and is governed by that provider's terms when you use that provider directly. For Foxl Relay models, Amazon Bedrock processes the content; the model publisher does not receive it.
  • Resend - transactional email (sign-in links, receipts, and product notices you have not turned off), and the copy of each issue report sent to the Foxl support inbox.
  • Apple and Google - push notification delivery to your devices.
  • Google (Gmail) - only if you connect Gmail in the desktop app: the emails you ask Foxl to send go from your computer to Gmail, which delivers them from your account.
  • Discord - hosts the Foxl community server. Issue reports from the app do not go there; a bug you post there may be filed as a public issue as described in section 1.
  • GitHub - if you connect a repository to Foxl Code, and for issue reports: the whole report described in section 1, filed in Foxl's private repository, and, when a team member chooses to, a public issue on foxl-ai/foxl as described there.
  • Google Analytics - page-view measurement on our websites, and only if you accept analytics cookies. It receives your IP address (truncated by Google), the page you viewed, your browser and device type, and an approximate location derived from that address. It does not receive your conversations, notes, files, code, or account identity.
  • YouTube (Google) - video players in some blog posts, embedded in YouTube's privacy-enhanced mode (youtube-nocookie.com). When such a post loads a player, YouTube receives your IP address, your browser and device type, and the page the player is on; that, and anything you do in the player, is governed by Google's privacy policy. It does not receive your conversations, notes, files, code, or account identity.

We require third parties processing Relay content to provide the same or equivalent protection described in this policy, including confidentiality, restricted access and secure transmission, under their applicable service terms and data protection commitments. AWS describes these contractual and technical protections in its data privacy commitments. The service-specific uses and retention described above remain applicable.

5. Recording other people

Foxl Notes records whatever your microphone can hear, which in a meeting includes other participants. Laws on recording conversations differ by country and by state, and in many places every participant must consent. You are responsible for having that consent before you record.

6. Retention

  • Account and profile data: kept while the account exists.
  • Usage and credit records: kept for billing history and dispute resolution.
  • Foxl Code conversations and task history: kept until you delete the task or the account.
  • Foxl Code cloud task files: the repository clone is erased with the task's virtual machine, after 15 idle minutes and at most 8 hours. The coding agent's files for the task, including Claude Code's conversation, stay in AWS session storage for up to 14 days after the task's session was last used, whether or not the task or the account has been deleted.
  • Foxl Code assistant files: what the assistant creates in its own AWS session storage, which can include a copy of your repository, stays for up to 14 days after the assistant last ran, whether or not the account has been deleted.
  • Channel and DM messages: kept until the author, or an owner or admin of the channel, deletes them. They do not expire. Deleting a message removes its text at once and deletes the files its author attached; an empty placeholder stays so replies keep their thread.
  • Shared files and documents: kept until deleted. A deleted file, including a deleted message's attachment, stops being available to anyone at once. A deleted workspace can be restored with its files for 7 days. Deleting a shared document removes its text at once.
  • Saved meeting audio: kept on your device until you delete the recording. Amazon Transcribe's handling of streamed audio is described in section 2.
  • iOS Relay permissions: kept with your account. Withdrawal disables sharing and retains a change record so another device cannot restore an older approval. Deleting the account deletes this record.
  • Push tokens: removed when notifications are disabled or the token stops working.
  • Tunnel audit records: retained briefly for abuse investigation, then pruned.
  • Issue reports: kept in the private GitHub issue and the support inbox, and in a public issue if one was filed, until we delete them. Deleting your account does not remove them; write to support@foxl.ai to have a report removed.

7. Your choices and rights

  • Export. Settings has a data export that returns your account data as JSON: your profile, credit and usage records, and your Foxl Relay data-sharing permission. It does not include channel or DM messages, shared files or shared documents.
  • Delete. Settings has account deletion. It removes your account and the records keyed to it, including your channel memberships, reactions and mentions and the folders and files in your Personal space. Deletion is permanent. Some records are not deleted with it, because other people or a workspace depend on them: messages you posted in channels and DMs, and files and documents you added to a team space, stay with that space for its other members; a workspace keeps its audit log and the records of your huddle time and active days that it was billed for; reports other people made about your messages stay with our moderation records; and if you unsubscribed from email, your address stays on the unsubscribe list so it is not mailed again. The AWS session storage of Foxl Code cloud tasks and of the Foxl Code assistant expires as described in section 6.
  • Email. Product notices can be turned off, and marketing email is off unless you explicitly turn it on. Every marketing email carries a one-click unsubscribe that works without signing in. You can manage this at relay.foxl.ai/email/preferences using the link in any email we send.
  • Notifications. Each notification category has its own switch in Settings, and marketing notifications are off unless you turn them on.
  • Analytics. Nothing is collected until you accept, and you can withdraw at any time from the Cookie settings link in the footer of foxl.ai. One choice covers all four websites. Withdrawing stops collection immediately rather than at the end of the visit.
  • Access and correction. Email us and we will help. If you are in a jurisdiction with statutory data rights, they apply.

8. Security

  • HTTPS/TLS for everything in transit; encryption at rest in the database.
  • Short-lived access tokens with rotating refresh tokens, and per-device sessions you can revoke.
  • TLS between the web or mobile app, the relay, and your own desktop. The relay stores none of that traffic, but it can read the messages it routes - it is a trusted-service hop, not an opaque pipe. Run the desktop locally with remote access off and no relay is involved at all.
  • Passwords hashed with PBKDF2-SHA256 and a per-account salt, never stored in plain text.

No system is perfectly secure. We aim to be honest about the boundaries rather than promise more than software can deliver - see the security documentation for where each product keeps its data.

9. Children

Foxl is not intended for children under 13, and we do not knowingly collect their information.

10. International transfers

Our infrastructure is globally distributed and our model and transcription providers operate in the United States. Using Foxl involves transferring your information to those facilities.

11. Changes

We will update this page when the product changes, and will tell you about material changes by email or in the app.

12. Contact

Questions about privacy, or a request about your data: support@foxl.ai.