Trust and safety
Agents do the work. People stay in charge of it.
What agents may do, what they never do, where your code goes, and what your teammates and Vixentio can see.
People decide what agents may do
Vixentio’s own guard checks every action an agent wants to take, on a Mac or in a cloud workspace. A permission mode decides what may run without asking; it never widens what’s allowed at all.
Always Ask
Every edit and every command asks first.
Auto
Edits inside the project and its own safe commands run; anything else asks.
Bypass Permissions
Nothing asks, and everything below is still refused. Off for requests from others unless a Mac’s owner turns it on.
Never, in any mode
- Git or GitHub writes from the shell
- Force pushes, history rewrites or deleting branches
- Merging without passing checks
- Recursive deletes, or dropping a database
- sudo and system changes
- Piping a download into a shell
- Publishing or deploying
- Writing outside the project, or inside .git
- Reading .env files, private keys or credentials
Commands are read and parsed, not matched as text, so another spelling of the same thing is refused too.
Nothing ships without a person
- Review: The team reviews versions of the change with before-and-after pictures and the project’s checks. Nobody approves their own result.
- Accept: The person whose run produced the change accepts it. Until then, Undo removes only Vixentio’s own change.
- Publish: A Publish step pushes the change’s own branch and opens a pull request. A merge happens only once checks pass.
Where your code goes
Your Mac
Agents work in a project folder you authorized, under your own Claude Code sign-in. Your code stays in that folder; teammates see progress, preview pictures and the review, not the code.
A teammate’s Mac
Only when its owner turns on Share This Mac as a Host. The Mac connects outward and never opens a port, and its owner decides who may start runs and in which modes.
A cloud workspace (rolling out)
Off until the team’s owner turns it on for a project. One short-lived machine per run, in the United States, deleted when the run ends. It gets a token for one repository only, and no key is ever stored inside it.
What your team sees
By role
Viewers follow, commenters add guidance and reviews, editors start runs, owners manage the team. The server checks the role on every action, so removing someone takes effect at once.
Content-light by default
Live previews share the picture, its route and its width. Run updates carry steps and counts, not code or commands.
Opt-in, never by default
Sync, sharing a Mac as a host, cloud workspaces and sharing a Terminal session (rolling out) all start switched off.
Your data
Local-first
Screenshots, Boards and Notes are stored on your Mac and work offline. An account is optional for working on your own.
No training on your content
Our AI service keeps usage records, never the content of prompts or answers. Anthropic processes requests under terms that don’t allow training on your content.
Secrets removed
Keys and tokens are removed before anything leaves your Mac or a cloud workspace, and checked again on our server.
Plain about encryption
Sync is off until you turn it on, and it isn’t end-to-end encrypted. Accounts and synced documents are hosted in the United States, encrypted in transit and at rest.
Go deeper
Security questions or a review for your team: sales@vixentio.ai. To report a vulnerability or anything else: support@vixentio.ai.