Active Reader: Privacy Policy

⚡ Executive Summary

Active Reader is engineered to operate almost entirely on your local device. The sole exception is the optional Supporter Program: if you input a supporter code, your code and email are transmitted exclusively to our secure database provider to verify your active status. Nothing else about your browsing activity is ever harvested, tracked, sold, or shared.

📦 Data Storage Matrix

We strictly never collect page text contents, browsing histories, IP addresses, or tracking telemetry. Zero cookies or external ad trackers are utilized.

💎 The Supporter Program Mechanics

Backing the project via Ko-fi generates a supporter code. Providing that code alongside your email within the extension syncs both tokens to our secure Supabase database solely to cross-reference an active validation match. This represents the single outward network request triggered by the extension, occurring strictly on-demand.

Your email serves one function: verifying your supporter tier or delivering initial redemption codes via Ko-fi support channels. It is never monetized, leaked, or repurposed for marketing workflows.

Purge local credentials instantly via your extension options panel, or request complete database record erasure anytime through our contact channels.

🌐 Third-Party Infrastructure

• Supabase: Hosts the backend database designated for secure supporter tier validation. Review Supabase's Privacy Policy.
• Ko-fi: Manages ecosystem contributions. Ko-fi operates independently under separate terms; we obtain only your registered email and contribution tier type, bypassing all underlying payment details entirely.

No ad networks, analytics suites, or tracking pixels exist within our build ecosystem.

🎮 User Control & Freedom

• Toggle reading telemetry and history states off instantly within settings.
• Erase saved supporter records from client storage dynamically at will.
• Uninstalling instantly obliterates all local storage artifacts.
• Full core feature access remains entirely unlocked without entering a supporter key.

🔄 Policy Updates

Should structural changes alter our data processing framework, this document will update accordingly alongside direct in-app notifications prior to implementation deployment.