Claude Usage Exporter privacy notice
Last updated: 2026-09-16.
This notice describes what the DoiT Claude Usage Exporter browser extension does with data. It supplements the DoiT Privacy Policy and, for DoiT customers, the Data Processing Agreement. It is written to satisfy the Chrome Web Store User Data Policy, including its Limited Use requirements.
What the extension is
The extension runs inside your Chrome profile and exports the spend report that claude.ai offers Claude Team organization Owners under Settings > Analytics, one day at a time. It stores the exported CSV files locally and, only if you turn on Send each daily CSV to DataHub, uploads them to your own DoiT Cloud Intelligence™ account.
Data the extension stores locally
In your browser profile only:
- The daily spend report CSV files exactly as claude.ai produced them. Each row contains a member's email address, an account identifier, a product, a model, token counts and USD amounts.
- The claude.ai organization identifier shown on the analytics page.
- Run history, error states and a short diagnostic log with secrets removed.
- If you enable the DataHub upload: the DoiT API key you paste and, if you enable email hashing, a random salt. Both stay in the extension's local storage, are never written to the log, and are excluded from exported diagnostics.
The extension does not read, store or transmit your claude.ai password, session cookies, chat content, or any page content other than the analytics page elements needed to drive the export and the CSV file produced for you.
Data the extension transmits
- Upload off (default): nothing leaves your browser. The only network host the extension contacts is
claude.ai, where you are already signed in. - Upload on: each daily CSV is sent to the DoiT API (
api.doit.com) with your DoiT API key so that Cloud Intelligence™ can show Claude spend next to your other cloud costs. The upload contains the CSV rows, including member email addresses, unless you enable Hash user emails, in which case the email column is replaced in memory by a keyed hash before upload; the stable account identifier remains so that per-user grouping still works. The locally stored copy is never modified. - The extension contacts no other host. This is enforced in the extension's content security policy and checked in its build.
How DoiT uses uploaded data
Uploaded data is processed under the agreement between DoiT and the customer whose API key was used, solely to provide cost analytics to that customer in Cloud Intelligence™. DoiT does not sell it, use it for advertising, or use it to train models.
Limited Use disclosure
The extension's use of information received from claude.ai pages adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. Data is used only to provide the single purpose described above, is transferred only to the customer's own DoiT account when the customer enables it, and is never used for advertising, for determining creditworthiness or for lending purposes, and is never sold.
Retention and deletion
Local data is kept until you remove the extension (chrome://extensions > Remove) or clear its storage. Uploaded data can be deleted from the DoiT console in DataHub, per dataset or per uploaded batch.
Contact
Questions about this notice: [email protected].