1. Who this policy covers
This policy applies when you visit frockbot.com, use the hosted FrockBot app at bot.frockbot.com, or use a FrockBot desktop client with those services. “FrockBot”, “we”, and “us” mean the service operated by Tim O'Connell.
FrockBot is also open-source software. If you run your own copy, the person operating that copy is responsible for its data practices; this policy does not describe their deployment.
2. Information FrockBot handles
Sign-in and profile information
FrockBot uses Google sign-in. We receive the information needed to identify you and create your FrockBot user, such as your Google account identifier, name, email address, profile image, and sign-in status. Authentication records may include encrypted OAuth tokens, session tokens, sign-in dates, IP address, and user-agent details.
The beta waitlist
If you join the beta waitlist on frockbot.com, we keep your email address, when you joined, and the first job you said you'd hand off, if you told us. We use them to decide when to invite you and to send you one email when your invite is ready, and for nothing else. Your entry is removed when you first sign in, or when you ask us to remove it.
Your bots, sessions, memory, and files
The hosted app stores the content you provide and the records it needs to make bots persistent. This can include bot identifiers and configuration, your inputs, ordered session events, model requests and responses, tool calls and results, routines, standing memory, and files you or a bot add to memory. Memory content is split into chunks and converted into numerical embeddings so relevant material can be found later.
Messages on your Mac
Messages access is optional. When you enable it in your account and consent in the FrockBot Mac app, requested message content, participant details and attachments may be sent from your Mac to FrockBot’s cloud and the AI providers used by your bots. Reading history requires macOS Full Disk Access; sending requires Automation permission and your approval of the recipient and exact text. The Mac app stores its pairing token in Keychain and local send receipts to prevent duplicate sends after interruptions.
Withdraw consent, disable the account setting, sign out, quit the Mac app or revoke its pairing to stop future access. This does not delete content already shared into conversations or processed by providers; the retention and deletion practices below apply.
Technical and support information
We may handle request and device details needed to deliver, secure, and troubleshoot the service, including IP address, browser or app details, timestamps, authentication state, and error or diagnostic information. If you contact us, we handle your contact details and whatever you include in the correspondence.
3. How information is used
We use information to:
- authenticate you and keep your sessions working;
- run bots, preserve session history, search memory, and store files;
- send requested material to models and tools and return their results;
- operate, secure, debug, and improve FrockBot;
- respond to questions, privacy requests, and disputes; and
- comply with applicable law and protect users, FrockBot, and others.
4. Hosted FrockBot and Cloudflare
The FrockBot app runs on Cloudflare. Its current hosted architecture uses Cloudflare Workers and Durable Objects to run the app and keep bot session state, D1 to store authentication records, R2 to store persistent memory files and application artefacts, Vectorize to index memory embeddings, and Workers AI to create those embeddings. Cloudflare therefore processes hosted-service information on our behalf as part of providing this infrastructure.
These hosted stores are separate from data held by an optional desktop integration. Using the website alone does not give FrockBot access to arbitrary files on your computer.
4a. Deploying FrockBot to your own Cloudflare account
If you use frockbot.com/deploy, you sign in with Cloudflare and choose to install FrockBot in your own Cloudflare account. With your permission, the page uses Cloudflare’s API to check that the account can run FrockBot (briefly creating, then deleting, a test Worker named frockbot-plan-check) and to create the install: its Workers and container, R2 buckets, a search index, a workers.dev address, a Zero Trust team if you don’t have one, and Cloudflare Access applications that let only your email sign in. Your bots and their data then live in your account, not ours.
Your Cloudflare sign-in token is kept on our servers, never in your browser, only while you are signed in to the page (at most twelve hours) or while a deploy you started is running. After that it is deleted and revoked. To show your installs and update them later, we keep a short record of each one: its name, the Cloudflare account’s ID and name, its workers.dev address, your email, the release it runs, its Access team and audience, and when it was created and updated. We keep no secret from your install. Ask us to remove those records at any time.
5. AI models and tools
A bot may send information needed for a turn to an AI model provider. Depending on your setup, that can include instructions, relevant session history and memory, your input, tool descriptions, and tool results. A configured OpenAI-compatible provider receives requests at the endpoint selected for that desktop runtime. The provider handles that information under its own terms and privacy practices.
In the hosted service, Cloudflare Workers AI receives memory text to produce embeddings used by memory search. Installable packages and tools can introduce additional data flows; review a package and its configuration before enabling it.
6. Optional desktop and Fly Sprite integration
Desktop FrockBot can optionally be configured with a Fly.io Sprite, a remote persistent computer. When you enable it, the desktop-hosted integration uses the configured Fly Sprites token and sends commands and browser actions to Fly. The Sprite can retain a bot's workspace, files, browser profile, standing memory, and a mirrored session record on its persistent filesystem. Its browser can also communicate with sites you direct it to.
Sprite storage is not the same store as hosted R2, Vectorize, or Durable Object data, and the repository does not automatically synchronise those stores. Local desktop settings, selected folders, clipboard content, and notifications are handled by the desktop and its operating-system permissions unless a feature, package, or your instruction sends that information to the hosted service, an AI provider, a Sprite, or another destination.
9. Retention and security
We keep information for as long as it is needed to provide and secure FrockBot, maintain persistent bots and sessions, meet legal obligations, and resolve disputes. What is needed depends on the type of information and how the service is used. You can contact us about deletion; we will assess requests under applicable law and any operational or legal requirements.
We use technical and organisational safeguards appropriate to the service, including access controls and encryption of stored OAuth tokens. No internet or storage system is completely secure, so we cannot guarantee absolute security.
10. Your choices and privacy rights
You choose what content to give a bot and whether to enable packages, model endpoints, or the Fly Sprite integration. Depending on applicable law, you may have rights to ask for access to or correction of personal information, or to make a privacy complaint. Email us to make a request. We may need to verify your identity before acting.
11. Children
FrockBot is not designed for children who cannot lawfully consent to the handling described in this policy. A parent or guardian who believes a child has provided personal information should contact us.
12. Changes to this policy
We may update this policy as FrockBot changes. We will publish the updated version here and change its effective date. Where required, we will provide additional notice or seek consent.
Questions or requests
13. Contact
Contact the operator, Tim O'Connell, at privacy@frockbot.com.