Privacy Policy
Last updated: October 28, 2026
Your reading history is personal. The Slideshow Reader extension extracts and formats articles locally inside your browser so what you read stays on your device.
Local DOM Parsing Only
Articles are sliced into slides directly inside your local browser memory. Article URLs, titles, highlights, and page text are never uploaded to our servers.
No Third-Party Trackers
We embed zero third-party analytics SDKs, ad networks, or tracking pixels. Anonymous first-party event counts can be disabled anytime with one switch.
Local Storage Persistence
Reading progress, saved articles, and preferences live in your browser's chrome.storage.local and chrome.storage.sync.
Data-Only Sponsor Cards
Optional sponsor cards on the final slide are rendered strictly as plain text with a clear Sponsored label — never remote scripts or pixels.
Anonymous Usage Counts & Opt-Out
By default, the extension stores a random local install ID (iid) in chrome.storage.local and sends lightweight anonymous event counts (daily_active, slideshow_opened, slideshow_completed, and sponsor_view) to our Cloudflare Worker. Country-level totals are derived from Cloudflare's request metadata without storing IP addresses, and sponsor link clicks are counted via /go/:sponsorId redirects.
Never collected: We never collect or store article URLs, article titles, article text, reading history, or personal browsing data. You can disable “Share anonymous usage stats” at any time in the extension settings to send zero usage events.
Permissions Explanation
The Chrome Web Store requests the following permissions for the extension to function:
- activeTab & scripting: Allows the extension to extract the article DOM and present the slideshow overlay when you trigger it via shortcut or toolbar click.
- storage: Retains your reading progress, font size, theme preference, cached sponsor card, and opt-out setting across sessions.
Contact & Inquiries
If you have questions or concerns regarding privacy, please contact the maintainer directly via X at @thekaranmundra.