Privacy policy

This policy explains what the vAPI website and console store, when data reaches a service provider, and how account, listing, and payment records are handled.

Last updated: 2026-11-10

Who we are

This website and the vAPI console are published by vAPI Foundation, trading as vAPI Network.

Marketing website

The marketing website does not load analytics or advertising trackers by default. Our hosting provider may keep standard access logs, including IP address, browser details, requested page, and request time, for security and operations.

The website stores the vapi-theme cookie so your light or dark theme choice works across vapinetwork.ai. The cookie is functional and does not identify an account.

Optional analytics

Google Analytics 4 loads only after you choose Allow in the consent notice. If you allow analytics, Google receives usage data such as pages viewed, approximate location derived from IP address, device type, and browser type. Advertising signals are disabled.

You can withdraw consent through Cookie preferences in the footer. Withdrawing consent prevents new analytics collection on later page views. Google may retain data already received under its own privacy and retention terms.

The vAPI Google Analytics property uses the shortest event-data retention period offered by Google, which is two months.

Console account and payment data

When you use the console at api.vapinetwork.ai, we process your public wallet address, username, session data, API key metadata, service-listing and activity records, campaign applications, and related security events. Blockchain transactions and wallet addresses are public on Base.

vAPI Call providers receive signed payment authorizations and may process request data under their own terms.

Email and Google sign-in

We store your sign-in email once on your account, normalised. We use it to sign you in, send sign-in codes and keep one email from being attached to two accounts.

Supabase Auth, our sign-in provider, checks your 6-digit email code or Google sign-in. The email contains no link. Postmark, our email delivery provider, sends it from a vAPI address. With Google sign-in, we receive your verified email and Google's account identifier through Supabase.

We refuse throwaway addresses for new accounts and accept relay addresses.

Coinbase, our wallet provider, creates your wallet and keeps its key after login. Coinbase holds the key; a vAPI-issued token unlocks it. We send Coinbase a short-lived token naming our internal account id. We do not send Coinbase your email address or Google profile. The wallet runs in your browser and connects to Coinbase, which applies its own privacy terms to what it receives.

Add funds uses Coinbase Onramp, Coinbase's own service with its own checks and terms. You can export your wallet key through Coinbase's export flow in the account menu.

We keep a masked email in your browser's local storage for the welcome-back screen. Signing in with a browser wallet involves no email and is unchanged.

vAPI Router

vAPI Router is an OpenAI-compatible inference endpoint. Requests are paid from a prepaid Router balance or from the daily Compute usage limit that stakers receive.

For each request, vAPI Router records usage metadata: the Router key, model, token counts, cost, and time. We use it to meter balances and limits and to show your usage. vAPI Router does not store prompt or response content.

Requests are forwarded to the upstream inference provider of the model you choose, and each model in the catalogue is labelled private or anonymized. For anonymized models, Venice strips user-identifying metadata; the upstream provider's own retention and training policy applies.

API keys and connections

API key secrets are shown when created and are used to authenticate agent requests. Archiving an API key disables it and retains its metadata and activity record.

OAuth clients receive access and refresh tokens after approval. Token rotation and supported revocation endpoints control token validity. Removing a connection from a third-party client may not remove records held by that third party.

Rewards campaign and linked accounts

If you join the rewards campaign, we process your quest activity, points and leaderboard position through our rewards provider, Gizmolab (Loyalty Stacker). Gizmolab receives your account ID, wallet address and username. If you arrive through a referral link, we store which account referred you.

If you link an X, Discord, Telegram, GitHub or LinkedIn account, we store that account's ID and username, and for X, Discord and GitHub when it was created. We use this to verify quests and to check that a linked account is at least 30 days old. A linked account is shown on your public profile only if you choose to make it public.

Abuse and bot protection

When you sign in to the console, we check that the request is not automated. Cloudflare Turnstile runs in your browser for this check, and Cloudflare receives the data it needs under its own privacy terms.

For each new account we keep a record that helps us find automated sign-ups and many accounts made by one person. It holds keyed hashes of your IP address, network range, browser user agent and a device identifier, together with your browser family, first browser language, the network type and country reported by Cloudflare, the timing of the sign-in and setup steps, and the result of an in-browser bot check. We store the hashes, not the raw IP address, user agent or device identifier.

For email and Google sign-ups, this record also holds the sign-in method, a keyed hash of the normalised email and a broad email-domain category, excluding the address itself.

We use a device-intelligence provider, Fingerprint. Its script runs in your browser at sign-in and when you use Earn, loaded from fp.vapinetwork.ai, and Fingerprint processes your IP address and browser details to tell our server whether the browser looks automated, uses a proxy or VPN, or has been altered. The check also receives our internal account id, with no wallet, name or email. We store its verdict and a keyed hash of its device identifier. Fingerprint applies its own privacy terms to the data it receives.

We use these records to give each account a risk score for the rewards campaign. A score can put an account's quests on hold or exclude the account from the leaderboard and from campaign rewards. A person reviews held accounts, and you can ask for a review before rewards are distributed. The score does not stop you from signing in or from using paid services.

We delete sign-up, sign-in and Earn records after 180 days. If the campaign's appeal window is still open at that point, we keep them until 30 days after it closes. Risk scores and review decisions are kept for 400 days.

Third parties

The website and console link to or send requests to service providers such as Base, BaseScan, Circle, Railway, Supabase, Postmark, Coinbase, Upstash, Cloudflare, Fingerprint, Gizmolab, X, Discord, Telegram, GitHub, Google sign-in, Google Analytics when allowed, and providers selected for vAPI Call. Each provider applies its own privacy terms to data it receives.

Changes and contact

Policy changes are posted here with a revised Last updated date. This version is dated 2026-11-10.

Until a Foundation email is published, contact @vAPI_Network on X.

This policy is under review by counsel.