Data-flow sheet · last reviewed 7 October 2026 · wording updated 16 October 2026
Security and data flow. One page your compliance officer can file.
Written against the code in today’s build, not against a brochure. Where something is not built yet, it says “not on ANVE yet”.
01
What stays on the box
Meeting audio, transcripts, minutes and confirmed actions.
Your documents, the search index built from them, and the private GPTs that answer from them.
Chats, drafts, finance records and the record of AI use.
All of it in one database on the box. Full-disk encryption and secure boot are part of the appliance image, which is not on ANVE yet.
02
What can leave the box today, and how you control it
ANVE’s own software sends no usage data to ANVEAI. In today’s build these are the only paths out, and each is visible:
Podcast narration: the script is sent to a cloud voice service for the audio. Don’t use podcasts and nothing is sent. A local voice is not on ANVE yet.
Cloud models: only if an administrator adds a cloud provider, and answers from them are labelled. A policy that blocks confidential data from cloud models is not on ANVE yet.
The research app’s optional online source lookup.
Connectors: only if an administrator approves one, for example to Google Workspace or Zoho. A connector sends that service only what it is asked to fetch or send, and every call is logged on the box. Ready-made Google Workspace and Zoho connectors are not on ANVE yet.
Downloads of models and software during setup.
03
Who can see what
Every person signs in with their own account.
Meetings are visible to their owner; documents are private or shared with the office.
Research and Design are each one shared workspace for everyone an administrator gives access to; presentations are kept per person.
Today there are two roles, administrator and user. Teams, finer roles and single sign-on are not on ANVE yet.
04
The record of AI use
Every model call is logged on the box with the person, the app, the model, and whether it ran locally.
Every confirmed meeting action records who confirmed its owner, and every action keeps the quote it came from.
Tools an agent can use must be approved by an administrator; a tool that changes is switched off, and every tool call is logged.
Not on ANVE yet: a tamper-evident register, export and retention settings, and one-click AI-use statements for courts and regulators.
05
Updates
Today we install updates on site. Signed update packages you can apply offline, by USB, are not on ANVE yet. ANVE does not update itself over the internet.
06
If ANVE shuts down
Your box keeps working.
Every order includes a perpetual licence for the software delivered with the unit.
There is no remote kill switch.
07
Physical controls
Our own sealed unit, now in design, adds two physical switches: one that cuts the network and one that cuts the microphones, each with a light you can see from across the room.
08
What is not claimed
No certifications yet. Designed for readiness is not the same as certified.
Government sales in India also need BIS/CRO registration and a GeM listing; neither is done yet.
No sealed ANVE unit exists yet. The software runs today on a development machine.