Support

Choose the safest path for the help you need.

UYB support starts with routing. Product feedback, account requests, safety concerns, and privacy questions should not ask you to share private writing.

Send feedback Read help

Support by person

Start with who you are right now.

Pick the lane that feels closest. UYB should make support feel plain whether you are ten, forty, worried, locked out, or just confused.

KidI need simple words

Use kid-safe help when you feel stuck, pressured, unsure, or need a trusted grown-up.

Open kid helpTeenI need this to feel less awkward

Use teen help for plain language, privacy, pausing, safety, and what to do when sharing feels too much.

Open teen helpParentI want to understand the boundaries

Use parent help for safety, privacy, consent, kid-friendly language, and what UYB can and cannot do.

Open parent helpPartnerI need the next relationship step

Use relationship help when the journal, invite, answer status, waiting, or reveal flow feels unclear.

Open flow helpAccountI cannot sign in or find my data

Use account support for sign-in, shared links, deletion, correction, export, or profile questions.

Start account helpSafetySomeone may be unsafe

Leave the app and use emergency, crisis, local, or trusted adult help first if there is danger.

Use real help

kid-safe pathadult-clear pathaccount pathreal help firstno private writing

The audience guide routes you only. It does not collect age, verify identity, start live chat, notify anyone, replace trusted adults, or ask for private journal writing.

Support first choice

Choose what kind of help you need first.

Start with the closest safe path. UYB should not need private journal writing to help you move to the right room.

ConfusedSomething in the app did not make sense

Report the screen, device, expected action, and what felt unclear.

Send product feedbackAccountI need help with sign-in or data

Use account support for sign-in, exports, deletion, correction, or shared-link access.

Start account requestPrivacyI have a data or consent question

Read privacy, cookies, notifications, and terms before sending a safe question.

Review privacyUnsafeSomeone may be unsafe

Leave UYB for emergency, crisis, trusted adult, or local support when there is danger.

Use real helpLostI just need the next step

Open Help for invites, writing, waiting, reveals, private spaces, and plain words.

Open help

choose before sharingsafe details onlyprivate writing stays outreal help first

This support choice guide routes you only. It does not send a message, start live chat, verify account ownership, provide legal advice, provide therapy, monitor crisis, or store private journal writing.

Support receipt

Support receipt.

Support should help you choose the right path before you share anything. It should use safe details, protect private writing, and show what happens next.

PathChoose first

Pick product feedback, account help, privacy, safety, or launch tester reporting.

Safe detailScreen and device

Share the screen, device, request type, and what looked wrong without quoting private writing.

NextRight owner

Product notes go to triage, account requests need verification, and safety concerns use real help first.

PrivacyPrivate words stay out

Support should never ask for journal answers, drafts, reveal text, solo notes, invite links, passwords, or codes.

safe details onlyno private writingidentity check for account actionsreal help first for danger

The support receipt can explain routing and safe evidence. It does not prove live chat, therapy, crisis monitoring, legal advice, account ownership, or emergency response.

Support promise receipt

Support can route the next step, not replace real help.

Use this receipt before you send anything. It separates what UYB can safely route from what still needs identity checks, human ownership, or real-world support.

Routesend safe notes to the right path

Product feedback, account requests, privacy questions, safety guidance, and tester reports each have a different path.

Protectkeep private writing out

Support needs screen names, devices, request types, and safe summaries, not journal text.

Explainshow what happens next

Account actions need identity checks, safety concerns need real help first, and product feedback goes to triage.

not live chatnot crisis monitoringnot legal advicenot account proof by itself

safe summaries onlyidentity checks stay separatereal help firstno private journal text

This support promise does not prove live coverage, emergency response, legal approval, account ownership, export, deletion, correction, sign-in recovery, or broad launch readiness.

Start here

Support should be clear before you share anything.

Start by choosing the request type. UYB support should help with the product, account access, privacy questions, and launch feedback without asking for private writing.

Keep private writing out of support.Do not send private journal answers, drafts, reveal text, or another person's writing through support or feedback.Use support without private journal text, journal answers, drafts, reveal text, or solo notes.

Choose the path

Pick product feedback, account help, safety, privacy, or launch tester reporting.

Send safe details

Share the screen, device, account marker, or request type. Leave out private answers and reveal text.

Wait for the right follow-up

Sensitive account requests should require identity verification before support changes or exports anything.

Use real help for danger

If someone may be unsafe, pause UYB and use emergency, crisis, or trusted adult support first.

Find the path

Pick the sentence that matches you.

Use the closest match. Support should move you to the right place without asking for private journal text.

I cannot find somethingFind my journal or account path

Use this when sign-in, shared links, journals, or account access feels unclear.

Open pathThe app felt confusingReport product friction

Use this when a screen, button, status, or mobile flow did not make sense.

Open pathI have a privacy questionCheck data and consent

Use this for privacy, cookies, notifications, exports, deletion, and account data.

Open pathSomeone may be unsafeUse real help first

Use this when the moment involves danger, pressure, self-harm, abuse, or urgent safety.

Open path

Do not include journal answers, drafts, reveal text, invite links, passwords, one-time codes, or another person's private writing.

Routes

Choose the right support path.

UYB separates product feedback, safety resources, account help, and privacy questions so people do not have to guess where sensitive notes belong.

Product feedbackSend product feedback

Use this for confusing screens, unclear wording, bugs, mobile friction, or what felt useful.

Account or sign-in helpStart account request

Use support when sign-in, exports, deletion, shared links, or finding your journals feels unclear.

Safety concernReview safety route

Use real-world help right away if someone may be unsafe. UYB is not emergency support.

Privacy or legalAsk privacy question

Use privacy, terms, cookies, and notifications pages for data, consent, and product boundary questions.

Launch tester reportReview launch checks

Use this when feedback came from a real test session and needs triage before it becomes product work.

Support is not live chat, therapy, crisis monitoring, legal advice, medical advice, or a place to paste private journal text.

Response expectations

What to expect after you ask for help.

Different requests need different handling. UYB should keep the next step visible so people are not left guessing.

Product feedbackReviewed for patterns

Useful notes may become fixes, clearer copy, or tester packets. They may not receive a personal reply.

Account requestNeeds verification

Exports, deletion, correction, and sign-in issues should verify the requester before sensitive action.

Privacy or legalHandled carefully

Privacy questions should route to the public privacy, terms, cookies, and notification pages first.

Safety concernUse real help first

UYB can show safety guidance, but it is not emergency support or crisis monitoring.

Never include:journal answersdraft textsolo notesreveal textinvite linkspasswordsone-time codes

Support replies should talk about product steps, account verification, and safe next actions, not ask users to prove a private feeling.

Accountability loop

What happens after feedback.

Feedback should not disappear into a quiet box. UYB turns safe notes into a visible review loop so confusing moments become clearer product work.

ReceiveRead the safe context

Screen name, device, expected action, and what felt confusing are enough.

RouteSend it to the right owner

Product, account, privacy, safety, and launch QA feedback do not belong in the same pile.

DecideFix, clarify, or park it

Accepted issues should become copy updates, UI fixes, tests, evidence, or a clear parked decision.

CloseShow proof without private content

Closure can name the route, fix, status, and test proof without storing journal words.

safe summaries onlyowner and statustest or evidence linkno private writing

The feedback loop can track product confusion and support status. It must not store journal answers, drafts, reveal text, solo notes, invite links, passwords, one-time codes, OAuth tokens, or crisis details.

After you ask

What happens after a support request.

Each request type needs a clear first response, escalation path, and closure proof so people are not left guessing and support does not collect private writing.

Pattern reviewProduct feedback

Review during the next product triage pass.

Escalate when the same confusion appears in tester reports, mobile QA, or live support notes.

Link the accepted issue to a test, evidence note, or parked decision.

Identity requiredAccount request

Confirm the request type, then verify the account before export, deletion, correction, or sign-in action.

Escalate shared-journal, deletion, child-safety, or suspicious access requests to the privacy owner.

Record the request type, verification status, action taken, and safe account marker only.

Careful reviewPrivacy or legal

Point to the public policy page first, then collect only the request type and safe account marker if needed.

Escalate retention, deletion, consent, child, or legal language questions to the privacy review owner.

Record route, policy area, owner, decision, and whether follow-up is needed.

Use real help firstSafety concern

Tell the person to use emergency, crisis, trusted adult, or local support before product troubleshooting.

Escalate only safe category notes and route gaps. Do not store crisis stories or private writing.

Record that real-world help was shown and whether product copy or routing needs review.

Launch QALaunch tester report

Classify as blocked, confused, polish, safety, account, legal, parked, or decision needed.

Escalate blocked flows, private-content risk, auth failures, data loss, and mobile obstruction before broad launch.

Record route, device, expected result, actual result, severity, owner, and proof command.

Safe to record

route or policy page
request type
device and browser
expected result
actual visible result
safe account marker if needed
owner and status

Never record

journal answers
draft text
solo notes
vent text
reveal text
invite links
passwords
one-time codes
OAuth tokens
crisis details

Support operations should prove the request was routed and handled. They must not become a second place to store private writing, account secrets, invite links, or crisis details.

Still unsure where to go?

Start with Help if you are confused, Feedback if the product felt unclear, and Safety if someone may be at risk.

Open help