JARVIS
Jarvis Personal Assistant · Data practices

Privacy policy

Effective 24 October 2026. Jarvis Personal Assistant is a privately operated assistant for its operator’s personal use.

Google information accessed

With the operator’s Google authorisation, Jarvis can read Gmail message metadata, snippets and selected message contents, and Google Calendar names and events. It requests gmail.readonly, calendar.calendarlist.readonly and calendar.events.readonly. These permissions do not allow it to send or modify mail or create, edit or delete calendar events. The current readers do not retrieve email attachments.

Purpose and processing

Google information is retrieved on demand to answer the operator’s questions, such as finding a message or checking an agenda. The data is processed by the operator’s local workflow service and local AI model, and may be included in private chat or spoken responses. Google content is treated as reference material rather than permission to perform other actions.

Google user data is not sold, used for advertising or used to train a general-purpose AI model. It is not deliberately sent to public web search. Additional services or permissions require a separate setup decision and, where applicable, a new Google authorisation.

Storage and retention

Google authorisation credentials are held in the operator’s local credential storage. Retrieved information and responses may be retained in local workflow execution records and chat history, including voice chats. These records remain until the operator deletes them or their configured retention rules remove them. The public pages on this website do not contain or connect to the operator’s Google account data.

Service providers

Google provides the authorised Gmail and Calendar APIs. The operator hosts the workflow, chat and AI processing services. Cloudflare delivers this public information website and may process ordinary website request information, such as IP addresses and security logs, as described in Cloudflare’s privacy policy. No Google account contents or authorisation credentials are sent to this public website. It sets no application cookies and has no forms, advertising or third-party analytics scripts.

Revoking access and deleting copies

The operator can revoke Jarvis’s access in Google Account connections and remove the corresponding credentials from the local integration. Revocation stops future authorised reads; it does not remove previously retrieved copies. Retained chat and workflow records can be deleted separately in their respective applications. The original messages and events remain in Google unless changed independently by the account holder.

Limited Use

Jarvis Personal Assistant’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.

Contact and updates

The operator can be contacted through the support email shown on Jarvis’s Google authorisation screen. Changes to these practices will be reflected on this page with an updated effective date.