JJARVIS
Effective October 29, 2026

Privacy Policy

This policy describes how the owner-operated Jarvis personal assistant uses information from Google accounts that their account holders expressly connect. Jarvis is not a public service or a Google product.

1. Google account data requested

Depending on which features an account holder elects to connect and the scopes presented on Google's authorization screen, Jarvis may access:

Actual permissions are determined by Google OAuth consent. Not every connected account has all of these permissions. An authorization for one Google account is not permission to access another.

2. How the data is used

Google account data is used to provide the user-requested functions above: summarizing relevant correspondence, presenting reminders, preparing approval-gated messages, helping with documents and school-related organization where authorized, and carrying out expressly approved calendar or file actions. Jarvis is not used for advertising, building consumer profiles, resale, or credit decisions.

3. Processing and sharing

The Jarvis system primarily runs on equipment controlled by its operator. It can use local models and separately configured AI or service providers to process selected information for requested assistant features. If an enabled feature sends selected Google information to a third-party processing service, that provider receives information associated with that request and applies its own data-handling terms. The operator should review the enabled integrations before using them with sensitive account content.

Jarvis does not sell Google user data, share it with advertising networks, or intentionally supply Google data for training generalized AI models. It only transfers account data to perform authorized user-facing features, to maintain security, or where legally required, consistent with Google's API Services User Data Policy.

4. Storage and security

OAuth credentials and local work records are stored on the operator's own computer in access-restricted files. The assistant may store message-derived task notes, local documents, audit receipts, scheduling information and limited cached information needed to provide continuity. Some files may be backed up to owner-controlled storage. The public website you are currently reading is separate from the private application and does not host Gmail inboxes, Google account files or OAuth tokens.

Connections to Google use Google's authorization system and encrypted HTTPS requests. No security measure completely eliminates risk; the operator limits local access and maintains appropriate software controls.

5. Retention and deletion

Local data is retained while needed for requested assistant functions, follow-up history, or authorized backups. Account holders may revoke Google access at any time in Google Account Connections. Revocation prevents future authorized access but does not automatically delete local copies previously made; users may request removal of locally stored account-derived materials and backups from the operator. Removing data may affect the assistant's history and reminders.

6. Children and additional accounts

Google accounts used for household or school assistance are treated separately. Access is requested and verified for each authorized identity. When a minor's account is involved, connections and use must be authorized by a parent or other permitted account administrator and comply with the account's applicable Google controls.

7. This public site

This site contains static information pages and does not include an application sign-in form, analytics scripts, advertising trackers or third-party fonts. The web host may maintain ordinary server records such as IP addresses, request times and browser details for security and operations.

8. Changes and contact

This policy may be updated as Jarvis features or providers change. The updated effective date will appear here. For questions about Google account access, privacy, or deletion requests, contact the operator at howcome008@gmail.com.