Privacy

What Jarvis does with your data

Jarvis is a Mac app that reads your mail, your calendar, and your chat so it can tell you what your day looks like. That is an unusual amount of access, so this page is specific about what it reads, where the result sits, and the one case where anything leaves your machine.

The short version

Your mail stays on your Mac: Jarvis reads Gmail into a database inside your own user library. There is no copy of it on any server we run.
We hold no account for you: The app has no backend that stores your messages, meetings, or tasks. Nothing to breach, nothing for us to hand over.
One thing does leave: Text is sent to Anthropic when Jarvis writes your day or finds tasks. Section 5 says exactly what, and how to turn it off.
Deleting is deleting: Drag the app to the bin and delete one folder. The data is gone, because it was only ever in that folder.

1Who we are

Jarvis is built and operated by Palina Shymanovich, an individual trading as Jarvis, based in Poland. For the purposes of the EU General Data Protection Regulation, she is the data controller for the limited personal data described in sections 9 and 10.

Reach us at jarviscontext@gmail.com. This policy covers the Jarvis macOS application and the website at www.jarviscontext.com.

2Google user data we access

Jarvis accesses Google user data only through the OAuth scopes below. When you connect a Google account in Settings, it asks for the two read-only data scopes. The three sign-in scopes are asked for only if you sign in with Google to use shared access. Each scope is here because a specific feature needs it, and Jarvis accesses no other Google user data.

gmail.readonly

Reads: Messages in your inbox, for the history window you pick: the sender, subject, date, and body text of each one, plus the connected mailbox's own address, used to label the account. Attachments are never downloaded.
Used for: Finding the requests, tasks, and commitments buried in your mail, and showing you which email a task came from.
Stored: A database file on your Mac. Read only: Jarvis cannot send, delete, or alter a message.

calendar.events.readonly

Reads: Today's events on your primary calendar: title, start and end time, how many people are invited, your own reply (so declined meetings are hidden), and the joining link, which Jarvis looks for in the event's conference details, location, or description.
Used for: Drawing today's meetings on the Focus screen, with a Join button that opens the call.
Stored: Nowhere. Calendar events are held in memory while the screen is open and are never written to disk.

openid · email · profile

Reads: Your name, email address, profile picture, and Google account ID, from the signed token Google returns when you sign in with Google. Requested only if you use shared access.
Used for: Signing in to shared access (section 5). Our relay checks the verified email address against the list of people we have given access.
Stored: Nowhere on our side. The relay reads the email address, issues a time-limited session token, and keeps nothing. The app stores that session token on your Mac.

You choose how far back the first sync reads, 7, 30, or 90 days, in Settings before you connect. Jarvis never requests write access to Gmail or Calendar, so it cannot send mail, delete mail, or change an event.

Limited Use

Jarvis's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Concretely: Google user data is used only to provide and improve the features described above. It is never sold, never used for advertising, never used to train any machine learning or generative model, and is never read by a human at Jarvis. We have no ability to read it, because we never receive a copy.

Jarvis does not use Google Workspace API data to develop, improve, or train generalized or non-personalized AI or ML models. The model provider named in section 5 does not train on data sent through its API.

3Where it is stored

Everything Jarvis syncs is written to a single folder on your own Mac: ~/Library/Application Support/JarvisGuide/.

messages.db holds the text of synced emails and meeting transcripts, and the tasks Jarvis found in them.
meetings/ holds meeting audio and transcripts, if you use meeting capture.
OAuth credentials are stored beside them as files readable only by your own user account.

Nothing in that folder is copied to a server we run. It stays there until you delete it, as described in section 8.

4How we protect your data

Google user data, and everything else Jarvis reads, is protected in the following ways.

Encrypted in transit. Every request to Google, to Anthropic, and to our relay uses HTTPS (TLS). The only unencrypted connections are the ones that never leave your Mac, such as the sign-in redirect back to the app on 127.0.0.1.
No passwords. Google sign-in uses OAuth 2.0 with PKCE in your own browser. Jarvis never sees your Google password.
Credentials locked to your account. OAuth tokens are stored on your Mac as files only your macOS user can read (permission 0600, in a folder only you can open), and never on a server.
Stored on your device. Email text and tasks sit only in your own user library, behind your macOS login. We recommend keeping FileVault on, which encrypts the whole disk, this folder included.
Only what is needed. Scopes are read-only. Only your inbox, within the window you pick, is synced. Attachments are never downloaded, and calendar events are never written to disk.
No central copy. We run no database of your content, so there is no central store to breach. Our relay forwards requests without storing or logging their content.
Verified software. The app is signed with an Apple Developer ID, notarized by Apple, and runs with the hardened runtime. Updates are cryptographically signed, and the app checks the signature before installing one.
Access ends on disconnect. Disconnecting a Google account asks Google to revoke the token and deletes it from your Mac.

If you find a security problem, write to jarviscontext@gmail.com.

5When data leaves your Mac

Some Jarvis features are written by a large language model: the sentence that opens your day, the task finder, task extraction from mail, and meeting summaries. Those features send text to Anthropic, the company behind Claude. This is the only routine case where content leaves your machine.

What is sent

The relevant excerpts for that request, which can include the subject and body text of emails, Slack or Teams messages Jarvis read for that request, the transcript of a meeting you recorded, and the titles of tasks Jarvis already knows about. Only what the request needs is sent, not your database.

How it is sent

With your own Anthropic API key, the app calls Anthropic directly over HTTPS. Nothing passes through us.
With shared access, the request is relayed by a small server we run so that our key can be used instead of yours. That server forwards the request to Anthropic and returns the answer. It does not store, log, or inspect the content of your request.

What Anthropic does with it

Anthropic processes the request to produce a reply and does not use data submitted through its API to train its models. Their handling is governed by their own terms and privacy policy, which you can read at anthropic.com/legal/privacy.

Turning it off

These features are the reason to use Jarvis, so they are on by default. If you remove your API key and do not use shared access, the model features stop. The rest of the app keeps working: mail still syncs, your meetings still show, and meeting capture still records, but Jarvis stops finding new tasks.

6Slack, Microsoft Teams and meetings

Slack and Microsoft Teams

Both are read live and nothing is kept. When Jarvis looks for tasks, or shows you where a task came from, it asks their API at that moment, uses the reply, and discards it. No Slack or Teams message text is ever written to the database. Jarvis only ever looks in the conversations you select.

Meetings

Meeting capture is off until you start it, and it records the audio of the call on your Mac. Transcription runs on your machine with a speech model that ships with the app, so the audio itself is never uploaded anywhere. The resulting transcript is text like any other, which means a summary of it follows section 5.

Recording other people has legal requirements that vary by country. Telling the people on the call is your responsibility, not ours.

7What we never do

We never sell your data, and we have nothing to sell: we hold no copy of it.
We never use your content for advertising or profiling.
We never use your content, or any Google user data, to train a model.
No employee or contractor reads your messages. There is no administrative console that could show them.
We do not share your content with any third party beyond the model provider named in section 5.

8Deleting data and revoking access

Because your data lives on your own machine, deleting it is something you do rather than something you request.

Disconnect the account

Settings, then Gmail, then Disconnect. This asks Google to revoke Jarvis's access to that account and deletes the stored credential from your Mac.

Delete the local data

Quit Jarvis and delete ~/Library/Application Support/JarvisGuide/. That folder is every message, meeting, task, and credential the app holds.

Revoke our access at Google

Independently of the app, at myaccount.google.com/permissions. Revoking stops any further reading immediately.

If you would rather we did it, or you want confirmation of what we hold, write to jarviscontext@gmail.com and we will answer within 30 days.

9This website

The website is separate from the app and is the only place we collect anything ourselves.

Analytics. We use PostHog, hosted in the European Union, to count visits and see which pages work. Session recording is on, with every form field masked, so what you type is not captured.
Early access list. If you give us your email address, we store it in a private spreadsheet to email you about Jarvis. Ask us to remove it at any time and we will.

Website data is kept for as long as it is useful and no longer than two years. We do not run advertising trackers.

10Your rights

Under the GDPR you may ask for a copy of the personal data we hold about you, ask us to correct or erase it, object to our using it, ask us to restrict how we use it, or ask for it in a portable form. Write to jarviscontext@gmail.com.

In practice the answer is usually short, because the only personal data we hold about you is an email address you gave us and the website analytics in section 9. Everything the app reads stays with you. If you believe we have handled your data badly, you may complain to your national data protection authority. In Poland that is the President of the Personal Data Protection Office.

11Changes to this policy

If this policy changes in a way that affects what Jarvis does with your data, we will change the effective date below and say what moved. Continuing to use Jarvis after that counts as accepting the new version. A change that would widen what we collect will be put to you in the app before it takes effect, not buried here.

22 September 2026: added section 4 on how we protect your data, listed the sign-in scopes in section 2, and removed references to a local search index the app no longer builds. What Jarvis collects did not change.

12Contact

Palina Shymanovich, operating as Jarvis, Poland.
jarviscontext@gmail.com

Questions about a specific clause are welcome and get a real answer.

Effective 22 September 2026. See also the terms of service.