cronk - Privacy Policy
Effective date: 10 June 2026
cronk is a personal day-planning app for iPhone. You speak or type what you have on, and cronk uses an AI service of your choice to turn it into a to-do list and calendar time-blocks.
This policy explains what happens to your information.
The short version: cronk has no servers, no accounts, and no analytics. The developer never receives your data. Your information stays on your device, in your own iCloud, and is sent only to the AI provider you choose, using your own API key.
Who we are
cronk is made by an independent developer. There is no backend operated by cronk and no company servers. We cannot see, collect, or access your data.
What cronk stores on your device
- Your tasks, daily plans, and weekly routine are stored locally on your device using Apple's SwiftData.
- Your AI API key is stored in the iOS Keychain on your device. It is never written to disk in plain text and is never sent anywhere except, as an authorization header, to the AI provider you selected when cronk makes a request on your behalf.
- If you are signed into iCloud, your tasks and plans may sync across your own devices through your private iCloud (Apple CloudKit) database. This data lives in your Apple account, is controlled by Apple, and is not accessible to the developer. See Apple's privacy policy for how iCloud handles your data. Your API key does not sync; it stays on each device's Keychain.
What is sent off your device, and to whom
To generate a plan, cronk sends the following directly from your device to the AI provider you chose (Anthropic Claude, OpenAI ChatGPT, or Google Gemini), authenticated with your own API key:
- the text of your morning brief (your spoken words are transcribed on-device first; see below),
- your existing cronk tasks and your weekly routine,
- read-only context from your calendars for roughly the next three weeks (event titles and times), if you have enabled "Read my other calendars" in Settings.
This is sent only when you ask cronk to plan, and only to the single provider you selected. The developer is not involved in this transfer and never receives a copy.
How that provider handles the data is governed by their own privacy policy: