Privacy Policy: OMAE JARVIS Calendar
Effective October 24, 2026
This policy covers OMAE JARVIS Calendar (the "App"), a private macOS desktop application operated by OMAE AI (omaeai.com). The App connects its owner's Google Calendar to JARVIS, the owner's personal assistant. Only the owner uses the App, with the owner's own Google account, and it is not offered to the public. This policy does not cover any other OMAE AI product.
1. Google data the App accesses
With the owner's consent through Google's sign-in, the App requests exactly two Google permissions:
https://www.googleapis.com/auth/calendar.calendarlist.readonly: the list of calendars (names, IDs and access level).https://www.googleapis.com/auth/calendar.events: events on those calendars (such as title, time, location, description, attendees and recurrence), plus the ability to create, change and delete events.
The App does not request or access Gmail, Google Drive, Contacts, the Google profile, or any other Google data. It never asks for or stores the owner's Google password.
2. How the App uses that data
- Reading. When the owner asks a question, the App reads only the events and calendars needed to answer it. Examples are "What's on my calendar tomorrow?", "Am I available Friday afternoon?" and "Which events require my attention?".
- Changes. The App creates, changes or deletes an event only after the owner approves that exact change in a native macOS dialog on their Mac. Higher-risk changes, such as recurring events, events with other attendees, or events within 24 hours, also need a typed confirmation code. Each approval is single-use and expires. The App never invites or notifies other people unless the owner chooses that for the specific change.
- No AI model receives Google data. Calendar requests are interpreted by code running on the owner's Mac, so Google Calendar data is not sent to any AI or language-model service.
- Google user data is not used for advertising, is not sold, and is not used to build user profiles or to train AI models.
3. Where data is stored, and for how long
| Data | Where | Retention |
|---|---|---|
| OAuth client credentials and Google refresh token | macOS Keychain on the owner's Mac | Until the owner disconnects, or until Google expires or revokes the token |
| Short-lived Google access token | In memory only | About one hour at most; gone when the App stops |
| Calendar events and calendar lists read from Google | In memory only, while a request is answered | Not written to disk by the App |
| Proposed changes waiting for approval | In memory only | Until approved, rejected or expired (at most 10 minutes), or until the App stops |
| Settings: time zone, connection status and date, granted permissions, an account label, a partial OAuth client identifier, optional calendar categories, and the ID and name of one calendar the owner selected for testing. A previous copy of this file is also kept. | Local files on the owner's Mac, readable only by the owner's macOS account | Until the owner deletes them |
| Audit log of operational metadata: time, type of action, risk level, calendar category, counts, and a shortened fingerprint of each approved change. It contains no event titles, descriptions, locations or attendee addresses. | Local file on the owner's Mac, readable only by the owner's macOS account | Kept as a security record until the owner deletes it |
OMAE AI runs no server for the App. Google data goes directly between the owner's Mac and Google.
4. Third parties
- Google. The App talks to Google's Calendar API and Google's sign-in service (
accounts.google.com,oauth2.googleapis.com,www.googleapis.com). Google's own privacy policy applies to data held by Google. - Voice features of JARVIS (optional). When the owner speaks to JARVIS, the browser's speech recognition may send audio to its provider (Google, in Chrome) to turn it into text. JARVIS may speak answers using the browser's speech voice, or, in the owner's full JARVIS configuration, ElevenLabs text-to-speech. In that case the text of a spoken answer, which can include event titles and times, is sent to ElevenLabs to produce audio. The owner can type instead of speaking.
- Other JARVIS requests. Requests that are not calendar requests are handled by other parts of JARVIS, which may use third-party AI providers. Google Calendar data obtained by the App is not included in those requests.
Google user data is not shared, transferred or disclosed to anyone else, except where the law requires it.
5. Google API Services User Data Policy
OMAE JARVIS Calendar'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.
6. Revoking access and deleting data
- Within the App, the owner can disconnect at any time. This revokes the token at Google and deletes it from the Keychain.
- Access can also be removed from the Google Account at myaccount.google.com/permissions.
- The local settings file and audit log can be deleted from the owner's Mac at any time.
7. Security
The App uses Google's OAuth 2.0 flow for desktop apps, with PKCE and a loopback redirect, and connects to Google only over HTTPS. Credentials are kept in the macOS Keychain. Changes are checked on the Mac before anything is sent to Google: each needs explicit owner approval, a single-use approval that expires, and a check that the event has not changed since it was read. An emergency STOP ALL switch blocks every calendar action.
8. This website
omaeai.com is a static website. It sets no cookies and uses no analytics or tracking scripts. The hosting provider may keep standard server logs, such as IP addresses, under its own policy.
9. Children
The App is not directed to children and is used only by its adult owner.
10. Changes and contact
If this policy changes, the updated version will be posted on this page with a new effective date. Questions: privacy@omaeai.com.