Privacy Policy

Your privacy is our priority. Readlet processes everything locally—we never see your documents.

Last updated February 3, 2026

No Data Collection

The extension doesn't collect any personal information, browsing data, or document contents.

100% Local Processing

All PDF rendering and OCR happens in your browser. Nothing from the extension is sent to servers.

No In-Extension Tracking

No analytics in the extension, no ads, no tracking pixels. Store listing analytics are aggregate only.

Full Policy

Everything you need to know

1 Introduction

Welcome to Readlet PDF Viewer. Readlet is a Chrome browser extension that replaces Chrome's default PDF viewer with a modern, beautiful reading experience.

This Privacy Policy explains how we handle information when you use our extension. The short version: The extension does not collect, store, or transmit any of your personal information. Your documents stay on your device, always. Our Chrome Web Store listing uses Google Analytics 4 to understand listing performance in aggregate.

2 Information We Collect

We believe in privacy by design. Readlet is engineered to function without collecting personal information.

We Don't Collect

Never sent to servers
Personal information
Browsing history
PDF contents or metadata
In-extension analytics or tracking data
Device identifiers
IP or location data

What We Store

Locally on your device
Theme preference
Ambient mode setting
Focus mode preferences
Viewing preferences

Preferences are stored in your browser's local storage and never transmitted externally.

3 How We Use Information

Readlet processes information entirely locally on your device:

  • URL Detection: We detect PDF file URLs to open them in Readlet. This happens locally and is not logged.
  • PDF Rendering: Your PDF files are processed within your browser to display them beautifully.
  • OCR Processing: Text extraction from scanned documents happens locally using Tesseract.js.
  • Preference Storage: Your viewing preferences are saved locally for a consistent experience.

All operations happen client-side. No data from the extension is ever sent to external servers.

4 Data Storage

Readlet uses your browser's local storage for preferences. This data:

  • Remains exclusively on your device
  • Is never synchronized to any cloud service by us
  • Can be cleared through your browser settings
  • Is automatically removed if you uninstall the extension

We do not operate any servers that store user data.

5 Third-Party Services

Readlet does not integrate with any third-party services that collect user data within the extension:

  • Store Listing Analytics Only: Our Chrome Web Store listing uses Google Analytics 4 to measure listing performance (page views and installs) in aggregate. The extension itself does not use analytics.
  • No Advertising: We don't display ads or use advertising networks.
  • No Tracking In Extension: We don't use tracking pixels, beacons, or similar technologies in the extension.
  • No External APIs: PDF processing happens entirely offline using bundled libraries.

6 Permissions Explained

Readlet requires a few Chrome permissions to work properly. Here's exactly what each one does and why we need it:

webNavigation

Lets us know when you're opening a PDF so we can display it in Readlet instead of Chrome's basic viewer.

webRequest

Helps us detect PDFs that don't have ".pdf" in the URL. Some websites serve PDFs without obvious filenames, so we check the file type to catch these.

activeTab

Gives Readlet access to your current tab when you click our icon, so you can open PDFs with a single click.

Host Permissions (All URLs)

Allows Readlet to load and display PDFs from any website. Without this, browser security would block us from showing PDFs hosted on external sites.

These permissions are used exclusively for PDF detection and display. We do not collect, store, or transmit any of your browsing data or PDF contents. All processing happens locally in your browser.

7 Data Security

Your data security is guaranteed by our architecture:

  • No Data Transmission: Since the extension doesn't collect data, there's nothing to secure in transit.
  • Local Processing: All rendering and OCR happens in your browser's sandboxed environment.
  • No Server Infrastructure: We don't operate data collection servers.
  • Open Source Libraries: We use well-maintained, auditable libraries for PDF processing.

The most secure data is data that's never collected.

8 Children's Privacy

Readlet is a general-purpose PDF viewer not directed at children under 13. However, since we collect no personal information, we are inherently compliant with COPPA and similar regulations.

Parents can be confident that no data about their children is collected by Readlet.

9 Chrome Web Store Compliance

In accordance with Chrome Web Store Developer Program Policies:

No Sale of Data: We do not sell or transfer user data to third parties for any purpose.
Core Functionality Only: Any information accessed is used solely for displaying PDF files.
No Creditworthiness Use: User data is not used for creditworthiness or lending purposes.

10 Changes to This Policy

We may update this Privacy Policy to reflect changes in our practices or for legal reasons.

  • The "Last Updated" date will be revised when changes are made
  • Significant changes will be noted in the Chrome Web Store listing
  • We encourage you to review this policy periodically

Continued use of Readlet after changes indicates acceptance of the updated policy.

11 Contact Information

If you have questions about this Privacy Policy or our data practices, we're happy to help.

Questions? We're Here to Help

Have questions about privacy or how Readlet handles your data? Drop us a line.

Send an Email
or find us at
Developer codernoel
Website codernoel.com
Email contact@codernoel.com