VEYRA

Privacy Policy

This policy explains what information VEYRA collects, why it is collected, how long it is kept, and the choices you have. VEYRA is a personal AI assistant that only acts on your data to deliver the features you ask for.

Last updated: 30 August 2026

1. Account and profile data

When you create a VEYRA account we process your name, email address, authentication identifiers and basic profile settings such as time zone, language and notification preferences. This information is used to create and secure your account, personalize your assistant, and communicate essential service messages.

2. Conversation and task data

Your messages to VEYRA, its responses, the tasks and priorities you create, and the memories you explicitly ask VEYRA to remember are stored so the assistant can maintain context across sessions. You can review, edit and delete this content from within the product. Deleting a conversation, task or memory removes it from your active workspace.

3. Gmail data

If you connect Gmail, VEYRA accesses message metadata (such as sender, recipients, subject, labels and timestamps) and message content where it is needed to surface relevant email context, detect important or time-sensitive email, extract tasks, and prepare drafts or replies you requested.

  • Drafts and replies are sent only after your explicit approval for the specific action.
  • VEYRA does not delete or modify email.
  • Gmail content is never used to train generalized or third-party AI models.
  • Gmail content is not used for advertising or profiling of any kind.

4. Google Calendar data

If you connect Google Calendar, VEYRA's access is read-only. It reads events, times, locations, attendee information and availability solely to build accurate meeting and calendar context for your daily briefing and suggestions. VEYRA does not create, move, cancel or otherwise modify calendar events.

5. Google Contacts data

If you connect Google Contacts, VEYRA's access is read-only. It reads contact names, email addresses and phone numbers solely to resolve the people you mention to the correct recipient. VEYRA does not add, modify or delete contacts. Contact data is not used to build marketing lists, is not shared with other users, and is not enriched with external data sources.

6. OAuth credentials

When you connect a Google service, Google issues VEYRA an access token and a refresh token. These credentials are stored encrypted at rest, scoped to the permissions you granted, and used solely to make API requests on your behalf. VEYRA never receives or stores your Google password, and never asks you for it.

7. Why VEYRA accesses this data

Access is strictly purpose-limited. Each permission maps to a feature you asked for:

  • Daily context and priorities — combining calendar, email and task signals into a single clear briefing.
  • Email awareness — surfacing important messages and drafting replies for your review.
  • Calendar context — using read-only calendar information to inform scheduling suggestions and daily planning.
  • Correct recipients — matching the people you mention to real contacts.

VEYRA does not use connected data for advertising, resale, credit assessment, or any purpose unrelated to the features described in this policy.

8. Data retention

Account data is retained while your account is active. Conversations, tasks and memories are retained until you delete them or request account deletion. Data fetched from Google services is kept only as long as needed to deliver the requested feature, and cached copies are refreshed or discarded on an ongoing basis. Account and stored Google user data deletion is available on request as VEYRA moves toward public release; when an account is deleted, associated personal data and stored Google user data are deleted from production systems, with routine backups expiring within 30 days. Limited records may be kept longer only where required by law.

9. Disconnecting Google integrations

You can disconnect any Google integration at any time from VEYRA's settings, or revoke access directly from your Google Account permissions page at myaccount.google.com/permissions. Disconnecting revokes the stored tokens, stops all further API access, and deletes cached data derived from that integration.

10. Security safeguards

  • Encryption in transit (TLS) and at rest for stored data and credentials.
  • Least-privilege access controls and scoped OAuth permissions.
  • Secrets kept in managed secret storage, never in application code.
  • Audit logging of sensitive operations and administrative access.
  • Approval gates in front of every action that sends, changes or deletes your data.

No system can guarantee absolute security, but VEYRA is designed to minimize the data it holds and the number of paths that can reach it.

11. No sale of user data

VEYRA does not sell, rent or trade user data or Google user data, and does not transfer it to third parties except to service providers strictly necessary to operate the product, when required by law, or with your explicit instruction.

12. Google API Services User Data Policy

VEYRA's use and transfer of information received from Google APIs to any other app adheres to the Google API Services User Data Policy, including the Limited Use requirements.

13. Changes to this policy

If this policy changes materially, VEYRA will update the date at the top of this page and notify you in the product before the change takes effect for connected data.

14. Contact

Privacy questions, access requests and deletion requests can be sent to lobukk12@gmail.com.