Privacy Policy

Last updated: May 2025

Calendar Countdown & Alerts (“Extension”, “we”, “us”) respects your privacy. This policy explains how we collect, use, and disclose your data when you install or use our Chrome extension.

1. Information We Collect

• Google Calendar & Profile Data: We request read-only access to your Google Calendar (calendar.readonly) and event details (calendar.events) to display real-time countdowns and one-click action.

• User Identifier: We store a unique user UUID in your browser via chrome.storage.local for device and usage mapping.

• Device & Environment Metadata: Each device upsert includes your browser version, operating system, extension version, and timestamps (UTC serverTimestamp & client-formatted).

• Usage Analytics: We log minimal events (e.g., banner shown, button clicked) for performance monitoring and license enforcement. No PII is transmitted outside your browser.

• Cookies & Local Storage: We do not use third-party cookies. All data persists in Chrome’s local storage; no data is stored on external cookies or localStorage beyond extension scope.

• Children’s Data: Our Extension is intended for users 18+ and does not knowingly collect data from children under 18 .
  
  

2. How We Use Your Information

• Core Functionality: To power countdown banners, color thresholds, and “Join Meeting” / “View Details” actions.

• Device Mapping & Support: To group events by browser installation for troubleshooting and user-experience improvements.

• Analytics & Licensing: To measure usage volume, monitor errors, and enforce $5 USD/user-month commercial licensing where applicable.

3. Cookies, Tracking Technologies & Third-Party Services

• We do not embed analytics SDKs or third-party trackers (e.g., Google Analytics) in the page context—our analytics runs entirely via Firestore writes.

• We may employ Firebase as a data processor; they are bound by our instructions and EU standard contractual clauses if you’re in Europe.

4. Data Sharing & Disclosure

• No Sale of Data: We do not sell or rent your personal data to third parties.

• Service Providers: We use trusted cloud providers (e.g., Google/Firebase) under confidentiality obligations.

• Legal Compliance: We may disclose data to comply with legal obligations or protect our rights.

5. Your Rights

Under applicable laws, you have rights to:

• Delete your user document, UUID, and analytics logs (“Right to be Forgotten”).

• Restrict or object to processing (e.g., analytics).

• Withdraw Consent for OAuth at any time via Google Account → Security → Third-party access.
  
  

6. User Controls & Opt-Out

• Consent: On first run, you grant read-only Calendar and email scopes via Chrome’s OAuth—without consent, polling and tracking are disabled.

• Opt-Out: Toggle “Enable Banner Alerts” off in the popup to stop all polling and analytics.

7. Data Retention & Deletion

• Retention Period: analytics logs (email, UUID, events) are retained for up to 24 months.

• Right to Erasure (GDPR): under Article 17, you may request deletion of your personal data without undue delay when there is no overriding legal obligation to retain it.

• Right to Delete (CCPA): California residents may request deletion of any personal information collected, and we will comply within 45 days, subject to CCPA’s limited exceptions (e.g., legal obligations).

8. How to Request Data Deletion

To exercise your deletion rights under GDPR or CCPA, please choose one of these methods:

• Web Form: Visit our secure deletion request form at
  https://sites.google.com/view/calendarcountdownbanner/home/request-data-deletion
  and follow the prompts. You’ll receive an acknowledgement and status updates via email.

We may request minimal verification (e.g. matching email) to prevent fraudulent requests.

9. Security

• Encryption: All data in transit is encrypted via HTTPS/TLS.

• Token Storage: OAuth tokens are stored securely by the Chrome Identity API and cleared on purge.

• Access Controls: Only authenticated form submissions or verified email requests can trigger data deletion.
  
  

10. Changes to This Policy

We may update this Privacy Policy; the Effective Date above will be revised. Continued use after changes constitutes acceptance.