Privacy Policy
Journal Assistant is a private tool for users of the Hermes agent. It runs on each user's own computer and stores everything locally. This policy explains what it accesses, what it does with it, and what it never does.
1. Who operates this app
Journal Assistant is operated by each user for their own personal use, on their own machine and with their own Google account. It is not distributed, not offered for sign-up, and has no users beyond those who run it themselves. Contact: stuartguthrie@gmail.com.
2. What Google user data is accessed
Only the user's own Google account is ever accessed, and only while the user is running the tool. The app requests these Google scopes:
-
calendar— read the user's own calendar events. -
gmail.readonly— read the user's own mail, only when the user asks for it. -
gmail.sendandgmail.modify— prepare draft messages for the user to review, and label or file mail. The app does not send any message the user has not reviewed first, and does not delete mail.
The app does not access contacts, files in Google Drive, photos, or any other Google service. It does not access any other person's Google data.
3. How the data is used
Google user data is used only to provide the app's features to the user who is running it. It is never used for advertising, marketing, profiling, creditworthiness assessment, or sale. It is never used to develop, train, or improve any machine-learning or artificial-intelligence model, whether the user's own or a third party's.
4. How the data is stored
Everything is stored on the user's own computer:
- The app's output — including calendar tables — is written as plain text files into a folder on the user's local machine.
- The Google OAuth authorisation token is stored as a local file readable only by the user's own account, protected by the operating system's file permissions. It is not encrypted with a separate passphrase.
There is no cloud database, no server running outside the user's control, and no backup of Google user data held by the app. Data leaves the machine only if the user chooses to move or sync those files using tools the user controls.
5. What is shared with third parties
Nothing. Google user data obtained by this app is not transferred, disclosed, or shared with any third party, and it is not made available to any other person. The app calls only Google APIs, over HTTPS, from the user's machine.
6. How long data is kept
Files the app produces remain until the user deletes them. The OAuth token remains until the user revokes access or deletes the token file. Revoking access in the Google Account permissions page (myaccount.google.com/permissions) immediately prevents any further access.
7. Compliance with Google's Limited Use requirements
Journal Assistant's use of Google user data is limited to providing the user-facing features described above. It complies with the Google API Services User Data Policy, including the Limited Use requirements. In particular, Google user data is not used for advertising, is not sold, is not used to train models, and is not shared with third parties.
8. Security
The app runs locally with no remote access. Tokens are held in a file with owner-only permissions. Each user's Google account remains protected by their own Google account security settings, including two-factor authentication where enabled.
9. Children
The app is not directed at children and is used only by the adults who run it.
10. Changes to this policy
If the app's behaviour or its use of Google user data changes, this page will be updated and the "Last updated" date above revised.
11. Contact
For any question about this policy or about how Google user data is handled: stuartguthrie@gmail.com.