Privacy Policy

Who we are

Clean Reader is a browser extension that extracts article content with per-site rules and an immersive reading view. This policy covers the extension and related support pages on this website.

Questions: digapp.top@gmail.com

Summary

• Reading rules, templates, and settings are stored locally in your browser by default.
• We do not sell personal data or run third-party advertising analytics in the extension.
• Optional features (Google Drive sync, license activation, server cloud sync) only send data when you use them.
• Page content you read stays on your device unless you export or sync it yourself.

Data we process

Stored on your device

Using Chrome’s (or Firefox’s) extension storage, Clean Reader may keep:

• Site extraction rules and match settings
• Reading preferences (theme, font size, layout)
• Reading templates and Obsidian-related settings you configure
• License status and a local device identifier used for activation limits
• UI state such as welcome flags and sync timestamps

Offline saves and Obsidian exports you trigger are written only to locations you choose (local folder or vault). We do not upload those archives automatically.

Website browsing

This marketing site is static. Hosting providers may process standard server logs (IP address, user agent, request time) as part of delivering pages. We do not use the site to build a personal profile of you.

Optional connections

Google Drive sync

If you sign in with Google, Clean Reader can sync rules, templates, and settings to Google Drive’s application data folder (not shown as ordinary Drive files). OAuth is handled by the browser’s identity APIs. Google’s own privacy policy applies to your Google account. You can disconnect Google from the extension options; remove the app connection in your Google Account settings if you want to revoke access fully.

License purchase & activation

Plus is a one-time purchase processed by our payment provider (Creem). When you activate a license key, the extension contacts our license API with the key and a device/instance identifier so we can validate activation limits. Purchase and billing details are handled by Creem; we receive what is needed to confirm entitlements, not your full card number.

Server cloud sync (complimentary / may change)

When available and enabled, licensed users may upload and download configuration (rules and templates) to Clean Reader’s servers, authenticated with the license key and instance id. Article page bodies are not part of this sync. This server sync may change or stop; Google Drive sync and local backup remain the long-term options.

Permissions (why the extension asks)

• Storage — save rules, preferences, and license state on your device.
• Identity — optional Google sign-in for Drive sync.
• Host access / network — read the current page to extract content, apply rules, and (when you ask) fetch media for offline save. Broad host access is needed because articles and media CDNs live on many domains.

Clean Reader does not use these permissions to scrape your browsing history for advertising or to inject third-party trackers into pages.

What we do not do

• Sell or rent personal information
• Use your reading content for AI training pipelines run by us
• Require an account just to use free reading and local rules

Data retention & deletion

• Local data — remove it by clearing extension data or uninstalling the extension.
• Google Drive app data — delete via Drive / Google Account tools after disconnecting, or contact us if you need help identifying app-data files.
• License / server config — email digapp.top@gmail.com to request deletion of server-side config associated with your license key. We may retain minimal records needed for fraud prevention or legal compliance.

Children

Clean Reader is not directed at children under 13 (or the equivalent age in your jurisdiction). We do not knowingly collect personal information from children.

International users

Servers and processors may be located outside your country. By using optional online features, you understand that data may be transferred to those locations with appropriate safeguards where required.

Changes

We may update this policy as the product evolves. The “Last updated” date at the top will change when we do. Material changes for Chrome Web Store users will be reflected here before or when the related extension update ships.

Contact

Privacy requests: digapp.top@gmail.com