Legal
Privacy Policy
In short. JARVIS is a private AI operating system that runs on its owner’s own Mac and is used by its owner. It connects only to accounts the owner authorizes, mostly with read-only access. Its records and credentials are stored on that Mac. When the owner asks JARVIS for help, relevant information is sent to a third-party AI provider to produce the answer. Raybird AI does not sell personal information, does not use it for advertising, and does not use Google user data to train AI models.
1. Who we are and what this covers
Raybird AI (“Raybird AI”, “we”, “us”) is a privately operated AI technology project. It makes JARVIS, a private AI operating system. This policy explains how JARVIS accesses, uses, stores, shares and deletes information, and how this website handles visitor information.
JARVIS is not offered to the public. It runs on its owner’s own Mac and is used by that owner (the “owner”), who connects their own accounts. No one else can create an account. People reach JARVIS only from the owner’s paired devices over a private, encrypted network connection; it is not reachable from the public internet.
2. Information JARVIS processes
JARVIS processes only information the owner provides or connects:
- Conversations and requests the owner types or speaks to JARVIS, and the notes, memories, tasks and decisions the owner chooses to keep.
- Files the owner adds, such as documents, spreadsheets, images, audio and video.
- Connected accounts the owner authorizes. Depending on what the owner connects, these can include Google services (described in section 3), other email accounts (read-only), Slack (read-only), Shopify (read-only reports, products and inventory), and Meta advertising (read-only reporting).
- Public information, such as public websites JARVIS reads when the owner asks for research.
- Supervised browsing. If the owner turns it on and approves a session, JARVIS can read pages in a browser limited to approved sites. These sessions are read-only.
- Device information needed to pair the owner’s devices and, if the owner enables it, deliver notifications to them.
3. Google user data
If the owner connects a Google account, JARVIS uses Google’s OAuth sign-in, and the owner sees and approves the permissions on Google’s consent screen. Each Google service is connected separately and asks only for the access that feature needs.
| Google service | Access requested | What JARVIS does with it |
|---|---|---|
| Google account basics | openid, email | Identifies which Google account was connected, so the owner can tell connections apart. |
| Gmail (read) | gmail.readonly | Reads message details (sender, recipients, subject, date, labels and a short preview) to show the owner’s inbox and what needs attention. It reads full messages and attachments only when the owner opens or asks about them. |
| Gmail (drafts and replies, optional) | gmail.compose | Requested only if the owner chooses to enable replies. JARVIS saves drafts and sends replies only after the owner approves the exact message, and only to people already on that email thread. |
| Google Ads | adwords | Reads account and campaign performance (such as cost, clicks, impressions, conversions and conversion value) and keyword planning ideas, for reporting and analysis. JARVIS does not create, change or delete anything in Google Ads. |
| Google Drive | drive.readonly | Searches and reads the owner’s files when the owner asks, and imports copies of files the owner chooses so JARVIS can use them. JARVIS never changes or deletes Drive files. |
How Google user data is used
Google user data is used only to provide and improve the features the owner uses in JARVIS: showing and summarizing the owner’s information, answering the owner’s questions, preparing reports and drafts the owner requests, and sending replies the owner approves.
How Google user data is stored
Information retrieved from Google is stored on the owner’s Mac, in JARVIS’s local database and files. Google sign-in credentials (refresh tokens) are stored in the macOS Keychain. Short-lived access tokens are kept only in memory. Raybird AI does not operate a cloud server that receives or stores this data.
How Google user data is shared
To answer a request, JARVIS sends the relevant information to its AI provider, Anthropic (section 5). This can include email details or text, advertising figures, or Drive file contents. It happens when the owner asks JARVIS something that needs that information, or when a recurring report the owner set up and approved includes it. Google user data is not shared with anyone else, except where the law requires it (section 7).
Limited Use
Raybird AI’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In particular:
- Google user data is used only to provide or improve user-facing features of JARVIS.
- It is not sold, and it is not used or transferred for advertising, including retargeting or interest-based advertising.
- It is not used to determine creditworthiness or for lending.
- It is not used to develop, improve or train generalized AI or machine-learning models.
- No person reads it except the owner, unless the owner explicitly asks for help with specific data, it is necessary for security or to comply with the law, or it has been aggregated and anonymized for internal operations.
4. How information is used
- To answer the owner’s questions, by conversation or voice.
- To show what needs attention, summarize messages, and prepare drafts, reports, plans and analyses the owner asks for.
- To run recurring reports and alerts the owner sets up and approves.
- To carry out actions the owner explicitly approves, such as sending an email reply.
- To keep JARVIS secure: pairing devices, restricting sensitive settings to the owner’s Mac, and recording what JARVIS did.
JARVIS does not profile people for advertising and does not make automated decisions with legal or similarly significant effects.
5. AI providers
Anthropic (Claude). JARVIS uses Anthropic’s Claude models to understand requests and write responses. AI processing is used only after the owner enables it and sets a spending limit. When it is used, JARVIS sends Anthropic what that request needs. This can include recent conversation messages, relevant notes and memories, files the owner attached, the owner’s reference documents, and results JARVIS retrieved from connected accounts, which may include Google user data as described in section 3. Anthropic processes this data under its own terms and policies. See Anthropic’s Commercial Terms and Privacy Policy. How long Anthropic keeps this data is governed by its terms for API customers; this policy does not claim zero data retention.
OpenAI (image generation, optional). If the owner enables image generation and approves a specific request, JARVIS sends the image prompt and any reference images the owner selects to OpenAI. See OpenAI’s Privacy Policy.
Voice. Speech is normally transcribed on the owner’s Mac, and audio is not sent to an AI provider. If the owner allows a browser speech-recognition fallback, the browser may send audio to its own speech service, such as Google’s in Chrome.
When AI is off. Without AI processing, JARVIS answers simple requests with rules running on the Mac, and nothing is sent to an AI provider.
AI output can be wrong. JARVIS labels where figures come from, and the owner reviews anything that matters before acting on it.
6. Storage and security
- Location. JARVIS’s records, files and cached data from connected accounts are stored on the owner’s Mac. Local backups are also kept on that Mac.
- Credentials. Passwords, tokens and API keys are stored in the macOS Keychain, not in JARVIS’s database or files.
- Access. JARVIS accepts connections only from the Mac itself and from devices the owner pairs with a one-time code, over a private encrypted network. Connecting accounts, changing credentials and changing budgets are allowed only from the Mac.
- Least access. Integrations use read-only access wherever possible. Actions that change anything outside JARVIS need the owner’s explicit approval.
- Encryption. Connections to connected services and AI providers use HTTPS. Data stored on the Mac is protected by macOS security, including full-disk encryption (FileVault), which is turned on for the Mac that runs JARVIS.
- Notifications. If the owner enables notifications, they are delivered through the device platform’s push service (such as Apple’s) in encrypted form. By default a notification shows a short private line, not figures or message content.
No system is perfectly secure. Raybird AI holds no security certifications, and this policy does not claim any.
7. Sharing
Raybird AI does not sell or rent personal information, and does not share it for advertising. Information leaves the owner’s Mac only:
- to the AI providers described in section 5, to answer the owner’s requests;
- to the connected services themselves, when JARVIS requests data from them or carries out an action the owner approved, such as sending an approved email;
- to device push services, for notifications the owner enabled;
- when required by law, or to protect the security of JARVIS or the rights and safety of others;
- in a merger, acquisition or sale of assets, and for Google user data only with the owner’s prior explicit consent.
8. Retention
- Conversations, files, notes and reports are kept until the owner deletes them.
- Cached data from a connected account, such as email details and advertising figures, is kept while the account is connected and deleted when it is disconnected.
- Meeting recordings are deleted automatically after 30 days by default. The owner can change this, and can set a limit for transcripts.
- Paired-device sessions expire after 60 days without use.
- Local backups are kept on the owner’s Mac until the owner removes them.
9. Revoking access and deleting data
- Disconnecting a Google account in JARVIS deletes its stored sign-in token from the Keychain, asks Google to revoke the token, and deletes the cached data from that connection.
- Revoking from Google. The owner can also remove JARVIS’s access at any time at myaccount.google.com/permissions.
- Imported items. Copies of files or attachments imported into a conversation stay until that conversation is deleted. Deleting a conversation deletes its files and removes them from local backups.
- Backups. Local backups made before a disconnection may still contain earlier data until the owner deletes those backups.
Because JARVIS runs on the owner’s Mac, the owner controls deletion directly. Others whose information may be in JARVIS can contact us (section 14).
10. Information about other people
Connected accounts can contain information about other people, such as senders of emails or members of a Slack workspace. JARVIS processes this only to help the owner with their own work, under the same protections described here. For research, JARVIS reads public business websites and public sources only. It does not access private accounts or get around logins, CAPTCHAs or other technical protections.
11. This website
This website is a static information site. It uses no cookies, no analytics, no advertising trackers and no third-party scripts. It is hosted on Cloudflare Pages. Like any web host, Cloudflare processes technical information, such as IP addresses, to deliver and protect the site. See Cloudflare’s Privacy Policy. The website gives no access to JARVIS.
12. Children
JARVIS is not directed to children under 13 (or the equivalent minimum age where you live), and Raybird AI does not knowingly collect their personal information.
13. Changes to this policy
We will update this policy when JARVIS’s handling of information changes, and change the date above. JARVIS will not use Google user data in a new way until this policy describes it and the owner has agreed.
14. Contact
Questions or requests about privacy: raybirdent@gmail.com.