GLANCE Apps

dayGLANCE Privacy Policy

Last updated July 10, 2026

dayGLANCE is a local-first, privacy-first day planner. We do not store your data, collect analytics, or require accounts. This policy explains what data the app accesses, where it goes, and who controls it.

Who we are

GLANCE Apps is an independent software studio publishing applications including dayGLANCE, lifeGLANCE, and lastGLANCE. GLANCE Apps is a Colorado registered trade name of Jason Krellner and is the party responsible for the data practices described in this policy.

This policy covers dayGLANCE specifically. For our publisher-level practices and the glance-apps.com website, see the GLANCE Apps privacy policy.

Data we do not collect

  • We do not collect personal information.
  • We do not use analytics or tracking.
  • We do not have user accounts.
  • We do not store your data on any server we operate. (The web app uses a stateless relay for some traffic, described below; it stores nothing.)

Note for the web app: because browsers block direct cross-origin requests, calendar and WebDAV sync traffic on the web version of dayGLANCE passes through a stateless relay we host. Your server address, your login credentials, and your file contents pass through this relay in transit but are never stored or logged. The native mobile apps and the desktop app connect directly to your servers and do not use any relay.

Data the app accesses

Calendar data (CalDAV / Nextcloud)

dayGLANCE connects to CalDAV-compatible servers (such as Nextcloud) that you configure. Calendar data is stored locally on your device. On the native and desktop apps it is fetched directly from your server. On the web app it is fetched through the stateless relay described above (in transit only, never stored).

Health data (Health Connect and HealthKit)

dayGLANCE may read activity and sleep data (specifically: daily step count and sleep session duration) from Health Connect on Android or HealthKit on iOS, to display progress toward user-configurable daily goals as "habit rings" in the day view. Granting Health Connect or HealthKit permissions is entirely optional; the rest of the app functions normally without them.

Health data is read locally on your device and is never used for analytics, shared with third parties, or written back to Health Connect or HealthKit. If you have enabled optional cloud sync, habit data (including steps and sleep duration) is included in the sync payload. GLANCEvault sync is always end-to-end encrypted; WebDAV sync is encrypted only if you turn on the sync-encryption option (it is off by default), and is otherwise stored on your server as plaintext. Summary statistics about your habits (such as how often a step or sleep goal was met, never raw health measurements) may also be sent to your configured AI provider if you use the optional AI summary features. Health data is never synced to iCloud Drive: in keeping with Apple's requirement that HealthKit data not be stored in iCloud, dayGLANCE excludes all health-derived data from the iCloud sync payload.

Obsidian vault

dayGLANCE can read from and write to your local Obsidian vault. All vault access occurs on-device. No vault content is transmitted to dayGLANCE or any third party.

Note that once you import content from your vault, imported daily notes and note-derived tasks become part of your dayGLANCE data. Like your other tasks and notes, they are then included in cloud sync, in prompts sent to your AI provider, and in TRMNL display pushes, if and only if you enable those optional features.

Cloud sync and remote backup

dayGLANCE supports optional cloud sync and remote backup to destinations you configure: GLANCEvault, a WebDAV-compatible server (such as Nextcloud), or iCloud Drive. Each uses a different encryption model, described below.

GLANCEvault: your data is always encrypted client-side before leaving your device using AES-256-GCM, with keys derived from a sync passphrase you choose via PBKDF2 (310,000 iterations). The server stores encrypted content only. It does, however, see limited metadata it needs to route and merge changes: labels identifying each item's type and id (for example that a daily note exists for a given date), and modification timestamps. It never has access to your item contents, your passphrase, or your encryption key. GLANCEvault is a sync server you run on your own infrastructure; GLANCE Apps does not operate any GLANCEvault instance and has no access to its contents.

WebDAV-compatible servers (such as Nextcloud): client-side encryption is optional and off by default. When you enable the sync-encryption option, files are encrypted with AES-256-GCM using a passphrase-derived key (PBKDF2, 310,000 iterations) before upload, and the server stores only ciphertext. If you do not enable it, your data is stored on your WebDAV server as plaintext, protected only by that server's own access controls and transport security.

iCloud Drive: if you choose iCloud Drive, your files are stored in your personal iCloud account and protected by Apple's standard encryption. This path does not use the app's passphrase-derived encryption described above. Apple's privacy policy governs data stored in iCloud.

Your passphrase is never stored anywhere. So that you are not prompted on every launch, the derived key is cached locally on your device: on Android it is held in the hardware-backed Android Keystore, and on iOS, macOS, and the web app it is stored in the app's sandboxed local storage. If you forget your passphrase, your encrypted data cannot be recovered. This is by design.

Shared member names: if you enable multi-user mode, the display names of household members are stored in a small shared file on your sync destination so that other GLANCE apps you use can recognize the same members. This file currently stores member display names in plain text even when sync encryption is enabled. It lives only on the destination you control and is never sent to us.

If you use multi-user mode with sync encryption and opt in to syncing calendar credentials, the usernames and app passwords for your configured calendar servers are included (encrypted) in the sync payload so your other devices can connect without re-entering them.

GLANCEintents cross-app integration

dayGLANCE optionally communicates with other GLANCE Apps (such as lastGLANCE) through a cross-app protocol called GLANCEintents. When enabled, dayGLANCE reads and writes small event files containing task metadata (such as task title, due date, and a source identifier from the originating app) to the sync destinations you enable for it: your WebDAV server, iCloud Drive (on Apple platforms), and/or your GLANCEvault server. These files allow other GLANCE Apps you use to receive the same data. For example, a chore you log in lastGLANCE can appear as a scheduled task in dayGLANCE, and completing it in dayGLANCE can be reflected back in lastGLANCE.

GLANCEintents is opt-in and off by default. Event files can optionally be encrypted using the same passphrase-derived encryption model described in the Cloud Sync section above. When encryption is enabled, event contents are encrypted, though a small routing header (the originating app, the source item id, and the due date) remains readable to the storage destination. Event files are written to and read from your own WebDAV server, iCloud Drive, or GLANCEvault instance only. They are never transmitted to dayGLANCE servers (we do not operate any) or to any third party. The GLANCEintents protocol specification is publicly available at github.com/glance-apps/glance-intents.

AI features

Beyond voice input, dayGLANCE offers several optional AI-assisted features, including daily and weekly summaries, an evening reflection, smart scheduling and rescheduling suggestions, focus-block nudges, subtask generation, and task suggestions. When you use these features, dayGLANCE sends relevant planning data to the AI provider you have configured. Depending on the feature, this can include task titles, dates, times, durations, priorities, deadlines, and tags; calendar event titles and times; habit, goal, and project names and progress; and, for subtask generation, the task's notes. Raw daily-note text is not sent. The focus-block nudge may send this data automatically when you open a focus block, rather than only on an explicit request. All AI requests go directly from your device to the provider you chose; dayGLANCE operates no AI backend of its own.

dayGLANCE uses your microphone for AI-powered voice task input: you can speak to create, move, reschedule, or edit tasks. Audio is processed as follows:

  • Cloud AI providers: If you configure a cloud-based AI provider, your audio is sent to that provider for transcription, and the resulting text is sent together with context about your existing tasks so the assistant can act on your request. You are responsible for reviewing that provider's privacy policy. dayGLANCE does not control how third-party AI providers handle your data.
  • Local AI: If you configure a local AI instance, audio processing occurs entirely on your device or local network. No data is sent externally.

The choice of AI provider is yours. dayGLANCE is a bring-your-own-AI (BYOAI) application and does not provide or operate any AI backend. AI features are not available in all countries.

Third-party services

dayGLANCE does not integrate with any third-party analytics, advertising, or data brokers. The only third-party services involved are those you configure yourself:

  • Your CalDAV / Nextcloud calendar server
  • Your WebDAV / Nextcloud sync server
  • A GLANCEvault instance you self-host
  • iCloud Drive (protected by Apple's standard encryption)
  • Your AI provider (cloud or local)
  • Apple App Store or Google Play (purchase verification)
  • RevenueCat (subscription entitlement management, on Apple platforms only)
  • TRMNL (only if you enable the TRMNL display feature): dayGLANCE pushes a compact agenda (task titles, times, habit names, and a short daily-note excerpt) to the TRMNL webhook you configure, on a periodic schedule while enabled
  • Weather providers (only if you enable weather): to show local weather, dayGLANCE sends your postal code, place name, or approximate coordinates to public weather and geocoding services (such as open-meteo.com)
  • GitHub (api.github.com): the app checks for new releases on some platforms; no personal data is sent
  • Optional daily-content services (such as a fact or joke of the day), if enabled; no personal data is sent

Payments and subscriptions

dayGLANCE offers optional subscriptions and one-time purchases. On Android these are processed entirely by Google Play; on iOS and macOS they are processed entirely by the Apple App Store. We do not collect, see, or store your payment information. The relevant store may share a purchase token with the app solely to verify your subscription status; this token is used on your device and is not transmitted to dayGLANCE servers (there are none). The applicable store's privacy policy governs all payment processing.

On Apple platforms (iOS and macOS), dayGLANCE uses RevenueCat to manage subscription entitlements. RevenueCat receives an anonymized app-user identifier and your Apple purchase receipt, from which it determines your entitlement status. On Android, subscriptions are handled entirely on-device through Google Play and RevenueCat is not used. RevenueCat does not receive your name, your app content, or other personally identifying information. RevenueCat's privacy policy governs its handling of this data.

Children's privacy

Our Apps are not directed at children under 13. We do not knowingly collect information from children.

Changes to this policy

If this policy changes materially, we will update the "Last updated" date above and note the change in the app's release notes.

Contact

Questions about our privacy practices? We're happy to answer them.

privacy@glance-apps.com