← BackPrivacy Policy
You Again is operated by Diverse Innovations Inc. · Last updated October 16, 2026
You Again holds a record of how you answered questions about yourself over time. That is personal, and we treat it that way.
Diverse Innovations Inc. operates You Again. This policy explains what we collect, why, who else sees it, and what you can do about it. We handle personal information in accordance with Canada’s Personal Information Protection and Electronic Documents Act (PIPEDA) and, where they apply to you, the GDPR and UK GDPR.
The short version
We do not sell your information, we do not advertise against it, and nobody else sees your check-ins, journal or chats unless you choose to share a read. There is one exception, and we would rather state it plainly than bury it: if a message in one of the AI chats matches our crisis-language detection, it may be emailed to the operator so a person knows about it. That section is below, and it is worth reading before you use the chats. You can ask us to delete everything at any time.
Questions, requests or complaints: hello@youagain.io
What we collect
Things you give us
- Account information — your email address, and either a password (stored only as a secure hash, never as text we can read) or the fact that you signed in with Google. Optionally a name, used so a read you share can say whose it is.
- Your check-ins — the answers you choose in each check-in and the temperature check at the start.
- Who you want to become — the direction you set, and anything you write about why it matters and by when. We also keep the directions you have set before, and the daily steps and moods you log against them, so you can look back at them.
- Your journal — notes you write, and your saved conversations with the app’s AI (both Reflect and the Assistant), including what you typed and what it replied.
- Voice notes — if you choose to speak instead of type, the recording is sent to our transcription provider, turned into text, and discarded. We do not keep the recording, and the text only goes where you then choose to put it: it appears in the box for you to edit, and nothing is saved or sent until you do.
- Feedback you give or receive — reactions and comments left on a shared read, by you or by other people.
- Support messages — if you use the help button, what you wrote, the email address you gave us for a reply, which page you were on, and your browser and device type. These are saved and emailed to us so we can answer.
- Correspondence — anything you send us by email.
Things produced by your use of the app
- Your results — the trait scores your answers produce, the nickname for the pattern they describe, which questions you were shown, the AI-written read for each check-in, your trends write-up, and the Insights write-ups for each life area you open.
- What your journal suggests about your traits — when the journal setting is on, the app asks the AI to pull out trait signals and short quotes from what you wrote, and saves those alongside the entry. This is on by default and you can turn it off at any time in Journal.
- Share records — the codes and links you generate, and a copy of the read as it appeared when you shared it.
- Payment records for paid features — a customer and subscription identifier from Stripe, the plan, its status, the date, and a count of Assistant conversations used in the current month so we can apply the plan’s limits. Payment card details are handled by Stripe; we never receive or store them.
- Technical and usage data — IP address, browser and device type, pages visited, and timestamps, in our hosting and database providers’ server and security logs.
We do not ask for — and you should not enter — information about your health, diagnoses, medications, treatment, or anything else you would not want stored. The app does not need it to work.
Why we use it, and on what basis
Create and operate your account, and produce your read
Performance of our contract with you
Keep your history so you can see how you change over time
Contract; your consent
Let your journal inform your trait results
Your consent — on by default, switchable in Journal
Generate AI readings, Insights and chat replies
Contract; your consent
Operate sharing and feedback where you turn it on
Your consent
Respond to a message that looks like a crisis disclosure
Our legitimate interests, and the vital interests of the person concerned
Process payments and keep payment records
Contract; legal obligation (tax and accounting)
Provide support and reply to you
Contract; our legitimate interests
Keep the app secure, prevent abuse, and fix faults
Our legitimate interests
Understand overall usage and improve the app using de-identified, aggregated information
Our legitimate interests
Send you product emails, if you opt in
Your consent
We do not sell personal information, we do not share it with advertisers or data brokers, and there is no advertising in You Again.
Crisis language in the AI chats
The two open-ended AI chats (Reflect and the Assistant) check each new message you send against a list of words and phrases that indicate someone may be in crisis — thoughts of suicide or self-harm, or being hurt or unsafe. When a message matches:
- the AI is instructed to take it seriously and offer real crisis resources instead of continuing in its usual tone; and
- the matched message may be recorded, and sent by email to the operator, so a person knows it happened. The email contains the text of that message (up to about 2,000 characters) and which chat it came from. It does not contain your journal or the rest of your conversation.
This is a keyword safety net, not monitoring and not a clinical safeguard. Nobody reads your conversations in real time, it will miss things worded indirectly, and it will sometimes flag something you did not mean that way. Please do not rely on it to summon help — if you need help now, the resources are listed in our Terms, section 4.
If you would rather nothing you write could be flagged this way, do not use Reflect or the Assistant; the rest of the app — check-ins, reads, trends, journal notes, directions and steps — does not run this check.
Sharing and feedback — how your information moves
This is the part of the app where your information reaches other people, so it is worth being precise:
- Nothing is shared by default. Your reads are private to your account until you create a share.
- When you share a read, we store a copy of it with a six-character code and a link. The copy holds the name you chose to show (if any), the nickname, its one-line summary and the traits behind it.
- Anyone who has the code or link can open that read, with no account and no sign-in. A shared read is not listed, indexed or searchable anywhere, but we cannot control who a link gets forwarded to, so please do not treat a shared read as private.
- People viewing a shared read can leave a reaction and a comment. We store what they wrote, and show it to you when you choose to look. They do not need an account, and we do not ask them for their name or email.
- Deleting a share deletes the shared view and the feedback on it. If you are worried about a read being seen by someone, delete the share — and in the meantime, treat the code as public.
Who else sees it
We use service providers to run You Again. They act on our instructions and may only use your information to provide their service to us:
- Supabase — the database, sign-in and storage that hold your account and everything in it. Our database is hosted in Supabase’s Canadian region.
- Vercel — application hosting and delivery, including server logs, and Vercel Web Analytics, which counts page visits for us (see Cookies and browser storage below).
- Anthropic — the AI that writes your reads and Insights and replies in the chats. What is sent is the relevant context (your recent results, your direction, the conversation itself, and your journal where the setting is on) — never your password or account credentials. Anthropic does not use content submitted through its API to train its models.
- ElevenLabs — speech-to-text for voice notes. Receives the recording only for as long as it takes to return the words. We send no account details with it, and we do not store the recording or the transcript on our side.
- Resend — email delivery: sign-up confirmation, password resets, support replies, and the crisis and support alerts described above.
- Stripe, Inc. — payment processing, receipts and the billing portal for paid features. Stripe receives your card details and billing address directly; we receive identifiers and the subscription’s status.
- Google — if you choose to sign in with Google, Google confirms your identity to us. Google also serves the fonts this site uses, which means your browser requests them from Google and Google receives your IP address as part of that request.
We may also disclose information where we are legally required to, to establish or defend a legal claim, to protect someone’s safety, or in connection with a sale or reorganisation of the business — in which case this policy continues to apply.
International transfers. Our database is in Canada. Our hosting, AI, email, payment and sign-in providers operate outside Canada, including in the United States and Europe, so your information may be processed there and may be accessible to courts and authorities under their laws. Where the GDPR or UK GDPR applies, transfers rely on appropriate safeguards such as standard contractual clauses.
How long we keep it
- Your check-ins, results, directions, steps and journal are kept while your account is open. The whole point of the app is to show change over time, so we keep your history rather than discarding old check-ins — but you can ask us to delete any of it.
- Saved chats are kept in your journal while your account is open, so the app has context. You can delete an entry yourself.
- Shares and the feedback on them are kept until you delete the share or your account.
- Crisis-flag records and support messages are kept while we may still need them — for a flag, so a follow-up is possible, and for support, so we can answer you and see whether a problem recurs. The alert emails sit in an ordinary mailbox and are deleted along with the rest when we clear it.
- Deleting your account deletes your check-in history, results, directions, steps, journal entries and chats, shares and the feedback on them. Copies may remain briefly in our database provider’s routine backups before those roll over on their own schedule.
- Payment records survive account deletion — transaction identifier, amount, product, date and status — because Canadian tax law requires us to keep them. We keep them for seven years.
- Technical and security logs are kept for the short retention period our hosting and database providers apply — days to weeks, not years.
Your rights
You may ask us to:
- give you access to the personal information we hold about you;
- correct it;
- delete individual check-ins, journal entries, directions or shares, or close your account entirely;
- stop relying on your consent — including turning off sharing, or the journal setting; or
- send you a copy of your history.
Two of these you can do yourself, right now, from Your account: download a copy of everything we hold about you as one file, or close your account and delete all of it. For the rest, email hello@youagain.io and we will do it. We respond within 30 days.
If you are not happy with how we have handled your information, you can complain to us, and then to the Office of the Privacy Commissioner of Canada — or to your local supervisory authority if you are in the EU or UK. Where the GDPR or UK GDPR applies to you, you also have rights to restriction, objection and data portability.
Security
- Encryption in transit (HTTPS/TLS), and encryption at rest through our infrastructure providers.
- Row-level security in the database, so your check-ins, results, journal, directions and the feedback on your shares are reachable only by your own account — enforced by the database itself, not just by what the app chooses to show.
- A read you have shared is deliberately reachable without an account, because that is what makes it shareable. Treat a share code like a password you have given away.
- The AI provider’s key is held server-side only and is never exposed to your browser.
- Restricted access to production systems, security headers, and standard application hardening.
- As the people who built and run You Again, we keep the same back-end access any operator has to their own systems. That is for fixing bugs, answering support requests and following up a crisis flag — not for browsing people’s reflections.
No system is perfectly secure. If a breach occurs that creates a real risk of significant harm to you, we will notify you and the Office of the Privacy Commissioner of Canada, as PIPEDA requires.
Cookies and browser storage
We use cookies and similar browser storage only to run the app: keeping you signed in, holding a check-in in progress, and security. We do not use advertising cookies.
We count visits with Vercel Web Analytics so we can see which pages people reach and where they stop. It records the page visited, the referring site, and coarse device and location information (country and browser type, derived from your connection and not stored). It sets no cookies, keeps no identifier that follows you between visits or across other sites, and never sees what you write in the app. It is the only analytics we run.
Age
You Again is for people aged 18 and over. It is not directed at children or teenagers, and we do not knowingly collect information from anyone under 18. If you believe someone under 18 has created an account, contact hello@youagain.io and we will delete it.
Changes
We may update this policy. Material changes will be posted here with an updated date, and where a change affects how we use information you have already given us, we will contact you.
Contact
Diverse Innovations Inc. · Peterborough, Ontario
hello@youagain.io
This app is small and independently built. That is not a reason to be vague with you — if anything on this page does not match what the app actually does, tell us and we will fix the page or the app, whichever is wrong.