We don’t store your
prompts or responses.
Your API content is processed to fulfil the request. It is not saved in r2hub’s persistent request history.
Content is not your usage record.
Prompts, code, conversation messages and model responses pass through the gateway to complete your request. We don’t rewrite or shorten your prompts, insert our own instructions, or automatically substitute a different model.
Protocol fields may be normalized and output limits enforced. This is not a byte-for-byte passthrough or a promise of complete API compatibility.
No model training at r2hub.
r2hub does not use your prompts, code, conversation messages or responses to train or fine-tune models. We process your API content to fulfil your request.
Our business is API access: we buy tokens from providers at volume discounts and pass part of the saving on to customers. Our margin comes from the difference between our purchase and selling prices.
What we do retain.
We keep the metadata needed to operate your account, calculate charges and investigate failures: model and request identifiers, timestamps, status, token counts, costs, latency and technical error codes. Request fingerprints may be retained for duplicate detection; they are not copies of your prompt.
Account details, Stripe payment references, balance transactions and support messages are separate records. Please do not put API keys or confidential prompt contents into support messages.
What this statement covers.
This page describes storage by r2hub. “We don’t store your prompts or responses” does not mean that we keep no account, usage, security or billing data. It does not promise EU-only processing.
Website analytics are separate.
Optional website analytics run only with your consent. API content, API keys and payment details are not sent to marketing analytics. You can change your choice using Privacy settings.
For processing purposes, recipients, legal bases and your rights, read our Privacy notice. Questions: support@r2hub.com.