Security and deployment

How Token Gear handles your keys and your data.

How keys, provider credentials and request content are stored, used and recorded, how Token Gear is offered, and who to reach when something is wrong. Only what is in place today: anything not described here is not claimed, with no compliance certification and no published availability commitment.

What a request passes through

  1. The key is checked Keys are stored only as a hash; a revoked or disabled key stops working from its next request.
  2. Limits and data constraints apply The key’s budgets, rate limits and model allow-list; data constraints only narrow the providers it may go to, and with no compliant provider it is refused before it is sent.
  3. It goes to the provider that serves it Provider credentials are stored encrypted, used only for this step, and never returned to you.
  4. Usage and charge are recorded The request and each upstream attempt for it, with its usage and charge.

Request bodies are not kept unless your account turns content logging on. A response is kept for 24 hours for retries; the Your data section below says more.

Access

Keys and accounts

How API keys, console sessions and providers’ credentials are kept and used.

  • API keys

    Shown once, when created, and stored only as a hash; revoking or disabling one takes effect on its next request.

  • Key limits

    Each key can carry budgets, rate limits and a model allow-list.

  • Console sessions

    A session ends on sign-out, and can be ended from any other session.

  • Provider credentials

    Stored encrypted, used only to send requests upstream, and never returned to customers; customer APIs show no supplier prices or diagnostics.

Your data

What happens to a request

Where a request goes, whether its body is kept, where it may go, and what is recorded.

  • To the provider that serves it

    A request’s content goes to the provider that serves it, and its answer back to you.

  • Bodies are not kept by default

    Request bodies are not kept unless your account turns content logging on: then they are kept encrypted for 90 days, and can be deleted at any time (API docs). Two exceptions: a response is kept for 24 hours so that a retry with the same Idempotency-Key gets it again, and a request flagged for abuse is kept for a short period (Privacy Policy).

  • Data constraints only narrow

    Data constraints on regions, training and retention only narrow where a request may go; a request no compliant provider can serve is refused before it is sent.

  • Every attempt is recorded

    Every request and each upstream attempt for it is recorded with its usage and charge. What we keep, and for how long, is in the Privacy Policy.

Deployment

Deployment options

How Token Gear is offered, and where each option stands.

  • Invite-only

    Hosted by FreshToken

    The service FreshToken runs, at the API base URL in the docs, for customers under an offline contract.

  • Planned

    Private deployment

    Token Gear in your own environment is not offered yet: contact us if you need it.

Availability and support

Availability, status and support

How availability is agreed, where to check the service, and who to reach.

  • Availability commitments

    There is no published availability commitment: any commitment is made only in a separate written agreement (Terms).

  • Health check

    The API’s health check answers at /health, in JSON; there is no status page.

  • Support and security questions

    Write to support@freshtoken.ai.

Questions about security?

Write to FreshToken directly, or ask sales about the offline contract and how Token Gear is offered.