← Back to Browsy

How Browsy handles your data

Last updated: June 2026

What data Browsy accesses

Browsy requests access to the following data solely to provide its features:

• Gmail (read-only): Subject lines, sender names, and email previews of today's unread messages — used to generate your daily digest.
• Page content: The visible text of the current webpage — used to generate a page summary.
• Your Claude API key: Stored locally in your browser using Firefox's storage.local API. Never transmitted to any server other than Anthropic's.

How your data is used

When you trigger a Gmail digest or page summary, Browsy sends the relevant content directly from your browser to the Anthropic Claude API. The result is displayed in the extension and immediately discarded — nothing is stored.

Browsy does not:

• Store your emails or page content anywhere
• Send your data to any server we operate
• Share your data with third parties beyond Anthropic (for Claude) and Google (for Gmail OAuth)
• Use your data for advertising or analytics

Google Gmail access

Browsy uses Google OAuth 2.0 to request read-only access to your Gmail (gmail.readonly scope). This access is used exclusively to fetch today's unread email metadata (subject, sender, preview) for the digest feature.

You can revoke Browsy's access to your Gmail at any time by visiting Google Account Permissions and removing Browsy.

Data storage

The following data is stored locally in your browser only:

• Your Claude API key
• Your Gmail OAuth access token (expires after 1 hour)
• The position of the pet on screen

None of this data leaves your device except as part of the API calls described above.

Third-party services

• Anthropic Privacy Policy — governs how Claude API processes your requests.
• Google Privacy Policy — governs Gmail OAuth and API access.

Contact

If you have any questions about this privacy policy, please open an issue or reach out via GitHub.