TARS Privacy Policy
Last updated: October 29, 2026
TARS is a personal assistant tool that MMML operates for their own use. It accesses only the developer's own Google account. This policy describes how TARS handles Google user data.
Data TARS accesses
With the developer's authorization, TARS uses these Google API scopes:
Gmail (https://www.googleapis.com/auth/gmail.readonly): message headers, labels, and message text in the developer's mailbox, and the developer's send-as addresses and their signatures
Gmail (https://www.googleapis.com/auth/gmail.compose): only to save a draft (a reply or a new message) in the developer's drafts folder when the developer asks, and to check that the draft was saved. This scope also permits sending, but TARS has no code that sends email
Google Calendar (https://www.googleapis.com/auth/calendar.readonly): the developer's calendar list and events
Google Calendar (https://www.googleapis.com/auth/calendar.events.owned): only to create an event in the developer's own primary calendar when the developer picks it, and to check that the event was created. This scope also permits changing and deleting events on calendars the developer owns, but TARS has no code that edits, moves, or deletes calendar events
TARS never sends email, never deletes or changes existing email, and never edits or deletes existing calendar events. The only changes it makes are the ones the developer asked for: a draft in Gmail, which the developer reviews and sends themselves, and a new event in the developer's own calendar, with no guests and no invitations or notifications sent to anyone.
How TARS uses the data
To find work requests, deadlines, and follow-ups, and to give the developer briefings and reminders
For messages the developer marks with the Gmail label TARS-restricted, TARS keeps only metadata such as the sender, date, and subject. It does not store their body or attachments and never sends them to an AI service
To understand message text, TARS sends it to the Anthropic Claude API, under Anthropic's commercial terms, only to produce results for the developer
To write a draft, TARS sends the developer's instruction, a few of the developer's own sent replies (as a style example), and either the email thread (for a reply) or the recipient's name and address and the developer's Gmail signature (for a new message) to the Anthropic Claude API. Messages labeled TARS-restricted are never used for drafts
For a new message, TARS finds the recipient's address by name among the senders and recipients of the developer's collected mail, without sending that list to any AI service. Messages labeled TARS-restricted are not searched
To find confirmed events and deadlines missing from the calendar, TARS reads the developer's calendar events each time the developer asks and does not store them. Calendar event titles are never sent to any AI service; to judge whether an event time is confirmed, TARS sends only the task record and its recent messages to the Anthropic Claude API
When the developer picks an item, TARS creates the event with the task's title and time from its own task records and a link to the related message. It never creates events for messages labeled TARS-restricted
TARS does not use Google user data to develop, improve, or train generalized AI or machine learning models
TARS also reads the developer's Slack conversations and stores and processes them the same way
Storage and security
Data is stored only on the developer's own computer, in files that only the developer's user account can read
Access tokens are kept in the same protected files and are never shared
Message bodies are deleted one year after they are collected. Metadata and the developer's own task records are kept
TARS keeps no backups or cloud copies of the data
Sharing
TARS does not sell Google user data, does not use it for advertising, and does not share it with anyone other than the Anthropic processing described above.
TARS's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Removing access and data
The developer can revoke TARS's access at any time at https://myaccount.google.com/connections and can delete all data by deleting TARS's local folder.
Changes
If TARS starts using Google data in a new way, this page will be updated before the change.
Contact