Security
Built to pass the review you are about to run.
The questionnaire answers, in one table. Forward this page.
| Who is behind it | OptiFlume is a small team founded by Raghav Joginipally. Security questions go straight to the engineers who build it: support@optiflume.ai. |
|---|---|
| Where it runs | On the developer's Mac, in every tool it supports: Cursor, Claude Code and Codex, in VS Code and the terminal. Routing decisions need no server: every one is made locally. The network calls are sign-in and the plan check, updates, the price and compatibility lists, and the optional usage report, each described under Data in transit. |
| Data in transit | Sign-in and a plan check up to twice a day (the Mac's session token in, a signed license out), an update check every few hours that installs only verified, Apple-notarized updates, a signed daily compatibility list, and a daily usage rollup of counts only, on by default and switchable off. These go over HTTPS to optiflume.ai; update packages download from get.optiflume.ai. A signed daily list of Cursor's current model prices; when Cursor offers a model no list covers, the Mac reads Cursor's public price page (cursor.com/docs/models-and-pricing.md), at most once a day. The local models (about 1 GB) download once from get.optiflume.ai, or huggingface.co as a fallback. |
| Data at rest | Under ~/.optiflume on the developer's disk: routing log, code index, session state, working-memory notes. Readable plain text and SQLite. The full list of what the installer adds, including one PATH line in the shell profile, is in What is stored where (/docs/data). |
| Prompt and code content | Never transmitted by OptiFlume. Cursor, Claude Code and Codex still send the prompt to the model, as they always have. The routing log keeps the first 40 characters of each prompt locally for the developer's own analytics. |
| Credentials | OptiFlume holds no model-provider keys and never sees Claude or ChatGPT credentials or API keys. Cursor, Claude Code and Codex keep their own sign-ins. The Mac stores only its OptiFlume sign-in session, readable by the user alone. |
| Licensing and the local bridge | Licenses are Ed25519-signed and verified on the Mac. The Cursor companion extension listens only on 127.0.0.1 and accepts requests only with a per-session token that only the user can read. |
| Failure mode | Fail-open. Any error in any hook results in the prompt going through unchanged on the selected model. |
| Secret handling | The Guardian: files that look like secrets, and personal details, card numbers and bank details, are redacted or blocked before they reach a model. Destructive shell commands are warned or blocked. Both are logged locally. |
| Automatic switching | In Cursor, finishing an automatic switch needs macOS Accessibility permission for Cursor; organizations that rule this out can run suggest-only mode, which does not. Claude Code and Codex need no extra permission. A switch never changes the developer's saved default model. |
| Updates | The install script verifies the package's SHA-256 before installing, and optiflume doctor checks every shipped file against its checksum. Update notices and the pause list are signed documents, so a breaking Cursor version can have automatic switching paused the same day, without a release. |
| Uninstall | One command (optiflume uninstall) removes the program and everything it added for Cursor, Claude Code and Codex, and restores editor settings; settings and logs stay in ~/.optiflume. With --purge it also deletes that local data. |
| Reporting a vulnerability | Email support@optiflume.ai with "Security" in the subject; we reply within two business days. Also published at /.well-known/security.txt. |
Need a signed copy, a data-flow diagram, or a call with one of the engineers who build it? support@optiflume.ai