Privacy Notice

OneProvider Ltd. (“OneProvider”, “we”, “us”, or “our”) operates an OpenAI-compatible and Anthropic-compatible API gateway available at https://api.oneprovider.dev/v1, the Telegram bot @oneprovider_robot , and the web cabinet at app.oneprovider.dev . We are headquartered in Cyprus and host the gateway in Frankfurt, Germany.

We designed the service to minimize what we collect. We do not store the content of your API requests and responses, we do not train models on your data, and we do not share API traffic with analytics or advertising networks. Only on oneprovider.dev, the web cabinet at app.oneprovider.dev and the redeem and dashboard pages, we use Google Analytics 4; it is not loaded if you reject it, and in the EU, UK and Switzerland cookies and ad signals stay off until you agree. It receives the page address without query string or fragment and anonymous events; keys, codes, emails and account identifiers are never sent. Whatever you choose, we also keep our own anonymous site statistics in our database and share them with no one: where a visitor came from (utm tags, the referring site's domain, whether a Google click id was present, the first page) and which steps they took; instead of an IP address it holds a daily visitor code that changes every day, and it never holds keys, codes or emails. We also report that an order was paid (the order number only, never the amount or the plan name) to Google from our server: for web orders only if analytics was allowed, for Telegram bot orders under a pseudonym that does not reveal your Telegram account. Messages you send to support yourself are processed so that we can answer them (Section 2.3). This Privacy Policy explains what we do collect, why, and how to exercise your rights over that data.

1. What We Don’t Collect

Through the API gateway, OneProvider does not store, log, or persist:

• Prompt content — system messages, user messages, tool inputs, attached images.
• AI-generated responses — model completions, tool-call outputs.
• The body of any HTTP request or response flowing through the gateway.
• Behavioural profiles, advertising identifiers, or third-party tracker data.

Request bodies are streamed through our proxy layer to the model that serves your request and discarded. They are never written to disk, never buffered to log files, and never shipped to a third-party observability service. This applies to API traffic; support messages are handled differently, see Section 2.3.

2. What We Do Collect

2.1 Billing metadata (always)

• Request timestamp, HTTP path, status code, duration.
• Model identifier and token counts (input, output, cache-creation, cache-read) reported by the model provider.
• Per-request cost in USD, computed from the published rate.
• A truncated internal key reference (the first eight characters), used to bind usage to your balance and insufficient to authenticate API requests.

This metadata is the absolute minimum required to deduct the correct amount from your balance, respond to disputes, and detect abuse.

2.2 Proxy access logs

• Source IP address.
• User-Agent string.
• Response status code and byte counts.

Access logs are kept on our servers for a limited time. They allow us to triage outages and respond to abuse reports. We do not correlate IP addresses with prompt content because we do not store prompt content in the first place.

2.3 Telegram (if you use our bots or sign in with Telegram)

If you onboard through @oneprovider_robot or contact @Oneproviderhelpbot , Telegram shares your numeric user ID and your public username with our bot. We use that ID solely to deliver keys and codes, to confirm purchases, to sign you in to your cabinet, and to respond to support requests. We process the messages and images you send to the bot and to support so that we can answer your request, and keep them in the support conversation for as long as the service needs them. On request we delete them where possible.

Support may request a full API key only through the protected support-bot linking flow. If a full key is sent in a plaintext chat message, the bot makes a best-effort attempt to delete the message; the plaintext key is never relayed to staff or persisted by our systems. Staff see only a masked internal note.

2.4 Web cabinet (if you use it)

The web cabinet at app.oneprovider.dev shows the same balance, keys and history as the cabinet in the Telegram bot. To sign you in and run the cabinet we store:

• Telegram sign-in: your numeric Telegram ID and public username.
• Google sign-in: your Google account ID (subject) and the email address Google shares. We never receive your Google password.
• Email and password sign-in: your email address and a password hash (Argon2id). We do not store the password itself.
• Sessions: sign-in method, sign-in and last-activity times, IP address and browser User-Agent. A session lasts up to 30 days or until you sign out.
• Support chat: messages and images you send in the cabinet support chat. They are kept in the same conversation as your Telegram support requests.
• Receipt email: if a payment provider asks for an email for the receipt, we store it with the order and pass it to that provider.

Cabinet emails (address confirmation, password reset, balance notices) are sent through Resend. The sign-up, email sign-in and password reset forms are protected by Cloudflare Turnstile: Cloudflare checks technical browser data, such as your IP address, to tell people from bots.

Cookies. The cabinet sets only necessary cookies: the session cookie __Host-op_app (HttpOnly, Secure, SameSite=Lax, up to 30 days) and short-lived cookies for Telegram and Google sign-in and email confirmation. On oneprovider.dev, app.oneprovider.dev, redeem.oneprovider.dev and dashboard.oneprovider.dev, Google Analytics 4 (cookies _ga, _ga_*) works like this: in the EEA, the UK and Switzerland cookies and ad signals stay off until you allow them; elsewhere they are on until you decline. The consent also covers Google Ads measurement: _gcl_* cookies and Consent Mode signals (ad_storage, ad_user_data, ad_personalization) show which ad led to a sign-up or top-up and let us show our ads to people who visited the site. The page address may include a Google click id (gclid) and utm tags. To carry you from the site to the cabinet we also set, whatever you choose, the cookie op_visit for 30 minutes (domain .oneprovider.dev; it holds only where you came from and your first page; the cabinet reads it once and deletes it). Your choice is stored in the cookie op_consent (value accepted or declined, 12 months, on the .oneprovider.dev domain, so it applies on all these pages). The cabinet shows no notice: the same rules apply there, and your choice on the site, the redeem page or the dashboard is honored. You can withdraw consent at any time via the “Cookie settings” link in the site footer or in the cabinet Settings.

2.5 Marketplace orders (when applicable)

If you purchase a code through one of the marketplaces, the marketplace shares the order code and (for some marketplaces) a buyer reference with us so we can deliver the key. We do not receive your real name, payment instrument, or marketplace sign-in credentials.

3. Why We Process This Data

• To meter usage and deduct the correct amount from your balance.
• To process refunds in accordance with our Refund Policy .
• To detect, prevent and investigate abuse (including bonus abuse and multiple accounts) and violations of our Acceptable Use Policy .
• To monitor the performance, reliability and security of the Service.
• To respond to your inquiries and to operational notices about the gateway.
• To comply with applicable legal obligations.

Legal bases (GDPR Art. 6). Billing metadata and key-bound usage records are processed on the basis of contract (Art. 6(1)(b)) — we cannot meter a prepaid key without them. Proxy access logs, abuse detection and security monitoring are processed on the basis of our legitimate interest (Art. 6(1)(f)) in keeping the gateway available and free of abuse. Telegram on-boarding identifiers are processed on the basis of your consent (Art. 6(1)(a)) — given when you initiate a chat with our bot, and revocable by deleting the chat or asking support to delete it. Web cabinet sign-in data (email, password hash, Google account ID, session records) and support chat messages are processed on the basis of contract (Art. 6(1)(b)): we cannot sign you in or manage your balance without them. Cloudflare Turnstile checks and sign-in rate limits rely on our legitimate interest (Art. 6(1)(f)) in protecting accounts. Analytics on the website and in the cabinet runs only with your consent (Art. 6(1)(a)). Payment confirmations are retained on the basis of a legal obligation (Art. 6(1)(c)) under Cypriot tax and anti-fraud law.

4. Data Retention

We keep data for as long as needed to run the service, meet legal and accounting obligations, resolve disputes and protect against abuse. On your request we delete or anonymise data where possible. Data that the law requires us to keep (for example payment confirmations) and copies in backup storage may be kept longer.

5. Third Parties

To run the service we use trusted infrastructure, payment and communication providers, and share data with them only as far as needed to deliver the service.

5.1 Model processing of requests

Your prompt content is processed by the model that serves your request. Only the prompt, model name and request parameters are sent for processing — never your OneProvider key, your IP, your Telegram ID, your email or any other identity-linking identifier. We do not use your requests to train models.

5.2 Payment services

Top-ups go through third-party payment services (see Payment Methods ). They receive the amount, the order reference and, if the provider asks for it, an email for the receipt. Payment-card data is handled by the payment service; we do not store it ourselves. OneProvider receives only the payment confirmation.

5.3 Other providers

Hosting, email delivery, bot protection for forms (Cloudflare Turnstile), Telegram (bots and Telegram sign-in) and Google (sign-in with Google if you choose it, and Google Analytics 4 and Google Ads measurement on the site, the cabinet, redeem and dashboard pages after your consent).

6. International Transfers

Telegram, Google and other providers operate internationally and may process data outside the European Economic Area, as may model providers. For such transfers we rely on the safeguards that the relevant providers put in place.

7. Your Rights

If the GDPR, UK GDPR, California Consumer Privacy Act or another regional data protection law applies to you, you have the following rights:

• Correction. Ask us to correct data that is inaccurate.
• Erasure. Ask us to delete your data, subject to legal retention obligations.
• Restriction. Ask us to limit how we process your data.
• Portability. Receive a machine-readable export.
• Objection. Object to processing we do on the basis of legitimate interest.
• Complaint. Lodge a complaint with your local supervisory authority.

To exercise a right, message @Oneproviderhelpbot or the support chat in your web cabinet with a short description of your request. You can withdraw analytics consent via “Cookie settings” in the site footer or in the cabinet Settings. If key ownership must be verified, support starts the protected key-linking flow: send the full key only after that prompt. The key message is deleted where technically possible, is not relayed to staff or persisted, and staff sees only a masked system note. We respond to verifiable requests within 30 days.

8. Security

We protect your data in transit and at rest with industry-standard controls:

• TLS 1.3 on all gateway traffic. Certificates renewed automatically via Let’s Encrypt.
• HTTP/2 with HSTS enforced.
• Database encryption at the filesystem layer on the host.
• Role-restricted SSH access; no shared credentials.
• Vulnerability patches applied on a rolling 7-day window for non-critical CVEs and within 24 hours for critical CVEs.

These are the controls we operate today. We do not claim ISO 27001, SOC 2 or PCI-DSS certification because we have not been audited against those standards. We will update this policy if and when an audit completes.

9. Children

OneProvider is not directed at individuals under 18 years of age. By using the Service you represent that you are at least 18 years old. If we learn that we have processed personal data of a person under 18 we will delete it promptly. If you believe a minor has used the Service, contact @Oneproviderhelpbot .

10. Changes to This Policy

We may revise this policy from time to time. The current version is always published on this page with the “Last updated” date at the top; for material changes we may also notify you in the Telegram bot.

11. Organizations and Data Processing

We process account data (sign-in, email, payments, support requests) as a controller. API request content only passes through the gateway to fulfil the request and is not stored. If you use OneProvider on behalf of an organization and need a written data processing agreement, message support and we will review the request.

12. Contact

• Telegram (preferred): @oneprovider_robot
• Support tickets: @Oneproviderhelpbot
• Support chat in the web cabinet: app.oneprovider.dev
• Email: support@oneprovider.dev
• Legal entity: OneProvider Ltd., Privacy Office, Nicosia, Cyprus. Full registered address available on written request via Telegram support.

Data Protection Officer. We have not appointed a Data Protection Officer under Art. 37 GDPR: our processing is not large-scale, systematic monitoring of public spaces and does not involve special-category data at scale. For any data-protection inquiry, message @Oneproviderhelpbot with the subject line “Data protection” and we route it the same day.

OneProvider · API gateway

Privacy in one line

No prompt logging under our policy. No training on your data. Billing metadata only.