Trust, Security & Data Handling | TokenUse
Understand TokenUse security, privacy controls, and data handling practices.
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 how TokenUse handles security, privacy, and operational safeguards for production AI systems.
What You Can Do With TokenUse
- Understand trust, security & data handling | 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
- Review metadata collection boundaries and retention defaults.
- Confirm encryption and access control expectations with security teams.
- Map privacy and legal obligations to documented policy pages.
- Route unresolved compliance questions through enterprise support.
How It Works
- Review what metadata TokenUse collects and what it does not.
- Verify encryption, access control, and retention policies.
- Check subprocessor and hosting details for compliance needs.
- Submit security questionnaires or follow-up questions via contact.
Who It's For
- Security Teams — Review encryption, access controls, and data handling practices.
- Legal & Compliance — Evaluate privacy policies, retention, and subprocessor details.
- Engineering Leadership — Understand operational safeguards before rollout.
Implementation Context
Operational Snapshot
Trust documentation explains TokenUse security posture, privacy boundaries, and data handling controls for production AI workflows.
Use this route to align security review, legal review, and engineering implementation expectations before rollout.
Common Workflows
- Review metadata collection boundaries and retention defaults.
- Validate security controls and transport protections.
- Coordinate procurement and compliance review with legal pages.
Common Questions
- Does TokenUse capture prompt content?
- No. Tracking is metadata-first and focuses on token and cost telemetry rather than prompt or response body content.
- How should security teams evaluate deployment?
- Use trust, privacy, and terms documentation together with technical docs to complete governance reviews.
- Where can we ask follow-up trust questions?
- Use contact routes for security review coordination, data handling questions, and enterprise onboarding support.
- Which controls are most important for initial review?
- Teams typically validate retention boundaries, encryption in transit, access controls, and support paths for privacy requests.
- Is data encrypted in transit and at rest?
- Yes. All data is encrypted with TLS 1.2+ in transit and AES-256 at rest. API keys and credentials are stored using industry-standard encryption.
- What is the data retention policy?
- Usage metadata is retained according to your workspace configuration. Teams can set custom retention windows and request data deletion at any time.
- Does TokenUse have SOC 2 certification?
- TokenUse infrastructure runs on SOC 2-compliant hosting. Our own SOC 2 compliance program status is available upon request through enterprise contacts.
- How are access controls managed?
- Role-based workspace controls and scoped API keys are on our roadmap and not yet available.
Related Pages
- Privacy Notice: Data collection, retention, and privacy rights information.
- Terms of Service: Legal terms for account use, billing, and obligations.
- Contact: Sales, support, and enterprise onboarding channels.
- Docs/authentication: Related TokenUse page.