Privacy policy
Last updated 7 October 2026
mhud is a private, invite-only workspace: a kanban board, a meeting heads-up display and a CRM, run by Autogeny (autogeny.ai). This page explains what mhud reads from your Google account, what it keeps, who can see it and how to have it removed.
What mhud reads from Google
Google Drive, Docs, Sheets and Slides (read-only)
Used when you choose Connect Google in Settings and then attach a Drive link to a card.
- mhud reads the file's name, type, size and last-modified time. For a folder, it lists the files up to three levels deep, at most 50 of them.
- It reads a file's contents only when an AI review of that file runs: a document's text, the first 100 rows of each sheet, and each slide's text with up to five of its images.
- mhud does not keep copies of your files. It stores the file name, a link to the file and the review the AI writes, which is posted as a comment on the card.
- It never creates, changes or deletes anything in your Drive.
Gmail (read-only)
Used only when an organisation admin connects a mailbox in the CRM, so that email with your contacts appears on their timelines.
- mhud reads message headers (From, To, Cc, Subject, Date and the message ID), four headers that mark mailing-list and automated mail (List-Id, List-Unsubscribe, Precedence and Auto-Submitted), and the short preview Google provides for each message. The four extra headers are used only to tell bulk mail from mail between people. It does not read message bodies or attachments.
- When a mailbox is first connected, it looks back 90 days for email with your CRM contacts; older mail is stored only when it involved a contact. After that it checks for new email about every five minutes.
- For each message it checks, it stores the senders' and recipients' addresses and display names, the message ID, the subject, the preview, and a yes or no for "bulk mail". It never stores the four list headers themselves. When a message involves one of your contacts, it also adds an email entry to that contact's timeline and may create a reminder to reply.
- Suggested contacts: from those stored headers, the CRM suggests people your organisation's admins have written to, or who have written to them at least twice, who are not contacts yet. Mailing lists, automated senders and messages to more than ten people are left out. The suggestions are worked out from the stored data with no further call to Google, and are shown only to your organisation's admins (and to an AI agent an admin connects with CRM read access, which sees names, addresses and message counts, never subjects or previews). Nobody becomes a contact unless an admin adds them or approves an agent's proposal to, and an address an admin dismisses is remembered so it is not suggested again.
- It never sends, changes or deletes email.
Your Google account's email address
When you connect Google, mhud records the account's email address and Google account ID so it can show which account is connected.
Where it is kept and how it is protected
- Everything is stored on a single server that mhud rents from Hetzner Online.
- The access Google grants mhud (its access and refresh tokens) is stored encrypted with AES-256-GCM, using keys held only in that server's configuration.
- Backups are kept on the same server: one copy a day for the last 14 days and one a week for the last 8 weeks.
- Error and page-view reports go to Autogeny's own monitoring service, with email addresses and access tokens removed first.
Who can see it
- Drive: members of your organisation in mhud can see the names of files attached to cards and the AI reviews of them. Any member can ask for a fresh review, which reads the file again using the access of the person who attached it.
- Gmail: your organisation's admins can see the stored headers, previews and timeline entries for every mailbox connected to its CRM, and the contact suggestions made from them. Other members cannot.
- AI agents: an admin can connect an AI agent to mhud with an API key. An agent given CRM read access can read the same CRM records an admin can, including email subjects and previews, and the list of suggested contacts (names, addresses and message counts).
Services mhud shares data with
- Anthropic (Claude) powers mhud's AI features. It receives the contents of a Drive file when an AI review of it runs, and CRM records, which can include email subjects and previews, when an admin asks mhud's assistant or a connected AI agent about the CRM.
- Apollo.io, if an admin connects it, exchanges contact details with the CRM: name, email address, job title, company and LinkedIn address. No Gmail or Drive data is sent to Apollo.
- mhud does not sell data, show advertising or share data with anyone else.
Google API Services User Data Policy
mhud'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. In particular:
- Google user data is used only to provide the features described on this page.
- It is not used for advertising, not sold, and not used to decide creditworthiness or for lending.
- It is not used to develop, improve or train general-purpose AI or machine-learning models.
- Apart from the people in your organisation who can see it as described above, nobody reads it unless you ask us to, it is needed for security, or the law requires it.
The optional Inbox Agent
If you install mhud's Inbox Agent, it runs as a Google Apps Script inside your own Google account, with permissions you grant to that script rather than through mhud's Google connection. It sends parts of incoming email (up to 1,500 characters of each message, or a few recent messages of a thread when it drafts a reply) to Anthropic's Claude to summarise them, and sends mhud a card or reminder with the subject, sender, a link to the message and the summary. It can also send a push notification through ntfy.sh if you set that up. Removing the script from your Google account stops it.
Keeping and deleting your data
- Disconnect Google (Settings): mhud revokes its access at Google and deletes the tokens it stored. File names and reviews already on cards stay until the attachment is removed.
- Disconnect a Gmail mailbox (CRM, Gmail): syncing stops and the stored tokens are deleted. To end the access on Google's side as well, remove mhud at myaccount.google.com/permissions. Timeline entries already created stay.
- Stored messages that involved none of your contacts are deleted automatically 180 days after they were sent. Everything else is kept while your organisation's CRM exists.
- Addresses an admin dismissed from the suggested contacts are kept until an admin restores them.
- To have all of your Google data deleted, including synced email records, dismissed suggestions and attachments, email cunningham.be@gmail.com. It is deleted within 30 days, and the copies in backups expire within 8 weeks after that.
Changes and contact
If this policy changes, the date at the top changes with it. Questions go to cunningham.be@gmail.com.