Scope of this policy
This policy applies to Ratatoskr, a macOS desktop application from Tigerclaw Technologies, LLC. It describes Ratatoskr's handling of information received through Google OAuth and the Gmail API.
Google user data Ratatoskr accesses
- The email address of the Google account the user authorizes, so Ratatoskr can bind that authorization to the correct local Chrome profile.
- Gmail metadata available through
gmail.metadata, including message and thread identifiers, sender and subject headers, dates, labels, and unread state.
Ratatoskr does not request or store message bodies, attachment contents, drafts, sent-message contents, contacts, passwords, or permission to send, modify, or delete email.
How Google user data is used
Ratatoskr uses Google user data only for its visible user-facing features: a local unified inbox index, account status, incremental metadata refresh, and opening a selected message in the Chrome profile assigned to that account.
Storage and transmission
- OAuth access and refresh tokens are stored in the user's macOS Keychain.
- Account mappings and cached message metadata are stored locally in Ratatoskr's macOS Application Support directory with owner-only permissions.
- Ratatoskr communicates directly with Google's OAuth and Gmail API services. Google user data is not uploaded to or stored on a Tigerclaw server.
Sharing, sale, advertising, and AI training
Tigerclaw does not sell Google user data, share it with data brokers or advertising platforms, use it for advertising or credit decisions, use it to train generalized AI models, or permit employees, contractors, or other people to read it. Ratatoskr does not transfer Google user data to third parties.
Retention and deletion
Ratatoskr retains cached metadata on the user's Mac until the user disconnects or removes the account, or manually removes Ratatoskr's local Application Support data. Disconnecting an inbox removes its OAuth token from Keychain and its cached metadata from Ratatoskr. A user may also revoke Ratatoskr through their Google Account security settings. Removing only the application bundle does not necessarily remove its local Application Support data.
Security and account separation
Ratatoskr uses OAuth Authorization Code with PKCE, a loopback-only callback, macOS Keychain for tokens, owner-only local file permissions, and an explicit one-to-one account-to-Chrome-profile mapping. It rejects a Google identity that does not match the adopted profile and blocks browser operations when browser-wide Chrome management prevents Ratatoskr from assuring profile separation.
Google API Services User Data Policy
Ratatoskr's use and transfer to any other app of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Changes and contact
Tigerclaw will update this page before Ratatoskr materially changes how it handles Google user data. Questions or privacy requests may be sent to hello@tigerclawtech.com.