Bugle
Privacy Policy
Last updated 16 August 2026
Bugle turns your meetings into real alarms. To do that it needs to know when your meetings are — not what they are about, and not who is in them.
The short version. Your calendar's contents — event titles, descriptions, locations, attendees — stay on your iPhone. They are never sent to our servers. If you connect Google Calendar, our server receives only the timing of your events (start, end, cancelled or not) so it can tell your phone when something moved. We have no user accounts and we never ask for your name or email address.
What stays on your device
Bugle reads your calendar through Apple's EventKit framework, directly on your iPhone. Everything it needs to schedule an alarm — the event's title shown on the alarm screen, its notes, its location, its video-call link, the list of attendees — is read, used, and kept on the device. None of it is transmitted to us or to anyone else.
What our server receives if you connect Google Calendar
Connecting Google Calendar lets Bugle fix your alarms when a meeting moves, even while the app is closed. Google notifies our server that something changed, and our server asks Google what the new timing is.
When it does, it requests only these fields:
- the event's identifiers (
id,iCalUID) - its start and end times
- its status (confirmed or cancelled)
- whether you personally accepted or declined it
Event titles, descriptions, locations, attachments, and the identities of other attendees are never requested and never received. When your phone shows you a notification that says which meeting moved, the name of that meeting is filled in on the device, from the copy of the calendar already on your iPhone.
What we store
- A random identifier generated on your device. It is not derived from your phone, your name, or your Google account, and it is not linked to any identity.
- An encrypted Google access credential, used only to read the timing fields listed above. It is encrypted at rest and can be revoked by you at any time.
- A synchronisation cursor and the start and end times of your upcoming events for the next seven days, so we can tell what changed.
- An Apple Push Notification token, so we can reach your device.
We do not store your name, your email address, your Google account address, or the contents of any event.
Google API Limited Use
Bugle's use of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Specifically: data obtained through the Google Calendar API is used solely to schedule and correct alarms on your own device. It is never transferred to third parties, never used for advertising, never sold, and never read by a human, except where required by law or with your explicit consent for support purposes.
Analytics
Bugle records anonymous product analytics through PostHog so we can tell whether alarms are firing reliably. These events contain counts, timestamps, and fixed labels such as "alarm scheduled" or "alarm fired". They never contain event titles, calendar names, or any other calendar content.
Your control
Disconnecting Google Calendar in Bugle's settings deletes the stored credential, event timings, and synchronisation state from our server. Deleting the app removes everything held on your device. You can also revoke Bugle's access directly from your Google Account permissions page. Because we hold no account and no contact details, disconnecting is the complete deletion process — there is nothing left for us to associate with you.
Children
Bugle is not directed at children under 13, and we do not knowingly collect information from them.
Changes
If this policy changes materially, the updated date above will change and the app will tell you before the new terms take effect.
Contact
Questions about privacy: [email protected].