Receipt: privacy

Version 0.8 · August 2026

Nothing leaves your device. There is no server. The extension makes no network requests of any kind.

What it records

Three values per prompt, and nothing else:

Field	Example	Why
Timestamp	`1755950400000`	To group by week
Hostname	`claude.ai`	To count tools used
Mode	`standard` / `thinking`	The whole point of the tool

Plus, only if you press the buttons yourself: image counts, "did without" counts, and your reclaim log (free text you type).

What it does not record

Anything you type into an AI tool. Not prompts, not responses, not drafts.
Your name, email, IP address, device identifier or account details. It has no concept of who you are.
Which conversations you had, their titles, or any content from them.
Any browsing outside the seven AI sites listed in the manifest.

Verify it yourself

Don't take my word for it. In the extension folder:

grep -rE "fetch\(|XMLHttpRequest|sendBeacon|WebSocket|EventSource|https?://" *.js

That returns nothing. There is no code capable of transmitting anything. You can also open DevTools, go to the Network tab, and use an AI site: Receipt generates no requests at all.

About the keystroke listener

content.js attaches a keydown listener to the document on the seven AI sites. This looks alarming and is worth explaining: it checks one property, e.key === "Enter", to know that a prompt was submitted. It never reads e.target.value or any typed text. The code is commented at that line. There is no network code to send anything with even if it did.

About the permission warning

When you install, Chrome will say Receipt can "read and change your data" on chatgpt.com, claude.ai and the other listed sites. That is Chrome's standard wording for any content script and cannot be softened. It is accurate in the sense that a content script could do those things. This one counts submissions and shows a nudge.

The source is short, around 200 lines, and readable in ten minutes. There is no innerHTML anywhere in the codebase: all interface text is built with createTextNode, so no stored string can be interpreted as markup. The Firefox build passes Mozilla's web-ext lint with zero errors, zero warnings and zero notices, and declares data_collection_permissions: none.

Retention

Prompt counts, image counts and "did without" counts: automatically deleted after 90 days.
Reclaim log: never auto-deleted, because it is yours. Delete entries individually, or everything at once.
"Delete all my data" on the Share tab clears the lot immediately and irreversibly.

Export

The Share tab produces a JSON file of weekly totals, saved to your downloads. It contains counts by tool and mode, and the calculated energy and carbon ranges. It does not contain your reclaim log, your name, or anything you typed. Nothing is sent anywhere: the file goes to your machine, and what you do with it is your decision.

GDPR

For an individual using Receipt personally, no personal data is transmitted or shared with anyone, so there is no controller, no processor, and nothing to have a lawful basis for. Personal household use is outside the scope of the UK GDPR in any case.

If you are an organisation: this changes if you ask staff to send you their exports. At that point you are processing employee data and the relevant framework is workplace monitoring. You would need transparency, a lawful basis, and realistically a DPIA if participation were mandatory.

Receipt is designed for voluntary individual use. Do not make it compulsory. A tool built so that nobody can watch you, deployed so that somebody does, becomes the opposite of what it is for.

Methodology

How the energy and carbon figures are calculated, with full sources, is set out separately in the methodology note.

Contact

Questions, or something here that does not match what the code does: marie@springcorp.co.uk

Back to Receipt

Receipt is an independent project. It is not selling you an AI product and never will.