Today and Updates can show status-only reminders after sign-in.
Reminders should be useful and private.
UYB notifications are designed to point users back to the app without exposing private journal text.
Know who gets nudged before you turn anything on.
Use this quick receipt before changing settings. It separates reminders for you, updates for the other person, and anything that should stay completely private.
This choice receipt changes navigation only. It does not turn on alerts, send a reminder, email the other person, request device permission, subscribe anyone, read private writing, or prove provider delivery.
Reminders can be tested before you rely on them.
In-app updates are ready, device alerts still need permission, and email reminders can be tested from the signed-in Updates page.
Phone or browser alerts work only after the user allows them.
Email reminders still need a private test before anyone depends on them.
Newsletters and product messages use separate consent from journal reminders.
- Step 1send a private test update
- Step 2check the message has no private writing
- Step 3keep unsubscribe and settings visible
This reliability receipt is a status guide only. It does not turn on reminders, request device permission, send email, subscribe anyone, expose private writing, or prove delivery without a test.
A reminder should never make the moment heavier.
Use this receipt before choosing alerts. UYB reminders should return you to the right room, stay private, and stay easy to change.
Users choose in-app, device, email, and product email paths separately.
Messages point back to UYB instead of carrying answer, draft, reveal, solo note, or reflection text.
Reminder language should avoid blame, urgency, streak pressure, and relationship scoring.
Profile, Updates, device settings, and unsubscribe paths keep control visible.
This safety receipt does not turn on reminders, send a test, subscribe anyone, prove email delivery, replace device permission, change reveal rules, or expose private writing.
Choose how loudly UYB should bring you back.
Reminder pace lets your side choose Quiet, Gentle, or Steady without changing reveal rules, sending anything by itself, or telling the other person.
Useful when you want UYB to stay out of the way unless something really needs you.
A balanced default for returning to journals without pressure, blame, or streaks.
Helpful when you want journal status easier to notice while still keeping private text out.
Reminder pace explains tone and visibility only. It does not send a reminder, turn on email, request device permission, reveal writing, notify the other person, publish profile choices, or prove provider delivery.
Choose what you need from reminders.
Start with the reason you came here. UYB will point you to the safest next room without exposing private journal text.
This guide changes navigation only. It does not send a reminder, change consent, expose private writing, subscribe anyone, publish profile choices, or prove email delivery before the provider is connected.
Notification receipt.
Use this receipt to see what can reach you, what stays private, and what still needs permission or provider setup before reminders are dependable.
Today and Updates can show journal status without exposing private writing.
Phone or browser alerts need the user to allow them before UYB can nudge the device.
Email reminders need the production provider key and verified sender before broad use.
Newsletters and product notes stay separate from private journal reminders.
The notification receipt explains reachability only. It does not send reminders, reveal private writing, include answers in messages, share invite links, publish profile choices, or prove email delivery before the provider is connected.
In-app updates.
UYB can show private updates for journal events such as a joined invite, a started question, or a ready reveal.
Email reminders.
Users can opt into email reminders from Profile and choose which journal events can email them. Reminder emails should never include private journal answers, drafts, or reflections.
Device alerts.
Supported browsers can show local device alerts after the user allows them. Users can block alerts in browser or device settings.
Marketing messages.
Newsletters and product marketing should use a separate opt-in from journal reminders, with unsubscribe controls and no private journal content.
Know what can reach you today.
UYB separates working in-app status from device permission, journal email setup, and product newsletters so users know what is live and what still needs consent or provider setup.
Today and Updates can show private status after a journal event.
Phone or browser alerts require install support and explicit permission first.
Email reminders can send only after the production provider key and verified sender are connected.
Product emails are separate from journal reminders and can be unsubscribed.
- Choose settingsUsers choose in-app, device, journal email, and marketing preferences in Profile.
- Send a testUse a private test update before relying on any notification path.
- Confirm providerProduction email needs a non-empty Resend key and verified UYB sender before broad use.
Delivery readiness explains channels only. It does not send reminders, expose private answers, include reveal text, share invite links, publish profile choices, or prove email delivery before the provider is connected.
What UYB may notify about.
Open the journal to see the next safe step.
Write your side, continue a draft, or let it rest.
The reveal is ready inside the journal, never inside the notification.
Gentle nudges stay focused on status and next action.
How users stay in control.
- In-app updatesKeep useful journal status inside UYB.
- Device alertsAllow browser alerts only if you want phone-level reminders.
- Email remindersOpt into specific journal events from Profile.
- Test updateSend a private test update before relying on reminders.
What a safe reminder can say.
UYB reminders should feel human and useful without revealing what anyone wrote. The message can name the status, the next room, and the amount of pressure.
Someone joined the private journal. Open UYB to choose your next step.
Come back when you have space. Your draft stays private.
Your side is saved. UYB will keep the next step clear when the other person is ready.
Read slowly when the moment feels right. The notification does not include the reveal.
A reminder must not include private answers, solo notes, draft text, reveal text, reflection text, or another person's words.
When UYB should reach out.
A good reminder protects attention. UYB should send a nudge only when there is a real next step, and it should stay quiet when pressure would make the moment worse.
Confirm the private journal exists and show the share link or first writing step.
Tell the creator the journal is active and point both people to the same guided question.
Let the writer know their side is safe. Avoid pushing the other person too quickly.
Send a soft return reminder only if the user opted in and the journal still needs attention.
Bring the reveal forward without putting any reveal text in the notification.
Notification cadence is about status and consent. It must never expose private answers, draft text, solo notes, reveal text, reflections, or another person's words.
How a UYB update moves.
Updates should help someone return to the right place without exposing what anyone wrote.
- Something changes
A person joins, a question starts, a draft waits, or both sides save.
- UYB writes status only
The update names the next action, not the private answer.
- Your settings decide delivery
In-app updates, device alerts, and email reminders follow the choices saved in Profile.
- You return to the app
The update opens Today, the journal, or the reveal so the private content stays inside UYB.
Notifications must never include private journal answers, solo notes, drafts, reveal text, or reflections.