JARVISby Vyaxai

JARVIS / Privacy policy

Privacy policy

A personal assistant should be clear about what it remembers, where it goes, and who stays in control.

Last updated 14 October 2026

Who operates JARVIS

JARVIS is a personal assistant project operated by Supriyo Dey under the Vyaxai name. This policy covers jarvis.vyaxai.com and the owner-configured JARVIS companion application. Contact supriyo.d.1999@gmail.com with privacy or deletion requests.

This public website

The site describes JARVIS and links to privacy and terms information. It does not offer public registration, access private assistant records, request Google account permissions or record your microphone. Its conversation examples are local demonstrations, not an AI chat.

We do not add advertising trackers or analytics scripts. Vercel hosts this site and may process IP addresses, request details and operational logs to deliver and secure it under its own policies. If you choose to remember a workspace address, it is saved in this browser’s local storage. Clear site data to remove it. It is not sent to this website.

Information in the private assistant

Depending on the features you use, the private app stores your tasks, notes, memories, people, projects, conversations, profile preferences and review receipts on your configured host. The browser can retain drafts and offline records. Connected features may retain permitted WhatsApp messages or summaries, Instagram links, collection names, downloaded media, transcripts and analyses. Only the permissions and scopes you configure apply; a person’s name does not establish access.

Voice and AI processing

When enabled, microphone recordings are processed by the local Whisper service, and spoken replies are generated by a local Chatterbox service. Recognised speech used as a command becomes part of the assistant conversation. Ambient wake-listening transcripts are discarded unless a configured wake phrase is detected.

Your requests, bounded conversation context and relevant selected or recall-enabled records can be sent to OpenAI through your configured ChatGPT connection. Reel understanding may include audio transcripts and sampled video frames. This is not entirely offline processing. The app requests responses with storage disabled; OpenAI’s applicable terms, privacy controls and retention rules also apply. Other providers are not silently substituted.

Google user data: intended connection use

Google connections are currently in setup. Creating this OAuth configuration does not grant JARVIS access to a Google account. Any future connection will require your separate Google consent and will request only permissions needed for the enabled feature.

Planned uses are Gmail messages and metadata for requested summaries and reminder suggestions; Calendar events and availability for planning and reviewed event changes; Drive files you permit for search and knowledge capture; and Google Photos content only through access supported and authorised by Google. Availability depends on the API and the permissions actually granted. JARVIS does not currently claim access to a complete Photos library.

Relevant Google content may be sent to the configured AI provider only when you choose AI processing for that feature or explicitly request it, and only to provide that user-facing assistance. Google content will not be published on this website. Credentials remain server-side and are not included in model prompts. Connection-specific retention and deletion controls must be available before a Google integration is enabled.

JARVIS’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements. We do not sell Google user data, use it for advertising, credit decisions or training general-purpose AI models. Human access is limited to your explicit permission, necessary security or legal purposes, or other uses permitted by that policy.

Storage, security and retention

The public hosting service does not store the private assistant’s databases or credentials. Private remote access uses Tailscale identity checks and workspace authentication. Some connection credentials and Evergreen caches have separate encrypted storage; not every local database, downloaded file or export is encrypted by JARVIS. Protect the host account, device and backups accordingly.

Records and conversations may remain on the host until you remove them. Deletion of a record does not automatically remove earlier conversation snapshots, exports or recovery copies. General record recovery snapshots may be retained locally for up to 14 days; copies you export are controlled by you. Disabling memory recall stops future automatic recall but does not erase previous snapshots.

Your choices and requests

You can review, correct or remove saved information, disable automatic recall, stop microphone features and disconnect available integrations. You may revoke Google access in your Google Account’s third-party connections settings; revocation stops future authorised access but does not itself delete previously saved local copies. Remove those copies through the applicable app controls or contact the operator for assistance. You can request access, correction or deletion using the contact email above.

No system is perfectly secure. JARVIS is intended for its configured owners, not for collecting information about people without an appropriate purpose or permission.

Changes to this policy

We will update this page when data practices change. Material changes to the use of connected Google data will be explained and consent requested before that new use begins.