Trust
Privacy Policy
This page explains the operational data SmarToken uses for API access, billing, support and account safety. Production legal language should be reviewed before public launch.
Website analytics
We use a first-party browser identifier lasting up to 30 days to record viewed page paths, referring website domains, campaign labels and device categories. When you register or sign in, these visits can be associated with your account and server records of registration, API calls and payments to understand where people arrive and stop. This analytics record excludes IP addresses, full user-agent strings, prompts and other URL query values. Do Not Track and Global Privacy Control signals disable this collection. Missing or blocked collection means some journeys cannot be attributed.
Account data
SmarToken stores account identifiers, login state, API-key metadata, wallet balance and support records needed to operate the dashboard and API gateway.
Chat content records
For support and operational review, SmarToken stores submitted conversation text and model answers in encrypted form after the response ends. Authorized administrators can view these records. They are retained until manually removed. Up to 100 recent messages and 65,536 characters of input, plus 65,536 characters of answer text, are retained for each call. Longer content is marked as truncated. Interrupted responses can leave a partial answer. Contact support with questions about these records.
Usage data
API calls may generate model ID, token counts, estimated cost, latency, status and billing ledger entries. These records help users audit spend and help operators maintain route quality.
Payment data
Payment providers process sensitive payment details. SmarToken stores operational order records such as amount, channel, status, provider reference and timestamps.
Security
Provider keys and sensitive configuration are protected server-side. Users should keep API keys private, apply budgets and revoke exposed credentials immediately.
Contact
Use support tickets for privacy, account access and billing questions so the request can be handled with the relevant account context.