Cuttlefish runs AI across your real computer — your files, your browser, your tools — so it is built to do the least it needs to, ask before anything that matters, and leave a record you can read. This page explains exactly what it protects and how, in plain terms, and gives you a real way to report a problem.
Cuttlefish ships cautious. It can only reach what you have given it, it does the smallest version of any task, and content it reads is treated as information — never as orders it has to follow.
Reaching your folders, your browser, or a tool on your machine is a permission you grant and can take back. Cuttlefish never assumes access it was not given, and removing a connection leaves your actual files exactly where they sit on disk.
Nothing reaches an outside model or tool unless you connect it and choose to use it — task by task. Your conversation history and memories are saved to your Cuttlefish account, as the privacy page explains.
Keys for compatible on-device models use protected device storage. Cloud-provider keys are encrypted in Cuttlefish’s credential service for authorized requests. Removing a connection removes its active stored credential. Revoke the key with its provider when you need to invalidate it outside Cuttlefish as well.
When you turn repeated work into an app, it runs inside a walled-off space with no automatic reach into your computer. It only gets the specific permissions you grant it, and you can roll it back to an earlier version at any time.
Organization policy and valid permissions control changes such as sending, editing, publishing, or spending. Actions that need additional authority wait for an authorized person’s approval. An action outside the allowed limits does not proceed.
A web page, an email, or a pasted document is read as information to work with, not as instructions Cuttlefish must obey. Generated and fetched content is watched as it streams, so a hidden "ignore your rules" never quietly takes the wheel.
We welcome reports from security researchers and customers. If you believe you have found a vulnerability in Cuttlefish — the desktop app, the website, or the services behind them — please report it to us privately so we can fix it before it is disclosed.
Email us with the details below. Please give us a reasonable window to investigate and remediate before any public disclosure.
Send your finding to security@getcuttlefish.app. Keep it private until we have had a chance to investigate and ship a fix — please do not post it publicly or share it with others in the meantime.
A clear summary, the area affected (the desktop app, the website, or a service), the version or URL, steps to reproduce, and what you believe the impact is. A short proof-of-concept helps us confirm and fix it faster.
We review every good-faith report, confirm what we can reproduce, and keep you updated as we work toward a fix. We will let you know when the issue is resolved and are glad to credit you for the find if you would like.
If you make a sincere effort to follow this process — test only against your own account, avoid accessing or destroying other people's data, and give us time to respond — we will treat your research as authorized and will not pursue action against you for it.
Cuttlefish classifies every action by its effect. Reading a file is judged differently from changing one, and the same tool writing to a normal folder is treated more carefully when it targets a system location.
Looking things up, reading, searching, and summarizing happen without interruption so the work keeps moving.
Changes you can easily undo — a draft, a saved workspace, a staged edit — proceed under the permissions you have set, and ask only when you have told it to.
An action requiring approval presents its target and proposed effect for an authorized person to review. Allowed reads and preparation can run within existing permissions. Existing grants and organization policy determine the available actions; a missing required approval does not authorize a change.
Anything Cuttlefish has not been explicitly allowed to do is refused before it starts. It is an allowlist of permitted actions, not a blocklist of bad ones — so an action it was never taught is denied, never guessed at.
The keys that connect your models and tools are some of the most sensitive things you give an AI app. Cuttlefish keeps them in your operating system's password store or encrypted in its own credential service, and keeps them out of everything that does not strictly need them.
Keys for models on your own machine go straight into your computer's own secure keychain — the protected store your operating system already uses for passwords. Keys for cloud model providers travel over an encrypted connection to Cuttlefish's credential service and are stored there encrypted. Neither is ever written into a log.
The model you are chatting with and the apps you build do not receive your keys. Cuttlefish uses a credential to reach a connected service on your behalf; the secret itself stays sealed away from the conversation and from generated code.
Remove the connection in Settings to remove its active credential from Cuttlefish. Provider-side access and retained backups follow their own controls and retention policies. Revoke the credential directly with its provider if it must no longer be usable elsewhere.
Cuttlefish keeps a clear line between what lives only on your machine, what follows your sign-in, and what your organization manages — so the boundary between your own work and shared work is real, not a label.
Your files stay on your computer, and your conversation history and the details Cuttlefish remembers are saved to your Cuttlefish account. A model you run on your own machine processes the exchange there — no AI provider receives it, because there is no provider in the loop.
What lives only on your machine — local data, browser profiles, and private model connections — stays yours, while your organization's shared work, connected systems, and managed settings live alongside it under their own permissions. Joining your organization never quietly absorbs your private data.
Nothing reaches a cloud model or an outside tool unless you connected it and chose to use it for that task. You can keep sensitive work on a private local model and reach for a cloud model elsewhere — in the same workspace, the same day.
An AI app that can reach your real computer has to update itself safely. Cuttlefish checks that an update genuinely came from us and arrived unchanged before it is applied — so an update is something you can trust, not a new way in.
Each update carries a signature that Cuttlefish verifies before installing. If an update did not come from us, or was altered along the way, it is not applied. You are never silently moved onto something we did not publish.
You see what version you are on and decide when to move. Nothing about how Cuttlefish behaves — your permissions, your cautious defaults — is loosened by an update without you knowing.
The same plain, tamper-evident record that backs everyday actions means there is an honest account of what the app did and when — including the work that keeps you current. If you ever ask "what changed?", there is a real answer.
If you are evaluating Cuttlefish for a team or company, we are glad to walk your security and compliance people through the control model, the approval and proof system, and how data isolation works for your environment.
See how the governed workspace fits your requirements, and get the detail your reviewers need to sign off.
Organization policy, required approvals, and available action records also apply to connected enterprise systems. The Trust Center explains these controls and the scope of the evidence they provide.
What we collect, what stays on your machine, and how it is handled are laid out plainly in our Privacy page and our Data Processing Addendum.
The agreement that governs your use is in our Terms, and the services we rely on to operate Cuttlefish are listed in our Subprocessors register.
