§ 0 The short version
The Halton Meter daemon runs entirely on your machine. It writes to
~/.halton-meter/ and nowhere else. No LLM request data,
no cost figures, no project names, and no API keys ever leave your
machine as a result of installing or running this product.
This is the point of the product.
The website (haltonmeter.com) has no analytics, no cookies, no tracking pixels, and no third-party scripts. If you submit a form, we receive what you typed and use it only to reply.
- analytics
- cookies
- tracking pixels
- third-party scripts
- telemetry
- mailing lists
§ 1 What the product collects
Local SQLite, loopback only
The Halton Meter daemon is a local network proxy. It intercepts
outbound LLM API calls from processes on your machine, logs metadata
about those calls (timestamp, model, token counts, latency, computed
cost, project attribution), and writes that data to a SQLite database
at ~/.halton-meter/db.sqlite.
This data never leaves your machine. The daemon does
not send telemetry, usage statistics, or any other data to Halton Labs
or to any third party. Its two housekeeping checks — a
pricing-manifest pull and a PyPI update check — are fail-open,
opt-out, and carry no usage data. The local HTTP API is bound to
127.0.0.1 loopback only and is not accessible from
outside your machine.
By default the daemon also stores full request and response bodies
locally, with credentials redacted before anything is written, a
90-day retention sweep, and a per-project opt-out
(halton-meter bodies). Bodies never leave the machine
unless you separately opt into body sync.
If you opt into Halton Meter Cloud
(halton-meter cloud connect), the daemon uploads request
metadata to the hosted service at cloud.haltonmeter.com. Request
bodies upload only with a separate opt-in, and only from the moment
you enable it. Until you pair, the daemon transmits nothing. The
cloud service's own privacy policy governs synced data.
§ 2 What the website collects
Only what you type into a form
The site sets no cookies and runs no analytics. It loads no third-party scripts and makes no tracking requests. Cloudflare (our CDN and DNS provider) processes each HTTP request to serve the page. Cloudflare's own privacy policy governs what Cloudflare retains at the network level; we do not receive individual visitor data from Cloudflare.
If you submit the Cloud sign-up form, we receive what you typed — email, team size, and anything you put in the free-text field. Submissions are delivered to us by Resend, our email processor, and used only to reply. Nothing else is collected.
If you contact us by email, we receive your email address and the contents of your message. We use it to respond. We do not add it to a mailing list or share it with anyone.
§ 3 API keys and credentials
Keys pass through; we do not retain them
The daemon routes traffic through a local proxy but does not log, store, or inspect API keys. Your keys remain in the environment or credential store where your LLM client reads them. They pass through the proxy in request headers in the normal way; the proxy does not extract or retain them.
§ 4 Children
Not for under-16s
This product is intended for developers and technical teams. We do not knowingly collect any information from anyone under 16.
§ 5 Your rights
Local data, local control
Because the daemon stores all data locally on your machine, you
already have complete control over it. To delete your data, delete
~/.halton-meter/. To inspect it, open the SQLite file
directly or use halton-meter report.
If you have contacted us by email and want us to delete your message, email operator@haltonlabs.com and we will do so.
§ 6 Changes to this policy
Material changes get a date bump
If we make material changes, we will update the effective date above and note the change in the product changelog. Continued use of the product after a material change constitutes acceptance of the updated policy.
§ 7 Contact