Effective October 19, 2026.
Who is responsible
AI Internet Ventures, at 28 Geary Street, Suite 650, San Francisco, CA 94108, United States, operates Enterface. Privacy requests: build@enterface.io. This notice concerns the Vercel integration; it is separate from Vercel's privacy notice and the Enterface website's signup notice.
Information processed
- Vercel account information returned during identity verification, including an account label; installation and team identifiers; and authorized project API responses used to display project names and IDs.
- An encrypted provider access token, connection identifier, status, expiry times and hashed authorization and handoff values.
- A temporary secure browser cookie and a local callback port used to bind approval to the requesting Mac. The desktop stores an encrypted connection handle rather than the provider token.
- Hashed client-network identifiers for rate limiting. Hosting infrastructure may process IP addresses, request metadata and operational logs.
- Information you choose to send in a support request.
Purposes and access limits
This information enables the connection, verifies authorization, displays accessible projects, prevents replay and abuse, and supports troubleshooting. The implemented integration does not request your Vercel password, read repository contents or environment-variable values, or send project content to an AI model. Provider APIs can return additional fields that the service processes transiently without displaying them.
Storage and service providers
This connection is not entirely local. The Enterface authorization service is configured to store encrypted credentials and connection metadata in Neon Postgres in AWS US East 1 (Northern Virginia, United States). The service runs on Vercel, with its configured function region in Washington, D.C., United States (iad1). These are the configured database and function regions, not a guarantee that all provider processing occurs only in those locations. The desktop stores a protected local handle. Vercel also processes your approval and API requests under its own policies. Hosting, database and support providers may process data to operate these services. Contact us for details about support-mailbox processing or international transfers.
Retention and deletion
Connected token records remain until disconnected. Incomplete authorization attempts expire and are cleaned during later connection starts, rather than immediately at expiry. Disconnect removes the active server-side connection record and local handle. Provider-side authorization must also be removed in Vercel. The configured Neon database history-retention window is six hours; this is recovery history, not the lifetime of active records or a guarantee about every provider backup. Vercel's Hobby runtime-log viewing window is one hour; that is not a promise that all infrastructure or security logs are deleted within one hour. Hosting-provider backup and log retention may be longer; contact us for details. Local caches may remain until cleared or replaced.
Support correspondence
Support and privacy requests go to build@enterface.io. We retain support correspondence for up to 12 months after resolution, unless longer retention is necessary to meet legal obligations or resolve a dispute. This policy applies to support correspondence, not users' Enterface projects or conversations.
Controls and requests
You choose whether to connect and what Vercel access to approve. You can stop using the integration, disconnect, revoke authorization in Vercel, and contact Enterface about access, correction or deletion. Depending on applicable law, you may have additional privacy rights and a right to complain to a regulator. Identity may need verification before a request is fulfilled.
Security and updates
The implementation uses HTTPS, authenticated token encryption, browser-bound state and single-use desktop handoffs. These measures reduce risk but cannot guarantee security. Material changes to data handling should be reflected in an updated notice. Do not send credentials in support messages.