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-08-06

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 console.vapinetwork.ai, we process your public wallet address, 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.

Compute status

Compute is not active. The current console exposes only its future product status.

Pricing, data retention, privacy, and provider terms will be published before Compute opens.

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.

Third parties

The website and console link to or send requests to service providers such as Base, BaseScan, Circle, Railway, 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-08-06.

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

This policy is under review by counsel.