Read & Retain Chrome extension
This notice explains how the Chrome extension published by EmbeddingMe handles data when you capture an article into your Read & Retain account.
Capture is initiated by you
The extension reads the active page only when you choose to capture it. You can adjust the selected content and edit its title, author and Markdown before confirming. It does not continuously monitor your browsing or collect a browsing-history feed.
What is saved and uploaded
Local extension storage holds editable drafts, recent capture records, task status and account authorization tokens. After you confirm a capture, the extension sends the source URL, title, author, edited Markdown, selection metadata and a sanitized snapshot of the rendered document to the Read & Retain API. The snapshot can include page text outside your final article selection. Scripts, form controls, frames, event handlers and the extension overlay are removed before upload.
If image capture is enabled by the service administrator, the extension may also upload readable images retained in your confirmed article. Otherwise it keeps safe source-image URLs. Loading a source-image URL may send a request to its original host; managed images use high-entropy links that anyone holding the link can access.
Account authorization and permissions
Chrome identity is used for a Read & Retain authorization flow with PKCE. Short-lived access tokens and rotating refresh tokens are stored locally to connect the extension to your account. The extension does not request access to your Google account data. It does not upload page cookies, request headers, browser passwords or form values. The activeTab and scripting permissions enable your requested capture; storage saves local state; alarms resume uploads; the API host permission enables account authorization and capture submission.
Creating or signing in to a Read & Retain account involves your name, verified email and authentication information in the web app. Email verification uses the service’s email delivery provider. API requests also carry network metadata such as IP address and user agent, which the service and its infrastructure providers may process for delivery, operational logs and abuse prevention. Captured source URLs and article titles identify the pages you explicitly chose to save; the extension does not collect a general browsing history.
How data is used and shared
Capture data is used to process your confirmed article and make it available in your personal library. The API stores source artifacts privately and processes them using Cloudflare infrastructure. Your articles are not placed in a public capture index or sold for advertising. The extension does not run remotely hosted executable code. If you later request an AI feature in the web app, relevant content may be sent to the configured AI provider to fulfill that request; capturing an article does not itself request AI generation.
Your controls
You can cancel a capture, edit it before confirmation, remove local capture records, disconnect the extension and uninstall it. Removing a local record does not delete an article already saved to your account. Manage saved articles and deleted items in the web app; account closure is available in its security settings. Uploaded data follows the service's material deletion and account-closure workflows.
Questions and support
For privacy questions, use “Contact developer” on the Read & Retain Chrome Web Store listing. Do not include passwords or authorization tokens in a support message.