đź”’ Privacy Policy for Leo
Effective Date: November 6, 2025
This Privacy Policy explains how the Leo Chrome Extension (the "Extension") handles the information you provide and the data used when you use the AI assistance features (e.g., summarize, draft, translate, improve writing, fill form) on web pages.
We are committed to user privacy and transparency. You retain control over your data. The Extension only sends data to the Leo backend service when you use AI features, and we describe below what is stored locally versus what is sent to our systems.
1. 🛡️ Data Controller and Ownership
- You are in control: When you use this Extension, you choose what content to send for AI processing (e.g., selected text, custom prompts). You are the controller of that content and of any credentials you use (such as Google sign-in).
- Leo backend service: The Extension sends content and authentication identifiers to the Leo API (a backend service operated by the Extension provider) to provide AI features, usage tracking, and subscription management. Processing of your data by that service is described in this policy.
2. 📝 Information We Handle and How It Is Used
The Extension handles the following categories of information.
A. Optional Google Sign-In (Authentication)
- Information handled: If you sign in with Google, the Extension stores your Google OAuth token, Google account ID, and profile information (email, name, profile picture) in your browser using Chrome’s sync storage. This data is used only within the Extension to show your account state and to authenticate you with the Leo API.
- Use: Your OAuth token and/or Google account ID are sent to the Leo API so we can associate usage with your account, enforce usage limits, and provide subscription status. Profile information (email, name, picture) is stored and used only locally in the Extension and is not sent to our servers for storage.
- Storage location: Authentication data is stored in your browser (Chrome storage). We do not store your Google password; sign-in is handled by Chrome’s identity API.
B. Anonymous Identifier (When Not Signed In)
- Information handled: If you do not sign in, the Extension creates and stores a persistent anonymous identifier in your browser’s local storage.
- Use: This identifier is sent to the Leo API for usage tracking and rate limiting so we can provide the service without requiring an account.
- Storage location: The anonymous ID is stored only in your browser (Chrome local storage).
C. Page Content You Send for AI Features