Trust & privacy

What we store, and what we never do.

Plain words about this site, the demo and the evidence our product produces.

This website

No tracking cookies. No profiles.

The site is static pages. It sets no advertising or analytics cookies and loads fonts from one font host. A contact message is stored so we can answer it, and emailed to us; it is kept no longer than the conversation needs.

The demo — Build your agent

Your description goes to the factory. Nothing else does.

The text you write is sent to the HexaBox Agent Factory, which builds the agent and keeps the build session and its audit chain, attributed to a fixed demo owner — never to you. The factory uses a model provider under a data-processing agreement to read your description. The page stores nothing about you; if you ask us about the agent, your description travels with your message because you chose to send it. Do not put personal data or secrets in a description — the demo needs neither.

Limits

Three builds per visitor per ten minutes. A daily share for everyone.

When the demo rests, the page says so in a sentence. It never shows an error you have to decode.

The views on this site

Simulated fleets and customers. Never real ones.

The Wind Shield, the Customer Shield and the Tech World on this site run on simulated data and say so on the glass. No customer's data, no partner's feed and no live system is drawn on a public page. The real views live in the Driver Seat, behind the login.

Verifying a HexaRecord

Proof that does not require trusting us.

Every report a HexaBox agent writes carries the hash of its evidence chain and the instructions to verify it. The chain is SHA-256: one per customer, with one per case inside it; each entry links to the one before.

01
Take the reportIt carries the chain hash and the verification instructions.
02
Recompute the chainHash each entry with the hash of the one before, from the first to the last — offline, with your own tools.
03
CompareThe last hash must equal the one in the report. Alter one entry and it does not.

The same holds for the agent itself: it carries a signed, root-chained identity and can prove it is unchanged with one command. CEVE is HexaBox's structural re-verification score — not a certification.

Security

Found something? Tell us.

If you believe you have found a security issue in this site, the demo or a HexaBox product, write to contact@hexabox.one with "security" in the subject. We answer within one working day and we do not pursue good-faith research.