Last updated 16 November 2026
Privacy policy
Your privacy matters.
Calendelle processes your calendar data locally on your device. We do not collect, upload, or store your calendar events or their contents. Your calendar information is never included in analytics or crash reports.
We collect limited app usage analytics and technical diagnostics solely to monitor performance, identify issues, and improve Calendelle.
We never sell this information, share it with advertisers, or use it for advertising, profiling, or cross-app tracking. No Calendelle account is required.
This privacy policy covers Calendelle for iPhone and iPad and its widgets, and this support website. The analytics and crash reporting described below are introduced in version 1.1.
Calendar access
With your permission, Calendelle uses Apple’s calendar framework to read and display calendars and events on your device. This can include event titles, dates, locations, notes, links, recurrence details, and attendee information. When you choose to create, edit, or delete an event, Calendelle applies that change to the selected calendar, where permitted.
Your calendar provider, such as iCloud, Google, or Exchange, may sync those events according to your account settings and its own privacy policy. Calendelle does not operate a separate service that stores your calendar contents or receive your calendar-account password.
Local storage, highlights, and widgets
The app stores preferences such as visible calendars, their order, the default calendar, display settings, and language. It also keeps local records needed to identify events and remember which ones you have highlighted. Removing a highlight can leave a record of that removal so the decision is preserved.
When iCloud is available, Calendelle syncs eligible highlight selections between your devices using Apple’s CloudKit and your private iCloud database. These records contain event-matching identifiers, highlight decisions, and date or revision information. Event titles, notes, locations, participants, and calendar names are not included in these synced highlight records. This is separate from your calendar provider’s event sync and from our analytics.
The app shares a local snapshot with its own widgets. It contains event titles, dates, times, colours, and highlight status for the current and following month, plus display preferences. Event notes, locations, links, and attendee information are not included in that widget snapshot. Widget content can be visible to anyone who can see the screen where you place a widget.
App data may be included in device backups or transferred to another device by Apple’s system features, depending on your settings.
Usage analytics and handled errors
We use TelemetryDeck to understand which features are useful and where the app needs improvement. The app sends limited signals such as:
- App sessions, screens opened, and actions such as creating, editing, or highlighting an event. The event’s contents are not sent.
- Whether a call, map, or link button was used, with a general provider label such as FaceTime or Apple Maps. The address, telephone number, destination URL, and invitation details are not sent.
- Purchase and restore attempts and their outcomes, the package category, and where the purchase screen was opened.
- Calendar-permission outcomes and predefined error categories, such as a network failure or unsuccessful save. Raw error messages and the records involved are not sent.
TelemetryDeck also includes an anonymized installation or device identifier, a session identifier, timestamps, session counts and duration statistics, and technical metadata such as app and operating-system versions, device model, screen characteristics, language, region, time zone, and display or accessibility settings. Region and time zone come from device settings; we do not send GPS location to our analytics.
TelemetryDeck hashes identifiers before transmission and applies further anonymization on its servers. We do not supply names, email addresses, Apple Account identifiers, calendar contents, payment details, or transaction identifiers to TelemetryDeck, and we do not attempt to connect its analytics to a person’s identity. TelemetryDeck states that it does not retain IP addresses. See its privacy FAQ for details about processing and retention.
Crash reporting
We use Sentry to diagnose and fix app crashes. A report can include the time of the crash, app version and build, operating-system version, device model and architecture, crash type, and technical stack and binary information needed to locate the fault in our code.
Our crash-reporting configuration removes user identifiers, event and calendar contents, URLs, raw exception messages, source-file paths, and attachments. Screenshots, screen recordings, session replay, network-request recording, and performance tracing are disabled. We do not attach a user profile or enable Sentry’s automatic IP-address collection.
Reports are sent to our Sentry project using its EU ingestion endpoint. Like any network service, the provider must process connection information to receive requests. See Sentry’s data-collection documentation, data-processing terms, and privacy policy.
Purchases
Apple handles payments and App Store purchases. Calendelle uses Apple’s StoreKit framework to verify purchase entitlements and restore access to paid features. We do not receive your payment-card details. The limited purchase and restore analytics described above include package categories and outcomes, not receipts, transaction identifiers, prices, or Apple Account details. Apple’s handling of purchases is covered by Apple’s Privacy Policy.
How this information is used and retained
Usage and purchase signals help us evaluate features and improve Calendelle. Crash reports and handled-error diagnostics help us resolve technical problems. We do not sell this information, use it for targeted advertising, or combine it with data from other companies to track you across apps or websites.
TelemetryDeck retains anonymized analytics for longer-term analysis; its current retention guidance does not set a fixed automatic deletion deadline for stored analytics events. Sentry’s standard error-event retention is 30 or 90 days depending on the plan in effect when the report is received. Reports expire under that retention policy; issue summaries and backups can follow separate retention rules. See Sentry’s retention documentation.
These providers process the information on our behalf using their hosting providers and subprocessors. Processing can involve countries outside your country of residence. Their linked privacy and data-processing information describes their arrangements and safeguards.
Your choices and removing data
You can revoke calendar access in Settings → Privacy & Security → Calendars → Calendelle on your iPhone or iPad. You can also hide individual calendars in the app, remove highlights, remove widgets, and manage iCloud and backups through Apple’s settings.
In version 1.1, the limited analytics and crash reporting described here run automatically; there is no separate in-app switch. Revoking calendar access does not disable these reports. Deleting the app stops further reporting from that installation but does not delete reports already received by our providers.
Deleting Calendelle removes its app-local data from that device; offloading retains data. Deleting the app does not delete calendar events, iCloud highlight records, or backups. Manage those separately through the relevant calendar provider and Apple’s iCloud settings.
For privacy requests, contact gr09oizv@anonaddy.me. Where applicable, you may request access, correction, deletion, or restriction of your personal information, object to its processing, or complain to your local data-protection authority. Because analytics and crash reports do not contain your name or email address, we may be unable to identify which reports relate to you.
Maps, links, and other apps
Showing an event’s map preview can send its location text or coordinates to Apple’s mapping and geocoding services. If you choose to open a website, location, telephone number, or meeting link, the relevant information is passed to the app or service you open. Those providers’ privacy policies apply. These destinations and calendar details are not sent to TelemetryDeck or Sentry.
If you contact support
If you email the developer, your email address, message, and any attachments are used to respond and investigate the issue. Email is handled by the email services involved in delivering and receiving it. Please send only the information needed to explain your question and hide private calendar details in screenshots.
Support correspondence is kept only as long as reasonably needed to handle your request and related follow-up, or meet legal obligations. You can request access, correction, or deletion of information you have sent using the privacy contact above.
This website
These pages contain no analytics, advertising, or tracking scripts, and set no cookies. They are hosted by Cloudflare Pages. Cloudflare may process ordinary connection information, such as IP addresses and browser requests, to deliver and protect the website. See Cloudflare’s Privacy Policy.
Changes and questions
This policy may change when the app or its data handling changes. The date above identifies the latest version. For privacy questions, contact gr09oizv@anonaddy.me.