Privacy Policy

Your privacy is our priority. CalendarLint is designed so that your calendar files and their contents stay on your device.

Overview

CalendarLint processes ICS files in your browser using client-side JavaScript. Your calendar files are not uploaded to CalendarLint, stored on our servers, or sent to Google Analytics. This includes event titles, dates, times, locations, descriptions, attendees, meeting links, UIDs, source lines, project identifiers, and file names.

The original file remains unchanged. Repairs and exports are created locally in your browser for you to review and download.

Data We Do Not Collect

CalendarLint does not collect or transmit:

• Your ICS file or its contents.
• Event titles, descriptions, locations, attendees, or meeting links.
• Calendar identifiers, UIDs, source lines, or file names.
• A copy of an original file or a repaired file.

The workspace may store local projects and preferences in your browser so that you can continue your work. This browser storage is not sent to CalendarLint.

How Local Processing Works

When you choose a file, your browser reads it directly into local memory. Parsing, previewing, diagnosing, repairing, comparing, and exporting happen in the browser. No calendar-content upload is required for these features.

Optional Analytics

CalendarLint can use Google Analytics to understand which product modules are used and whether general workflows succeed. Analytics is loaded only after you give consent.

Analytics events use allowlisted, non-content values such as a module name, a coarse count range, a success state, or an export type. Dynamic project paths are replaced with placeholders and query parameters are excluded. Calendar contents and file names are not included.

You can reject analytics without losing product functionality. Use the Cookie settings control in the site footer or privacy bar to change your choice. Withdrawing consent stops future analytics and removes the Google Analytics cookies that this site can access.

Cookies and Local Storage

The site may use browser storage for essential functionality, such as your theme preference, privacy choice, and local workspace projects. Optional analytics cookies are used only when you consent to Google Analytics.

Retention

Calendar files and their contents are held in your browser while you work and are not stored by CalendarLint. Local projects and preferences remain in your browser until you remove them or clear site data. Google Analytics data follows the retention settings configured for the CalendarLint property.

Security

Keeping calendar processing in the browser limits the amount of calendar information that needs to leave your device. You should still use a current browser, protect your device, and avoid opening files from untrusted sources.

Your Choice and Rights

You can use the core workspace without creating an account. You can decline optional analytics, change your choice later, and clear local projects or browser storage from your device.

If you have a question about this policy or want to make a privacy request, contact the CalendarLint project through its published support channel.

Changes to This Policy

We may update this Privacy Policy when the product, analytics configuration, or applicable requirements change. The updated version will be posted on this page with a new date.

Contact Us

Questions about this Privacy Policy can be directed to the CalendarLint project maintainers.

Last updated: November 1, 2026