Product feedback
Send product feedbackUse this for confusing screens, unclear wording, bugs, mobile friction, or what felt useful.
Choose route
Choose feedback path.
Pick the closest path before typing so private writing, account requests, privacy questions, and safety concerns do not land in the wrong place.
ProductProduct feedbackUse this for confusing screens, unclear copy, mobile polish, bugs, or moments that felt safer than texting.AccountAccount helpUse this for sign-in, exports, deletion, correction, shared links, or finding journals.Q&APublic Q&A ideaUse this for reviewed product questions that could help other people without sharing a private story.PrivacyPrivacy questionUse this for privacy, terms, cookies, notifications, consent, retention, export, deletion, or marketing questions.SafetySafety concernUse this for product safety wording, consent boundaries, pressure, trusted-adult guidance, or knowing when to pause.
safe context onlyprivate writing stays outaccount actions need verificationreal help first for danger
The path chooser changes the form guidance only. It does not start live support, prove legal review, verify an account, send an emergency alert, or review private journal content.
Support routing
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.
Account or sign-in help
Start account requestUse support when sign-in, exports, deletion, shared links, or finding your journals feels unclear.
Safety concern
Review safety routeUse real-world help right away if someone may be unsafe. UYB is not emergency support.
Privacy or legal
Ask privacy questionUse privacy, terms, cookies, and notifications pages for data, consent, and product boundary questions.
Launch tester report
Review launch checksUse this when feedback came from a real test session and needs triage before it becomes product work.
Do not send private journal answers, drafts, reveal text, or another person's writing through support or feedback.
Before you send
Send feedback without sending private writing.
Useful product feedback names the moment, the friction, and the next thing you expected, without copying private journal text.
- RemoveLeave out private words
Do not paste journal answers, drafts, reveals, solo notes, invite links, or another person's writing.
- NameName the screen or step
Tell us where you were, what button you tapped, or what you expected to happen.
- ImpactSay how it felt
Confusing, too much scrolling, unclear status, safer than texting, or not ready yet are all useful signals.
- RouteUse the right path
Product feedback, account requests, privacy questions, and safety concerns need different handling.
I only saw a share link and did not know I could write first.The answer helper inserted text below where I was typing.I wanted to know if the other person had saved their side.
Feedback is not emergency support, live chat, therapy, or account verification. If someone may be unsafe, use real help first.
Try: I was on [screen], I expected [action], but [result] happened on [device].
Tester report
Make a tester report useful.
When a tester says the app felt unclear, the strongest report names the screen, expected action, actual result, and device context.
Name the page or step, such as Journal home, Start a question, Reveal, Profile, or Updates.
Say the action you expected after tapping, saving, signing in, sharing, or returning.
Describe the visible result, missing status, scroll problem, lost draft, confusing wording, or dead end.
Include phone model if known, browser, screen size feeling, and whether you were signed in.
BlockedI could not finish the task.ConfusedI finished, but I did not understand the flow.PolishIt worked, but it felt rough, crowded, slow, or visually unclear.
Do not include journal answers, drafts, reveal text, invite links, screenshots with private writing, or another person's words.
Mobile tester pass
Run a mobile tester pass without collecting private writing.
Give testers a small set of flows and ask for safe observations. The goal is to learn where the app loses clarity, trust, or momentum on a phone.
First startStart from the public site, sign in or sign up, and choose a profile guide.
/start-here, /sign-up, /profileTester can explain what UYB is for, what stays private, and what to do first.
Create and writeCreate a journal, write before or after sharing, and identify the invite step.
/pair/new, /dashboard, /pair/[inviteCode]Tester understands that the link invites the other person and the answer stays private until reveal.
Return and recoverReload or leave the page, then find the draft, waiting state, or next action.
/dashboard, /journeys, /updatesTester can return without founder help and without losing trust in saved writing.
Private safetyUse private writing or vent space, then find help without sharing private text.
/solo, /vent, /safety, /supportTester knows private writing is not sent, scored, monitored, or copied into support.
- route or screen name
- device and browser
- expected next action
- actual visible result
- safe screenshot description
- severity: blocked, confused, or polish
- journal answers
- draft text
- solo notes
- vent text
- reveal text
- invite links
- passwords or one-time codes
- real names or private family details
tester reached first saved answertester found the return pathtester understood reveal timingtester found safety or support without private text
Mobile tester notes are product evidence, not customer support records. Store safe observations only, and turn accepted issues into bounded work after triage.
Fix retest
Retest the fixes that used to confuse people.
These checks turn the original tester confusion into simple mobile tasks. A pass means the tester can explain the screen without founder help.
Shared inviteSign in after someone shares a UYB link, then find where to paste or open the shared journal.
/dashboardTester can find the invite path, knows no answer opened, and knows the next step is a shared question.
Before questionCreate a journal and stop on the journal home before the other person joins.
/pair/[inviteCode]Tester understands that the invite link comes first and the question appears after the journal is ready.
Write firstStart the first guided question and save your side before the other person answers.
/pair/[inviteCode]/question/newTester knows their writing is private, the reveal is locked, and waiting does not mean they did anything wrong.
Phone interruptionType a short safe placeholder, leave or reload the page, then return to the same writing room.
/pair/[inviteCode]/question/[sessionId]Tester can see the restored draft or saved state and does not have to scroll around to understand the next action.
- tester found the right screen
- tester named the next action
- tester understood what stayed private
- tester could pause without pressure
- real journal answers
- draft text
- invite links
- reveal text
- names of the other person
- screenshots with private writing
A retest note should describe product clarity only. It should not store private writing, invite links, real relationship details, screenshots with private text, or customer account secrets.