🔒
What we collect
We collect aggregate usage signals to measure reliability and improve the extension over time.
- Download outcomes (success, fail, cancel) as counts — never individual file details.
- Browser and extension version for compatibility tracking.
- Country-level activity trends for service quality monitoring.
- Aggregate page and interaction counts on the CQD website (e.g. which guides are read or which FAQ questions are opened) — no personal identifiers attached.
🚫
What we do not collect
We avoid collecting sensitive personal content and keep public data privacy-safe.
- No classroom document content, file names, or assignment text is collected.
- No account passwords, emails, or Google credentials are accessed.
- No raw IP lists are published in public website data.
- No browsing history, search queries, or tab contents are tracked.
- No personally identifiable information (PII) is ever stored.
💡
Why this helps users
This limited data helps us prioritize fixes, improve stability, and keep downloads fast for students.
- Improves reliability during high-volume download sessions.
- Helps focus engineering work on real-world issues.
- Supports safer, more stable releases across all browsers.
⚡
How data is processed
All analytics are processed at the network edge using Cloudflare Workers. No raw data is stored — only pre-aggregated totals.
- Data is aggregated in real-time at the edge, never stored as raw events.
- No central database of individual user interactions exists.
- Country-level resolution is derived from the request, then immediately aggregated — the raw signal is discarded.
- All processing happens within Cloudflare's global network infrastructure.
🗓️
Data retention
Aggregated counters are retained indefinitely to show lifetime stats. No personal data is retained because none is collected.
- Aggregate download counts and country totals are kept for lifetime statistics.
- No individual session logs, timestamps, or user identifiers are retained.
- Rate-limiting data (e.g. IP-based cooldowns) is ephemeral and expires automatically.
- You can request deletion of any data via the contact email — though there is no personal data to delete.
🧩
Your rights
CQD respects your privacy rights. Because we don't collect personal data, most data rights are satisfied by default.
- GDPR: Data minimization is met by design — no personal data is collected.
- CCPA: No personal information is sold or shared with third parties.
- Right to deletion: No user-specific data exists to delete.
- Right to access: The public overview page shows all aggregate data we hold.
- Right to opt-out: Uninstalling the extension immediately stops all data collection.
⚖️
Children's privacy
CQD is safe for users of all ages. No age verification is required because no personal data is collected.
- The extension does not collect age, name, email, or any identifying information.
- No COPPA-regulated data is collected from any user, regardless of age.
- Google Classroom already handles age-appropriate access — CQD inherits those protections.
- Parents and educators can review the full source code on GitHub.
👶
Browser permissions explained
CQD requests only the minimum permissions needed to function. Here's what each one does and why.
- "downloads" — Required to save files to your device through your browser's normal download flow.
- "storage" — Keeps your in-extension preferences and download state on your own device.
- "alarms" — Schedules routine cleanup of stale internal download records in the background.
- "identity" — Optional and only active in the opt-in "API (beta)" engine mode: lets CQD get a read-only Google token so the optional Classroom API assist (including the "Download all classroom files" button) can list class files you already have access to. Off by default; never runs in the background.
- "Host access to classroom.google.com" — Lets CQD detect attachments and add download buttons inside Classroom.
- "Host access to drive.google.com and drive.usercontent.google.com" — Used only when a bulk download has to fetch a file through Drive (including the "can't scan for viruses" interstitial), never to browse your Drive.
- "Host access to accounts.google.com" — Resolves which of your signed-in accounts can access a file during bulk downloads.
- No "tabs", "history", "bookmarks", or "activeTab" permissions are requested.
- All permissions are listed in the extension manifest, which is publicly auditable on GitHub.
🔑
Contact & policy changes
If you have questions about privacy, reach out anytime. We'll notify users of any material changes to this policy.
- Contact: adhamhaithameid@gmail.com for any privacy questions.
- The full privacy policy is maintained at PRIVACY.md in the GitHub repository.
- Material changes will be communicated through extension update notes and this website.
- This summary page is updated whenever the underlying policy changes.