GlideNote
Support Privacy Terms

Privacy

GlideNote Privacy Policy

GlideNote keeps your notes and preferences on your Mac and uses only the services needed to sync, improve app stability, and provide optional usage analytics.

Last updated: October 25, 2026

Summary

GlideNote is a lightweight macOS utility for notes and tasks. It stores your app content and preferences on your Mac and, when iCloud sync is enabled and available, syncs note and task data through Apple's iCloud/CloudKit service for app functionality.

GlideNote is also available for iPhone and iPad. This policy applies to that app as well; see GlideNote on iPhone and iPad for what is specific to it.

GlideNote does not sell personal information, does not use advertising SDKs, and does not track you across apps or websites.

Information We Collect or Process

Notes, tasks, and preferences

The app stores the following information so core features work as expected:

  • Notes, tasks, checklist state, and recently deleted state you create in the app
  • Task ordering and selected note/task state
  • iCloud sync preference and local-to-iCloud migration state
  • Display-specific enable/disable preferences
  • Appearance, language, onboarding, and launch-at-login preferences

This data is stored locally on your Mac using system storage such as Core Data and UserDefaults.

iCloud sync data

If iCloud sync is enabled and available on the device, GlideNote syncs note and task data using Apple's iCloud/CloudKit private database infrastructure. This may include note text, task text, checklist state, deletion/restore state, sync metadata, and local-to-iCloud migration markers needed to keep the app's local and iCloud accounts consistent.

GlideNote does not operate a separate server for your note or task content. iCloud data is handled by Apple according to the iCloud account and CloudKit services available on your device. You can turn iCloud sync off in GlideNote settings. If iCloud sync is off or unavailable, the app keeps using local storage on the device.

Pro purchase records

To verify Pro access and help prevent duplicate purchases, GlideNote stores purchase-access records on your device, including product and transaction identifiers, purchase and verification dates, and expiration or revocation status, along with records of unresolved purchase attempts. The access cache uses device-local Keychain storage; purchase-attempt records use the app's local storage. These records are not included in iCloud sync.

An attempt record is cleared when its outcome is confirmed and may remain across relaunches while the outcome is unknown. Reinstalling the app does not guarantee deletion of all local or Keychain records. Transaction identifiers and exact transaction times from these records are not sent in usage analytics events.

Diagnostic information

If the app crashes or crosses stability thresholds, we may receive diagnostic information through Firebase Crashlytics. This may include:

  • Crash logs, stack traces, and relevant application state at the time of a crash
  • Device, OS, app version, and build information
  • Non-content stability diagnostics such as memory bucket, uptime, screen count, notch controller count, lifecycle event name, line counts, checklist counts, and checklist refresh counters

Crash diagnostics are used only to diagnose crashes, investigate performance or stability problems, and improve compatibility. GlideNote does not intentionally send note body text or task body text to Crashlytics.

Optional usage analytics

Only when you choose “Share” in the first-run guide or the in-notch prompt, or turn on “Share app usage data” in GlideNote settings, Firebase Analytics may collect product usage information such as:

  • The type of feature invoked by a button, menu, shortcut, drag and drop, or Spotlight, Siri, and Shortcuts, its surface, input method, and success or failure result (for example, saving a text drop, using task window search, opening a task from a reminder, or copying or deleting a clip card)
  • How often the notch is opened and what opened it (a click, a reminder, onboarding, and so on), and the kind of screen it was opened on (a built-in screen with a notch, a built-in screen, or an external display)
  • Onboarding start, step views, completion, or skip, how it was completed, and the approximate time until the notch is first opened afterward
  • Edit sessions whose content was successfully persisted and whether first value was reached
  • Free/Pro feature-gate reasons with the screen area and input method where a limit was hit, paywall views and closes, the plan type chosen in the paywall (monthly, yearly, or lifetime), and verified Pro purchase, restore, and related commerce outcomes; prices, currencies, and transaction identifiers are not included
  • Your current Free or Pro status, whether your Mac’s built-in screen has a notch, and the language the app is shown in (English, Korean, Japanese, Simplified Chinese, or Traditional Chinese), used to compare analytics between Free and Pro, across Mac types, and across app languages; this does not include the purchased product, price, or expiration date
  • Allowlisted setting-change categories such as iCloud sync, display, or launch-at-login preferences; for notch and text size only whether it was made larger or smaller is sent, not the exact value
  • The kind of iCloud sync warning (for example, iCloud storage full, a network problem, or the iCloud account being unavailable); error messages and record identifiers are not included
  • App version, operating system, device category, an app-instance identifier, and technical app or session information automatically generated by Firebase
  • Your device’s language setting and an approximate country- or region-level location inferred from your IP address, collected automatically by Firebase; precise location is not collected

Usage analytics does not include note or task titles or body text, content length, raw keystrokes, file paths, Apple ID, CloudKit IDs, task UUIDs, or StoreKit transaction IDs. GlideNote does not set an Analytics user ID or link this data to an app account.

Usage analytics is off by default. If you haven’t chosen yet, GlideNote asks once in the first-run guide or an in-notch prompt. It begins only after you explicitly allow it, and you can turn it off at any time in settings. Every feature works the same whether or not you allow it. Turning it off stops future collection and resets the Firebase Analytics identifier state stored on the device.

Website visits (glidenote.app)

When you visit glidenote.app, Cloudflare Web Analytics measures aggregated site traffic, such as page views, referring pages, browser, operating system, device type, country, and page-load performance. It does not use cookies or local storage to identify visitors and is not used to track you across websites. Visiting the website is separate from using the app, and website analytics is not linked to your notes, tasks, or app usage.

When you open a promotional link starting with glidenote.app/go/ or click the App Store button on the website, we record the link's campaign name, the time, country, device type (Mac, iPhone, and so on), the referring page's domain, and whether the request came from an automated link preview in Cloudflare D1, so we can count which promotional channels lead to App Store visits. We do not store IP addresses, raw browser identification strings, or cookies, and we do not link these records to app usage or purchase records.

App Store purchase notifications

When an App Store transaction changes, such as a Pro purchase, subscription renewal, refund, turning off auto-renewal, or expiration, Apple notifies our server through App Store Server Notifications. To understand revenue and subscription retention, GlideNote stores the notification type, product, price and currency, App Store country, and purchase and expiration times in Cloudflare D1, and revenue events are summarized in a developer-only Discord channel. The original transaction identifier is not stored as is; it is replaced with an irreversible value derived with a secret key and used only to group status changes of the same subscription. These notifications do not contain your name, email address, Apple ID, or payment method.

Support information you choose to send

If you choose the in-app bug report action, GlideNote opens Apple Mail with a prefilled draft. The email is sent only if you review it and choose to send it yourself. If you send the email, we receive the email address and support content included in that message.

GlideNote on iPhone and iPad

GlideNote for iOS and iPadOS is a notes and checklist app that uses the same iCloud sync as the Mac app. Everything above about notes, tasks, preferences, and iCloud sync applies to it as well, with your iPhone or iPad as the device. This section covers what is specific to the iOS app.

Reminder notifications

If you turn on “iPhone & Apple Watch Alerts” (on iPad, “iPad Alerts”) in GlideNote settings, the app asks for notification permission and schedules local notifications on the device for the checklist reminder you set up on your Mac. These notifications are created on your device and are not sent by a developer server. When your iPhone is locked and you wear an Apple Watch, iOS may forward the notification to the watch. You can turn alerts off in GlideNote settings or in the Settings app at any time.

Reminder schedule shared through iCloud

To schedule those alerts, GlideNote for Mac stores a small reminder schedule in iCloud Key-Value Store: the identifier of the task being reminded about, the next reminder time, the reminder interval, and whether the reminder is active. It contains no note text or titles. The schedule is stored in your iCloud account and is read only by GlideNote on your devices.

Continue-on-iPhone alert

When you close or lock your Mac and step away, GlideNote for Mac (1.10.1 or later) writes one record to your private CloudKit database containing the task's identifier and title, the time, and what triggered it (for example, lid closed or screen locked). Your iPhone subscribes to this record so that iCloud can deliver a single “Continue on iPhone?” notification. The record holds only the task title, never the note body, and each new record replaces the previous one. This alert follows the same alerts toggle.

Live Activity

When you tap “Continue from Mac” or a reminder notification, GlideNote shows that task on the Lock Screen and in the Dynamic Island as a Live Activity: its title, checklist lines, and progress. The content is rendered on your device from your own notes and is not sent anywhere. The Live Activity ends when the checklist is complete, when you dismiss it, or when iOS ends it.

Background notifications

The iOS app registers for remote notifications only to receive iCloud/CloudKit notifications: silent notifications that let the app sync changes, and the subscription notification for the alert above. GlideNote operates no push server and sends no marketing notifications.

No diagnostics or analytics on iOS

The iOS app does not include Firebase Crashlytics, Firebase Analytics, or any other analytics or advertising SDK. The “Diagnostic information” and “Optional usage analytics” sections above apply to the Mac app only. If you choose the in-app bug report action on iPhone or iPad, the same support email terms apply.

Information We Do Not Collect

GlideNote does not use ad tracking, third-party advertising identifiers, or data brokers, and does not combine behavior across apps or websites for tracking. Optional Firebase Analytics is not used for advertising or personalized marketing.

GlideNote does not require account creation in the app and does not collect passwords, payment information, contacts, calendars, location, camera, microphone, or screen recording data.

How We Use Information

We use local and iCloud-synced app data to:

  • Show your notes and tasks
  • Preserve your app preferences
  • Restore app state between launches
  • Sync notes and tasks across devices that use the same Apple Account, when iCloud sync is enabled

We use crash and diagnostic information only to:

  • Investigate crashes and non-fatal stability problems
  • Improve app reliability, performance, and compatibility

We use usage analytics that you choose to share only to:

  • Improve the usability of core features and onboarding
  • Understand button, menu, and shortcut usage and feature outcomes
  • Identify friction in feature gates and Pro purchase flows
  • Compare usage between Free and Pro and across Mac types, countries, and app languages

We use support information only to:

  • Respond to your support request
  • Reproduce or investigate the issue you reported

Promotional link clicks and App Store purchase notification records are used only to:

  • Compare traffic from promotional channels
  • Understand revenue, free-trial conversion, and subscription cancellation and refund trends

Third-Party Services

  • Apple iCloud/CloudKit: app functionality sync for notes and tasks when iCloud sync is enabled
  • Firebase Crashlytics: crash diagnostics and app stability improvement
  • Firebase Analytics: optional product usage analytics that you explicitly enable
  • Cloudflare Web Analytics: aggregated visit statistics for the glidenote.app website
  • Cloudflare Workers and D1: promotional link redirects and click counts, and processing and storing App Store purchase notifications
  • Discord: receiving purchase notifications in a developer-only channel

Firebase and Google Analytics process diagnostic and optional usage analytics information under their terms, privacy practices, and configured Console data-sharing settings. The current Analytics account permits aggregated participation modeling and business insights, necessary technical-support access, and service recommendations; Analytics sharing for improving Google products and services is disabled.

Data Retention

Local content remains on your device until you delete it, remove the app, or remove the app's local data.

Pro purchase-access records remain on the device as needed to verify access and prevent duplicate purchases. Confirmed purchase-attempt records are cleared; unresolved attempts may remain across relaunches. Removing or reinstalling the app does not guarantee deletion of every local or Keychain purchase record.

iCloud-synced content remains available through iCloud according to your Apple Account, iCloud settings, and app deletion behavior until you delete it or disable/remove the relevant data.

Crash diagnostics are retained only as long as reasonably necessary for debugging and stability analysis.

The current Google Analytics property retains event data for 2 months and user data for 14 months, and resets the user-data retention period when new user activity occurs. These controls may not affect some aggregated standard reports. Turning analytics off stops future collection and resets the on-device Analytics identifier state, but data already transmitted and aggregated may not be deleted retroactively.

Website visit statistics are kept in aggregated form within Cloudflare Web Analytics and are used only to understand overall site traffic and performance.

Promotional link click and App Store purchase notification records are kept in Cloudflare D1 for a reasonable period needed to compare revenue and marketing trends.

Support emails are retained only as long as reasonably necessary to respond to and resolve the support request.

Your Choices

  • Delete notes and tasks inside the app
  • Turn iCloud sync off in GlideNote settings
  • Turn iPhone & Apple Watch Alerts (or iPad Alerts) off in GlideNote settings or in the Settings app
  • Turn Share app usage data on or off from the Support screen in GlideNote settings
  • Manage iCloud data through your Apple Account and iCloud settings
  • Stop using the bug report action
  • Remove the app and its local data from your Mac, iPhone, or iPad

Contact

If you have privacy questions, email oscar08193@gmail.com.

References

  • Apple App Store Review Guidelines
  • Apple App Privacy Details
  • Firebase Apple App Store data disclosure guide
© 2026 GlideNote
한국어 Support Home