Privacy Policy
Google user data JARVIS accesses
When the user explicitly connects a Google account, JARVIS may access the minimum Google user data needed for the enabled feature. This can include Google account identity information used to verify the connected account, Google Calendar event data used for personal calendar look-ahead, Gmail message metadata and message content needed for user-requested search or reminder functions, Gmail label information, and OAuth credentials required to maintain the authorized connection.
How Google user data is used
Google user data is used only to provide the personal functions requested or configured by the user. Examples include showing upcoming personal calendar events, identifying reminders in Gmail messages that have been explicitly authorized as personal data, and carrying out narrowly scoped Gmail mailbox-management actions that require separate user authorization under JARVIS's permission model.
Google user data is not used for advertising, marketing profiles, credit decisions, or sale to third parties.
Storage and security
JARVIS runs primarily on the user's personal Windows computer. Google OAuth credentials are stored locally and protected using Windows Data Protection API (DPAPI). JARVIS is designed to keep authentication secrets out of command-line arguments, version control, and ordinary audit records.
Google message or calendar content may be processed locally when a requested feature needs it. JARVIS may retain minimal local operational state needed for execution, verification, deduplication, scheduling, and auditing. It is designed to avoid copying full provider content into version-controlled memory or ordinary audit logs when that content is not necessary.
Sharing and disclosure
JARVIS does not sell or rent Google user data. JARVIS does not intentionally disclose Google user data to advertisers or unrelated third parties. Data is transmitted to Google APIs as necessary to perform the authorized Google integration itself.
Permissions and user control
JARVIS separates permission to act from permission to process data. Gmail content-processing features use a positive personal-data authorization model so that messages from unknown or ambiguous sources are not automatically treated as personal data. Higher-impact mailbox changes require separate action authorization.
The user can revoke JARVIS's Google access through the Google Account permissions interface and can remove locally stored JARVIS credentials and operational data from the user's computer.
Data retention
JARVIS retains only the local information needed to operate its configured features, verify actions, prevent duplicate processing, and maintain security and auditability. Retention may vary by feature. The user controls the local computer and may remove JARVIS runtime and credential data when the integration is no longer wanted.
Google API Services User Data Policy
JARVIS's use of information received from Google APIs is intended to comply with the Google API Services User Data Policy, including its Limited Use requirements.
Changes to this policy
This policy will be updated if JARVIS materially changes how it accesses, uses, stores, or shares Google user data.