Privacy policy
Effective October 1, 2026
This policy explains how Veya handles information on this website and in its website account system. Contact Veya at raghava.madhavan@gmail.com with privacy questions or requests. This policy does not describe location processing within the separately installed Veya app.
Information we collect
- Email accounts: your email, name, phone number, and password are submitted to Supabase for account creation and authentication. Passwords are handled by Supabase Auth; the website does not display or store your password in purchase records. Your phone number is a profile field, not a verified phone number.
- Google sign-in: with your permission, Google supplies your account identifier, email address, name, and profile picture to Supabase for your Veya account. We request only identity, email, and basic profile permissions.
- Account activity: account identifiers, authentication sessions, confirmation status, and sign-in timestamps support login and security.
- Purchases: when checkout is enabled, Stripe processes payment details. Veya stores account-linked references to the customer, purchase, plan, payment status, and subscription period so it can recognize paid access. Veya does not receive full card numbers. Checkout currently runs in Stripe test mode.
- Technical information: hosting, authentication, and content-delivery services may process IP addresses, browser information, request times, and logs to deliver the website and protect their services. Information you send to our support address is used to answer your request.
How we use information
We use account information to create and authenticate your account, maintain your session, answer support requests, protect accounts, and associate confirmed purchases with the correct account. Account and purchase identifiers are intended to let you use the same account in the Veya app when that integration is available.
We use Google account information only for these account and authentication purposes. We do not sell Google user data, use it for advertising, or access your Gmail, Drive, contacts, or calendar. Veya’s use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.
Services that handle information
Supabase provides authentication and database storage. Vercel hosts this website. Google provides Google sign-in and web fonts on pages that load them. jsDelivr delivers the authentication library on the account page. Stripe processes payments when you use Stripe checkout. These services receive the information needed to perform their roles and may process it outside your country.
We may also disclose information when required by law or necessary to investigate fraud, protect accounts, or enforce legal rights. We do not include advertising trackers or third-party analytics scripts in this website’s current code.
Browser storage and location
The website stores authentication session tokens in your browser’s local storage to keep you signed in, and a theme preference if you choose day or night mode. Signing out clears the local authentication session. You can also clear site storage in your browser; doing so signs you out on that browser.
This website does not request your device’s precise location. Its day/night theme uses your browser’s time-zone settings locally and does not send those settings to Veya for that calculation.
Retention and security
Account information is retained while needed to provide your account and related services. Purchase records may need to be retained for accounting, fraud prevention, disputes, or legal obligations after an account is closed. Service providers may retain security logs and backups under their own retention practices.
We use HTTPS and authenticated database access. Purchase records are restricted to the owning account, and users cannot change payment status through the website. No internet service can guarantee absolute security.
Your choices and requests
You can choose email sign-in instead of Google. You can revoke Google access in your Google account connections; revoking access does not automatically delete your Veya account.
To request access, correction, deletion, or a copy of your account data, email raghava.madhavan@gmail.com. We may ask you to verify account ownership before acting. Your rights depend on applicable law, and some records may need to be retained for the reasons above. Please do not send passwords or card numbers in your request.
Changes to this policy
We will update this page when our website’s data practices change and update the effective date. If we seek new Google permissions or use Google information for a new purpose, we will explain that change and obtain consent where required.