Privacy Policy

Hermes Plumeria · last updated 7 November 2026

Hermes Plumeria is a private, single-user personal assistant operated by Tianshu Chu in Australia. This policy explains what it does with data obtained from Google APIs. It is short because the scope is short: one person, one account, one server.

1. Who is responsible

Tianshu Chu, an individual, Australia. Contact: ts.chu.qd@gmail.com.

2. What Google data is accessed

The assistant acts only on the Google account of its owner, after the owner grants access through Google Sign-In. Depending on the permission granted, it may access:

• Gmail — message headers, bodies, attachments and labels, to triage mail, summarise threads and draft replies.
• Google Calendar — events, to read the schedule and create events.
• Google Drive, Docs and Sheets — files the owner opens or has the assistant work with, including business records.
• Google Tasks — task lists.
• Google Contacts (read-only) — names and addresses, to identify correspondents.

No other Google data is requested, and no data about any person other than the account owner is collected deliberately. Correspondence naturally contains information about other people; that is inherent to reading mail, and it is handled only as described below.

3. Where it is stored

On the owner's own server, in the owner's own home, in Australia. The OAuth credentials that allow access are stored on that server and nowhere else. The assistant does not operate a cloud database, does not run analytics, and does not maintain user profiles.

4. How it is used

Google user data is used for one purpose: performing the tasks the owner asks of the assistant — searching and summarising mail, drafting replies, reading and writing documents and spreadsheets, managing calendar entries and tasks. Nothing else.

5. What it will never do

• Sell Google user data, or transfer it to anyone for advertising, marketing, credit assessment or data broking.
• Use Google user data to train, fine-tune or improve generalised or foundation machine-learning models.
• Allow any human other than the owner to read it.
• Transfer it to a third party, except to the model provider described in section 6 — which processes content to answer a specific request, under contract, and does not retain it for training.

6. Automated processing

The assistant is powered by a large language model reached through a commercial API. When the owner asks for a summary, a draft or an answer, the relevant content — for example the text of an email thread — is sent to that provider so the request can be completed. The provider is used strictly as a processor for that request. The owner selects which provider is in use, and no content is sent unless the owner is asking the assistant to work on it.

7. Retention and deletion

Data is kept on the owner's server only as long as it is useful for the assistant to work. The owner can delete it at any time by deleting the corresponding records on that server. Access can be revoked immediately, by the owner, at myaccount.google.com/permissions — revoking it stops all further access and invalidates the stored credentials.

Because there is a single user and a single data store, deletion is immediate and complete; there is no backup copy held by any third party beyond the owner's own encrypted offsite backup, which only the owner can decrypt.

8. Security

Access is over HTTPS. Credentials are stored on a server that is not exposed to the public internet, behind a private network; Google data is not served from this website. Backups are encrypted at rest with a key held by the owner.

9. Children

The assistant is not directed at children and has no users other than one adult.

10. Changes

If this policy changes, the date at the top changes with it. There is no mailing list to notify, because there is one user, who will be told directly.