Privacy Policy

This policy explains how Hagrid, a private and non-commercial personal AI assistant, handles data when it reads Gmail and Google Calendar and performs confirmed write actions on behalf of two authorized users.

Effective date: 1 November 2026. Last updated: 1 November 2026 (two-user access and confirmed write actions).

1. Who operates Hagrid

Hagrid is a personal project operated by an individual on a private server. It is not a company, a public service, or a commercial product. It serves exactly two authorized users; each person authorizes their own Google account and is bound to exactly one Telegram identity on the server. The operator is the data controller for the assistant's local storage. You can contact the operator through the private Telegram chat in which you use Hagrid.

This website is a static informational site. It does not provide the assistant itself and does not ask you to sign in.

2. Google access and scopes

Hagrid uses Google OAuth to access only the services you authorize. The current deployment requests the following scopes for each user who completes the consent flow:

Scope	Purpose
`gmail.readonly`	Search and read Gmail messages, threads, attachments, and labels.
`gmail.labels`	Create and manage Gmail labels you ask for.
`gmail.modify`	Apply labels, archive, mark as read or unread, and move messages to Trash after confirmation.
`gmail.compose`	Create and update drafts, and send a draft you confirmed.
`gmail.send`	Send a new message or a reply in the existing thread after confirmation.
`calendar.readonly`	List calendars, read events, and check free/busy information.
`calendar.events`	Create, update, or cancel events you confirmed, including attendees and timezone.
`calendar`	Full Calendar access requested by this deployment. It permits managing calendars and their sharing settings; the assistant currently exposes only reading and confirmed event changes, and blocks calendar creation, deletion, and access-control changes until dedicated server-side restrictions and confirmations exist.
`openid`, `userinfo.email`, `userinfo.profile`	Identify the authorized Google account and display basic account information.

Hagrid does not request Drive, Docs, Sheets, Contacts, Gmail settings, Gmail filters, or any other Google service. It cannot permanently delete Gmail messages, run bulk operations, change account settings, create or delete calendars, change calendar sharing or access-control settings, or send automatic or scheduled mail. Trash is the only deletion path exposed for mail, and every write action requires an explicit confirmation from the same Telegram user before the server calls Google.

3. What data is processed

Telegram messages you send to the assistant, including the requests you type.
Selected Gmail content such as message metadata and the body of messages you ask Hagrid to read.
Selected Google Calendar content such as calendar names, event details, and free/busy results you ask for.
OAuth credentials (access and refresh tokens) issued by Google for the authorized account. Each user's credentials are kept in a separate restricted store.
Pending action previews you confirm in Telegram: recipients, subject, body, label changes, or event title, time, timezone, and attendees. A pending action expires and is not written to ordinary logs or shared memory records.
Confirmation metadata such as the approving Telegram identity, action status, expiry, and an idempotency key, used to prevent replay and double execution.
Assistant session history and operational metadata needed to run the assistant, diagnose failures, and maintain security.

Diagnostic records for Google tool calls are designed to exclude message bodies, event details, OAuth tokens, authorization codes, and authorization URLs; they retain only operational metadata such as the tool name, status, duration, and size. A confirmation claimed by the language model is not an authorization; only a confirmation received from the bound Telegram user is accepted.

4. How data is used and shared

Data is used only to perform the requests you make, to operate and secure the assistant, and to comply with applicable law. Hagrid does not sell Google user data, does not use it for advertising, and does not use it to determine creditworthiness or for lending.

Hagrid does not use Google user data to develop, improve, or train generalized AI or machine-learning models.

External LLM provider

Hagrid uses an external large language model provider, DeepSeek, to understand requests and compose responses. When you ask about Gmail or Calendar, the selected content needed to answer the request may be included in the prompt sent to DeepSeek. This can include message bodies, event details, and the text of your request.

DeepSeek processes that data under its own terms and privacy policy. The operator does not control DeepSeek's retention, deletion, or training practices and does not represent that DeepSeek never stores or uses data for model improvement. Review DeepSeek's current privacy policy before sending sensitive content. If you are not comfortable with this, do not ask Hagrid to read sensitive messages or events.

Other service providers

Google provides Gmail and Calendar APIs under Google's terms and privacy policy.
Telegram delivers the chat messages you send; Telegram's terms and privacy policy apply to that transport.
The static hosting provider for this website may keep standard access logs under its own policy. This site does not add analytics.

Data may also be disclosed if required by law, to protect the security or rights of the operator or others, or with your consent. It is not shared for unrelated purposes.

5. Storage, security, and backups

OAuth tokens are stored on the operator's private server in separate restricted stores, one per user, with access limited to that user's assistant profile. They are not stored in this website or in the public repository.
Pending write actions are stored server-side only until they are confirmed, cancelled, or expire, and are bound to the Telegram user who requested them.
Session history and operational records are stored on the same private server and are separated per user profile.
Backups may include stored tokens and session data. Backups are encrypted at rest and retained according to the operator's backup rotation policy.
Reasonable technical and organizational measures are used, but no system can be guaranteed to be completely secure.

6. Retention and deletion

OAuth tokens are kept until you revoke Google access or ask the operator to delete them. Revoking one user's access does not affect the other user's account. Session history and assistant records are kept until deleted or rotated. Encrypted backups may retain earlier copies until they expire under the backup rotation schedule. Pending write actions expire automatically and are deleted when confirmed or cancelled.

To delete local data, send a deletion request through the Telegram chat used to access Hagrid. To revoke Google's authorization, visit Google Account permissions and remove Hagrid's access. Revocation stops future API access; it does not automatically delete copies already present in backups until those backups rotate.

7. Google API Services User Data Policy and Limited Use

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

Google user data is used only to provide or improve user-facing features that are visible in the assistant.
Google user data is not sold.
Google user data is not used for advertising.
Google user data is not used to determine creditworthiness or for lending purposes.
Google user data is not transferred to third parties except as necessary to provide or improve user-facing features, to comply with applicable law, or as part of a merger, acquisition, or sale of assets with notice to users.
No human reads Google user data except with your affirmative consent, for security or legal reasons, or where the data has been aggregated and anonymized.
Write actions are executed only after the bound Telegram user confirms the exact pending action; the language model cannot approve its own action.
Each user's Google data is reachable only through that user's own credentials and profile; another user's request cannot select or switch to it.
Hagrid does not use Google user data to develop, improve, or train generalized AI or machine-learning models.

The external LLM provider receives selected content only to generate the response you requested. Its own retention and training practices are governed by its terms, as described in section 4. Hagrid does not claim otherwise.

8. International processing

Google, Telegram, DeepSeek, and the static hosting provider may process data in countries other than your own. Their respective privacy policies describe their safeguards and transfer mechanisms.

9. Cookies and tracking on this website

This website is static. It does not set cookies, run JavaScript, use analytics, or include advertising or tracking pixels. It loads no external fonts, scripts, or images. Following an external link takes you to a third-party site with its own practices.

10. Children

Hagrid is a personal tool and is not directed to children. It is not intended for use by anyone under the age required to consent to online services in their jurisdiction.

11. Changes to this policy

This policy may be updated when the assistant's data handling changes. The effective date at the top of this page will be revised. Continued use after an update means you should review the current version.

12. Contact

For privacy questions, deletion requests, or security concerns, contact the operator through the private Telegram chat in which you use Hagrid. Please do not send OAuth tokens, authorization codes, or other secrets in a message.