mb-assistant Privacy Policy
Last updated 2026-10-25
1. Who operates mb-assistant and who uses it
mb-assistant is built and operated by Sam Al-Harbi, an individual, for his own use. It is a single-operator application: the only Google accounts it connects to are the operator's own accounts, and the only person whose data it processes is the operator. It is not offered to the public and has no other users. This website sets no cookies and runs no scripts; it is hosted on GitHub Pages, whose own privacy statement covers that service's server logs.
Contact: samuel.alharbi.re@gmail.com.
2. Current status
mb-assistant is in development. Its Google OAuth application is in Testing status and, as of the date above, no Google user data is processed or stored in production. This policy describes how the application is designed to work and will be updated when that changes.
3. Google data accessed
mb-assistant uses Google OAuth. The operator authorizes each of his Google accounts separately, and each can be disconnected separately. The scopes are:
| Scope | Status | Used for |
|---|---|---|
https://www.googleapis.com/auth/gmail.readonly | Requested now | Reading mail to prepare the brief, triage and reply drafts |
https://www.googleapis.com/auth/calendar.readonly | Planned | Reading events for the brief, conflicts and open times |
https://www.googleapis.com/auth/calendar.events | Planned | Placing calendar holds and, after the operator approves, events with invitees |
https://www.googleapis.com/auth/gmail.compose | Planned | Saving drafts and, after the operator approves each one, sending replies |
Within those scopes the application reads message headers and bodies and calendar event details. It is designed to strip attachments at intake and to filter out financial account numbers and government identifiers so that such content is neither stored nor sent for processing.
4. How the data is used
Google data is used only to provide the assistant's functions to the operator: a daily brief and recap, sorting the inbox, drafting replies in the operator's own voice, proposing meeting times, and creating reminders. Message content is processed by Anthropic's Claude API under Anthropic's commercial API terms to produce those drafts and summaries. Content is limited, in code, to the thread being worked on and the matched contact's own records.
mb-assistant does not use Google user data for advertising, does not sell it, and does not use it to develop, improve or train generalized artificial-intelligence or machine-learning models. No person other than the operator reads the data, except as needed for security purposes, to comply with applicable law, or with the operator's explicit consent.
5. Where the data is stored and how it is protected
The application runs in the operator's own Amazon Web Services account in the us-east-1 region. Data at rest is encrypted (DynamoDB server-side encryption and S3 encryption with AWS KMS). Google credentials are held in AWS Secrets Manager and each component may open only the secret it needs. Read access and send access use separate credentials, and only one component holds send credentials. Nothing is sent to anyone unless the operator has approved that exact message.
6. How long data is kept
- Message text used for drafting: designed to be kept for 30 days.
- Proposals, decisions and execution records: 90 days, deleted automatically.
- Audit records of approved actions: locked for 366 days in write-once (compliance-mode) storage. These records cannot be altered or deleted by anyone, including the operator, before the lock expires. A body-free index of each approval (hash, message id, timestamp) is designed to be kept for six years.
- Application logs: 30 days; logs never contain a full message body.
7. Sharing
Google user data is not sold, rented or shared with third parties. It is handled only by the service providers that operate the application on the operator's behalf: Google (the source of the data), Amazon Web Services (hosting and storage) and Anthropic (the Claude API). Emails the application itself sends go only to the operator's own addresses, which are fixed in the code; replies drafted for other people are sent only after the operator approves each one individually.
8. Revoking access and deleting data
The operator can revoke mb-assistant's access to any connected Google account at any time at https://myaccount.google.com/permissions. Revocation stops all further reading of that account. Stored records then expire on the schedules in section 6; locked audit records cannot be removed until their retention period ends and become eligible for deletion only then. Questions about this policy or about stored data go to samuel.alharbi.re@gmail.com.
9. Google API Services User Data Policy
mb-assistant'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.
10. Changes to this policy
Changes are posted on this page with a new "Last updated" date.