Privacy

Email and issue reports

Report an issue opens your email application with a draft. ByeTokens does not send the message automatically or store a submitted web form. If you send it, the project owner receives your email address and the content you choose to include. Issue drafts contain a page path and relevant data identifiers; private scenario inputs and share fragments are not added automatically.

Server errors are logged with safe status codes, without request bodies or credentials. Optional client error events contain a fixed error code, not exception text or prompts.

Saved scenarios

Saved scenarios stay in your browser’s local storage. Share links store the scenario inside the URL fragment, which is not sent to the server during the page request.

Analytics

Analytics is disabled unless the site owner configures a provider. When enabled, events contain coarse calculator actions—not scenario names, raw share payloads, prompts, emails or keys. An anonymous ID in session storage groups actions within a browser session and expires after 30 minutes of inactivity. We record the entry page, referral hostname and campaign labels, without full query strings or URL fragments. Internal navigation keeps the session’s original source. This measures sessions, not unique people or cross-session retention. Closing the tab normally clears this session storage. Autocapture and session replay are not used.

Outbound links

A provider click may be counted as an outbound event. Purchases and provider-account activity are not tracked by this MVP.

Your usage CSV stays in your browser

Usage imports are parsed locally in a Web Worker. File contents, model names, token counts and costs are not uploaded, included in analytics or session replay, placed in URLs, or saved to browser storage. Resetting or reloading clears imported data. Downloaded comparisons are saved only when you choose to export them. We collect only generic comparison steps and error categories.