privacy policy
readmepls is a reader-first bookmarking app. This policy explains what data the readmepls service and the readmepls browser extension handle, why, and where it goes. Short version: we collect only what's needed to sign you in and save the pages you choose — nothing more, and we never sell it.
Last updated: 17 July 2026
who this covers
This policy applies to the hosted readmepls service and to the readmepls browser extension. If you use a self-hosted instance, your data is handled by whoever operates that instance, not by us — see self-hosting below.
what we collect
- Account details — the email address and password you use to create an account and sign in.
- Pages you save — the URL of any page you choose to add to your library, plus the readable content extracted from it and any highlights, notes, tags, and collections you create.
- Basic technical data — standard request information (such as IP address and timestamps) that any web server receives, used to operate and secure the service.
We do not collect health, financial, or payment-card data, your personal communications, your location, or your general browsing history. We only ever receive the URL of a page when you explicitly save it.
how we use it
- To authenticate you and keep you signed in.
- To extract, store, and display the pages you save so you can read, highlight, search, and organize them.
- To operate, secure, and debug the service.
We do not use your data for advertising, we do not sell or rent it to anyone, and we never use it to determine creditworthiness or for lending.
the browser extension
The extension saves the page you're currently viewing to your library in one click. It handles data narrowly:
- The current tab's URL is read only when you open the
popup and click Save (the
activeTabpermission). It reads the page URL only — never the page's contents, your other tabs, or your browsing history. - Your login session and settings (an authentication
token and, for self-hosters, your instance URL) are stored locally in
the browser via
chrome.storageso you don't have to sign in on every save. This stays on your device. - Your email and password are sent, over HTTPS, only to your readmepls instance to sign you in.
The extension talks only to your readmepls instance. It sends no data to any third party, contains no analytics or tracking, and runs no remote code — everything it executes ships inside the extension package.
who we share it with
We don't sell your data and we don't share it with third parties for their own purposes. Your data may be processed by the infrastructure providers that host the service, acting on our behalf solely to run readmepls. AI features, when you enable them, send the content of pages you save to the configured AI provider only to generate tags and summaries for you.
storage & retention
Your account and saved library are kept for as long as your account exists. The extension's locally stored session and settings remain until you sign out, clear the extension's storage, or uninstall it. When you delete your account, your associated data is removed from the service.
self-hosting
readmepls is open source and self-hostable. If you run your own instance, you (or your operator) control the server, the database, and any AI keys — your data lives on your infrastructure and is subject to your operator's practices, not ours. The extension can be pointed at a self-hosted instance in its options page; when you do, it communicates only with that instance.
your choices
You can delete pages, highlights, and collections at any time, sign out of the extension, or delete your account to remove your data. For access or deletion requests, contact us using the link below.
changes to this policy
If we make material changes, we'll update this page and the date at the top. Continued use after a change means you accept the updated policy.
Questions about privacy? Open an issue on GitHub.