Privacy policy
Gmail unread status · effective 9 September 2026
Who operates this tool
Emily Nováková, an individual, operates this tool for her own use. It is not a commercial service and it is not offered to other people. Questions go to hadikcze@gmail.com.
What data is accessed
With the read-only scope
https://www.googleapis.com/auth/gmail.readonly, the tool asks the Gmail
API for the identifiers of messages matching two searches and counts them:
in:inbox is:unread category:primaryin:inbox is:unread category:updates
The API response is restricted to message identifiers. Message bodies, subjects, headers, attachments, labels, contacts and settings are never requested. The tool cannot send, modify or delete mail.
Where the data is processed
Entirely on the owner's own computer. The tool has no server, no backend and no hosted component. It talks to Google's API directly and to nothing else. This website is static: it contains no analytics, no cookies, no trackers and no forms, and it never receives any Gmail data.
What is stored, and where
- The OAuth refresh token and client credentials live in the macOS login Keychain of that one computer.
- A short-lived access token and the resulting unread counts are cached in the owner's local cache directory, in files readable only by the owner's user account.
- The cache holds numbers only. No message content of any kind is written to disk.
Sharing
None. No data is transmitted, sold, rented, published or disclosed to any third party, and none is used for advertising, profiling or model training.
Limited use
The use of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.
Retention and deletion
The cached counts are overwritten on every refresh and can be deleted at any time by removing the local cache directory. Access can be withdrawn at myaccount.google.com/permissions, which invalidates the stored token immediately; deleting the Keychain entry removes it from the computer.
Changes
If this policy changes, the revised version is published on this page with a new effective date.