Privacy at Verception
The data that Verception keeps, why it keeps it, who else gets it, and how to delete it.
Updated
Who is responsible for your data?
Vercel Inc. operates Verception and is responsible for the data on this page. For a question or a request about your data, write to privacy@vercel.com and name Verception in the message.
What data does Verception keep?
| Data | Why Verception keeps it |
|---|---|
| Email, username, and a hash of the password | To sign you in. Verception never keeps the password itself |
| Hashes of API keys and OAuth tokens, with their names and scopes | To check each API request. The full key shows only one time |
| Projects, deployments, domains, and settings | To build and serve your apps |
| Uploaded files and build logs | To build each deployment and show its log |
| Encrypted environment variable values | To give them to your builds and apps. Nobody can read a value back |
| Chat messages of a project | To write and change the code of the project |
| Your GitHub user ID and an encrypted GitHub token, when you connect GitHub | To list your repositories and deploy each push |
| Counts of AI requests and spend for each day | To keep each account under its daily AI limits |
| Client IP addresses of failed sign-ins and of sign-ups, for a short time | To stop password guesses and mass sign-ups |
How do I delete my data?
Delete a project in its settings, or delete your account in the account settings. An account delete removes every project, deployment, domain, store, sandbox, API key, and OAuth token of the account at once. To ask for a copy of your data, or for a delete that you cannot do yourself, write to the privacy address above.