Heyno Government

Security and Data Handling

How a Heyno Government deployment stores your data, what never leaves your network, and how access and approvals are controlled.

Where data lives

Heyno Government runs on one server, delivered and installed inside your network perimeter. The models, the search index, the documents, the call transcripts and the credential vault all live on that machine. Data residency is a question of where the machine sits, not a clause in a contract.

What never leaves the building

No record, document, transcript or credential leaves your network. The models are US-developed open-weight models, running on your hardware, so a question asked of the assistant is answered on the machine. There is no outside AI provider in the path, and the system runs with the internet unplugged.

Access

Staff sign in once, in a browser, on your network. What a person can see follows from that sign-in, and the credential vault is never exposed to any third party surface.

Approvals

Anything with an effect outside the system waits for a person: mail about to be sent, a call about to be placed, a notice about to go out. The assistant prepares the work and shows it; a member of staff approves it.

Audit

What was done, by whom and when is retained on your server, so the question a records officer or an auditor asks a quarter later can be answered from the machine itself.

Updates

Updates are applied on site by your administrator. No component initiates outbound connections, and nothing updates itself from outside your network.

Request pricing Deployment Overview