Last updated 28 July 2026
The short version. Meeting Time reads your Google Calendar directly onto your iPhone and keeps it there. Your event titles, times, guests and links are never sent to us, and we operate no server that stores your calendar. The only thing the app can send us is a handful of anonymous counts, which you can turn off.
This policy explains what Meeting Time ("the app", "we", "us") does with your information. It applies to the Meeting Time iPhone app and this website.
When you connect a Google account, the app asks for the
read-only Google Calendar scope
(calendar.readonly). It cannot create, edit or delete
anything on your calendar.
Your iPhone requests events from Google directly. That data is not routed through any server of ours. From each upcoming event in the next one to two days, the app reads:
All of it is used for one purpose: deciding which events deserve an alarm and when that alarm should ring. It is stored in the app's private storage on your device — shared only with the app's own widget so it can display today's alarms — and is replaced each time the app checks your calendar. Events that have passed drop out.
We never receive your calendar data, and we never sell, rent or share it. No advertising or tracking company receives it either, because the app contains no advertising or tracking software.
Signing in also provides your name, email address, profile picture and Google account identifier, so the app can show you which accounts are connected. These are stored on your device only.
Sign-in tokens are held in the iOS Keychain, the system's encrypted credential store. They stay on your device.
To understand how much the app is used, it can send a small set of counts to a database we operate on Google Cloud Firestore. This is enabled by default and can be turned off at any time in Settings → Share anonymous stats.
| What is sent | Why |
|---|---|
| A random identifier created on your device | To count distinct devices without identifying anyone |
| How many alarms have fired in total | To understand typical usage |
| How many accounts are connected | To understand how people set the app up |
| App version and iOS version | To know which versions are in use |
| First and most recent use dates | To measure whether people keep using the app |
The identifier is randomly generated on your device. It is not your Apple ID, your Google account, your phone number, your device's serial number, or any identifier assigned by Apple or Google, and it cannot be traced back to you. It exists so two reports from the same phone aren't counted as two phones.
Sending happens at most once a day, and only when one of those numbers has changed. No calendar content is ever included — no titles, times, guests, links or account names.
There are no other third parties. The app includes no advertising networks, no analytics software development kits, and no social media trackers.
Calendar data lives on your device only, and only for the short window the app looks ahead. Removing an account deletes its stored data and sign-in tokens and cancels its alarms. Deleting the app removes everything it stored on your device.
Anonymous statistics are kept while they remain useful, and are not linked to any person.
Meeting Time is a workplace productivity tool and is not directed at children under 13. We do not knowingly collect information from them.
Sign-in tokens are stored in the iOS Keychain and calendar data in the app's protected storage, both encrypted by iOS. Network requests use HTTPS. No system is perfectly secure, but keeping your calendar on your device rather than on a server of ours removes the risk that a breach of ours could expose it.
If this policy changes, the date at the top will change and the current version will always be posted here. Significant changes will be highlighted in the app.
Questions, requests, or anything unclear: tayloreke@gmail.com.
Meeting Time