Privacy Policy

Calendars on your device

With your permission (Calendars, full access), Cadence reads events through Apple’s EventKit framework: titles, times, time zones, locations, notes, links, the calendar and account each event belongs to, the organiser, the attendees and their responses. That is the same data Apple Calendar shows for the accounts you have added to your Mac or iPhone.

Cadence uses it to draw your agenda, day, week and month views, list invitations that need a reply, detect double-bookings, find join links, schedule reminders and the daily brief, and fill its widgets and Live Activity. When you use quick add, Cadence creates the event through EventKit in the calendar you chose; when you share availability, the free times are copied to your clipboard and go only where you paste them. All of this processing happens on your device. Event titles, attendee addresses and notes are never written to logs and never sent to Coursion Studio.

Google Calendar

Linking a Google account is optional and only needed to answer Google invitations from inside Cadence. You sign in on Google’s own page; Cadence receives an OAuth token and requests one scope:

Find a time reads when the people you choose are free or busy, and nothing else (no titles, attendees or notes), to suggest meeting times. Cadence sends the email addresses you choose to Google's free/busy endpoint (scope calendar.freebusy, asked for the first time you use it) or Microsoft Graph's schedule endpoint, directly from your device. Nothing goes through a Coursion server.

If you turn on leave-by alerts, Cadence asks for your location while it is open and uses Apple Maps on your device to estimate travel time to meetings with a place. Your location is not stored or sent anywhere else.

If you turn on weather, Cadence uses your approximate location with Apple WeatherKit to show the forecast on each day. Apple receives the location to answer the request; Cadence does not store it.

If you turn on reminders, Cadence reads and completes reminders through Apple’s EventKit framework on your device. Nothing about them leaves your device.

If you add an Exchange account, Cadence sends your username and password only to the Exchange server you entered, over https, to send your replies. The password is stored in the Keychain.

If you add a CalDAV account (Fastmail, Nextcloud, Zoho, Synology, mailbox.org or any other CalDAV server), Cadence sends your username and app password only to the server you entered, over https, to find your calendars and send your replies. The password is stored in the Keychain and never leaves your device otherwise. Cadence looks up your email domain's public DNS records to find the server. Nothing goes through a Coursion server.

Cadence also asks for your Google account's email address (scope userinfo.email) so it can show which account is linked and match invitations to it. The address stays on your device.

Requests go directly from your device to www.googleapis.com. The data Google returns is used for that reply and then discarded; Cadence keeps no copy of it.

Microsoft 365 and Outlook

Linking a Microsoft account is optional. You sign in on Microsoft’s page and Cadence requests:

Requests go directly from your device to graph.microsoft.com. If your organisation requires an administrator to approve apps, Cadence shows you the message to pass on; nothing is sent anywhere else.

iCloud Calendar

To answer iCloud invitations, you give Cadence your Apple Account email and an app-specific password that you create at Apple. Cadence connects to caldav.icloud.com, fetches the one event you are answering by its UID, changes your attendance on it and writes it back. iCloud then notifies the organiser. You can revoke the password at any time at Apple without affecting anything else.

Where data is kept

• Tokens and passwords — Google and Microsoft OAuth tokens and your iCloud app-specific password are stored only in your device’s Keychain under the service com.coursion.cadence. They are never logged, never displayed, and only ever sent to the provider they belong to.
• Calendar data — stays in the system calendar database where it already lives. To feed widgets, Cadence writes a small summary of upcoming meetings into its own app group container on the same device.
• Pending replies — after you answer, Cadence remembers the answer locally until your calendar confirms it, so it can show “sent”, offer Undo or retry.
• Notifications — join reminders and the daily brief are scheduled locally by the system; they do not pass through any server of ours.

Settings sync through iCloud

If you are signed in to iCloud, Cadence keeps your settings in step between your Mac and iPhone through your own iCloud private database: calendar sets, time zones, hidden calendars, the active set, working hours, week start, default view, notification hours and which calendar account is answered by which provider. Apple stores this in your iCloud account; Coursion Studio cannot read it. Events, tokens and passwords are never synced this way.

Agents, the command line and Shortcuts

The Mac app can run a local server for AI agents (the Model Context Protocol) and for the cadence command line. It listens on 127.0.0.1 only, so nothing outside your Mac can reach it, and every request needs a token kept in your Keychain. Agents can read your schedule; replying on your behalf stays off until you turn it on in Settings → Agents. Shortcuts, Siri and the Focus filter use Apple’s App Intents on your device. Automations that run a Shortcut when a meeting starts or ends are off until you turn them on, and pass the Shortcut the event’s identifier only.

When you connect an agent of your choosing, what it does with the answers Cadence gives it is governed by that agent’s own terms. Cadence does not send your data to any AI service itself.

What Cadence never does

• No Coursion server: none of your calendar data, tokens or replies passes through us.
• No analytics, tracking or advertising SDKs, and no profile of you.
• No sale, rental or sharing of your data with anyone.
• No use of your calendar data to train AI models.
• No access to your contacts, mail or files.

If you have chosen to share crash reports with app developers in your device’s settings, Apple may pass anonymous crash reports for Cadence to us. You control that in System Settings or Settings on iPhone, under Privacy & Security → Analytics & Improvements.

Google API Limited Use

Cadence’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is used only to provide the reply feature you asked for, is processed on your device, is not transferred to Coursion Studio or any third party, is not used for advertising, and is not read by any person.

The App Store

Cadence is free and is distributed through the Mac App Store and the App Store. We receive no personal information about you from Apple, only the anonymous download reports Apple gives every developer.

This website

cadence.coursion.studio is a static site with no cookies, no analytics and no third-party scripts. Our web host may keep standard access logs, such as IP address and the page requested, for security and reliability; we do not use them to identify you.

Revoking access and deleting data

• Unlink an account in Cadence under Settings → Accounts. Its token or password is deleted from your Keychain at once.
• You can also revoke access at the provider: your Google Account’s third-party access page, Microsoft’s app permissions page (or your organisation’s My Apps portal), or the app-specific passwords section of your Apple Account.
• Withdraw calendar access in System Settings or Settings on iPhone, under Privacy & Security → Calendars.
• Deleting Cadence removes its local data. Settings synced to iCloud can be removed under your Apple Account’s iCloud storage settings.

Because we hold no personal data about you, there is nothing on our side to export or delete; if you think otherwise, write to us and we will check.

Children

Cadence is a general-purpose tool and is not directed at children under 13. We do not knowingly collect information from children.

Changes and contact

If Cadence starts handling data differently, this page will change first and the date at the top will move.

Coursion Studio is responsible for Cadence. Questions about privacy, or any request about your data: privacy@coursion.studio.