Privacy
We set no cookies on your browser.
The privacy notice below describes what is recorded, what is not recorded, and how packaging events are treated when the consumer is a verified bot or a token-holder.
Visitors
Browsers are guests.
No cookies are set. No analytics scripts run. No third-party trackers are loaded.
A visiting browser is treated as a guest. The site sets no cookies, runs no analytics scripts, and loads no third-party trackers. There is therefore no consent banner; if there is no data collected, there is no consent to obtain.
Standard server-side request logs are retained for thirty days for operational reasons (rate control, abuse mitigation, and infrastructure capacity planning). They are not joined to any other data set, are not shared with third parties, and are deleted at the end of the retention window.
Verified bots
Packaging events are recorded.
A packaging event records the bot identity, the request, the cycle, and the body hash. Nothing more.
Bot identity, request format, cycle timestamp, body hash, manifold-state hash, trust-key id.
IP-derived location, browser fingerprint, cross-request behaviour, identity beyond the bot signature.
Packaging-event records are retained for as long as the evidence locker stands, so a dispute may be resolved against any past delivery.
Token-holders
Contracts govern contracts.
A token-holder relationship is governed by the contract executed at enrolment and by this notice in the absence of a more specific term.
The application form at /token-program collects the operator name, a technical contact, the jurisdiction of incorporation, the declared ingestion target, the projected packaging volume, and a brief. These fields are read by a reviewer and retained for the life of the contract.
A token-holder may at any time request a record of the data the operator has supplied and a record of the packaging events charged against their token, in either case at no cost.