Essential account cookies.
UYB uses authentication cookies through its sign-in provider so users can create accounts, stay signed in, and access private journals.
This page describes essential cookies and device storage in plain language. It should be reviewed before broad public launch.
UYB uses authentication cookies through its sign-in provider so users can create accounts, stay signed in, and access private journals.
UYB can save unfinished writing and profile edits on the device so a call, reload, or connection loss is less likely to wipe the user's work.
UYB may remember local notification setup and delivered in-app notification IDs so the app does not repeat the same alert.
UYB should not add marketing or analytics cookies without a clear consent plan, privacy review, and user-facing controls.
A quick read of what this device may remember and what stays out of tracking.
Essential storage helps UYB remember sign-in, saved drafts, profile edits, and app setup on this device.
Product analytics and marketing storage stay off unless you allow them. You can change the choice on this device.
Journal answers, drafts, reveal text, invite links, names, emails, and comfort notes are not cookie or analytics data.
Clearing browser storage resets cookie choices and device-only recovery. It does not change journal privacy rules.
Cookie choices help the app remember safe settings. They must not be used to read, score, summarize, train on, or market from private journal content.
Start with the closest need. These choices are about device storage and optional tracking, not private journal content.
Sign-in, draft recovery, offline shell behavior, and profile edits need essential storage.
Always onOptional analytics can help find stuck screens without using private answers or reveal text.
OptionalMarketing storage stays off unless you choose it and must never include private journal content.
OptionalClearing browser storage resets cookie choices, local drafts, and device-only app setup.
Device onlyCookie choices must not expose journal answers, drafts, solo notes, reveal text, invite links, account secrets, or another person's private writing.
The cookie panel lets you save essential-only or optional storage choices on this device. Optional choices do not turn on private journal tracking.
Keeps sign-in, saved drafts, app setup, and private journal recovery working.
Would help UYB understand broken flows without using private journal text.
Would require separate consent and must never include private journal content.
Current storage key: uyb:v1:cookie-preferences. Clearing browser storage resets this choice.
The controls include Allow product analytics for safe product-status events only. Safe analytics events use route groups, status labels, and device class without private writing.
If UYB turns on optional product analytics later, the event map must stay small, consent-based, and useful for fixing broken flows.
Route group, device type, and whether a screen loaded. Do not store invite codes, journal IDs, names, or answer text.
Save success, validation state, draft restored, reveal ready, or invite copied. Keep it to status labels, not the private words.
Consent state, reminder kind, theme choice, guide style, or support mode. Do not record focus notes or comfort notes.
Page load failure, save error kind, offline state, or notification delivery state. Do not include private form values.
Only these product events should be considered after explicit analytics consent. New event families need review before they ship.
public_route_viewednavigationroute_group, device_class, signed_in_stateguided_flow_step_seennavigationflow_name, step_id, route_groupdraft_recovery_statusflow-statusdraft_kind, status, storage_scopejournal_status_changedflow-statusstatus, viewer_role, route_grouppreference_savedpreferencepreference_group, setting_key, setting_statenotification_status_seenpreferencechannel, event_kind, statussafe_error_seenreliabilityerror_area, safe_error_kind, route_groupoffline_recovery_statereliabilitynetwork_state, recovery_surface, route_groupUse short status labels, route groups, and device classes. Never send raw IDs, invite codes, free text, names, emails, or private writing.
Review ruleAny analytics event outside this allowlist should be treated as blocked until privacy and product review approve it.
Optional analytics cannot be used to read, score, summarize, train on, or market from private journal content.