Personal AI assistant
Your Gmail and calendar, through a private assistant.
Hagrid is a personal, self-hosted AI assistant for two authorized users. Each person's Google account is bound to their own Telegram identity on the server, so one user's requests can never read or change the other user's mail or calendar. Hagrid reads Gmail and Google Calendar and, after an explicit confirmation in Telegram, performs a limited set of write actions.
-
Gmail: read and controlled writing
Search and read messages, then create drafts, send a new message, reply in the same thread, change labels, archive, mark as read, or move a message to Trash — each only after you confirm.
-
Calendar: read and controlled changes
List calendars, read events, and check free/busy. Create, reschedule, or cancel an event only after a confirmation that shows the title, time, timezone, and attendees.
-
Telegram chat, one identity each
Ask in a private Telegram conversation. The server binds each verified Telegram user to exactly one Google account; a name or email typed in a message cannot switch accounts.
-
Explicit guardrails
No permanent Gmail deletion, no bulk operations, no filters or account settings, and no automatic or scheduled mail. A model's claim that an action is approved is never accepted.
How it works
-
You send a request in Telegram, for example to find a recent email or check your calendar.
-
The server resolves your Telegram identity from the authenticated message metadata. It does not use a name, username, or email supplied by the language model.
-
Read-only calls use only the Google account bound to that Telegram identity. The assistant has no path to another user's account.
-
For a write action, the server stores an immutable pending action, shows you a preview with the recipients, subject, body, or event details, and waits. Nothing is sent or changed until you confirm in Telegram and the server validates the action, its owner, and its expiry.
-
The result is used to compose a reply. To generate that reply, relevant content may be sent to the external LLM provider described in the Privacy Policy.
Privacy at a glance
Google access uses read scopes plus the limited Gmail and Calendar write scopes needed for drafts, sending, labels, archive, Trash, and event changes. Each user has a separate OAuth token stored on the operator's personal server, not on this website. Selected email or calendar content may be sent to the external LLM provider (DeepSeek) to answer your request. Write actions require a server-side Telegram confirmation and are never executed on the model's word alone. Hagrid does not sell Google user data, use it for advertising, or use it to train generalized AI/ML models. See the Privacy Policy for details, retention, backups, and revocation.