1. Who we are
Ura is operated by Maison Bear, based in Gold Coast, Australia. This policy covers Ura’s apps, website, support and creator services. Contact support@uraapp.com about your information or this policy.
Information about anxiety, panic, addiction, cravings, relationships and recovery can be sensitive health information. We treat that sensitivity as part of our responsibility, even when a feature is described as wellbeing support.
Features and privacy controls vary by platform and app version. A change to this website does not update an installed app. Optional AI, Health, recording and sharing choices are explained when relevant; reading this policy or continuing to use Ura is not a substitute for a required consent.
2. Your mental health is not for sale
Ura will never sell your personal mental-health information or exploit your emotional vulnerabilities for commercial gain.
- We do not sell your personal information, mental-health conversations or recovery records.
- We do not provide private AI conversations to advertisers for behavioural targeting.
- We do not create advertising profiles from your anxiety, addiction, cravings or emotional distress.
- We will not opt private mental-health conversations into programmes that train external AI models.
- You can review, change or remove what Ura remembers, using the controls available in your version or by contacting us.
Using a hosting, payment or AI provider involves sharing information needed to deliver that service. It does not give Ura permission to sell your struggles. Those providers, the information they receive and important limits are explained below.
Important current limitation: Android advertising measurement sends some information to Meta, as described in section 7. That creates a privacy risk even without chat text or health answers. We do not describe all advertising disclosures as anonymous, harmless or outside legal definitions of “sale” or “sharing”. The audit has identified changes needed to bring every app version into line with these commitments.
3. Information we collect and use
What Ura handles depends on the features you choose:
- Account and profile: sign-in identifiers, email, chosen name, profile/avatar information, age or birthday where supplied, preferences and consent records. Apple or Google sign-in supplies information authorised through that service. Firebase handles authentication credentials and tokens.
- Onboarding and recovery: your selected pathway, habit or substance choices, goals, triggers, feelings, frequency, support preferences, check-ins, Panic Flow outcomes, Journey progress, Playbook entries and reflections. Some information is self-reported; some records describe activity in Ura.
- AI features: messages, recent conversation context, selected saved memories, preferences, generated replies, feedback and optional summaries. Section 4 explains processing and storage.
- Circles and community: membership, chosen identity, messages, support requests and acknowledgements, availability/read information where enabled, reports, and content you submit to the Community Outpost.
- Media and contacts: a photo or Why video you choose to save, and a trusted contact’s name, phone number and permission details if you provide them. Camera, microphone and media access are used for the feature you start. Calls, texts and exports you choose also reach the recipient and relevant device or communications service.
- Purchases and referrals: store or payment identifiers, receipts/tokens, subscription and entitlement status, gifts, creator codes, attribution, commissions and payout records. Ura does not receive the full payment-card details handled by the payment provider.
- Operations and support: device/app information, network identifiers, notification tokens, errors, security records, product analytics and correspondence you send us. Company demo requests include your name, work email, company, team size and optional message.
Why we use it
We use information to provide your account and chosen support tools, personalise relevant suggestions, save progress, operate sharing and purchases, send permitted notifications, answer requests, prevent abuse and understand reliability and feature use. Automated rules and AI can personalise support, summaries or optional invitations using the information and permissions available to that feature. You can choose another tool and manage supported personalisation choices.
Some local tools work without a named account. Online features may still use a technical or anonymous account identifier. Declining optional AI or Health access does not itself remove non-AI guided support. If information is necessary for a feature, we will explain the effect of not providing it.
4. Ura AI, conversations and memories
What goes to OpenAI
With AI consent, relevant content passes through Ura’s backend to OpenAI to generate a reply or insight. Depending on the feature, this can include your message, recent chat turns, profile and onboarding preferences, recovery context, selected memories and recorded app activity. Separately approved Health summaries or session-card material can also be included. The AI needs readable content to respond; this processing is not an end-to-end encrypted conversation that Ura’s backend or OpenAI cannot read.
Voice features use the microphone when you start them. Speech recognition can run on-device when supported, or use Apple’s speech service on iOS or the speech service configured on Android. Features offering live AI voice may send audio to OpenAI. Reply text may be sent to OpenAI to generate speech. Providers and permissions depend on the voice feature and platform.
What Ura remembers
Memory can retain concise details such as goals, preferences, useful context and what helped, rather than keeping every conversation as a memory. After AI consent, memory may be on by default unless you have turned it off. Relevant saved details can be included in later AI requests while the applicable permissions are enabled.
Current app chat uses recent conversation context during the chat. Saved memories, short reflections, reminders, copied entries and feedback are separate records. A “full conversations are not saved as memory” statement does not mean that nothing you said can be retained elsewhere, including by an AI provider or a feature you explicitly use to save or share it.
Supported local memory uses protected device storage. Optional account memory sync stores a private copy in Firebase; the current sync format is encrypted in transit and by the service, but is not end-to-end encrypted. Authorised service systems and personnel may be able to process that account copy. Turning sync off stops sync on that device and leaves the existing account copy in place. Clearing with sync enabled or deleting your account can remove the relevant active copy.
Additional client-side saved-text encryption and recovery work is being prepared. We do not treat that unreleased work as protection already applied to every public app version or historical record. Nor do we claim that the founder cannot access any Ura data.
Training and provider retention
OpenAI’s API/business terms exclude model training on submitted content by default unless the organisation opts in. Our policy is not to enable optional training/data-sharing programmes for private conversations. The Ura Panic App organisation’s feedback, evaluation/fine-tuning and API input/output sharing controls were all disabled when reviewed on 1 November 2026. OpenAI’s business terms explain its commitments.
The inspected ordinary app-chat requests set store: false. This does not provide zero retention: OpenAI describes default abuse-monitoring retention of up to 30 days for many API endpoints, with exceptions and different treatment for some features or legal/security needs. Audio and hosted-session features can have different storage. We have not verified a special Zero Data Retention agreement for Ura. See OpenAI’s data controls.
Your controls
Use AI Settings to decline or withdraw AI processing, review/edit/forget memories, pause memory and manage available sync or sharing options. Some controls require an updated app. Withdrawal stops future requests under that permission; it cannot recall a request already processed. You may also request deletion through our privacy contact.
AI reply feedback may save a reason and a hashed turn reference. If you explicitly choose to share text with feedback, that text is retained for review. App-experience feedback can also be stored and emailed to support. Neither feedback route should be assumed to disappear merely because the chat closes.
5. Private Circles and sharing
Ura’s current iOS design focuses on private, personal Circles. Members can see the identity you share in that Circle, membership and messages or support actions made available to the group. Availability, support signals and read information depend on the feature and its settings. Someone with an invitation code may see limited invitation information. Only share codes with intended recipients.
A personal Circle does not automatically give members your private AI conversations, saved memories, raw Health records or private reflections. Information you post, copy, export or deliberately share becomes available to the chosen recipients. Members may retain copies or screenshots; leaving, unsending or deleting an account cannot recall those independent copies.
Earlier Clinic and Organisation Circle features
These features have been removed from the current iOS interface, but remain in available Android source and deployed backend services. We have not verified that every installed release has retired them. Earlier sharing permissions or records can therefore still matter.
Where enabled in those versions, authorised staff may access assigned-client messages, bookings, selected activity or consented summaries. Clinic AI-usage summaries use a separate sharing permission and structured categories/counts rather than the full chat transcript. A previously enabled permission is not automatically revoked by removing its screen. Contact us to review or stop legacy sharing if your version no longer shows the control. Independent providers may also hold records under their own duties.
Community Outpost
Content you submit can be visible to the Outpost audience after the relevant review, and to authorised moderators handling reports or safety. A public-facing or pseudonymous author label does not make the underlying submission anonymous to Ura’s systems. You can use available review, deletion, reporting and blocking controls.
Private session preparation
On supported iPhone versions, “For my next session” keeps talking points and takeaways in protected, device-only storage, including up to 12 past session notes. Saving a card does not automatically send it to a therapist or Circle. An AI summary or “Help me say this” request sends the selected material to OpenAI after the relevant approval. Use Session card options to delete these local cards; original check-ins or reflections and previously shared copies are separate.
6. Health, Watch and device permissions
Health connections are optional. In supported iPhone features, Ura reads permitted sleep and step information from Apple Health to show patterns. Supported Android features use permitted sleep and step records from Health Connect. A missing reading does not prove that no activity occurred.
Supported Apple Watch features can read permitted heart rate, heart-rate variability, sleep, steps and workout/activity context for local learning or invitations. Independent Watch learning remains on the Watch unless a feature explicitly shares information. Phone-companion features can exchange relevant state between your phone and Watch. Clear independent learning on the Watch as well as managing the phone’s settings.
Apple Screen Time uses the selections and opaque identifiers supplied by Apple’s privacy-preserving APIs. Android screen-use features require separate Usage Access and can read application-usage information locally to produce summaries. Device permissions and local summaries are separate from product analytics.
Optional gentle check-ins use permitted local context and notification choices. Supported iPhone invitation evidence has a seven-day local expiry. A check-in is an invitation to pause, not proof of a diagnosis or a prediction. Ura does not request precise GPS location for these features.
Raw Health or Screen Time access is not permission to send everything to AI. Where offered, a separate control approves a limited Health summary for Ura AI. That summary is still sensitive information and is processed by Ura’s backend and OpenAI. You can revoke permissions in device settings and turn off supported sharing in Ura.
We do not use Health or Screen Time records for advertising or send raw readings to product analytics. Revoking access stops future reads; it does not erase records held by Apple Health/Health Connect or information already processed under a previous approval. Notifications may be visible to someone who can see your device; manage their presentation in device settings.
7. Analytics, diagnostics and advertising
PostHog product analytics
PostHog receives feature-use events and technical information such as app/device version, timestamps, account or installation identifiers and subscription status. Current events can also include pathway choices, use of Panic Flow, outcome categories or changes in intensity. These can reveal sensitive recovery context and can be linked to a signed-in account. We do not describe them as wholly anonymous.
PostHog can derive approximate country, city or region from an IP address. This is separate from GPS permission. The inspected current event filters restrict free text, and the selected recent event schemas did not include raw chat messages or questionnaire answers. That is not a guarantee about every historical SDK version or event.
On versions offering “Share app usage recordings”, recording is optional and the inspected implementations start it after opt-in, with text/image masking and additional private-screen protections. It does not enable microphone or camera recording. Signing out resets the inspected recording choice. Older installed versions require separate verification; updating this policy does not change their behaviour.
The recording switch does not turn off ordinary product analytics. There is no separate general-analytics opt-out in the inspected clients. Contact us about analytics access, objection or deletion. We are reviewing the necessity of account-linked recovery events and the controls needed for them. PostHog replay retention is currently configured to 30 days; event/person retention is separate.
Crash and security diagnostics
iOS builds with Firebase Crashlytics send crash/device diagnostics to Google. These are separate from optional PostHog recordings. Backend security and error logs may contain technical identifiers, account IDs, error details and stack traces. We aim to keep private conversation content out of diagnostics, but do not promise that all historical logs are free of personal information.
Android Meta measurement
Android versions containing Meta’s SDK can send install/app-open activity, advertising or app/device identifiers, IP/network information and attribution data to Meta for Facebook/Instagram advertising measurement. Earlier builds enabled automatic event collection, which can include purchase/subscription events, without a separate Ura Meta-consent control.
The newer Android implementation reviewed for this audit starts measurement off, requires an eligible adult’s explicit choice and limits app-supplied measurement to install/app-open activity. It excludes Ura account identifiers, health answers, chat text, journals and purchase details from that measurement process. Turning the control off or signing out stops that implementation’s future measurement. We have not mapped this source to every distributed Android build; do not assume that every installation has the newer control.
Even basic use of a mental-health app can be sensitive. Meta’s Business Tools terms restrict health-derived information and permit wider advertising/product uses of event data. Meta is not simply a storage provider under Ura’s sole control. Its terms allow event retention for up to two years, and audiences can remain until deleted. Deleting a Ura account does not automatically erase Meta’s records.
Our commitment against exploiting mental-health information requires more than a policy statement. The audit recommends removing this app-level advertising integration and reviewing historical data. There is no equivalent Meta SDK identified in the current iOS source and no Meta Pixel identified in the inspected public website pages.
8. Website, cookies and support
Vercel serves the website and receives ordinary network information, such as IP address and request details, needed for hosting and security. The public pages inspected for this audit did not set cookies or start advertising/product-analytics requests on an ordinary visit. This does not mean that hosting logs, authenticated portal storage or every future/optional feature is absent.
Sign-in features can use browser storage for authentication. Local tools and media controls may keep preferences or progress in your browser. Some older pages request font styles from Google Fonts, which exposes ordinary request information to Google; this revised policy page uses local fonts. External sites, stores and social/donation links have their own privacy practices.
Website AI support: starting a support chat requires a sharing choice and sends what you type through the website backend to an OpenAI-hosted agent session. The browser conversation token expires after 30 minutes; that expiry is not deletion of the provider’s session. Current source does not automatically delete that hosted session when you close the widget. Contact us about access or deletion, giving enough non-sensitive information to help locate the interaction.
Abuse prevention uses hashed network/conversation identifiers and counters in Redis/Upstash. The inspected support counters expire within approximately two days. Demo-request deduplication/rate-limit records have separate short expiries. The demo form and app feedback can send your supplied details to our support mailbox through Resend. Email copies follow the recipient/provider’s retention, not the browser form’s lifetime.
If you use Ura tools within ChatGPT, the information returned into that conversation is also handled under that platform’s terms and the integration’s own notice. It is not automatically a private Ura account record.
9. Providers, recipients and locations
Depending on the feature and platform, recipients include:
- Google/Firebase: authentication, account/recovery data, databases, files, functions, notifications and, where enabled, Crashlytics. Relevant services operate under Google/Firebase processing and security terms; provider service/security data can have separate uses.
- OpenAI: consented AI content, relevant context, optional summaries and voice/speech processing. Its business terms and endpoint-specific retention apply.
- PostHog: product events, identifiers, diagnostics and optional masked recordings. Its DPA provides for processing on documented instructions; it does not make unnecessary sensitive collection appropriate.
- Meta: version-dependent Android advertising measurement, with the additional risks and provider uses explained in section 7.
- RevenueCat, where configured: account-linked store purchase, receipt and subscription synchronisation. We found no deliberate chat/health-content attributes in the inspected integration; account-side outbound integrations require separate review.
- Apple, Google Play and Stripe where applicable: sign-in, platform permissions/speech/notifications and the payments, purchase or refund records relevant to your chosen channel. These services also have their own notices and legal obligations.
- Wise and receiving banks: creator-beneficiary information, verification, currency conversion and payments. Financial providers process information needed for the payment and their legal duties.
- Resend and our support email service: messages and reply details you submit. Vercel and Redis/Upstash: website requests, security/usage controls and related technical records. Google Fonts on some older pages: ordinary font-request information.
- People you connect with: chosen Circle/Outpost audiences, authorised legacy staff and recipients of an export or message. Creators can receive relevant referral/purchase/commission information where that programme is used; private AI conversations and health records are not part of creator reporting.
Providers use authorised subprocessors and may process service, security or legally required information under their own applicable terms. We have not verified a bespoke agreement that eliminates every provider’s retention or access. Ask us if you need more detail before choosing an optional feature.
International processing
Ura operates from Australia. The production Firestore database and main file bucket inspected in this audit are in Australia’s southeast region. That does not keep all processing in Australia: inspected Cloud Functions run in the United States, PostHog uses its US region, and OpenAI and other providers use international infrastructure and support/subprocessors.
Likely recipient locations include Australia and the United States; creator payments can also involve the United Kingdom and the receiving country. Other locations depend on the chosen service, payment route and subprocessors. Transfers must have the safeguards required by applicable law; using a provider does not remove Ura’s responsibilities. Contact us for the locations and arrangements relevant to your request.
10. Storage, retention and deletion
Security and access
Network connections use HTTPS/TLS. Firebase and other providers apply storage encryption and access controls; local protected stores use device security. The inspected client rules restrict private account records to their owner and Circle records to the relevant roles. Server administrators and service accounts have separate privileged access. These safeguards are not a guarantee that no person or system can ever access information, and no method is completely secure.
Private profile photos and Why videos use account-owned file paths. Profile/avatar information deliberately shared in a Circle and public-facing branding are different from those private files. Saved or exported media in your photo library or another service is controlled there.
How long information stays
- Account, recovery and shared content: generally retained while needed to provide the feature, until removed through available controls or an account-deletion request. Most of these collections do not have a single automatic age-based expiry. Outpost submissions have no ordinary automatic expiry; account-deletion processing removes associated content, subject to legitimate legal/security exceptions.
- Legacy Clinic AI-usage insight events: expiry is set to 90 days and the relevant Firestore TTL policy is active. Aggregated summaries and other clinical records are separate and do not inherit that expiry automatically.
- Diagnostics: the inspected Google Cloud default log bucket retains 30 days; the required audit-log bucket retains 400 days. Crashlytics, PostHog events and other processors have separate retention. PostHog recordings are currently configured for 30 days.
- Deleted files: the inspected cloud bucket’s soft-delete period is seven days. This can retain a recoverable provider-side copy after deletion from active use. Other processor backups and legally retained records follow their own schedules.
- AI and website support: the provider limits in sections 4 and 8 apply. Chat/window expiry, a no-training setting and
store: falsedo not mean every provider record is immediately erased. - Purchases, creator payments and security: limited records may remain for refunds, commissions, reconciliation, fraud prevention, disputes or legal recordkeeping. We assess the purpose and applicable requirement, rather than treating account closure as permission for indefinite retention.
Deleting your account
Use the account-deletion option in Settings, follow our deletion instructions, or email us. The inspected server process removes the user’s Firebase account records and many associated active records, including nested account data, synced memories, private media and relevant Circle/Outpost records. Current clients also clear relevant local account stores on the device completing deletion.
Important limits: the deployed deletion process does not automatically erase PostHog history, standalone AI-feedback records, OpenAI-hosted website sessions, Meta records, RevenueCat records, support emails or every financial/processor record. AI feedback shared for review is stored separately without a direct account index; a hashed turn reference does not make identifying text anonymous. Request deletion of these through our privacy contact as well. We will assess what can be removed, ask relevant providers where appropriate and explain any lawful retention or practical identification limit. We do not promise complete instantaneous erasure.
Legacy Clinic/Organisation owners can be blocked by a requirement to transfer or close the managed Circle first. Contact support if that control is missing from your app. Independent care providers and other recipients may retain their own lawful records.
Clear independent Watch learning on the Watch. Deleting Ura does not delete Apple Health/Health Connect records or copies held by recipients. Uninstalling does not delete an online account, and protected local/keychain data can survive a reinstall. Account deletion and uninstalling do not cancel a store subscription; cancel with the relevant payment provider.
11. Your choices, rights and complaints
You can manage supported AI, memory, Health, Screen Time, recording, notification and sharing choices in Ura or your device settings. You can request access to or a copy of your information, correct inaccurate information, request deletion, withdraw applicable consent, or raise a concern by emailing support@uraapp.com. We may need proportionate identity checks before disclosing or changing records.
Where European/UK or other applicable law provides additional rights, these may include portability, restriction, objection and a complaint to your local supervisory authority. Consent can be withdrawn for future consent-based processing without changing the lawfulness of earlier processing. Rights have legal exceptions; we will explain a refusal or necessary retention and available complaint options.
We aim to respond within 30 days and meet any applicable statutory deadline. If more time is legally permitted and needed, we will explain why. If a privacy complaint is not resolved, you can contact the Office of the Australian Information Commissioner or another relevant regulator.
Legal, safety and breach handling
We may disclose information where required or otherwise lawfully permitted, for valid legal process, security, rights protection or a serious threat to safety. This is not continuous monitoring or a guarantee of intervention. Where a breach requires notification under applicable law, we will notify the relevant people and authorities as required.
12. Ownership and policy changes
Investment, acquisition or a change of operator must not become an excuse to turn mental-health information into an advertising asset. A lawful transfer needed to continue the service must be limited to that purpose, with appropriate security, confidentiality and notice, and fresh consent where required.
Our commitment is to require a successor to accept binding restrictions against selling personal mental-health information, advertising from private conversations or emotional profiles, and optional external-model training on that content. Due diligence should use de-identified or aggregated information wherever possible and exclude unnecessary private content. If a proposed new use cannot meet the existing commitments and applicable law, it must not simply be introduced through a silent policy edit.
These are commitments for how Ura will approach a transfer. They are not a claim that legally permanent acquisition protections or a particular successor agreement already exist. Enforceable transfer terms and applicable law matter.
Changes to this policy
We will update this notice when practices change and provide appropriate notice of material changes. Where a new purpose requires consent, we must obtain that consent rather than treating continued use as blanket permission. The review date above does not mean an unreleased app change has shipped.
13. Age requirements
Ura’s current signup direction is for people aged 16 or older, subject to any higher restriction from the app store, region or applicable law. Current store ratings and an app’s signup rule are different checks. Earlier releases may have allowed younger accounts, and we do not claim that every existing user’s age has been independently verified.
Contact us if you believe an account is below the applicable age or lacks required consent. We will investigate and take appropriate steps, including restricting processing or removing information where required. The newer Android advertising choice is restricted to known adults aged 18 or older; this does not validate advertising collection in earlier releases.
14. Contact
For privacy, access, correction, deletion or a complaint, contact support@uraapp.com.
Maison Bear · Ura · Gold Coast, Australia