Privacy Policy
Last updated: September 21, 2026
The short version
NeverLate has no accounts, no servers of its own, no analytics inside the app, and no advertising. It reads your calendar on your iPhone to schedule alarms before your events, and that calendar data is never uploaded by NeverLate. If you choose to connect Google Calendar, Google’s sign-in service is involved, and we describe exactly what that means below.
What NeverLate accesses and why
| Data | Why | Where it goes |
|---|---|---|
| Calendar events (title, time, location, notes, link, calendar, your attendance status, availability) from the calendars on your iPhone | To find upcoming events, decide which ones get an alarm, and show your agenda | Processed on your iPhone. Not stored by NeverLate beyond what is on screen; re-read from your calendar on every refresh. |
| Alarm records (an internal event identifier, the alarm’s identifier, its time, lead time and sound) | So NeverLate can recognise and update its own alarms instead of creating duplicates | A file on your iPhone. Entries disappear as soon as the event passes. |
| Your settings (lead time, sound, selected calendars, event filters, per-event choices, appearance, connected Google address) | To behave the way you asked | Stored on your iPhone only. |
| Widget snapshot (the next 24 hours of event titles, times, locations, and alarm times) | To show the Home Screen widget | Stored in NeverLate’s private app container on your iPhone; overwritten on every refresh. |
| Alarm details handed to iOS (event title, location, start time) | So the alarm screen — and a paired Apple Watch — can show which event the alarm is for | Held by iOS while the alarm exists; removed when it fires or is cancelled. |
NeverLate never accesses your contacts, location, photos, microphone, or notifications, and never reads attendee lists except to learn your own reply to an invitation. Attendees are never shown, stored, or logged.
Permissions
Calendar (Full Access). Reading events requires full calendar access; “Add Events Only” cannot read events. You can change this at any time in the iPhone Settings app → Apps → NeverLate → Calendars. Without it NeverLate cannot find events or schedule alarms, and the app says so.
Alarms. NeverLate uses Apple’s AlarmKit to sound prominent alarms, including when your iPhone is locked or silenced. You can turn this off in the iPhone Settings app → Apps → NeverLate → Alarms. Without it you can still see your agenda, but no alarms will sound.
NeverLate does not ask for notification permission and does not use push notifications.
Google Calendar (optional)
Most people don’t need this: if your Google account is added to the iPhone’s Calendar app, its events already reach NeverLate through Apple Calendar. The direct connection exists for people who prefer not to add the account to iOS.
If you tap Connect Google Calendar during setup, or Connect under Settings → Calendars → Google Calendar:
- You sign in with Google’s own sign-in screen. NeverLate requests read-only access to your calendar events (
calendar.events.readonly) and Google’s standard sign-in identity scopes. NeverLate never sees your Google password. - NeverLate fetches events from your primary Google calendar for the next seven days directly from Google to your iPhone, and treats them exactly like Apple Calendar events. If the same meeting also arrives through Apple Calendar, it is armed once.
- Your sign-in tokens are stored in the iPhone Keychain by Google’s Sign-In software. NeverLate never reads, copies, or logs them.
- What Google collects. The Google Sign-In software that performs the sign-in declares that it collects your name, e-mail address, phone number, coarse location, user ID, device ID and usage data, linked to you, for app functionality and Google’s own analytics — not for advertising tracking. This happens only when you use the Google connection, and it is governed by Google’s Privacy Policy. NeverLate itself receives only your e-mail address (to show which account is connected) and your calendar events.
- Disconnecting. Settings → Calendars → Google Calendar → Disconnect revokes NeverLate’s access with Google, removes the connection and its tokens from your iPhone, and cancels the alarms created for Google events. You can also revoke access from your Google Account under Third-party apps & services.
Diagnostics
Settings → Privacy & Support → Diagnostics shows the app’s own state: permission states, counts of events and alarms, timestamps, app and iOS versions. It never includes event titles, locations, or account details. Nothing leaves your iPhone unless you tap Copy Summary and paste it into an email to us.
How long data is kept
- Calendar events: not stored by NeverLate; read fresh each time.
- Alarm records and the widget snapshot: only while the event is upcoming; overwritten or removed automatically afterwards.
- Settings and the Google connection: until you change them, tap Disconnect, use Clear Local Data (Settings → Privacy & Support), or delete the app. Deleting the app removes everything NeverLate stored on your iPhone; if Google was connected, also revoke access in your Google Account.
Your choices
- Turn calendar or alarm access off at any time in the iPhone Settings app. NeverLate never asks again once you have decided; it links you to Settings instead.
- Choose which calendars are watched and which kinds of events get alarms inside NeverLate.
- Turn alarms off entirely, which cancels every NeverLate alarm.
- Disconnect Google, or clear all local data, from Settings → Privacy & Support.
Children
NeverLate is a general-audience utility and is not directed at children.
This website
never-late.app (this site, not the app) loads a page-view counter from Seline to see how many people visit. The app itself contains no analytics. The site is hosted on GitHub Pages, which may keep standard server logs.
Changes to this policy
If this policy changes we will update this page and the date at the top. The plan is to keep NeverLate this simple.
Contact
Questions or requests about your data? Visit the support page to email us.