Security: where your project lives and what leaves your machine
The short version: your project is a folder on your own disk and the game runs locally on Godot. Your API keys are kept in your operating system's keychain, and the ones that make pictures, 3D or sound pass through our server without being stored. Your Claude or ChatGPT sign-in stays with Claude Code or Codex, and the AI runs scripts on your computer while it builds. The app is closed source, so this page says what it does in terms you can check. It runs on Windows, macOS and Linux, on the official Godot engine.
AppImage, x86_64. Ubuntu 22.04, Debian 12, Fedora 39 or newer.
Intel or AMD Chromebook, with Linux turned on.
Your project is a folder on your disk
Flockbay is a desktop application for Windows, macOS and Linux. When you make a project, the project is a folder on your disk: a Godot project, which the app ships with a copy of Godot to run. There is no streaming, no remote rendering and no build queue, so your game itself runs entirely on your machine.
Nothing uploads that folder unless you ask: publishing it to your own GitHub repository, or sharing a playtest link. Otherwise you can copy it, back it up or open it in stock Godot like any other folder.
The app is closed source, and most of it can be checked anyway
What Flockbay writes into your project is ordinary Godot files: GDScript or C# scripts, scenes and resources, and the models, pictures and sounds it makes, all readable in any text editor or in the same folder in stock Godot. Godot is open source, and the copy the app ships is the official engine, not a fork.
The rest of this page is the part you cannot read in a project folder: where your sign-ins and keys are kept, what reaches our server, what the AI runs on your computer, which servers the app talks to, and how you can tell an update is ours. Each answer is something you can look at on your own machine.
Your Claude or ChatGPT sign-in stays with Claude Code and Codex
Sign in with Claude runs Claude Code's own sign-in in your browser, on Anthropic's page. Claude Code keeps the result in its own files, and Flockbay never reads them. Flockbay asks Claude Code three things: whether you are signed in and on which plan, which models it offers you, and how much of your plan's usage limits is left. On Linux it also reads Claude Code's settings file, to see which update channel you follow. Install skills and hooks, in Connect your agent, writes Flockbay's skills into your agent's own settings, and for Claude Code three hooks too, which then run in every Claude Code session on that computer.
Sign in with ChatGPT runs the sign-in of Codex, the OpenAI engine the app ships, on OpenAI's page. Its token is kept in a folder of Flockbay's that only your user account can read, and Flockbay reads your email address and plan from it to show which account is in use.
Neither sign-in is sent to Flockbay's server. A chat on one goes from your computer to Anthropic or OpenAI.
More on this: Cost per wishlist: how to measure it and what is normal
Your Flockbay and GitHub sign-ins sit in your credential store
Your Flockbay sign-in, a guest account's included, is kept in Windows Credential Manager, the macOS Keychain or the Linux Secret Service, or in a file encrypted to your Windows account if Credential Manager refuses it. It goes only to Flockbay's server.
Connect GitHub signs in with GitHub's own device code, on GitHub's page in your browser. The token is kept the same way, and the app sends it only to GitHub, when it pushes, pulls, clones or lists your repositories. It never reaches Flockbay's server.
More on this: Boosting a post or running a campaign: which for your game?
Your API keys sit in your keychain, and three kinds travel with a request
A key you add in Connectors is kept in Windows Credential Manager, the macOS Keychain or the Linux Secret Service. If Windows refuses to store it there, it goes in a file encrypted to your Windows account instead. The app never shows a key back in full, only its last four characters. While a turn runs, a picture, 3D or sound key is also copied into a private file in the app's data folder, where the tool that makes the request reads it; that file is deleted when the turn ends, or by the next turn if the app closed in the middle of one.
An OpenAI, Anthropic or DeepSeek key goes from your computer straight to that provider, and so does an OpenRouter key when it runs a chat. When a key makes something, an OpenRouter key a picture, a Tripo key a 3D model or an ElevenLabs key a sound, it travels with that request to Flockbay's server, which calls the provider on your key and keeps no copy of it, in a database or in a log.
Whichever key you add, make it a separate key with a spending limit set at the provider. That caps what any tool can spend on it, ours included.
A Steamworks Financial Web API key you add in Connectors for exact wishlists is kept the same way, one per computer, with a key of its own only for a game outside that key's Financial API Group. The app sends it only to Steam's partner API, from your computer, and asks only for the wishlist report; the days it reads stay in the app's data on your computer, and neither reaches Flockbay's server.
The AI runs code on your computer while it builds
To build and test your game, the AI runs scripts in it, in the Godot editor and in Blender, as your user account. Except in Claude's Ask before edits, Flockbay's tools for that run without asking, and the scripts they run are not held to the game's folder. It is how the AI plays what it made before it hands it back.
What asks first depends on the chat's Permissions menu. On Claude, a new chat runs Flockbay's tools and edits files in the game without asking, and asks before other commands as Claude Code's own accept-edits mode does; Ask before edits asks before every change, Flockbay's tools included; Full access asks for nothing, anywhere on the computer. On ChatGPT, unless you pick Ask before edits, and on the hosted AI and an API key, the AI's own shell commands run without asking, can use the network, and can change files only in the game's folder and the home folder the app gives its tools; Full access on ChatGPT lifts that limit. Your own Claude Code settings can allow more than any mode does.
The AI can also read the web and download a file from a public address when it brings in an asset it found.
More on this: What an AI can do of a game publisher's job
What reaches Flockbay's server
On the hosted AI, free or on a plan, your messages and the project context the AI needs go to Flockbay's server, which passes them to the provider behind the model, named in the privacy policy. Flockbay keeps the text of each message you send to the hosted AI for 90 days, then deletes it, and deletes it sooner if you delete your account. Building needs the connection; playing what you built does not.
On your own Claude, ChatGPT or API key, the conversation goes to that provider instead, and your sign-in and the key that runs your chats never reach Flockbay's server. What still reaches it is your first message in a new game, read once by a hosted model to tell whether it is 2D or 3D, and the request behind anything Flockbay makes for you: a picture, a sound, a voice-over, music or a 3D model. A character the modeler builds is sent to the server when it gets its walk and idle animations, and comes back with them.
The app also records what happens in it: a screen opened, a message sent, Play pressed, something failing and with which error. Those events carry an id for the install, your account when you are signed in, the app version and operating system, and, when the app opens, the city your connection comes from. They carry no prompt, no reply and no file contents. The only text of yours in them is a note you choose to add when you rate a chat or report something. Sign-in events name the kind of Claude or ChatGPT plan, and once per install the app reports whether Claude Code on this computer is already signed in and on which plan, and whether a Codex sign-in file exists, without opening it. The app-open event also carries the key of the website visit the app was downloaded from, and the first launch can open a flockbay.com page in your browser for the same reason: to match an install to its download and to the ad that led to it.
If you connect an ad account in Connectors, you sign in with Meta, Google, TikTok or Reddit in your browser and give Flockbay's ads provider access to run campaigns and read their results on that account. Flockbay's server keeps the campaigns you draft and launch, and their daily spend, impressions and clicks. Ad spend is billed by the ad platform to your ad account, and Flockbay never handles it. A Steam store page you link is kept against the game, and its public numbers are read once a day: followers, reviews and players.
More on this: Flockbay vs Orca Engine, what happened to Orca, and a free alternative
The servers the app talks to
Besides Flockbay's own server, the app connects to the hosts below, each for the reason beside it. Claude Code and Codex contact Anthropic and OpenAI themselves, as they do in a terminal, and the AI may fetch a page or a file from any public web address while it researches or brings in an asset.
api.flockbay.com Flockbay: sign-in, the hosted AI, generation, the asset library, playtests, updates, export templates, usage events
<account>.r2.cloudflarestorage.com playtest builds and sessions, through links the server signs
flockbay.com your account and sign-in, and the page the first launch opens, in your browser
api.anthropic.com an Anthropic key's chats, and checking the key when you add it
api.openai.com an OpenAI key's chats, and checking the key when you add it
api.deepseek.com a DeepSeek key's chats, and checking the key when you add it
openrouter.ai an OpenRouter key's chats, and checking the key when you add it
openapi.tripo3d.ai, api.elevenlabs.io checking a Tripo or ElevenLabs key when you add it
github.com, api.github.com Connect GitHub, and pushing, pulling and cloning your own repositories
kenney.nl free asset packs the AI imports
download.blender.org Blender, the first time a tool needs it
builds.dotnet.microsoft.com .NET, the first time a C# project needs it
registry.npmjs.org, formulae.brew.sh the latest version of a Claude Code you installed yourself
api.github.com the Phantom Camera add-on, checking for its own updates when the editor loads it
store.godotengine.org the Asset Store, in the Full editor view
www.youtube-nocookie.com, i.ytimg.com videos and their thumbnails on the Learn screen
checkout.stripe.com, billing.stripe.com paying for a plan, in your browser
www.remotion.pro a usage report when you export a video
partner.steam-api.com your Steamworks wishlist report, on your own keyAn update is signed, and installs when you press Update
The app checks for a new version and downloads it in the background. It installs when you press Update; a version too old to keep working asks you to update before it carries on.
Each update is described by a manifest signed with a key built into the app, which names the installer's exact size and SHA-256, and the app refuses an installer that does not match. On Windows the installer is also code-signed by 9560-9970 Québec inc., the company behind Flockbay: right-click it, open Properties, and the name is under Digital Signatures. On a Mac the update is a signed, notarized disk image: the app checks it against the SHA-256 the manifest names, then checks that the new app inside is signed by the same developer as this one.
Claude Code comes inside the Windows app as Anthropic publishes it. Codex is built from OpenAI's open-source code at a pinned release, with Flockbay's own changes to its Windows sandbox and file handling. In the Windows app both change only when the app updates. The Mac app runs the Claude Code you installed, or installs Anthropic's package with Homebrew, and ships Codex as OpenAI signs it. On a Mac, Update puts the new app in place after Flockbay quits, or opens the disk image in your browser when the app cannot replace itself. On Linux, the app tells you when a new AppImage is out, and you download it from flockbay.com.
You can check the current Windows installer yourself. Its file name, its SHA-256 and the address of its signed update manifest are at api.flockbay.com/v1/windows/app/version, and the manifest is signed with the Ed25519 public key 0ef72ed5b6af4b0d72897b6c94f8c13b269c319e43bcf72415b0bfc343e85ab4.
A game someone shares with you runs like any game you download
A playtest link plays another creator's build on your computer. Its files are checked against what was uploaded, so you get exactly the build they shared, but a Godot game's scripts can do what any program you run can do. Open links from people you trust, as you would any download. While you play, errors, frame times and your inputs, never what you type, are recorded for the person who shared it, and clips, a video of the session or your microphone only if you say yes to each.
Tell us what you find
If you find a security problem, in the app, in the website, or in how something is handled, email support@flockbay.com. The same address is in flockbay.com/.well-known/security.txt. Flockbay is early software, and the useful thing to do with an early report is fix it, not manage it.
Questions
- Is Flockbay open source?
- No. Godot is, and so is everything in your project. The app itself is closed source, which is why this page says what it does with your sign-ins, your keys and your computer in terms you can check.
- Is my game project stored on your servers?
- Not unless you ask. The project is a folder on your own machine, and Flockbay keeps no copy of it. Publishing a game to GitHub pushes it to a repository on your own GitHub account, and the app keeps your GitHub sign-in in your operating system's credential store, not on Flockbay's server. Sharing a playtest link uploads a build for your testers. Keep your own copies of anything you cannot afford to lose.
- Can Flockbay see my Claude or ChatGPT password?
- No. You sign in on Anthropic's or OpenAI's own page, in your browser, and the sign-in stays with Claude Code or Codex on your computer. Flockbay's server never receives it.
- Does Flockbay keep my API key?
- Only on your computer: in your operating system's keychain, or a file encrypted to your Windows account if Credential Manager refuses it, and, while a turn runs, in a private file the app deletes afterwards. A key that makes pictures, 3D models or sound passes through Flockbay's server with each request, and the server keeps no copy of it.
- Does my game phone home when someone plays it?
- An exported game sends nothing: it runs on Godot like any other. Played through a playtest link in Flockbay, it records errors, frame times and the tester's inputs, never typed text, plus clips, a video of the session or the microphone only if the tester says yes, and sends them to the person who shared it.
- Can I use it on a machine with no internet?
- You can play what you have already built. You cannot build, because the AI and asset generation come over the network.
- Do you store payment details?
- No. Building is free to start and needs no card. A paid plan is paid on Stripe's own checkout page, which holds the card, and Flockbay never sees the card number.
Flockbay is free to download for Windows, macOS and Linux.
Download Flockbay free