From c35b1c1cb4ed5e375083ad35fbecee569c16c400 Mon Sep 17 00:00:00 2001
From: Daniel Lynn <2+daniel@noreply.gitdan.com>
Date: Fri, 16 Oct 2026 23:33:51 +0000
Subject: [PATCH] docs: add PRIVACY.md

---
 PRIVACY.md | 36 ++++++++++++++++++++++++++++++++++++
 1 file changed, 36 insertions(+)
 create mode 100644 PRIVACY.md

diff --git a/PRIVACY.md b/PRIVACY.md
new file mode 100644
index 0000000..1c6462f
--- /dev/null
+++ b/PRIVACY.md
@@ -0,0 +1,36 @@
+# Privacy Policy - Hermes Brief
+
+Last updated: 2026-10-16
+
+Hermes Brief is a personal tool used only by its owner. It is not offered to the public.
+
+## What data it accesses
+
+With the owner's explicit consent it requests two read-only Google permissions:
+
+- `gmail.readonly` - to read recent unread message headers and snippets.
+- `calendar.readonly` - to read calendar events for the current day.
+
+It cannot send, delete, or modify mail or calendar data.
+
+## How the data is used
+
+The data is used only to produce a daily summary for the owner. The summary is generated by a language model that runs on the owner's own computer. The data is not used for advertising, profiling, or model training.
+
+## Storage and sharing
+
+- Mail and calendar content is processed in memory and is not stored by the tool beyond the generated summary, which is delivered to the owner's own phone through a notification server the owner runs.
+- The only credential kept is an OAuth refresh token, stored in a private file on the owner's computer.
+- Data is not sold, shared, or transferred to any third party.
+
+## Google API Services User Data Policy
+
+Hermes Brief's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
+
+## Revoking access
+
+Access can be revoked at any time at https://myaccount.google.com/permissions, and by deleting the token files on the owner's computer.
+
+## Contact
+
+Open an issue in this repository.