Privacy Policy
Last updated: September 30, 2026
Creator Revenue Radar is Windows desktop software designed to help creators monitor supported membership and revenue-notification emails and analyze locally detected paid events. This policy explains how the application accesses, uses, stores, protects and shares information, including Google user data.
1. Google / Gmail data we access
When a user chooses to connect Gmail, Creator Revenue Radar uses Google OAuth 2.0 and requests only the restricted scope https://www.googleapis.com/auth/gmail.readonly. This permits the application to read Gmail messages, but does not permit it to send, delete, modify, move, label or otherwise manage mailbox content.
The application reads relevant message headers, sender information, subject lines, snippets and message bodies only to identify supported paid-membership or revenue-notification emails and extract the information needed to provide user-facing alerts and analytics.
2. How Google user data is used
Google user data is used only to provide and improve prominent, user-facing Creator Revenue Radar features. In particular, the app uses supported Gmail notification content to determine whether a relevant paid event occurred and, when available, derive event information such as amount, membership or tier information, member or sender details, timestamp and source.
Creator Revenue Radar does not use Google user data for advertising, credit decisions, surveillance, or the creation of advertising profiles.
3. Local processing and storage
Gmail message processing occurs locally on the user's Windows computer. The publisher does not operate a Creator Revenue Radar server that receives Gmail message contents, OAuth tokens or the application's local revenue-event database.
Writable application data is stored under the signed-in user's local application-data directory in Creator Revenue Radar. This can include OAuth authorization tokens, monitoring state, application settings, logs and locally derived revenue-event records. Derived records can include Gmail account, member or patron name or email when present, tier, amount, currency, email subject, sender, source and Gmail message identifier. The application is not designed to persist the full Gmail message body in its revenue-event database.
4. Data sharing and transfers
Creator Revenue Radar does not sell Google user data or creator/member data. Google user data is not transferred to the publisher's servers and is not shared with third parties for advertising or marketing.
Google itself processes authentication and Gmail API requests according to Google's own terms and privacy policies. Other services referenced by notification emails remain governed by their respective policies.
5. Google API Services User Data Policy / Limited Use
Creator Revenue Radar's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Access to Google user data is limited to providing the prominent user-facing features described in this policy and in the application. Human access to Google user data is not part of normal operation.
6. Data retention, user control and deletion
Google OAuth tokens and local monitoring data remain on the user's computer until the user disconnects the Gmail account or deletes the application's local data. Disconnecting a Gmail account stops monitoring and deletes the local OAuth token for that account; it does not delete previously created local revenue-history records.
Users may delete those records and all remaining local Creator Revenue Radar data by closing the application and removing its Creator Revenue Radar folder from their Windows local application-data directory. Users may also revoke Creator Revenue Radar's access at any time in their Google Account settings.
7. Security measures
Creator Revenue Radar uses Google OAuth rather than collecting a user's Google password. Gmail API communications use Google's HTTPS/TLS endpoints. The application processes Google data locally and does not transmit Gmail message contents, OAuth tokens or locally derived revenue-event data to publisher-operated servers.
Local application data is stored inside the signed-in user's Windows profile; access to that data is controlled by the protections on that Windows user account. Users should protect their device, Windows sign-in credentials, backups and local application data. No security method can guarantee absolute protection.
8. Children's privacy
Creator Revenue Radar is business/productivity software and is not directed to children.
9. Independent third-party software
Creator Revenue Radar is independent third-party software and is not affiliated with, endorsed by, or sponsored by Google, Gmail, Patreon, or other supported services.
10. Changes to this policy
This policy may be updated to reflect changes in the application, legal requirements, or Google API requirements. The current version will remain publicly available at this URL with its updated date.
11. Contact
Privacy and support questions: [email protected]