Last updated · August 5, 2026
Privacy
Image to Calendar is designed to convert a file without building a permanent library of your schedules.
Files and event data
Your uploaded image or PDF is read in server request memory only to extract calendar events. The application does not write the file to permanent disk, object storage, or a database. Edited event data remains in your browser until you request an ICS download; the server then generates the file without saving the events.
Operational data
We may log anonymous operational facts such as file category, byte size, PDF page count, event count, processing time, token usage, request identifier, HTTP status, and error code. Logs must not contain filenames, file contents, event titles, locations, descriptions, API keys, verification tokens, or full IP addresses.
Browser storage
A small localStorage record counts successful conversions for the current date. It supports the three-conversion daily preview limit and can be removed through your browser settings.
Website analytics
We use Google Analytics to understand page visits and general usage patterns. It may process information such as page views, browser and device details, approximate region, and analytics identifiers using cookies or similar technologies. We also measure the conversion steps and non-content details such as file format, a coarse file-size range, event count, selected calendar app, and generic failure category. Uploaded files, filenames, and the calendar event contents extracted from them are not sent to Google Analytics.
Sensitive information
Do not upload unrelated medical, financial, identity, or other highly sensitive material. Only upload files you are authorized to process.