Privacy by architecture · Updated September 25, 2026
Your calendar stays on your device.
Local calendar processing
ICS files, pasted schedules and spreadsheets are read and processed in this browser. Local workers may process large files; these are browser threads, not remote servers. Calendar contents and filenames are not uploaded, sent to APIs, put in URLs or included in analytics.
Temporary workspace
Working calendars live in tab memory only. We do not store calendar contents in localStorage, sessionStorage, IndexedDB or a user database. Reloading or closing the tab clears the workspace. Downloads are saved by your browser to your device; you control those files. Clipboard copying and printing happen only when you choose them.
Your analytics choice
On your first visit, you can choose Accept all or Accept only required. Accept all loads Google Analytics for ordinary page traffic and records which calendar tool is opened. Accept only required does not load the Google Analytics tag and sends no analytics request to Google. We store only that choice in your browser so we can remember it. Use Analytics choices in the footer at any time to change or withdraw your choice.
How optional analytics helps us
We use optional analytics to understand site traffic and learn which tools and features are most useful. This helps us improve calendr.events and decide what to build next.
What analytics never receives
We do not send calendar contents, filenames, calendar or event titles, descriptions, locations, attendees, email addresses, UIDs, exact calendar dates, pasted text, spreadsheet values, generated QR contents or downloaded file data. We do not assign account IDs because the site has no user accounts. Advertising storage, ad personalization and Google Signals are disabled. We do not sell user data.
Withdrawing consent
Choosing required-only disables analytics and removes the Google Analytics cookies that calendr.events can access. Your required-only preference remains stored locally so the site does not ask again on every page. Your browser or Google may retain information already processed before consent was withdrawn according to their applicable retention settings and policies.
Normal hosting requests
Your browser still requests the site’s pages, scripts, styles and fonts. Hosting infrastructure may log ordinary request information such as IP address, user agent, URL path and timestamps. That is separate from calendar processing: calendar contents never form part of those requests. Deployment owners separately control provider logging and retention settings.
Supporting calendr.events
The Buy Me a Coffee button and floating widget are provided by Buy Me a Coffee. Their widget loads from their service, and choosing it opens their website. We never send your calendar contents or files to Buy Me a Coffee.
Other services and calendar apps
Optional analytics is provided by Google under its own data and privacy terms. Importing a downloaded file into Google, Outlook, Apple Calendar or another app is a separate action under that provider’s privacy policy. calendr.events does not connect to those calendar accounts. External help links are opened only when you choose them.
Before sharing a result
Anonymization is not a guarantee of anonymity. Exact timing, recurring patterns, custom properties and hashes can still identify people. Inspect your exported file and use the strict busy-only option when appropriate. Original local files are never overwritten.