Privacy Policy

Last Updated: November 8, 2026

Rize (“Rize”, “we”, “us”, or “our”) is a wellness application that supports mood tracking, journaling, meditation, breathing exercises, personalized wellness plans, AI-assisted wellness conversations, optional social, community and group features, and related tools. This Privacy Policy explains what information we collect, how we use it, who we share it with, how long we keep it, and the choices and rights you have.

Important: Rize supports your wellbeing and is not a medical device. It does not diagnose, treat, cure, or prevent any medical condition and is not a substitute for professional or emergency care. Rize’s Guide is an AI, not a person or licensed professional. In crisis, call or text 9-8-8 (Canada and US), call 911, or 112 in the EU. Our Crisis Protocol explains what happens when a safety check finds signs of a crisis.

1. Information We Collect

We collect the categories of information below so the app can function, personalize your experience, keep the service reliable and secure, and support optional features you choose to use. Some features are available only in newer versions of the app, and this policy says so where that matters.

In this policy, the greeting request is the message the app sends to open a day’s conversation with the Guide. The AI providers are Anthropic, which makes the Claude language models, and OpenRouter and the AI model hosts it uses. Text requests go to Anthropic directly, or through OpenRouter for a model we reach there. Speech and transcription go through OpenRouter, and so can some safety checks.

CategoryExamplesWhere it is stored / processed
Account & identity Email address, display name, user ID, authentication tokens, optional profile photo Supabase Auth, the profiles table, and Supabase Storage for profile photos you upload. Your photo sits at a public URL. Your preferred first name also goes in the greeting request and in the message after a practice.
Age, region & consents Region (your country, and your province in Canada or state in the US), that you are 18 or over, and the consent choices you make, each with the version of the wording you saw and the time In versions of the app that ask for them, stored in Supabase against your account. They are exported with your data and deleted with your account. Requests to the Guide carry a broad region only (Canada, US, EU or elsewhere), so the right crisis numbers can be shown.
Onboarding & wellness preferences Answers from the onboarding flow (for example goals, coping preferences, core values, and future-self letter content) Stored on your device in an encrypted local database and secure app storage. The greeting request carries your answers, free-form ones included, and your future-self letter to our AI orchestrator and the AI providers, to personalize the Guide.
Health & fitness Daily wellness check-ins, mood and PIES dimension ratings, optional check-in notes Stored on your device in an encrypted local database. Activity type and timestamp sync to Supabase through user_activity. The greeting request carries your latest ratings, and the notes of a check-in made today, to our AI orchestrator and the AI providers.
User content — journal Journal entries and journal prompts you view or write Stored on your device in an encrypted local database. Journal activity metadata may sync to Supabase. The greeting request carries your latest entry’s title and mood, plus its first 40 characters when you wrote it today, to our AI orchestrator and the AI providers.
User content — wellness plans Personalized plans, goals, and progress you create in the app, and plans a group assigns to you Stored on your device in an encrypted local database. Naming a plan sends its goals and length through our AI orchestrator to the AI providers. Plans assigned by a group come from Supabase, and your status on them goes back there.
AI chat & conversation data Messages you send to the in-app wellness Guide, conversation memories, summaries, and favourited exchanges Stored on your device in an encrypted local database. Messages go to our AI orchestrator, which sends them to the AI providers to write replies, summaries and memories. A summary request also carries the memories already kept, so the list stays current. The greeting request also carries your first name, earlier summaries and memories, plans assigned to you and your last three days of practice, with the sound and music you chose. An exchange you favourite is stored in Supabase favorited_chats as plain text, against your account, until you remove it or delete your account.
Voice input (conversation mode) What you say when you use voice chat, and the audio of it where your device can’t turn it into text On iOS, speech is transcribed on your device. On Android it is transcribed on your device where your phone offers that, and otherwise by the system recognizer, which the app asks to stay offline but which may still use Google’s speech service. Where neither can run, on a Premium account your audio goes through our orchestrator to OpenRouter and the AI model hosts it uses, which return the text. We don’t keep the audio. The text is handled like any other message to the Guide.
Text-to-speech Guide responses you choose to hear spoken aloud Where your device has no voice of its own, on a Premium account, the text goes through our orchestrator to OpenRouter and the AI model hosts it uses, which return the audio to your device.
Social & friends Your friends list, friend requests, and friend challenge participation and contributions Supabase tables such as friends and the challenge tables. Your friends list is a social graph built from requests you send and accept. The app never reads your phone’s contacts. Friends and challenge participants see your name and photo. Friend search shows the name, email address and photo of each member whose email starts with what is typed, and shows yours to others the same way.
Community content Posts (with any activity you attach), comments, reactions, and community challenge progress Supabase. Other members see these under your name and photo, unless a safe-space post is anonymous. If you ask for the Guide’s reply on a safe-space post, its text goes through our orchestrator to the AI providers, and the reply is kept in Supabase.
Groups & facilitators Group membership, your sharing choices, notification preferences, plan status, and the check-in scores, engagement and plan progress you choose to share Supabase. A group’s facilitators see you as a member and see only what you choose to share, while you share it, and each view is logged. Check-in scores sync only while a membership shares them. Your journal entries, check-in notes and Guide conversations are never shared with a group or organization.
Moderation & safety Reports you submit, accounts you block, safety checks on what you send to the Guide, and messages those checks stop Reports and blocks are in Supabase tables such as content_reports and user_blocks. Every message to the Guide gets safety checks, and the moderation scores are kept against your session without the text. A message stopped by a safety check is kept as written, up to 8,000 characters, with the check’s reasoning and a record of the stopped session. When quality review is on, each exchange it reads is kept too. All of these can be read by Rize staff. No facilitator or organization sees them. See our Crisis Protocol.
Purchases & redeemed codes Your subscription status, store receipt, product ID, and redeemed codes The app sends your store receipt through our orchestrator, which records what you are entitled to against your account. Apple and Google hold your payment details, and we never see them.
Push notifications A push token for your device, your platform and app version Firebase Cloud Messaging issues the push token, with Apple Push Notification service on iOS. Supabase stores it against your account until you sign out.
Activity metadata Practice type (for example meditation, breathing, journal, check-in), timestamps, and optional duration Stored locally and synced to Supabase user_activity for achievements, streaks, recaps, and social or group sharing you choose
Device & usage Operating system, device type, app version, sign-in timestamps, login method, and login success/failure status Supabase user_login_activity on sign-in; device/app version may also be sent with Guide chat requests and recorded in server operational logs
Diagnostics Crash reports, performance data, and technical error information Sentry, linked to your user ID. In versions of the app that ask for your consent, the app sends these reports only after you turn on Help improve Rize, and stops when you turn it off in Settings → Privacy. Personal wellness content is scrubbed before upload where possible.
Product analytics App usage events (for example app opens, screens viewed, and that a check-in, meditation, breathing, journal, or Guide chat session occurred), durations and counts, device model, operating system, app version, locale and timezone. Events can carry the length of a Guide message and never its text. Journal text and check-in notes and ratings are not sent to analytics. PostHog, hosted in the European Union, linked to your user ID and not your name or email. PostHog receives your IP address with each request. In versions of the app that ask for your consent, analytics starts only after you agree, and you can change your mind in Settings → Privacy.
Session replay Session replay is off in current versions of the app. Earlier beta versions could record the app screens you viewed and your interactions with them, and wellness content on screen may have been visible in a recording. PostHog, hosted in the European Union. Recordings from earlier beta versions are linked to a pseudonymous user ID and automatically deleted after 30 days.
Server operational logs Each request to the Guide and each call to a chat or moderation model, as sent, with the reply. That covers greetings, summaries, the message after a practice, plan names and the Guide’s reply to a safe-space post, so a log can hold your name, your messages and anything else listed above that the request carried. Our AI orchestrator’s logging system, where authorized staff can read them. They are linked to your account through your user ID and session, and are used for reliability, abuse prevention, and internal administration. They have no fixed retention period, as section 5 explains.

2. How We Use Your Information

We do not sell your personal information. We do not use your health or wellness data for advertising, and we do not use your data for cross-app tracking.

3. How Your Information Is Shared

We share data only with service providers that help us operate the app, with the people you choose to share with in the app, or when required by law:

We may also disclose information if required by law, to respond to lawful requests, or to protect the rights, safety, and security of our users and our service.

4. Local Storage, Encryption, and On-Device Data

Your most sensitive wellness content — including journal entries, mood and check-in details, chat history, onboarding answers, and wellness plans — is stored primarily on your device in an encrypted local database (SQLCipher). What leaves your device is described in section 1. App preferences and some onboarding progress may also be stored in secure on-device storage.

Deleting the app from your device removes local data unless you have cloud-backed account data still stored on our servers (for example community posts or your account profile).

5. Data Retention

6. Data Security

All network traffic between the app and our servers uses encryption in transit (HTTPS/TLS). Sensitive local data is encrypted at rest on your device. Access to server-side data is protected by authentication and row-level security policies. No method of transmission or storage is completely secure, but we work to protect your information using industry-standard safeguards.

7. Your Rights and Choices

8. Age Requirement

Rize is for adults. You must be 18 or over to use it, and we do not knowingly collect personal information from anyone under 18. If you believe someone under 18 has provided us with personal information, contact us at contact@rizeapp.ca and we will take steps to delete it.

9. Changes to This Policy

We may update this Privacy Policy from time to time. We will revise the “Last Updated” date above when we do. Material changes may also be communicated through the app or by other reasonable means where appropriate.

10. Contact Us

If you have any questions about this Privacy Policy or your data, contact us at contact@rizeapp.ca.

Account deletion instructions: https://auth.rizeapp.ca/account-deletion/