This page explains how the reference tools, ordinary website requests and correspondence relate to your information. Keep credentials and sensitive application material out of tool inputs and messages.

Planning-tool inputs

The planning tools calculate in your browser using reference data. Text entered for token counting is intended to remain in the browser rather than be sent to an inference provider. A shareable calculator URL can expose the assumptions encoded in that URL to anyone you share it with and may remain in browser history. Do not include secrets in those fields.

Website requests and cookies

Loading pages and reference data creates ordinary requests to the site’s hosting service. Hosting logs can contain request and connection information used to operate the site. WordPress uses cookies for functions such as authenticated administration, as described in its cookie documentation. The public reference does not require visitors to create an account to use its planning content.

Analytics and advertising

No third-party analytics or advertising service is part of this initial reference build. If one is introduced, this notice must be updated to describe the service, information involved and applicable controls before that integration is presented as active. Advertising disclosures belong with the actual commercial arrangement.

Correspondence

A message sent to the contact address includes the information you choose to provide and the ordinary email metadata needed to receive it. Send only what is necessary to explain the request. Remove API keys, passwords, personal records and unrelated source code before submitting a correction or support example.

Questions and updates

Use Contact for a privacy question or a request concerning information you sent. Identify the relevant message or page without adding unnecessary sensitive material. This notice should change when the site’s actual data-handling behavior changes.

Use the AI API cost calculator to turn the model and workload you are considering into an estimate.

Last verified · Source ↗

Frequently asked questions

Should I paste an API key into a tool?
No. Planning and token-counting inputs should never contain credentials.
Can a shared calculator link reveal assumptions?
Yes. Anyone receiving the link can inspect its encoded assumptions.
Does the site currently use third-party advertising?
No advertising integration is part of this initial build; the notice must change if one is introduced.
What should I remove from a correction message?
Secrets, personal records and unrelated application material.
How can I raise a privacy question?
Use the contact route and identify the relevant interaction with minimal necessary detail.

Sources

Last verified · Source ↗