Privacy policy
Last updated October 18, 2026
V8R (v8r.dev) provides sign-in for apps on v8r.app. This policy describes the information we handle when you sign in at auth.v8r.app.
Google user data
If you choose Google, we ask Google only for your name, email address, profile picture, and the basic account identifier used for sign-in. Those are the OpenID, email, and profile fields. We do not request Gmail, Drive, Calendar, contacts, or any other Google product.
We use that information only to:
- create and keep your V8R sign-in
- keep you signed in
- tell the specific v8r app you open your name, email address, whether that email is verified, and profile picture
We store that account record, the sign-in session, and the credential Google returns so we can recognize you on a later visit. The session includes the IP address and browser that started it, which we use only to keep the session working. We do not use the Google credential to read anything else in your Google account.
We do not sell Google user data. We do not use it for advertising. We do not use it to train models. We do not share it with anyone except the v8r app you chose to open, and the companies that host this service (Vercel, Neon, Resend, and Cloudflare). Those companies process it only to run sign-in and to send a verification or sign-in email you asked for.
V8R's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
GitHub and email
GitHub sign-in uses the same fields for the same purpose: name, email address, and profile picture. Email sign-in uses your email address and a hash of your password, not the password itself. We send sign-in and verification messages to that email address.
Deletion
We keep the account until you ask us to delete it. Email privacy@v8r.app from the address on the account and we will delete the account and the Google user data we stored for it.
Contact
Questions about this policy: privacy@v8r.app. The rules for using sign-in are in the terms of service.