Last updated · November 3, 2026

Privacy

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. File selections and edited events remain in this tab’s memory while you navigate within the site. They are not saved to browser storage and are cleared when you refresh, close the tab, or choose Discard this schedule. An ICS download sends the selected event data to our server, which generates the file without saving the events.

ICS to CSV conversion

The ICS to CSV converter reads selected calendar files and pasted calendar text on your device. Parsing, previews, timezone display, and CSV generation run in your browser. Calendar contents are not sent to our server or an AI provider, and are not saved in browser storage. Clear calendar removes the current input and preview; refreshing the page clears them and restores the fictional example. Analytics record conversion actions and event entry counts, without filenames or event contents.

Third-party AI processing

Image and PDF extraction sends your file content to AIHubMix, which routes it to the model provider that reads the schedule. The request also includes your selected timezone and the current date. We ask the extraction API not to store the response using its store setting. Our promise not to permanently store uploaded files describes this application; processing and retention by external providers are governed by their own policies and service terms. Review AIHubMix’s privacy policy before uploading information you do not want processed by an external AI service.

The manual ICS File Generator does not use AI or send event details to AIHubMix.

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.

Accounts, credits, and purchases

If you sign in, a third-party identity service processes your account identifier, email address, display name, and profile image. We store your credit balance, credit ledger, usage status, orders, and payment status in a managed database. These records do not include uploaded files or extracted calendar content.

We remember your first landing page and external referring website in browser storage for up to 30 days. When you create an account, we save this source and the registration page with your account. Orders include a snapshot of that registration source, the checkout page, and, when available, the site page that led you to pricing within the previous 30 minutes. Stored attribution URLs exclude query strings and fragments. Missing or blocked referrers remain unknown. These records help us understand which pages lead to registrations and purchases.

Payments

A third-party payment processor handles payment details and may receive your contact, billing, device, and transaction information. This application does not receive or store your full card number. We retain customer, checkout, payment, refund, and dispute identifiers so purchases can be fulfilled and audited safely.

Browser storage and checkout feedback

The manual Schedule Maker saves one editable weekly draft in local browser storage on your device, including activity titles, times, locations, and notes. It is not synced to an account or another device. Clearing browser data removes the saved draft. PNG and PDF exports are generated on your device. ICS export sends activity details to our server to generate the file without saving them. Schedule Maker does not use AI; its analytics include export format and activity count, not activity contents.

A signed cookie identifies whether the one-time guest conversion has been used. The browser may also remember an unfinished checkout so we can ask what stopped you when you return. Checkout feedback is optional. We store submitted feedback privately and may use an email service to send the feedback and your account email address to the site administrator. Free-text feedback is not used for website analytics.

Website analytics

We use a third-party analytics service 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 conversion steps and non-content details such as file format, a coarse file-size range, event count, selected calendar app, credit or checkout stage, and generic failure category. Uploaded files, filenames, feedback text, and extracted calendar event contents are not sent to the analytics service.

Sensitive information

Do not upload unrelated medical, financial, identity, or other highly sensitive material. Only upload files you are authorized to process.

Privacy questions and account requests

Contact support@imagetocalendar.app for questions about file processing, your account, or personal data. Include the account email if relevant; do not send passwords, card numbers, or private schedule files.