← Back to home

Security

How Flowviant handles access, credentials and deletion.

Last updated October 20, 2026

Where it runs

The app runs on Cloudflare Workers, with D1 for its database, R2 for files and Durable Objects for project documents. Other providers, including email and error reporting, are listed in the Privacy Policy. Hosted machines, when available, run on Amazon Web Services. Hosted availability remains disabled pending release verification.

Encryption

  • Connections. Connections to Flowviant use TLS.
  • Stored data. Encryption at rest for the database and files is provided by Cloudflare's platform. Flowviant's servers can read stored conversations, diffs and files.
  • Machine credentials. Machine credentials are verified against SHA-256 hashes. Copies kept so an owner can reveal them are additionally encrypted by Flowviant with AES-256-GCM.
  • Other credentials. CLI session tokens, invite links and webhook secrets are stored as hashes. A preview password is shown once, then retained only as a hash; live preview signing secrets remain readable by the servers that sign grants.

Sign-in

Sign in with an emailed code, an emailed link, Google or GitHub. Flowviant accounts have no passwords. Google and GitHub access, refresh and identity tokens returned at sign-in are not kept.

Access

Membership belongs to each project, with two roles: owner and editor. Project requests check membership and the permission needed for the action. An invitation to one project grants no access to another.

Removing a person ends their open Terminal tabs and New task chats and revokes their CLI session tokens. A machine they connected keeps serving the project until an owner disconnects it in Project settings › Machines.

Your machine

On a machine you run, the daemon runs under your operating-system login with a project credential an owner can revoke. Your repository stays on that machine; Flowviant keeps no copy of it and holds no credential for your git host. Your coding CLI uses your own login, which Flowviant never receives. Opened diffs, conversations, traces and artifacts can contain code and are relayed to Flowviant as described in the Privacy Policy. Hosted repository access and AI accounts are different and are described there.

Who can run work on your machine

A connected machine runs the work its project asks of it. Any member of the project, owner or editor, can open a Terminal tab or start an agent there. That CLI runs under the daemon's operating-system login and, by default, neither asks before each command nor runs in a sandbox (Claude Code with --dangerously-skip-permissions, Codex with full access). It can read and change anything that login can, run programs, reach the network and push with that login's git credentials. Invite only people you would give a shell on that machine.

Flowviant is inside that boundary too. The daemon carries out the work api.flowviant.com hands it and does not check for itself who asked: the server decides which member a request came from. Anyone able to change Flowviant's servers could send work to a connected machine in any member's name, and change what the app shows about it. The daemon also installs the version Flowviant's servers name. FLOWVIANT_NO_UPDATE=1 stops routine updates, but a daemon below the minimum version the server sets updates itself anyway. The Windows app updates itself from releases Flowviant signs.

What limits this today is on your side of the connection:

  • A dedicated operating-system user. Run the daemon under an account that owns only the checkout and ~/.flowviant. This is the one real boundary: work on the machine reaches only that account's files and logins.
  • FLOWVIANT_SAFE=1. Replaces the default with a short permission list for Claude Code and a workspace-write sandbox for Codex. The programs on that list can still run arbitrary code, so it narrows what a confused agent reaches for; it is not a sandbox. Antigravity has no such setting.
  • Branch protection on your git host. If the machine's git login cannot change it, it can require your review before anything the machine pushes reaches a protected branch.
  • Stopping the daemon. A machine with no daemon running takes no work.

Flowviant staff

Flowviant staff do not open a project, read its board or conversations, or send work to its machine unless someone on the project invites them. An invited staff member joins like anyone else: listed among the project's members, where an owner can remove them. Flowviant's internal console shows an account's details and plan settings, the names of the projects it owns and who is on them, and nothing inside a project. This is a policy, not a technical limit: the section above says what Flowviant's servers can do regardless.

Deletion

Deleting a project removes its database records, stored files and project document. Account deletion also removes the projects that account owns. If a cleanup step fails, the project or account record stays and the request reports that deletion is incomplete, so it can be retried. Hosted machines must be confirmed terminated before their project or account can be deleted.

Reporting a vulnerability

If you believe you've found a security issue, email security@flowviant.com with details and steps to reproduce. Please give us a reasonable opportunity to address it before any public disclosure. We will not pursue action against good-faith research that respects user privacy and avoids service disruption.

The reporting contact and policy are also published in security.txt.