Liquid Calendar is an iPhone calendar app. This policy explains what data the app can access, where that data is stored, and which third parties are involved.
1. What the app accesses
Calendar data
If you grant calendar permission, Liquid Calendar reads and writes events in the calendars available on your device. That includes Apple calendars and any Google calendars you connect through Google OAuth.
Liquid Calendar does not operate its own cloud event database. Your events remain in the calendar accounts you already use.
Voice input
If you use voice entry, the app uses iOS speech-recognition APIs to convert your speech into text for event creation. The app does not run its own speech-processing backend.
Local reminders
If you enable notifications and create or edit an event with an alarm, the app may schedule a local reminder on your device. Reminder content can appear on the iPhone lock screen depending on your iOS notification settings.
Location search
If you type a location while creating an event, Liquid Calendar can query Apple Maps autocomplete services to suggest matching places. Those queries are handled by Apple, not a Liquid Calendar backend.
2. Data stored by Liquid Calendar
App preferences such as selected calendars, view preferences, and Pro access state are stored locally on your device.
Google Calendar OAuth tokens are stored in iOS secure storage.
The app does not provide an in-app account system and does not maintain a user profile database.
3. Third-party services
Liquid Calendar may use the following third-party services:
Google Calendar for connected Google calendar access. Privacy Policy
Apple Maps for optional place autocomplete when you search event locations. Privacy Policy
RevenueCat for one-time Pro purchase entitlement and restore handling. Privacy Policy
PostHog for product analytics when configured. Privacy Policy
Sentry for crash reporting and diagnostics when configured. Privacy Policy
4. What the app does not currently do
No Liquid Calendar account signup or sign-in.
No Liquid Calendar-managed cloud sync.
No HealthKit integration in the shipped app.
No training or fine-tuning of AI models on your calendar data.
5. Security
The app relies on iOS secure storage for sensitive local tokens.
Network communication to third-party services uses HTTPS.
Calendar data is stored by the calendar providers you use, not by Liquid Calendar's own backend.
6. Retention and deletion
You can edit or delete events through the calendar account that owns them.
You can disconnect Google Calendar from inside the app, which clears the app's local Google tokens.
You can remove the app and its locally stored preferences from your device at any time.
7. Changes to this policy
This policy may change as the shipped product changes. The "Last updated" date above reflects the latest revision.
8. Contact
Questions about privacy or data handling can be sent to
mrjoevu@hotmail.com.