Privacy for calendar checks
Last updated November 3, 2026. This policy explains how CalendarCheck handles calendar files, account data, and subscription information.
One-time calendar checks
The checker receives uploaded or pasted calendar text over HTTPS and parses it in server memory. If you submit a calendar URL, our server requests it over HTTPS from a public internet host and temporarily holds the response while parsing it. Private calendar URLs can contain access tokens and work like passwords; submit only a URL you are authorized to use.
A one-time check does not save the uploaded file, URL, response, or result to an account or history. The application does not intentionally write calendar content or URLs to application logs. Standard hosting and infrastructure logs are retained for a limited period for security and operations.
Account and monitor data
Account and daily-monitor features store your name, email, authentication records and sessions. A saved monitor stores its name, feed host, encrypted full feed URL, schedule, email-alert preference, and recent check metadata.
Check history and related alert-delivery records are retained for up to 30 days. History contains check time, status, duration, event count, validation issue codes, and a keyed change fingerprint. Event titles, descriptions, guest details, raw feed bodies, and decrypted feed URLs are not saved in check history. You can delete a monitor with its history and queued alerts; account deletion requires confirmation through your verified email and removes the account's saved monitors and history.
Requests and email
The server receives connection information such as an IP address and request metadata to deliver and rate-limit a check. When you submit a URL, its calendar host receives a request from our server, including the requested path and query string. If you enable alerts for a feed, we send transactional email about detected changes or feed problems from the CalendarCheck mail server. Alert messages contain the saved feed name and host plus a general issue category; they do not include event titles, guest details, full feed URLs, or booking data.
Payments
Paddle processes subscription checkout and recurring charges. CalendarCheck stores the Paddle customer and subscription IDs, selected price ID, subscription status, billing-period end date, scheduled cancellation date, transaction status, and adjustment status for signed billing notifications. Payment card details are entered into Paddle Checkout and are not stored in the CalendarCheck database.
Questions
Contact highsave@gmail.com with privacy questions.