ReadEase

Privacy Policy

Your data stays on your device.

ReadEase is designed to improve on-screen readability without collecting personal data. This policy explains what we do—and do not do—with information when you use the web experience or the Chrome extension.

Effective date: February 11, 2026

What we collect

  • No accounts, emails, or personal identifiers are collected.
  • No analytics, tracking pixels, or third-party cookies are used.
  • Settings you choose (font, spacing, color theme, ruler, highlight, and bionic options) are stored locally in your browser (`chrome.storage`/`localStorage`) so they persist between visits.
  • Website content is processed locally only to apply your chosen styles.

Why we request permissions

The Chrome extension needs certain permissions to function. None of them are used to profile, track, or share your data.

  • activeTab: injects reading styles only into the tab you activate the extension on.
  • tabs: keeps styling in sync as you switch pages or open PDFs.
  • storage: saves your preferences locally so they persist across sessions.
  • <all_urls> host permission: required to apply styles on any page you choose; no page data leaves your device.

Sharing & selling

We do not sell, rent, or share any user data. There are no third-party analytics or advertising SDKs in the extension or the site.

Data storage & retention

  • Preferences are stored locally on your device and remain until you clear your browser data or uninstall the extension.
  • No copies are sent to remote servers; the project works offline after install.

Your choices

  • Adjust or reset preferences anytime in the extension popup.
  • Remove the extension to delete all stored settings, or clear site data in your browser to reset the web experience.
  • Reach out with questions via the feedback form.

Children

ReadEase is built for a general audience and is not directed to children under 13. We do not knowingly collect information from children.

Updates to this policy

If we change how data is handled, we will update this page and change the effective date. Significant changes will be highlighted in the extension release notes.