Privacy Policy

Who operates Daylog

Daylog is operated by Jay Tat.

Data that stays on the device

Guest entries, scores, notes, tags, preferences, and offline account copies are stored on the device. If photo access is allowed, Daylog reads the date and image needed to show photos beside the matching entry; it does not copy or upload the photo library. Widgets receive only a local summary through Daylog's app group.

Data Daylog collects

When an account is created, Daylog processes the email address or Sign in with Apple identity, a Daylog account identifier, and authentication records.

When cloud backup is used, Daylog stores scores, notes, tags, pinned state, entry dates, sync timestamps, versions, and deletion markers.

To provide Daylog Plus, Daylog stores App Store product and transaction identifiers, purchase and expiration dates, subscription status, and the app account token attached to the purchase. A purchase made while signed out uses a random, install-scoped token; it is not an advertising identifier. Daylog never receives payment-card details.

When Daylog communicates with its cloud service, Supabase automatically retains limited request and authentication metadata such as IP address, approximate city or country derived by its network provider, user agent, request time, route, and response status. Daylog uses this metadata only for authentication, rate limiting, abuse prevention, security, and service reliability. It is not used to build a location history, personalize content, advertise, or track activity across other companies' apps or websites.

Service providers

• Apple processes Sign in with Apple and App Store purchases.
• Supabase provides authentication, database storage, cloud functions, and operational security logs, including the limited network and request metadata described above.
• Sentry receives limited crash and diagnostic information so Daylog can identify failures. Sentry is configured not to collect default personal information, screenshots, view hierarchy, breadcrumbs, network request details, or performance traces. Daylog does not intentionally send journal entries, notes, tags, email addresses, or account identifiers to Sentry.

These providers process data only to deliver and protect Daylog under their own security and privacy terms.

Why data is used

Daylog uses collected data only to authenticate accounts, sync requested journal data, verify purchases, provide support, prevent abuse, keep the service reliable, and comply with legal obligations. It is not used for advertising or data-broker profiling.

Retention and deletion

Local guest data remains until it is removed or the app is deleted. Choosing Delete account in Settings permanently removes the active account and sessions, its cloud journal data, stored Apple credential, and Daylog entitlement row. Daylog also removes that account's offline store from the device. Guest entries remain.

Limited security logs and encrypted service backups may persist until the service provider's routine retention cycle expires, after which they are deleted. Diagnostic events remain only for the retention period configured for Daylog's Sentry project.

Deleting an account does not cancel an App Store subscription. Daylog offers a route to Apple's subscription management from the deletion prompt, and the account can still be deleted immediately.

Choices and rights

People using Daylog can:

• export entries as CSV;
• deny or limit photo access;
• use Daylog without an account;
• sign out while retaining the account and its separate offline store; or
• delete the account and cloud data inside Settings.

Email jaytat132@gmail.com for privacy questions, access requests, or deletion help.

Changes

This policy may be updated when Daylog's features or providers change. The effective date above will change when that happens.