Summary
This policy applies to the COMPANION website and Chrome extension. It explains what the software processes, what remains on your device, and the narrow circumstances in which infrastructure providers may process technical request information.
The website
The website does not use analytics scripts, advertising pixels, marketing cookies, account forms, or behavioral tracking. It does not intentionally collect personal information from visitors.
The website is intended to be hosted through Cloudflare Pages. Like most hosting and security providers, Cloudflare may process standard network and request information, such as an IP address, user agent, requested URL, timestamp, and security signals, to deliver and protect the site. That processing is governed by Cloudflare’s own terms and privacy practices. COMPANION does not add a separate analytics layer or use that information to build visitor profiles.
What the extension processes
Stored locally
- Extension settings and feature preferences.
- Claude numeric spend samples and derived local history.
- Bounded, normalized OpenAI numeric usage snapshots when supported fields are observed.
- Small caches and timestamps needed to operate usage displays, alerts, and reset windows.
Processed temporarily, not stored by COMPANION
- Prompt text needed for optional Lifejacket compression and preview.
- User-selected file contents needed for local conversion to Markdown.
- Provider response data needed to identify supported numeric usage fields.
Not collected or stored
- Prompt or reply history.
- Passwords, authentication tokens, or session cookies.
- Raw OpenAI account or conversation payloads.
- User-selected file contents after local processing.
- General browsing history.
Claude and ChatGPT boundaries
On Claude, usage reads are read-only and same-origin. Your browser authenticates those requests through your existing signed-in session. COMPANION does not read or store the session cookie.
On ChatGPT web surfaces, raw first-party responses remain in the page context. A randomized page channel forwards only normalized JSON containing recognized, bounded numeric fields. Extension components validate the origin, sender, frame, keys, units, ranges, timestamps, bucket names, and payload size before using those fields.
When you choose to send a prompt, the relevant provider receives that prompt under its own terms and privacy policy. COMPANION does not control the provider’s processing.
Retention and deletion
Local settings and numeric history remain in browser storage until you clear COMPANION data, reset the relevant history, remove the extension, or the browser removes that storage. Prompt text and file contents are not retained by COMPANION after the local operation completes.
Because COMPANION has no account or developer database, there is no remote user profile for the developer to retrieve, export, or delete.
Your choices
- Turn off or hide the usage widget, alerts, badges, and Lifejacket tools independently.
- Clear local COMPANION data from the extension settings.
- Remove the extension to delete its browser-managed local storage.
- Review the source code, permissions, and security documentation on GitHub before installation.
COMPANION is not directed at children and does not knowingly create profiles about children. It has no account registration or age-targeted advertising.
Changes to this policy
This policy may be updated when the extension’s behavior, permissions, hosting, or legal requirements materially change. The effective date at the top will be revised. Material privacy changes should also be described in the project’s release notes.
Contact
Privacy questions may be sent to zgbrenner@gmail.com. Do not include passwords, session cookies, account tokens, private prompts, or private files in a report.