Privacy Policy

Last updated: October 29, 2026 / 日本語

"Don't Be Late!" (the "App") respects your privacy and is committed to protecting your personal information. This Privacy Policy explains how the App handles data.

1. Information We Access

• Calendar data: The App reads event titles, start and end times, and calendar names from the calendars on your device (and, if you connect Google Calendar or Outlook in the iOS app, from those calendars; see "3."). This data is used only to schedule and show alarms (notifications and vibration), is never sent to us or any third party, and the App never writes to your calendars.
• Notification settings: The App checks whether local notifications are permitted.
• Advertising data: Pangle's ad SDK may collect your advertising ID, IP address, and device information in order to serve ads. Nothing is collected before you answer the ad choice (see "5. Advertising"). No ads are shown to Premium subscribers.

The developer does not collect directly identifying information such as your name, email address, or phone number (if you connect Google Calendar or Outlook, the account's email address is used on your device only, to show which account is connected). No account registration is required.

1-1. Permissions Used

• Read calendar: Used to retrieve the events you have chosen to monitor. The App never writes to your calendars.
• Google / Microsoft account (iOS, optional): Used to read your calendars with read-only access if you connect Google Calendar or Outlook (see "3.").
• Notifications: Used to display alerts before your events.
• Exact alarms (Android): Used to fire alerts at the exact scheduled time.
• Vibration: Used for vibration alerts.
• Foreground service (Android): Used to keep vibrating until you stop it.

2. Data Storage

The App stores the following settings only on your device (iOS: UserDefaults / Android: DataStore Preferences; on Android the ad choice is kept in SharedPreferences).

• Notification timing setting
• Morning reminder setting (on/off and time; iOS only)
• Vibration intensity setting
• Selected calendar IDs
• Muted event IDs
• Onboarding completion state
• Cached subscription purchase state
• Your ad choice (whether personalized ads are allowed)
• The name of the connected Google Calendar / Outlook account (such as its email address) and whether it needs to be reconnected (iOS only)

This data stays on your device and is never sent to any external server. Google Calendar / Outlook authentication tokens are stored in the iOS Keychain (see "4. Data Protection").

2-1. Retention and Deletion

The settings above are kept on your device until you uninstall the App. Uninstalling the App deletes all of this data. You may also clear the App's storage from your device settings at any time. Because the developer does not hold any of your data, no deletion request process is necessary. Google Calendar / Outlook authentication tokens may remain in the Keychain after you uninstall the App, so please disconnect the account in the Calendar tab before deleting the App (the App also deletes tokens left by a previous installation on its first launch after reinstalling).

3. Google Calendar and Outlook Integration (iOS, Premium)

In the iOS app, only if you sign in with your Google account from the Calendar tab, the App uses the Google Calendar API to read the following information with read-only access (scope: https://www.googleapis.com/auth/calendar.readonly).

• Your calendar list (names, colors and IDs). The ID of your primary calendar (your Google account's email address) is used to show which account is connected
• For the calendars you select: each event's start and end times, title, whether it was cancelled, and your own response to the invitation

This information is used only on your device to ring alarms (notifications and vibration) before your events and to show them in the App. It is never sent to our servers or any other third party, never used to serve or personalize ads, and never used to train AI or machine learning models. The App never creates, changes or deletes events.

The only things kept on your device are the IDs of the calendars you selected, the IDs of events you muted, the token used to stay signed in (in the iOS Keychain), and the alarm notifications scheduled with iOS (which contain the event title and start time and disappear once the event time passes or when they are rescheduled after an event changes or you disconnect).

You can disconnect at any time with "Disconnect" in the Calendar tab. This deletes the token from your device, asks Google to revoke it, and cancels the alarms for that account's events. You can also revoke access from "Third-party apps & services" in your Google Account (https://myaccount.google.com/connections).

Don't Be Late!'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.

Outlook (Microsoft) calendars: In the iOS app, only if you sign in with your Microsoft account from the Calendar tab, the App uses Microsoft Graph to read, with read-only access (permissions: Calendars.Read, User.Read, offline_access), your calendar list, the events in the calendars you select (start and end times, title, whether they are all-day or cancelled, and your own response), and the email address (or display name) used to show which account is connected. It is handled in the same way as Google Calendar data: used only on your device to schedule and show alarms, never sent to us or third parties, and never used for advertising or AI training. "Disconnect" in the Calendar tab deletes the token from your device (Microsoft provides no way for an app to revoke it, so you can withdraw the permission from Apps and services in your Microsoft account, or My Apps for work or school accounts).

Google Calendar and Outlook integration is a Premium plan benefit. If your Premium plan ends, the App stops ringing alarms for events from these accounts (the connection is kept and works again when you resubscribe). The Android app only reads calendars synced to your device and never connects to Google or Microsoft directly.

4. Data Protection

The App protects sensitive information such as your calendar events and sign-in credentials as follows.

• No servers of ours: Your calendar events, connected accounts and authentication tokens are never sent to our servers, and neither we nor our staff can see your events.
• Encryption in transit: Communication with Google and Microsoft goes directly between your device and their servers over HTTPS (TLS). Sign-in uses OAuth 2.0 (authorization code with PKCE) on Google's or Microsoft's own sign-in page, so the App never receives your password.
• Least privilege: The App requests read-only access to your calendars and never asks for write access.
• Protection at rest: Event data is processed in memory to schedule and show alarms and is never written to the App's files or databases. Alarm notifications are scheduled with the iOS notification system and disappear once they fire or are rescheduled. Authentication tokens are stored in the iOS Keychain, which is encrypted by the operating system, inaccessible to other apps, and kept on this device only (not included in backups or moved to other devices). Settings are stored in the App's own storage area provided by the OS, which other apps cannot read.
• Retention and deletion: Events are re-read each time you open the App or a background refresh runs, and are not retained. Tokens are kept in the Keychain until you disconnect the account in the Calendar tab, which deletes the token from your device and, for Google accounts, also asks Google to revoke it. Because Keychain items may remain on the device after the App is uninstalled, we recommend disconnecting before deleting the App (the App also deletes tokens left by a previous installation on its first launch). You can also revoke access at any time from your Google Account's third-party access settings.
• Incidents: Should we become aware of a security incident affecting your data (such as unauthorized access or a leak), we will post a notice on this page and notify affected users promptly.

5. Advertising

The App shows banner ads at the top of the Home screen through Pangle (an advertising platform operated by Bytedance). Pangle's ad SDK starts only after you have answered the ad choice described in "5-1. Your Ad Choice and Tracking", and may then collect the following information and share it with advertising partners taking part in bidding, for ad delivery, measurement, analytics and fraud prevention. Until you answer, the ad SDK collects nothing and no ads are requested.

• Device identifiers (the advertising ID on Android; the IDFA on iOS, only if you allow it in App Tracking Transparency)
• IP address and the approximate location derived from it (country, region or city level)
• Device information such as model, OS version and language settings
• Interactions with ads, such as views and taps
• Diagnostic information such as crashes and performance

The contents of your calendar events are never passed to the ad SDK. For details, see the Pangle End User Data Privacy Policy. After purchasing the Premium plan, no ads are shown and the ad SDK does not start.

5-1. Your Ad Choice and Tracking

After you finish the initial setup (onboarding), the App asks whether it may show ads based on your interests (personalized ads). How it asks depends on the platform.

• Android: you choose "Allow" or "Don't allow" on a screen in the App.
• iOS: the App asks through the system App Tracking Transparency (ATT) prompt only (no screen of its own). If you allow tracking in ATT, personalized ads are enabled; if you don't, it is treated as "Don't allow".

• Until you answer: the ad SDK does not start and no ads are requested.
• If you allow: ads, including personalized ads, are shown.
• If you don't allow: ads are still shown but are not personalized (the App tells Pangle that you have not consented to personalized ads).

After you answer, you can change this choice at any time from "Ad settings" in the App's Settings, and the change takes effect immediately. In regions where consent is required by law, such as the European Economic Area and the United Kingdom, the App asks for your consent in this way and passes it to Pangle.

On iOS, the IDFA is used only if you allow it in ATT; you can change this in Settings > Privacy & Security > Tracking. On Android, you can reset or delete your advertising ID from the "Ads" item in your device's Settings app (Google ad settings).

5-2. In-App Purchases

The iOS app (version 6.0 and later) offers a monthly subscription (the Premium plan) that removes ads and adds Google Calendar integration (the Android app does not offer it at this time). Payments are processed by Apple (App Store) or Google (Google Play); the developer never handles your payment card details. Purchase status is verified through StoreKit / Google Play Billing Library, and only the result (whether you have an active purchase) is cached on your device.

6. Sharing with Third Parties

Apart from the advertising service described above (Pangle), the App does not share or sell your information to third parties (communication with Google Calendar and Outlook only reads events from the account you connected and is not a disclosure of your information). Requests to access or delete data collected by Pangle can be made to Pangle through the contact listed in the Pangle End User Data Privacy Policy.

7. Children's Privacy

The App is not directed to children under 13. We do not knowingly collect personal information from children under 13.

8. Changes to This Policy

This Privacy Policy may be updated without prior notice. Any changes will be published on this page.

9. Contact

For a per-item list of what the App handles, why, where it is kept, for how long and how to stop it, see How We Handle Your Information. For a list of the information the App sends from your device, see Information Sent from the App.

For privacy-related questions, please reach us through the support page.