Privacy Policy

Last updated: February 12, 2026

1. Overview

hash-calendar is a client-only calendar. The app is designed to keep your calendar state in your browser and in the URL hash so there is no account system or server-side calendar database.

2. Data You Enter

Event titles, dates, recurrence settings, timezone choices, and similar calendar data are processed in your browser.

• Calendar state is encoded in the URL hash (`#...`).
• URL hash content is not sent in normal HTTP requests to the server.
• Language preference may be stored locally in your browser.

If you share your calendar URL, anyone with that link can access the shared calendar state in the hash. Treat shared links as sensitive.

3. Analytics

The main app page loads Google Analytics (GA4). It is configured to send only `origin + pathname` and not the URL hash, to avoid transmitting calendar payload data in analytics page URLs.

• Provider: Google Analytics (Measurement ID: `G-77V3TP2B5T`)
• Configured page location excludes the hash fragment

4. Third-Party Requests

The app may load third-party resources (for example analytics scripts, fonts, icon libraries, or QR code utilities). Those providers may receive standard request metadata such as IP address, user agent, and referrer.

5. Encryption and Security

The app includes optional password-based encryption for shared links. Encryption improves confidentiality, but no system can provide absolute security. Keep passwords private and avoid sharing them in the same channel as encrypted links.

6. Data Retention

hash-calendar does not run a backend that stores your calendar entries. Data retention is mainly controlled by your browser history, copied/shared links, and any third-party services you intentionally use.

7. Your Choices

• Do not share calendar links if they contain sensitive data.
• Use link encryption for shared calendars when needed.
• Use browser privacy controls or blockers to limit analytics.
• Clear browser history when you want to remove locally retained URLs.

8. Changes to This Policy

This policy may be updated as the project evolves. The date at the top of this page indicates the latest revision.

9. Contact

For questions, open an issue on GitHub: hash-calendar issues.