Security and Data Controls

1. Local records and credentials

JARVIS stores desktop conversations and connected-service context in a local SQLite database. API keys and connection credentials use macOS Keychain. From version 0.5.1, the database is encrypted with AES-256 (SQLCipher), its key is kept in macOS Keychain, and its folder is limited to your macOS account. Use an individual macOS account, keep your device updated, and consider FileVault and secure backups. Removing the app may leave data or credentials behind.

Website beta applications are separate server-side records. Applying for access does not upload your Mac’s mailbox or conversations to that application record.

2. Connections and permissions

Google connections use OAuth, so you authorise access on Google’s own consent screen. The email workspace requests read-only Gmail access and, from version 0.5.2, read-only access to Calendar events; the separate general-assistant connection has Gmail modification, Calendar and profile permissions. Review the scope of each connection. You can disconnect in JARVIS and revoke access through your Google Account. From version 0.5.1, removing or disconnecting an email-workspace mailbox also revokes JARVIS’s access at Google, unless it is the same Google account as the general-assistant connection. From version 0.5.2, the reverse also holds: disconnecting the general-assistant connection does not revoke access at Google while an email-workspace mailbox still uses the same Google account; revoke it in your Google Account to end both.

The email workspace’s analysis does not send email or execute its suggested next steps. Automatic sorting has no tools either: it only classifies messages, writes summaries and extracts follow-ups. The general assistant creates Gmail drafts for review. From version 0.5.1, it asks you to allow each memory it saves, email it archives, calendar event it deletes and follow-up it changes. Other connected tools can make changes within their supported permissions, so review actions and their results.

• Manage Google third-party connections

3. Cloud processing is a separate choice

Local storage does not mean local AI processing. General chat can use configured cloud providers and fallbacks; versions that ask you to choose an AI use only that one unless you add others. Email analysis uses the AI you chose or separate local, OpenAI and Bedrock settings; its cloud modes disclose the transfer of group messages, instructions and active memories. Automatic sorting, once you turn it on, sends message details to the AI you chose and, if you add its key, to TypeSafe. From version 0.5.1, email content goes only to AI services that do not train on it, as listed in section 7 of the privacy policy. Voice transcription and speech output have their own provider settings.

Cloud service requests use HTTPS. A supported local email-analysis model avoids that analysis transfer, but email synchronisation, updates, downloads and separately enabled cloud services still need a network connection. This is not an end-to-end encryption or zero-retention service.

4. Disconnecting and deleting

Disconnecting a mailbox stops its local connection and keeps downloaded copies. Explicitly deleting the mailbox account removes that account’s local mail and source-linked memories without deleting Gmail originals. Groups and memories have their own deletion controls. Revoking Google access does not erase existing local copies.

For website application deletion or help clearing local data and credentials, contact us. We may need to verify your identity for server-side records; we cannot remotely erase your Mac.

• contact@jarvis-automation.com

5. Current limits

No system can promise perfect security. JARVIS is in beta; permissions, external services, model behaviour and your device settings all affect risk. The current email workspace does not offer cloud backup or cross-device sync. Public policy pages do not establish a security certification, an independent audit or Google OAuth verification.

Keep independent backups and avoid sending sensitive content to a provider configuration that is unsuitable for that information. The Privacy Policy describes the relevant transfers and controls.

6. Report a security issue

Email contact@jarvis-automation.com with “[Security]” in the subject. Include the affected version or URL, a concise description and reproduction steps using synthetic or redacted data. Do not include live tokens, passwords or another person’s private content.

We review reports and coordinate follow-up through that address. There is no published bounty or guaranteed response-time commitment. Do not access other users’ accounts, retain unnecessary personal data, disrupt services or publicly disclose private information while reporting a concern.

• contact@jarvis-automation.com