MarrosLife Privacy Policy
MarrosLife is a personal tool for sorting email and tracking deadlines. It is built and used by one person, its developer, for the developer's own Google account. It is not offered to anyone else, and no other person's account is connected to it.
Google data MarrosLife accesses
| Permission | What MarrosLife does with it |
|---|---|
Gmailgmail.modify |
Reads message metadata (sender, subject, date, labels) and message text to classify mail and find
deadlines and amounts due. Adds and removes its own labels (names starting with ML/),
archives messages and moves messages to Trash. It never sends email and never permanently deletes
a message.
|
Google Calendarcalendar.events |
Creates or updates an event for a deadline found in an email, only when the user asks it to. |
What is stored, and where
- Stored: message metadata (sender, subject, date, labels), the results MarrosLife produces (category, deadline, amount due, processing status) and reminder records. They are kept in a Supabase (hosted PostgreSQL) database that only the developer can access.
- Not stored: message bodies and attachments. When message text is needed, it is read from Gmail at that moment and discarded after use.
- Credentials: the Google refresh token and client secret are kept in Bitwarden Secrets Manager. Access tokens exist only in memory.
- MarrosLife runs on the developer's own computer and is not reachable from the public internet.
Who else receives data
- Anthropic (Claude API): for each new message, the sender, subject, date received and message text are sent to Anthropic's API to classify the message and extract a deadline and an amount due. Under Anthropic's Commercial Terms, Anthropic may not train models on this content.
- LINE (reminders, when enabled): a reminder sent to the developer's own LINE account, containing only the sending organisation, the type of mail, the deadline and a short title — no account numbers, card numbers or full amounts.
- No one else. Data is never sold and never used for advertising.
Limited Use
MarrosLife's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is not used to develop, improve or train generalised AI or machine-learning models.
Keeping and deleting data
Stored records are kept while MarrosLife is in use, and the developer can delete them at any time. Revoking access (below) stops all further access to Gmail and Google Calendar.
Revoking access
Remove MarrosLife under Google Account → Security → Your connections to third-party apps & services (myaccount.google.com/connections). After that, MarrosLife can no longer read or change anything in Gmail or Google Calendar.
Security
- MarrosLife asks for the narrowest permissions that cover its features: no permanent deletion, no full mailbox access.
- All connections to Google, Anthropic, Supabase and LINE use HTTPS.
- Credentials are never written to logs or error messages.
Changes
Changes to this policy are posted on this page with a new “Last updated” date.
Contact
Questions about this policy or a request to delete data: privacy@marros.dev