CALENYTIC
Calenytic app privacy policy
Updated: 2026-10-18
1. Controller and scope
Mark Philipp Müller · MPM Apps
Lohhoferstraße 1
85386 Eching
Deutschland / Germany
calenytic@outlook.de
+49 176 47669451
This policy describes the current native Calenytic app based on its implementation on October 18, 2026. Features may vary by platform and released version. It does not retroactively replace the policy for an older app version.
2. Calendar access and local data
After your permission, Calenytic accesses device calendars through Apple EventKit. Data includes calendar names, event titles, start and end times, recurrence and other event information required for calendar features. Analytics, settings, planning drafts, templates and onboarding progress are processed or stored on your device. Providing requested calendar and planning features relies on Article 6(1)(b) GDPR. You can revoke system permission in Apple settings; calendar features will then be restricted.
3. Accounts, synchronization and sharing
The current app does not use the dedicated Google OAuth login described in the old policy. Calendars may come from accounts configured on your device, such as iCloud, Google or Exchange. Synchronization follows system settings and the calendar provider’s terms. Changes to shared calendars may reach other participants. You choose destinations for exports or shared content; the recipient’s terms apply there.
4. Live Activities and call reminders
For remote updates and call reminders, the iPhone app uses Firebase/Google Cloud and Apple Push Notification Service. An anonymous Firebase sign-in is created when needed. “Anonymous” here means without registering a name; a technical user identifier remains linkable. Depending on the feature, data includes activity or alarm IDs, push or VoIP tokens, scheduled times, language and technical environment. Live Activity payloads can also include event titles and status information; call reminders include the displayed caller name and, where applicable, an audio URL or Watch token.
5. Remote processing and retention
These data support the scheduled update or reminder you request under Article 6(1)(b) GDPR. Abuse controls and technical logs support secure operation under Article 6(1)(f) GDPR. The backend uses Cloud Functions, Cloud Tasks, Realtime Database and Cloud Storage for alarm audio. Source code references us-central1; exclusive EU processing is not promised. Cancellation attempts to remove scheduled tasks. Retention for authentication, logs, rate limits, tasks and audio needs separate operational confirmation. Disabling a feature or removing the app does not automatically erase all provider logs.
6. PostHog usage analytics
The app uses PostHog’s EU endpoint eu.i.posthog.com. Selected usage and onboarding events, launch and session times, usage duration, launch count, technical properties and an SDK identifier are processed. Treat these as pseudonymous; the previous blanket claim of anonymity without a device identifier is not retained. Connections also technically expose an IP address. Automatic screen and interaction capture, session replay, automatic error capture and person profiles are disabled in the integration.
7. Diagnostics setting and its limits
Extended mode captures additional feature events. Reduced mode is the current default and still sends launch, session, onboarding and settings events. Onboarding capture is not fully controlled by the general diagnostics filter. Turning off diagnostics therefore does not stop all PostHog transmissions. Analytics requiring consent is subject to Article 6(1)(a) GDPR and, where applicable, Section 25(1) TDDDG. The legal basis and permissibility of processing already occurring in reduced mode must be resolved before releasing the current app version; this policy does not replace required consent. The previous policy provides no reliable project-specific retention period.
8. Purchases and RevenueCat
Apple and RevenueCat manage purchases, subscriptions and restoration. Data includes purchases and transactions, product IDs, entitlements, a pseudonymous app user ID and necessary technical connection data. Processing provides and restores purchased features under Article 6(1)(b) GDPR. We do not receive payment details such as credit card information. Purchase management is independent of the diagnostics setting. Records may remain necessary for existing entitlements and statutory duties after uninstallation.
9. Recipients and international transfers
Depending on the feature, recipients include Apple, Google/Firebase, PostHog, RevenueCat and their service providers. PostHog EU hosting does not automatically restrict all support access and subprocessors to the EEA. Google/Firebase and RevenueCat in particular may also process data in the United States. Applicable contracting entities, retention periods and transfer mechanisms under Articles 44 et seq. GDPR need confirmation against the operator’s contracts and projects. Calendar data is not offered for sale.
10. Deletion, contact and rights
You can delete calendar events and local app data through available features and revoke permissions in system settings. Changes to synchronized calendars may affect other devices and participants. Uninstallation does not automatically delete calendar accounts, purchases or provider data. Contact calenytic@outlook.de for access or deletion requests. Subject to legal conditions, rights include access, rectification, erasure, restriction, portability, objection to legitimate-interest processing and withdrawal of consent for the future. You may complain to a data protection authority such as BayLDA.
11. Further information
The app is not specifically directed at children under 13. Apple system diagnostics depend on your Apple settings. Firebase Crashlytics capture mentioned in the old policy was not established in the reviewed current integration and is not asserted here. Calendar analytics does not make decisions about you with legal or similarly significant effects.