Privacy Policy

What we collect

Browser-only processing

• Your event data: Never uploaded to our servers. Processed entirely in your browser using JavaScript.
• Calendar mappings: Only stored in your browser's URL hash and localStorage if you choose to save them.
• ICS files: Generated locally in your browser, never sent to our servers.

Analytics

We use Plausible Analytics, a privacy-focused analytics tool. Plausible does not use cookies, does not collect personal data, and is fully GDPR compliant. We track basic usage metrics like page views and feature usage to improve CalendarMap. Your event data is never included in analytics.

Optional paid features

• Large event processing: If you purchase a one-off credit for calendars with 2,000+ events, we process payment through Stripe but do not store your personal information.
• Payment data: Handled entirely by Stripe. We only receive a success/failure notification.
• Token storage: A temporary token is stored in your browser's localStorage for 24 hours to unlock large file processing.

What we don't do

• ❌ Upload your CSV files to servers
• ❌ Store your event or schedule data
• ❌ Track you across the web
• ❌ Require user accounts or logins
• ❌ Sell your data to third parties
• ❌ Use cookies (we use cookie-free Plausible analytics and functional localStorage only)

Data retention

• CSV files: Never stored on our servers
• ICS files: Generated locally, never stored on servers
• Event mappings: Only stored locally in your browser
• Payment records: Handled by Stripe according to their privacy policy
• Tokens: Automatically expire after 24 hours

Open source transparency

CalendarMap is fully open source under the MIT license. You can review our code, host your own instance, or contribute improvements on GitHub.

CLI tool

Our command-line tool processes event files entirely on your local machine with no network connectivity required. It includes the same calendar conversion and timezone handling as the web version.

Questions or concerns

If you have questions about this privacy policy, please open an issue on GitHub.