Privacy Notice & Data Rights | TokenUse
Review what data TokenUse collects, how it is used, and your privacy choices.
TokenUse provides per-model, per-project, and per-session visibility with alerts, reporting, and budget controls for developers and teams using AI coding agents.
Quick Answer
Review what data TokenUse collects, how it is used, and your privacy choices. This page explains practical next steps for privacy notice & data rights | tokenuse.
What You Can Do With TokenUse
- Understand privacy notice & data rights | tokenuse in the context of AI token and cost operations.
- Connect product capabilities to measurable outcomes for engineering and finance.
- Use linked pages below to continue setup, evaluation, or procurement workflows.
Implementation Checklist
- Confirm the owner and measurable outcome for this workflow.
- Verify instrumentation captures model, project, and environment dimensions.
- Define alert and escalation rules before broad rollout.
- Link implementation docs and pricing assumptions for team review.
How It Works
- Install the TokenUse CLI with one command.
- Authenticate your account to connect tracking.
- Start the tracker to capture AI token usage automatically.
- View dashboards to analyze spend by model, project, and session.
Who It's For
- Engineering Leaders — Track AI usage across teams and prioritize optimization work.
- Platform Teams — Instrument AI operations with consistent telemetry and budget controls.
- Finance & FinOps — Forecast AI spend, allocate costs, and maintain budget discipline.
Implementation Context
Operational Snapshot
The privacy notice defines what metadata TokenUse processes, how long it is retained, and which rights are available to users.
Use this page with trust and contact routes to validate data governance and compliance expectations.
Common Workflows
- Confirm collection scope and retention windows for your workspace.
- Review deletion and access request paths for legal compliance.
- Coordinate privacy review with trust documentation and support contacts.
Common Questions
- What usage data is collected?
- TokenUse collects usage metadata such as token counts, model identifiers, and session details needed for cost observability.
- Can we request deletion?
- Yes. You can delete your account in account settings, or send a deletion or other privacy rights request using the contact details in the privacy notice.
- How should legal teams use this page?
- Use privacy terms alongside trust and product docs to evaluate compliance fit for your deployment model.
- Does TokenUse collect prompt or response content?
- TokenUse collects the text of prompts you enter when prompt capture is enabled, and you can turn prompt capture off in settings. It does not intentionally collect AI model responses or source-file contents.
- How long is usage data retained?
- Raw usage events are kept for a period that depends on your plan, and prompt text follows your prompt retention setting. The privacy notice lists the current periods and what remains after account deletion.
- Is data shared with third parties?
- Personal information is not sold or shared for advertising. It is disclosed to service providers that help run the service and in the other cases listed in the privacy notice.
Related Pages
- Trust and Security: Security, privacy, and data handling practices.
- Contact: Sales, support, and enterprise onboarding channels.
- Pricing: Plan limits, billing options, and upgrade paths.
- Terms of Service: Legal terms for account use, billing, and obligations.