Privacy Policy

This explains what Valni collects, and what we do with it, when you use Switchboard and our sites.

• Account details — your email, name, and organization if you give one.
• Usage data — which models you call, token counts, cost, timing, and error records. This is the metering that runs your bill.
• Payment info — handled by our payment processor, Stripe. We don’t store full card numbers.
• Request content — the prompts you send and the responses you get back. We pass these through to the provider to serve your request and count the tokens for billing. We don’t read them or store them.
• Tool calls, if you turn on our permissions policy — this is a product you opt into, not data we gather for ourselves. When you set a policy, it reads the tool calls in a response (a separate structured field, apart from the message text) and checks them against your rules to enforce them. It reads only that field, never your messages, and keeps nothing.
• Technical data — your IP address, device and browser details, and logs, used to secure and run the Service.

• To run the Service: routing requests, measuring usage, billing you, and helping you when you need it.
• To keep the Service secure and reliable.
• To give you and other customers useful insight — anonymized, aggregate stats like which models are popular and what requests cost, published for your benefit. This is data we build for customers, not a profile of you. It never includes your prompt content and can’t identify you.
• To reach you about your account or important changes.

• We’re a proxy, not a model company. Your messages and responses pass through us to the provider, and we don’t read them or store them.
• We don’t sell your personal data.
• We don’t share your content with anyone except the provider needed to serve your request, and the service providers below.

Valni is a gateway. To serve your request, we send it to the provider you route to, like OpenAI or Anthropic. That provider can see your prompt and its response, and may use them under its own terms — which often means training on them and reviewing content. Those practices are the provider’s, not ours, and they differ from provider to provider (see how each provider uses your data). When you route to a provider, you agree to its terms. Our promises in this policy are about what Valni does; they can’t control what a provider does with your request once it arrives.

• Model providers — we send your request to the provider you’re routing to (like OpenAI or Anthropic), under their terms.
• Service providers — infrastructure (Cloudflare), payments (Stripe), and similar vendors that help us run the Service, under confidentiality obligations.
• Authorities — if the law requires it, or to protect rights and safety.
• A buyer — if Valni is acquired or merged, data may move as part of that, under this policy.

Valni works the same whether you use it directly or build an app on it for your own end users. If you build on Valni, we give you the same kind of information about your end users that we give anyone about their own usage: the cost, tokens, model, and timing of each request. That metering is what powers per-user billing and controls. We never give you the content of your end users’ prompts or responses. And your end users get the same privacy described here: whether someone uses Valni directly or through an app built on it, their messages are handled the same way, never stored and never shared. One product, one data model, no special access.

We combine usage across all accounts into anonymized, aggregate stats — model adoption, average cost per request, reliability, and the like — and we publish them so you and other customers can compare models and understand what they cost. This is a product we build for customers, not a way to profile you. The stats are stripped of anything that could identify a person or account, and because they can’t be traced back to you, they’re separate from your personal data and aren’t subject to deletion.

• Account details — while your account is active, and for a period afterward as the law requires.
• Billing and payment records — as a payments company, we keep these as a financial record for around seven years, sometimes less. They live on an append-only ledger, so we can’t remove individual entries on request, and we don’t keep the ledger forever.
• Request content — we don’t store it (see what we collect, above).

We keep what we need to run the Service, meet our obligations as a payments company, and settle disputes, then delete or anonymize the rest.

Depending on where you live — for example, the EU/UK or California — you can see the personal data we hold about you, correct it, delete your account and personal data, object to or limit certain uses, and get a copy to take with you. There’s one exception: your usage and billing records are the financial record of your balance and bills, much like a bank statement. It’s used for accounting and payments and lives on an append-only ledger, so, like a bank statement, we keep it (around seven years, sometimes less) and can’t remove individual entries on request. It never includes your message content. To make a request, email [email protected]. We won’t treat you differently for asking.

We protect data with reasonable technical and organizational measures. No system is perfectly secure, but we work to keep yours safe and to tell you if something happens that affects you.

Our sites don’t use cookies, run analytics, or track you. To keep you signed in, we use your browser’s local storage, which stays on your device. Because we set no tracking or analytics cookies, there’s no consent banner to click.

The Service isn’t meant for anyone under 18, and we don’t knowingly collect their data.

We operate from Utah, United States. If you use the Service from somewhere else, your data may be processed in the United States.

We may update this policy. We’ll post the new version with its date and let you know about important changes.

Email [email protected].