Privacy notice
A journal should not become a surveillance system.
This notice explains what Dayloom can collect, why it is used, where it is processed, and the controls available to you. The product is designed to remain useful in Local Private mode without an account.
Effective 3 October 2026 · Version 1.0
1. Scope and product boundary
Dayloom is an adult personal-reflection application that turns user-approved signals into evidence-linked visual summaries. It is not a medical device, clinical service, public social network, advertising profile, or emergency service.
2. Data you choose to provide
- Manual text, mood, voice, and photo moments.
- Optional activity, health, calendar, coarse location, music, and weather context from sources you connect. Precise location and timestamps for walks or runs you explicitly start recording.
- Corrections, exclusions, visual preferences, consent choices, privacy zones, notification settings, and support requests.
- Account identifiers, encrypted sync objects, entitlement state, and content-free diagnostics when those features are enabled.
Dayloom does not scrape private messages or call logs, perform face recognition, start covert/random recording, or automatically post on your behalf.
3. Purposes
Data is used only to provide capture, personal-day organization, evidence review, canvas generation, private sync, export, deletion, purchases, fraud prevention, reliability, and support. Health or mood context is not used for diagnosis, employment, insurance, credit, or targeted advertising.
4. Processing choices
Local Private
Journal content and generated canvases stay in an encrypted SQLCipher database on your device. The database key is held by the operating system’s protected credential store.
Cloud Private
If enabled and selected for a specific job, Dayloom sends a minimized, consented evidence set to the configured private-generation service. Media paths and excluded evidence are not sent. This mode remains unavailable until its provider and contractual privacy controls are approved.
Encrypted sync
Optional sync encrypts payloads and media on your device before upload. The service stores ciphertext and cannot recover a lost recovery secret for you.
5. Permissions and sensors
Permissions are requested incrementally after a plain-language value preview. Denial does not block manual journaling. Voice capture requires an explicit foreground action and visible timer. Optional journey recording requests precise location only after you choose to start. An Android location foreground service keeps a visible recording notification and can continue the active journey while the screen is off. Pause stops location collection; Stop ends recording. Dayloom does not request always-on background location access or start journeys automatically. Route samples remain encrypted on your device and are excluded from cloud generation and sync. You can delete a saved journey. A private archive export may include its full route; optional route-image sharing first shows a preview with private edges removed and warns that the remaining shape may reveal where you went. Optional online maps send tile requests to the disclosed map provider only after you choose to load them. Daily reminders require notification permission and can be disabled; denying notifications or location does not block manual notes.
6. Service providers
Depending on the features you activate, Dayloom may use Apple and Google platform services, Firebase, Vercel hosting, RevenueCat, Sentry, Spotify, a coarse-weather provider, and an approved generation provider. Providers receive only the data required for their function and are configured separately by environment. Only providers needed for an enabled feature receive its data; unavailable integrations do not receive journal content.
7. Telemetry
Analytics and crash reporting are off before consent. If enabled, Dayloom uses a strict event-and-field allowlist. Journal text, prompts, health values, precise location, media, tokens, receipts, and private URLs must never enter analytics or diagnostic payloads.
8. Retention and deletion
Local content remains until you delete it or erase the app’s data. Expired raw signals, tombstones, and local audit records receive bounded maintenance. Account deletion initiates removal of authentication, structured cloud data, encrypted media, provider tokens, and entitlement mirrors; see the deletion page for the current process. Legal, security, fraud, or transaction records may be retained only when required and for a documented period.
9. Your controls and rights
You can inspect evidence, correct or exclude moments, disconnect a source, delete imported data, export a portable archive, disable telemetry, revoke consent, remain local-only, or request account deletion. Applicable law may also provide access, correction, portability, restriction, objection, grievance, appeal, and complaint rights.
10. Security and limits
Dayloom uses encrypted local storage, platform credential protection, authenticated encryption for sync, owner-only authorization rules, least-privilege provider access, and privacy-safe logs. No system can guarantee absolute security. Keep your device, recovery material, and account credentials protected.
11. Age and regional availability
Dayloom is intended for people aged 18 and older. Features involving ambient prompts or sensitive sources may be disabled by region until recording, privacy, and consumer-law requirements are approved.
12. Changes and contact
Last updated: 12 October 2026. This update explains user-started route recording and optional reminders.
Material changes will use a new notice version and, when required, renewed consent. Contact everydaylabstop@gmail.com for support and privacy requests, or use the support page or the in-app Privacy Center. Dayloom is operated by Repping Labs LLC, 30 N Gould St, Sheridan, WY 82801-6317, United States. Send privacy requests or unresolved complaints to the same email address. We verify account ownership before acting on requests and respond within applicable legal deadlines.