Zero Data Retention
Hexum’s Zero Data Retention (ZDR) policy applies to every plan: Usage and Teams. It is not an add-on, not a higher tier, and not something you turn on in Stripe. If MCP is serving your key, this policy applies.
- Scope
- What we do not keep
- What happens on a call
- What we do keep
- Plans
- Training
- hexum_check
- Limits of this policy
- How to ask
Scope
This policy covers payloads you (or your agent) send to POST /mcp and related engine routes: source files, prompts,
paths, stderr, and architecture.hexum. It does not replace the Privacy Policy for account, billing, or usage
meters. Those remain.
What we do not keep
- We do not write MCP request or response bodies to the application database.
- We do not keep a searchable archive of your repository, prompts, or diffs.
- We do not sell that content or use it for advertising.
- We do not train a Hexum model on it. Hexum is not a model.
What happens on a call
The payload is processed in memory to answer that tool call
(hexum_skill, hexum_shrink, hexum_expand, hexum_splice, hexum_check). A session may hold files in process so a later
expand or splice on the same turn can work. That session is discarded after 15 minutes idle. It is not written to disk as a customer
record.
Hosted Hexum does not copy SKILL.md onto your laptop. It
returns the body; your agent writes the file in your workspace.
What we do keep
These are not MCP payloads. They are how the product bills and signs you in.
- Account: email, profile, plan.
- Keys: name, prefix, hash of the secret — not the
hexum_live_…plaintext. - Usage: tokens in, tokens out, call counts, per user per day in
usage_daily. Numbers, not files. That table has no payload column. Usage and Teams share it. - Stripe customer id, invoices, and tax records as Stripe and law require.
- Teams: org name, members, roles, invites.
Short-lived server logs may exist for abuse and outages. They are not a product feature and not a prompt store. Detail: Privacy and Security.
Plans
Usage and Teams get the same ZDR terms. There is no enterprise-only retention mode in v1. Turning on usage billing or joining a team does not change how payloads are handled.
Rates stay on Pricing. ZDR is not a line item.
Training
We do not use MCP payloads to train a Hexum model, to fine-tune a third party, or to build a public dataset. Token counts used for billing are derived on the call and stored as numbers only.
hexum_check
The architecture check runs on the files in the current request. It does not send your repository to a third-party model. A pass is not a legal or security audit. You remain responsible for what you ship.
Limits of this policy
- Your editor, Git host, and model provider have their own retention. Hexum does not control those.
- If you paste a payload into Contact or email, that message is ordinary correspondence, not an MCP call.
- We may retain data we must keep for law, tax, or a good-faith abuse investigation. That is not “keep the repo.”
- v1 has no customer-visible audit log of payloads — because we do not store them.
How to ask
Privacy or security: Contact. Do not send live keys. Delete the account from /app to revoke keys and remove the profile we store.