Introduction

EasyView ("we", "our", or "the extension") is a Chrome browser extension designed to improve web accessibility for neurodivergent users. This Privacy Policy explains what information EasyView does and does not collect, how it works, and your rights as a user.

🔒
The short version

We collect basic account information (like email) for premium subscriptions, and anonymous usage analytics. All core webpage modifications happen locally on your device.

Information We Collect

To provide you with premium features and secure support, we collect the following limited data using Supabase:

  • Account Information: Your email address and basic profile data (via Supabase Auth/Google OAuth) to manage your premium subscription.
  • Subscription & Payments: We track premium status, order IDs, and payment status to enforce premium access. We do not store raw credit card numbers.
  • Feedback & Support: Any messages, bug reports, or emails you send us via our Contact Form.
  • Anonymous Usage Analytics: We log basic, anonymous feature usage (e.g., "Jargon Decoder used") to help us understand what tools help users the most.

Information We Do NOT Collect

Even with a premium account, EasyView does not collect any of the following:

Browsing history or the URLs you visit
The content of webpages you view
The text you select or decode using the Jargon Decoder
Your AI API keys
Device identifiers or IP addresses
Cookies or cross-site tracking data
Our backend server is strictly used for authentication, payments, and opt-in feedback. All reading features run locally on your device.

Information Stored Locally on Your Device

EasyView stores the following data locally on your device using Chrome's built-in chrome.storage.local API. This data never leaves your device unless you explicitly choose to share it.

User Preferences

  • Reading Mode settings (font, spacing, overlays, bionic reading)
  • Sensory Shield on/off state
  • Text-to-Speech settings (voice, speed, pitch)
  • Theme and display preferences (dark mode, reduce motion)

Custom AI API Keys (Bring Your Own Key)

If you prefer to bypass our Free/Premium quotas, you can optionally provide your own personal API key. If you choose this option, your key is:

  • Stored only in Chrome's local storage on your device
  • Never transmitted to EasyView or any EasyView-controlled server
  • Used only to make direct API calls from your browser to Google or OpenRouter
💡
How to delete your API key

Go to EasyView Settings → AI Configuration → Remove Key. You can also uninstall the extension to remove all locally stored data.

AI API Usage & Third Parties

How the Jargon Decoder communicates with AI models depends on your usage tier:

  • Free / Premium Tier (Built-in): Your request is securely routed through our backend using our corporate API keys. We do not store or log the text you highlight.
  • Bring Your Own Key (BYOK): Your browser makes a direct API call to the AI provider using your personal key. This call bypasses EasyView's backend entirely.
Your Browser
→ direct API call →
Google Gemini / OpenRouter
✕ EasyView servers

Third-Party Privacy Policies

We recommend reviewing these policies before configuring an AI provider.

Chrome Permissions Explained

EasyView requests only the minimum permissions needed to function. Here's exactly why each permission is required:

activeTab

Required to inject accessibility scripts (reading mode, sensory shield, TTS) into the page you are currently viewing. EasyView only accesses the active tab when you click the extension icon.

storage

Required to save your accessibility preferences and optional AI key locally on your device so your settings persist between browser sessions.

scripting

Required to inject content scripts into pages — this is how EasyView applies font changes, overlays, and sensory shield effects to webpages.

alarms

Used to periodically and securely verify your premium subscription status in the background without slowing down your browsing experience.

Data Security

Since EasyView does not transmit or store your data on any server, the primary security consideration is your own device security. Your AI API keys are stored in Chrome's local storage, which is sandboxed to the EasyView extension and not accessible by websites or other extensions.

Our Recommendations

  • Use a unique API key for EasyView rather than sharing one key across multiple applications
  • Revoke and regenerate your API key if you believe it has been compromised
  • Keep your Chrome browser updated to the latest version

Your Rights

You have full control over your data. You have the following controls:

🗑️
Delete Local Settings

Go to Chrome Settings → Extensions → EasyView → Clear Data

🔑
Remove API Key

EasyView Settings → AI Configuration → Remove Key

🚫
Uninstall

Uninstalling the extension removes all locally stored EasyView data

Open Source Transparency

EasyView is fully open source. You can inspect the complete source code to verify exactly how the extension operates and confirm this Privacy Policy is accurate.

💻
Verify it yourself

The full source code is available on GitHub. We believe code transparency is the strongest form of privacy protection.

View source on GitHub ↗

Changes to This Policy

We may update this Privacy Policy from time to time. Any changes will be reflected with an updated "Last Updated" date at the top of this document and on the EasyView website.

Our commitment: We will never introduce data collection without clearly disclosing it in an updated policy. Continued use of EasyView after changes constitutes acceptance of the updated policy.

Contact

If you have any questions about this Privacy Policy or EasyView's data practices, please reach out: