VRouter provides an OpenAI-compatible API gateway. This policy describes what data we collect, how we use it, and what we never touch.
2. What We Collect
Email address — Used solely for account creation, authentication, and OTP verification.
API usage metadata — Model name, token counts (input/output), request latency, and success/failure status. No prompt or completion content is stored.
Account activity — Total requests, cumulative token usage, and API key creation timestamps.
3. What We Do NOT Collect
Prompts or completions — Your request and response content passes through the gateway but is never logged, stored, or shared.
IP addresses — We do not log or store client IP addresses.
Browsing behavior — No analytics cookies, no tracking pixels, no third-party scripts on dashboard pages.
4. How We Use Your Data
Usage metadata is used exclusively for:
Routing optimization and provider failover decisions
Per-account usage display in the dashboard
Fair-use enforcement and rate limiting
5. Data Storage and Security
Account data is stored in an encrypted SQLite database on our infrastructure. API keys are hashed — we store only the derived hash, never the plaintext key. All communication occurs over TLS.
6. Cookies
VRouter uses a single session cookie for authentication. No advertising, analytics, or third-party cookies are set.
7. Third-Party Services
We forward API requests to upstream model providers (OpenAI, Anthropic, Google, etc.) to fulfill completions. These providers may process your prompts according to their own privacy policies. We do not share your email or account data with any third party.
8. Data Retention
Account data — Retained while your account is active. Deleted within 30 days of account deletion request.
Usage metadata — Retained for 90 days for routing analytics, then aggregated and anonymized.
API prompts/completions — Never stored.
9. Your Rights
You can request export of your account data or permanent deletion at any time by contacting us. Account deletion removes your email, API keys, and usage history.
10. Changes to This Policy
We will notify registered users of material changes to this policy via email. Continued use of the Service after notification constitutes acceptance.
