Privacy
Privacy policy
This page covers two separate systems: the tokenhush.com website and the Tokenhush product. The website uses cookieless, aggregate analytics. The product sends no telemetry by default, and its redaction and audit trail stay on your machine.
This website
This site is static. It has no accounts, no forms, and no place to submit personal information.
- Analytics
- The site uses a privacy-friendly analytics service that is cookieless. It counts aggregate page views without setting cookies, without browser fingerprinting, and without cross-site tracking.
- What we can see
- Aggregate numbers only, such as how many times a page was viewed. There is no visitor ID and no profile of you in those reports.
- What the site does not collect
- No sign-up, no newsletter, no contact form, and no email collection. There is no field on this site that accepts personal data.
- Hosting
- Like any website, the hosting provider processes the requests needed to serve pages and protect the service from abuse. That is standard request handling, not visitor profiling.
The product
The product is a local gateway. Redaction happens on your machine, and the audit trail stays there too.
- No telemetry. The product sends no telemetry by default. There is no analytics endpoint in the gateway that collects usage data.
- Content stays local. Your prompts, responses, provider keys, and audit records stay on your machine. The project does not operate a service that receives them.
- Keys stay yours. In V1 the gateway is passthrough: your tools keep their own provider keys, and the gateway forwards them without storing them.
- Verifiable in the source. The core is open source, so these behaviors can be checked in the code rather than taken on trust (fregie/tokenhush).
Third-party links
This site links to GitHub for source code, releases, discussions, and security advisories, and to the public documentation in the same repository. Once you follow one of those links, GitHub's own privacy terms apply.
Changes and questions
If this policy changes, the updated version is published on this page with a new date. Questions about the policy can be raised in GitHub Discussions. For vulnerabilities, use the private advisory channel instead of a public issue, as described on the security page.