Privacy, plainly.

Vercel access

You provide a Vercel Personal Access Token (PAT). Vercel API requests made with that token go directly from the app to Vercel. The token and saved-account metadata are stored using the iOS Keychain or encrypted Android storage protected by Android Keystore. You can remove them by deleting the saved account in the app.

Data kept on your device

App preferences, selected teams and projects, pinned projects, display settings, and cached API data remain on the device. Environment-variable responses and runtime logs are not written to the app's persistent query cache. Local data persists until it is reset or cleared in the app, removed with the app, or otherwise managed by your operating system.

Home-screen widgets use locally stored display snapshots, including project and deployment names and the selected team's usage and spending. Widget content can remain visible on your home screen while the app is closed. Open Vercat to refresh the displayed data.

Subscriptions

Vercat has no separate account or sign-in. Purchases are handled by Apple on iOS or Google Play on Android. RevenueCat receives a random app identifier and App Store or Google Play purchase information to determine your Pro access. To help us answer billing and support questions, RevenueCat also receives the email address, name, and username of the Vercel account you connected. Your Vercel tokens remain on this device and are never sent to RevenueCat. To use Pro on another device or after reinstalling, restore purchases with the same Apple Account on iOS or the same Google account on Android. Pro purchases are separate between iOS and Android; connecting the same Vercel account does not transfer purchases between stores. Apple or Google sends purchase and renewal receipts. Removing a Vercel connection or deleting the app does not cancel a subscription; manage cancellation in the store where you purchased it.

Basic app, onboarding, and paywall counts

The app sends PostHog a small event when it opens, when an onboarding page is shown, when a Vercel account connection is attempted, fails, or completes, and when the embedded paywall is shown or a purchase starts or completes. These counts are on in production builds so we can see where onboarding stops. Each installation has a separate random identifier used only for these counts. Events include the page name, the release build marker, and whether it runs on a simulator. Development and preview builds do not send these events. They do not include a Vercel account identifier, token, email, device model, or precise location. PostHog does not enrich these events with location from the network address. The identifier is not linked to your Vercel identity or to the optional analytics identifier. This basic counting cannot be turned off in Account settings.

Optional PostHog telemetry

Additional analytics is on by default for new installations. You can turn it off during onboarding or in Account settings. Existing preferences are preserved. Development and preview builds do not send analytics. If PostHog is configured for the distributed build and Additional analytics remains enabled, the app may also send:

• Account-connection, screen-view, app-lifecycle, screen-timing, and navigation data. Activation timing, deployment-action outcomes, logs-feature usage, widget opens, paywall interactions, purchase and restore outcomes, and API request durations and status codes.
• Uncaught exceptions, unhandled rejections, native crashes, and related error context.
• Approximate location derived by PostHog from the network address of a screen-view request, such as country, region, or city. The app does not request device location access.

This data is used to understand feature usage, improve reliability, and diagnose failures. Vercel account IDs, email addresses, names, usernames, PATs, environment values, and console logs are not sent as analytics properties. GeoIP enrichment is enabled only for screen views when analytics is on. Analytics uses a random PostHog installation identifier and is not linked to your Vercel identity. Turning the setting off stops future analytics and crash-event collection from the app.

Feature availability

The app may request anonymous PostHog feature-flag decisions so experimental Vercel API features fail closed if an endpoint changes. These requests use a random installation identifier plus basic app and device context. They are used for app functionality, not advertising, and are not linked to your Vercel identity.

Services and your controls

Vercel, RevenueCat, and PostHog process data under their own privacy policies and service terms. You control Vercel access by managing or revoking your PAT in Vercel and by removing saved accounts from Vercat. You can stop additional analytics at any time in Account settings and delete local app data by removing saved accounts or deleting the app. For privacy questions concerning this app, use the support contact listed with the app.

Request data deletion

Email support@vercat.dev with the subject "Data deletion request" to request deletion of data held by Vercat and its service providers. Include the email connected to your Vercel account and describe the data you want deleted. Never send your Personal Access Token, password, purchase receipt, or access code. We may ask for additional information to verify ownership and locate your records.

We delete records we can associate with your verified request, except information we must retain for legal obligations, fraud prevention, or unresolved transactions. Anonymous events may not be traceable to an individual. Removing Vercat does not delete your Vercel account or cancel an Apple or Google subscription; manage those directly with the relevant service.

Website analytics

This product website uses Vercel Web Analytics to measure aggregate visits and page usage. The website does not receive or process the Personal Access Token stored by the app.

Feature requests and votes

The feature-request board is public, and posting or voting does not require an account. To limit spam, we store a one-way hash of the network address that posted a request, and a one-way hash of a random browser identifier to limit each browser to one vote per request. Do not include credentials or other sensitive information in a feature request.

Support and sensitive information

Never submit Personal Access Tokens, passwords, API keys, webhook secrets, or other credentials in a support message.