Orivra1. Who and what this covers
Orivra is an independent project by Nayan Kanaparthi. This notice describes MailWeave, Orivra’s Gmail engine in public beta, and the Orivra pages on this website. Nayan is responsible for the practices described here. This policy does not cover future Slack or Google Drive connectors. Current downloads and requirements are listed on the setup page.
Contact: kanaparthinayan@gmail.com. Google and your AI client operate their own services under their own policies.
2. What Orivra accesses
After you authorize a Google account, the local connector uses Gmail’s API to search and read information needed by the tools your AI client calls. That may include your account email address, message and thread identifiers, message headers, participants, labels, Gmail receipt timestamps, snippets, message bodies, and supported attachment content when requested.
The requested permission is https://www.googleapis.com/auth/gmail.readonly. The connector cannot send, delete, archive, label or edit your messages. You sign in with Google; Orivra does not ask for your Google password.
Read-only access can still expose sensitive information. Only authorize a mailbox you have permission to connect to your chosen AI service.
3. Where your data goes
Retrieval and ranking: Orivra runs on your computer. It retrieves mail from Google, uses local models for semantic processing when available, and constructs the context returned by a tool call.
Your AI client: Selected message content, metadata, source references and graph information are returned to the connected client. In Claude Desktop, those tool results can be sent to Anthropic for model processing and retained in conversations or logs according to your account settings and its policies. Local retrieval does not make Claude’s model processing local.
Model setup: Initial provisioning downloads model files from Hugging Face and its download infrastructure. Those services receive normal download-request information, such as your IP address. This is separate from reading your mailbox; the download process does not send your Gmail messages or Gmail authorization token.
The project operator: The current connector does not route Gmail content or your Google tokens through an Orivra-operated cloud backend. Content you voluntarily send in a support request is a separate disclosure.
4. Storage and retention
The desktop package stores its Google authorization token and local model files under ~/Library/Application Support/Orivra Beta on macOS by default, with authorization in state/ and weights in models/. The self-managed path uses its configured state and model directories. Authorization is kept in a local file with owner-only access permissions; this is not a claim that the file is encrypted by Orivra or stored in the system keychain.
The current connector does not persist message bodies or attachments to an on-disk mailbox index. It holds query context and bounded caches in process memory. Local state such as configuration and freshness markers can persist separately. Closing the server clears its in-memory context, not the copies your AI client may have retained.
Optional local lifecycle diagnostics record call status, timing and schema-derived argument shapes. They are designed not to contain message bodies, subjects, free-text queries or authorization tokens. If you save raw tool results or your AI client logs them, those records can contain email content. You control their storage and deletion.
Local credentials, models and persistent state remain until you remove them. Optional diagnostic files remain at the location you chose until you delete them; they have no automatic retention deadline. Orivra cannot delete a conversation or log held by your AI provider.
5. Use and sharing
Google user data is used to provide the search, reading and information-navigation features you request. Orivra does not sell Gmail data, use it for advertising, or train general-purpose AI models on it. Its local ranking models perform inference only. These statements describe Orivra’s processing, not the independent practices of your AI provider.
We limit Orivra’s use and transfer of Google API data to the purposes described in this policy, in accordance with the Google API Services User Data Policy, including its Limited Use requirements. Sharing with your AI client is part of the requested, visible functionality; it is not permission for unrelated reuse.
The operator has no routine remote access to your mailbox. For support, share only the specific information you choose. Do not send private messages, credentials or tokens. Support correspondence is used to investigate and respond, and retained only as long as needed to resolve the request, related follow-up or a legal obligation. You may request deletion by email; information that must be retained by law is excepted. Copies in the email provider’s backups follow that provider’s deletion schedule.
Before connecting Gmail, review your AI client’s retention and model improvement settings. For Claude, see Anthropic’s retention information and model improvement controls. Orivra does not read or change those settings and cannot promise that the provider will never retain or use content it receives.
6. Your controls
- Revoke Orivra’s authorization from your Google Account’s third-party connections. This stops future authorized Gmail reads.
- Remove the extension or MCP server configuration from your AI client.
- Remove the corresponding local data directory to delete stored authorization and models. Removing the extension alone may leave that directory behind.
- Delete saved conversations, tool results and logs separately through the client or provider that holds them. Revoking Google access does not erase copies already returned.
- Email the contact above about information you sent directly for support, or to ask about access, correction or deletion where applicable.
These actions do not delete or change your original Gmail messages.
7. Website and contact
You can read these product pages without connecting Gmail or creating an Orivra account. These pages do not include a mailing-list form, advertising tracker or third-party video embed. The teaser is served as a static file from this website.
Vercel, the website’s hosting service, processes request information, such as IP addresses and browser details, to deliver and secure the site. Email sent to the contact address is handled by Google’s Gmail service. Those services have their own retention practices; the no-mailbox-backend statement above does not mean visiting this website creates no server logs.
Other sections of Nayan’s portfolio may provide separate features, such as a contact form. This notice does not turn those into Orivra account or Gmail connection services.
The portfolio’s shared stylesheet also loads a stylesheet from Google Fonts. Your browser contacts Google for that resource and may load font files, sharing ordinary network information such as your IP address. The new Orivra typography itself uses locally hosted fonts.
8. Updates and questions
We will update this policy and the product’s disclosures before a material change to Gmail data handling takes effect, and request renewed consent where required. The effective date above identifies the current policy. New connectors or a different data flow require updated disclosures; this policy does not silently extend to them.
Questions? Contact kanaparthinayan@gmail.com, or read the setup overview.