OneProvider
OneProvider

Security & Privacy: Prompt Logging Policy

Under our policy, OneProvider doesn't log prompt content or store it on the model side. All traffic is served from Frankfurt, Germany, over TLS 1.3.

Security · transport · privacy What we do with your traffic, and what we don't. Under our policy: no prompt logging, no model training, no third-party sharing. Read privacy policy Open status Request path · diagram EU-FRA / TLS 1.3
  1. 01 Your app SDK, Claude Code, Codex
    Transport
    TLS 1.3 · HSTS
  2. 02 OneProvider API EU Frankfurt
    API p50 · EU
    <40ms
    Uptime · 30d rolling
    PENDING
    Prompt log bytes, by policy
    0
  3. 03 Model provider No training
    Tokens / day
    75B+
01

EU Frankfurt

Dedicated servers in one EU region. Predictable latency from EU clients; <40ms p50 to most major capitals.

02

Encrypted transport

TLS 1.3, HTTP/2, HSTS preloaded. Certificates renew automatically.

03

One key, one balance

Your API key authenticates only your balance. No shared credentials, no organization tenancy mistakes.

04

Under our policy, we don't log prompt content

Request bodies go straight to the model you chose. Our policy is not to write them to disk, buffer them to logs or replay them.

05

We never train

OneProvider doesn't run or train models. We check your key and balance and deliver each request to the model provider you pick.

06

We never share

No analytics SDKs, no third-party trackers on the API surface, no ad networks. Your traffic is yours.

Logged
  • Request timestamp, path, status code, duration
  • Model name + token counts (billing)
  • Source IP, rotated every 30 days
  • Aggregate uptime and error metrics
  • Telegram numeric user ID (if you use @oneprovider_robot or sign in with Telegram)
  • Web cabinet sign-in: email, password hash, Google account ID, session IP and browser
Not logged under our policy
  • Prompt content (system + user messages, system instructions)
  • Model responses or completions
  • Tool-call arguments or results
  • Request or response bodies
  • Card data: handled by our payment provider, never stored by us
REQUEST INSPECTOR

Follow one request to the model

Pick a model or paste a key. Each step shows what passes on, what stays with us, and what is kept. Interactive example Runs locally · nothing is sent
  1. 01 Your app your machine POST /v1/messages Host: api.oneprovider.dev x-api-key: sk-•••••3a7f anthropic-version: 2023-06-01 Content-Type: application/json
  2. 02 OneProvider API EU · Frankfurt
    • Encryption TLS 1.3 · HSTS · HTTP/2
    • Key Checked against your balance, never passed on
    • Request Sent to the model as is; under our policy not written to disk or logs
    • Stays with us Your IP address and client tracing headers
    • Recorded Time, model, status and token counts for billing
  3. 03 Model provider claude-sonnet-5-5
    • Receives Your messages, model settings and tools
    • Never receives sk-•••••3a7f , your IP, account or balance
    • Response HTTP/2 200 · Streamed straight back to your app
What is kept, and for how long Privacy policy
Prompts and responses
Not stored under our policy
Access log: IP, path, status, timing
Up to 30 days
Usage record: time, model, tokens, key prefix
90 days

OneProvider · API gateway

Ready to start building?

The API is ready. Choose a key and make your first request.

Get your key Explore docs