Privacy Policy
Revision 2 · en-US · Effective 2026-10-22
About this policy
Dear Mori is operated by Kiwi Tree, Santa Clara, CA, United States (“Kiwi Tree”, “we”, “us” or “our”), which is the controller of the information described here. This policy explains how we handle information in the app, connected account and purchase services, gift pages and support. Contact support@ohmymori.com (Kiwi Tree, Santa Clara, CA) with privacy questions.
Your ordinary journal text stays on your device. Accounts, purchases and gifts require the information described below. Purchase and gift records can reveal the kind of Mori you select, even when they do not contain your private words. Gift messages are stored in encrypted form, except when a user chooses to include a message in a report for review.
Information stored on your device
Wishes, inscriptions, optional personal details, custom actions, reflections, feelings and outcomes are stored in your local journal. Natural practice progress remains local. Ordinary wallet synchronization excludes private wording and natural practice history. Gift sharing and reports are separate choices described below.
An unfinished wish and its customization stay on your device until you continue or delete them. Deleting an unfinished wish does not delete existing journal history, purchase records or a Google Play age restriction remembered on the device.
The journal relies on your device’s storage protections and is not separately encrypted by Dear Mori. Password-encrypted exports are a separate feature. Losing the device, clearing app storage or uninstalling the app can remove local records. We cannot retrieve journal text that was never sent to our services.
Wallet linking and activity rewards
Petals form one signed balance. All Petals have the same spending eligibility, regardless of how they were received. Daily activity rewards remain per device; signing out or changing accounts does not reset device reward limits or starter eligibility. Activity rewards are reported by the device and checked for valid amounts and duplicate events, not independently verified as completed activity by our service.
When you explicitly sign in or synchronize, existing device Petals and financial entitlements attach automatically to the selected account after the applicable account and Terms review. There is no separate linking confirmation. Linking does not itself accept Terms. Funds and pending actions already bound to one account never move to another account when you switch. Signing out preserves them and starts a separate local wallet for new guest activity.
Age information
We do not ask for your country, region, age group, exact age or date of birth, except during an access review for an existing guardian-managed or restricted account, described below. Where available, the app silently requests the age range and any verification or approval status that Google Play provides for your Google Play account. We use it only to apply the age restrictions described in Children and Parents and to meet related legal obligations.
For ordinary use, only the resulting restriction status is kept on your device and the Google Play age range is not sent to our servers. If an existing guardian-managed or restricted account needs another access review, you choose your country or region for that review. If Google Play does not provide an age range and that region allows it, you also choose an age group; we never ask for your exact age or date of birth. The country or region and the age range or age group are sent with that review. Earlier app versions could save a selected country, region and age group with your Firebase account; account deletion removes any such saved profile.
Free local practice and journaling do not require an account. Connected account services are contacted when you take an account action or use an eligible restoration feature. Public account setup offers email/password or Google sign-in; it does not offer parental enrollment. See Children and Parents for age restrictions and the privacy-request process for a child.
Account and purchase information
Firebase Authentication processes your sign-in credentials, email address, account identifier and information supplied by your selected sign-in provider. We use this information to create or authenticate your account, verify email addresses, recover access and connect sign-in methods you choose to link.
In the Android app, passwords are sent to Firebase. On a gift page, a password for an existing account passes through our gateway to Firebase for verification and is not stored by our gateway. Google sign-in on gift pages verifies an existing linked identity; it does not create a new account or link accounts based only on a matching email address.
Our commerce services process the signed wallet balance, ownership, consumable grants, financially acquired progression, transaction and refund references, purchase tokens and order information. Internal financial records retain activity, purchase, promotion or unknown historical origin, debit allocations, device-wallet and stream identities, immutable event identifiers, original and receipt dates, evidence classifications, migration claims and acknowledgment positions. These records support accounting, reconciliation, duplicate prevention, restoration and support. They do not contain ordinary private journal wording. Historical inferred records and device-reported rewards are distinguished internally from provider-verified purchases.
Financial operations also send Mori and activation identifiers, dates, progress totals, checkpoints and connection requirements. Mori identifiers may indicate interests in health, recovery, fertility or childbirth. These records may be sensitive even though they do not include your private journal text.
When you explicitly sign in or synchronize, existing device Petals and financial entitlements attach automatically to the selected account after the applicable account and Terms review. There is no separate linking confirmation. Linking does not itself accept Terms. Funds and pending actions already bound to one account never move to another account when you switch. Signing out preserves them and starts a separate local wallet for new guest activity. Synchronized Petals, Mori ownership, cosmetic unlocks, unused consumable uses and financially acquired durable connection entitlements restore through the same account. Private journal wording, reflections and natural practice progress remain local. Unsynchronized changes may be lost if device storage is lost. Restoring an active use preserves its original start and end dates; it does not start another 30 days.
Promotional codes
When you check or redeem a Dear Mori code, our service processes the code, account identifier, campaign and reward information, redemption time and retry reference. We use these records to check eligibility, prevent repeated use, restore rewards and handle support. Mori and appearance identifiers may reveal sensitive interests; journal text is excluded. Routine redemption records use code hashes rather than raw codes.
Your device keeps pending codes and requests in protected app storage until redemption and recovery are complete. Google Play purchase tokens awaiting a confirmed account claim may also be kept for recovery. Switching accounts does not transfer a pending claim.
Successful account deletion removes that account’s pending device claims and cloud redemption records. Campaign counts and consumed code hashes remain without the account identifier to prevent reuse. Google Play transactions remain subject to purchase-receipt retention.
Code distribution files and campaign administration records are restricted to campaign operation and support and are removed when no longer needed, subject to applicable retention obligations.
Invitations and account trophies
If you share an invitation code or join a friend’s invitation, including when a new account accepts a Mori gift and the gift counts as the sender’s invitation, our service processes your account identifier, a hash of your invitation code, the link between the inviting and invited accounts (and, for a gift, the gift identifier), the invitation status, counts of friends who joined and were rewarded, reward ledger records and retry references. We use these records to check eligibility, prevent self-invitation and repeated rewards, grant each reward once and handle support. Journal text, wish words and the content of your small steps are never sent.
While an invitation you joined is still counting, the app tells our service on a day you complete a small step, at most once a day and until three days are counted. Our service records the date it received each report. If you have not joined an invitation, the app sends nothing about your practice for this purpose. An inviting account sees only how many friends joined and were rewarded, not who they are or when they practice.
Account deletion removes your invitation code and your own invitation, and removes your account identifier from invitations you sent. Rewards already granted remain part of each account’s wallet history.
Account trophies count friends who joined through your invitation, gifts you sent that were accepted and verified Petal packs you bought, using the invitation, gift and purchase records described in this policy. Our service additionally keeps which trophies your account has claimed and the resulting reward ledger records, so each reward is granted once. Practice trophies are counted on your device and only their Petal amounts reach our service, as other activity rewards do. Account deletion removes the claimed-trophy record with the account.
Gifts and gift notifications
A gift provides one 30-day wish to an eligible recipient. We process the gift identifier, Mori and gift type, funding reservation, necessary sender and recipient account references, encrypted message, status and dates to deliver and restore the gift and prevent repeated use. Mori identifiers can reveal sensitive interests. These records exclude the recipient’s private practice, reflections and outcome.
Gift wording is encrypted on the sending or accepting device or browser before being stored by our service. The key remains in the private link and authorized clients, separate from the stored message. A written gift retains the sender’s wording. For a blank gift, the recipient’s words use a new key unavailable to the sender. Ordinary gift delivery does not provide the service with that key. Anyone who obtains the complete private link, including through a messaging service you select, may be able to open its contents subject to applicable account restrictions.
Gift pages initially show a cover without private wish wording. Eligible existing users can sign in and choose to open or accept the gift; new users must continue in Android. The page uses a temporary secure session cookie, request-forgery protection and abuse counters. Encrypted messages, keys and retry references may remain in browser session storage until the session ends or you clear them. Hosting and authentication providers also process technical request information.
Where enabled and permitted, the sender receives a viewed update when an eligible user deliberately displays the gift, an acceptance update and any preset thank-you the recipient chooses. A viewed update does not prove who read the gift. The sender does not receive view counts, recipient email, location, private journal activity or outcomes.
Gift updates appear in the account inbox. Optional push notifications use an account and device registration and a reference that lets the app retrieve the authorized update. The push payload excludes private wish text. Private, unaddressed links may be claimed by their first eligible holder; addressed gifts are restricted to the specified account. Receiving does not require a purchase. Gift contacts have no public directory or uploaded address book.
You can hide a gift, block a sender or report a concern. A report normally includes identifiers and a reason. If you preview and explicitly include the gift message, that selected text is made available for restricted moderation. Other journal entries are not attached. We use reports to investigate concerns, protect users and respond to abuse.
Pending gifts do not automatically expire. Cancelling a pending gift removes its encrypted message. Accepted encrypted recovery material remains for the recipient until they delete it or their account. Deleting a sender’s account does not remove an accepted recipient wish. Account deletion removes unnecessary account references, contacts, device registrations and browser sessions. Necessary spent or cancelled records and justified security or moderation records may be retained for their stated purposes.
Restoring access to the same account can recover gift records, but the private wording also requires an original or continuation link, authorized local material or a backup. Google Play install links do not receive the key. We cannot reconstruct lost keys. Copies another person has saved or shared are not automatically removed by your account deletion.
Legal notices and agreement records
The app keeps records of the legal information you reviewed and agreements you accepted, including document versions, text fingerprints, language and time of review or acceptance. These records are kept separately from journal exports and diagnostics.
You accept the Terms once on your device, during setup or when updated Terms are presented. When you create or sign in to an account on that device while the same version is current, we record that acceptance for the authenticated account, including when it was associated with that account. A guardian-managed account keeps its guardian’s agreement. Accepting the Terms does not enable usage and crash reporting, which is a separate choice.
Account deletion removes the account’s Terms acceptance records. Arbitration opt-out correspondence is handled separately so we can honor the choice you made, as explained below.
Usage analytics and crash reports
Usage and crash reporting is optional. You choose it with a switch shown with the Terms during setup, before you write your wish, and can change it at any time in Settings. The choice is separate from agreeing to the Terms, and Dear Mori works the same either way. Depending on where you are, the switch may start on or off. Where your consent is required, it starts off and nothing is collected unless you turn it on. To choose the starting position, the app uses the country of your Google Play account where it is available; if that country is unavailable, the switch starts off.
When reporting is on, Google Analytics for Firebase and Firebase Crashlytics receive limited app interactions, such as setup steps completed after you make this choice, completed daily steps, reminder and widget choices, shop and purchase steps and outcomes, including the price and currency of a completed Petal purchase, coarse progress counts, crash stack traces and technical device and app information. Their SDKs also process an app-instance identifier and may infer approximate location from your IP address without location permission. Event fields exclude private journal text, which Mori you choose, account identifiers and purchase receipts or tokens.
We do not collect the Android advertising ID, use these reports for advertising or allow ad personalization. Reporting is unavailable when Google Play reports an age restriction for the user.
Turning reporting off stops new reports, resets local Analytics data and deletes unsent crash reports. That does not erase reports already transmitted to Google. Applicable retention settings and privacy rights continue to govern those reports. Usage and crash reporting choices do not disable the authentication and security processing needed for connected services.
Security and technical information
Firebase Authentication, App Check, Google Play Integrity and our connected services process technical information such as IP addresses, app and device information and integrity signals. We use these services to authenticate requests, validate the app, protect accounts and prevent fraud or abuse. This processing is separate from optional analytics.
We use encrypted HTTPS connections, access controls and server-side purchase verification to protect information sent to our services. No storage or transmission system can be guaranteed completely secure.
Device features, exports and sharing
Optional reminders use local Android notifications. Widgets and live wallpaper display selected content on your device; supported wallpaper motion uses local motion signals. Image and video export saves an image or short video, made on your device, to your device or sends it to an app you select through Android sharing. When you leave the Made with Dear Mori option on, a shared image or video includes a public link to our website.
When you choose Paste while opening a gift link, the app reads the text currently on your clipboard once to fill in the link; it does not read the clipboard at other times. On a gift or invitation page, Get Dear Mori copies the private gift link or invitation code to your device’s clipboard so you can paste it after installing. Other apps on your device may be able to read the clipboard, so you may wish to clear it.
After you finish a wish or reach a weekly streak, the app may ask Google Play to show its rating card, at most once every 90 days. Google Play decides whether to show it and handles any rating under its own terms. The app does not learn whether or how you rated it and sends no app data for this.
When a newer version is available, the app may ask Google Play to show its update screen or download the update in the background. Google Play handles the update; the app sends no app data for this.
Where available, journal export creates a password-encrypted file containing journal history and any stored private gift material, including the keys needed to recover it. It excludes wallet balances, ownership and Terms acceptance records and is not an export of all account information. Keep the password safely; we cannot recover it. Journal import and export are unavailable while Google Play reports an age or approval restriction. Images and short videos can still be saved or shared then, without words the user wrote, such as a wish inscription or message. For a guardian-managed account, those words and journal export require the guardian's permission.
Files and links you share may be handled by the people, apps or storage services you select under their own privacy practices. Copies held outside Dear Mori must be managed separately.
Support and website visits
If you contact us, we receive your email address and the information you provide, such as an account identifier, order reference or description of a problem. We use it to respond, verify authority, process rights requests and resolve the issue. Please do not send passwords, full payment-card details or unrelated private journal content. An email link prepares a message; you must send it to submit a request.
We also use information you voluntarily provide to consider product suggestions and investigate intellectual-property complaints. Necessary information may be shared with people assisting with that request or professional advisers. The feedback licence in the Terms does not authorize reuse of personal information.
Our legal and support pages contain no advertising or analytics scripts added by us and do not require an account. Firebase Hosting processes technical requests and logs to deliver and protect the website. Browser and email providers may process information under their own policies.
The landing pages and free browser preview are covered by our Website and Preview Privacy Notice. Preview wishes and reflections remain in page memory; an explicit website theme preference may be saved in browser storage. Gift-page sessions are described in the gifting section.
We do not use advertising integrations, sell journal entries or use these static pages for cross-site behavioral tracking. The static pages do not respond differently to a browser’s Do Not Track signal. External sites and services have their own privacy practices.
Service providers and international transfers
We use Google and Firebase services for authentication, database storage, connected app functions, app integrity checks and Google Play payments. Optional gift notifications use Firebase Cloud Messaging. Google sign-in on gift pages loads Google Identity Services when selected. Support email is handled through Gmail. If you allow usage and crash reporting, Google Analytics for Firebase and Firebase Crashlytics receive the reports described above.
Providers receive information needed for the services they supply. Their responsibilities and privacy practices depend on the particular service. Google Play, Google sign-in and other services may also process information for their own purposes under their applicable policies.
Our commerce functions run in the United States. Other processing locations depend on the provider and service, and your information may be processed outside your country. Where transfer safeguards are required by applicable law, they must apply to the relevant transfer. Contact support@ohmymori.com for information about the locations and safeguards applicable to your data.
Business transfers
In connection with a proposed sale, reorganization or other lawful transfer of the Dear Mori business, we may disclose necessary account, transaction or support records to prospective counterparties and professional advisers, subject to appropriate confidentiality, security and legal safeguards. This is limited to information we hold; it does not give us access to a local journal that was never uploaded.
A successor receiving personal information must assume the applicable privacy obligations. We will give required notices and obtain any consent or provide any choice required by law before a transfer or materially different use. This provision does not authorize transfers to data brokers, new advertising uses or unrestricted reuse of sensitive information.
Legal requests, disputes and arbitration choices
We may disclose information reasonably necessary to comply with a binding legal requirement, respond to lawful process, investigate fraud or abuse, protect rights and safety, or establish, exercise or defend a legal claim, subject to applicable law. Recipients may include professional advisers, an arbitrator, a court or a competent authority. Disclosures are limited to information relevant to the matter.
Dispute correspondence is retained according to the claim, legal obligations, limitation periods and any applicable legal hold. Please provide only information needed for the issue. Account Terms acceptance records are deleted with the account.
If you opt out of arbitration, we process your name, mailing address, account email if any, opt-out statement and timing information to identify and honor your choice. We retain only the evidence reasonably needed for that purpose or related legal obligations or claims, subject to review and applicable deletion rights. These records are separate from account Terms acceptance records.
This policy does not waive privacy rights or authorize processing by itself. The Terms contain arbitration provisions for covered United States disputes, with a 30-day opt-out and stated exceptions. They do not prevent a privacy request or regulator complaint, waive non-waivable rights or require Terms acceptance to exercise those rights.
Retention and deletion
We retain information for as long as needed for the purposes described in this policy, taking into account the service requested, account status, refund and transaction requirements, security needs, applicable legal obligations and any specific dispute. We delete or de-identify information when it is no longer needed for those purposes.
Local journal records remain until you erase them; exported copies remain where you save them. We maintain connected account records to provide balances, ownership, restoration and support. Account deletion removes the account and its Terms acceptance records, while leaving the local journal until you erase it separately.
After account deletion, we retain limited purchase receipts, settlement records and account-deletion or security records as needed to complete outstanding payments, handle refunds, prevent repeated credits and meet legal obligations. Pending purchase records are assigned a 30-day expiry and temporary deletion markers a one-day expiry. Expiration processing is asynchronous, and an unresolved payment may require separate settlement records; these expiry values are not maximum retention periods for all transaction or security information. Account deletion removes staged import payloads and unnecessary account-identifying import details. A minimal consumed-import marker remains outside the deleted account to prevent the same device funds from being claimed again, including from copied databases. Delayed import, reward or purchase callbacks do not reopen the deleted account.
When a recipient reports a gift message, the text they choose to submit is retained while the report is open. After the report is closed, that text is scheduled for deletion after 30 days and processed by daily cleanup. Processing may take longer during a backlog or service failure. If specific evidence must be preserved for a legal obligation, claim or safety investigation, an authorized reviewer may record a limited hold with a reason, case reference, review date and expiry. Holds require review at least every 30 days and cannot continue past their review or expiry date without renewal. Deleting the reported text does not remove the separate moderation outcome, account restrictions or records needed to prevent abuse. You may request access or deletion through the privacy-request process; applicable rights and exceptions are assessed separately.
Clearing app storage does not delete account records, service logs, previously transmitted diagnostics, support correspondence or rights-request records held elsewhere. Provider logs, backups, gift records and case-specific legal records follow their applicable retention requirements. Contact us to request information or deletion through the privacy-request process.
Your rights and choices
You can use free local features without an account, control local notifications, use available journal export tools and request account deletion. You can turn optional usage and crash reporting on or off at any time in Settings. Depending on the law that applies to you, you may have rights to access, correct, delete or receive a copy of your information, object to or restrict processing, withdraw consent, appeal a decision or complain to a supervisory authority.
Contact support@ohmymori.com or use the Privacy Requests page to exercise your rights. We may request information reasonably needed to verify your identity or authority and will respond within applicable legal deadlines. A journal export does not replace access to account or support information we hold. No purchase or Terms acceptance is required to make a request.
Where EEA or UK data-protection law applies, the legal basis depends on the activity: providing requested account and purchase services, complying with legal obligations, protecting service and account security where a legitimate-interest basis is available, or consent for processing that requires it. Sensitive intention metadata requires any additional safeguards and legal basis required by law. Acceptance of the Terms is not consent to optional or sensitive-data processing. You may ask us about the basis applicable to your information.
Where other data-protection laws apply to you, for example in Switzerland, India, Singapore or Hong Kong, you may exercise the rights they give you through the same routes, and this policy serves as our notice of who we are, what we process and why. Users in India have additional information below.
Information for users in India
If you are in India, the Digital Personal Data Protection Act, 2023 applies to the account, purchase, gift and support information described in this policy as its provisions come into force. We process that information to provide the services you request, to keep them secure and to meet legal obligations, as described above. Your journal stays on your device, and optional usage and crash reporting starts off in India.
You may ask to access, correct or erase your account information, withdraw consent for optional processing, and nominate a person to exercise your rights if you cannot, using Settings or by emailing support@ohmymori.com with the subject “Privacy request”. For a grievance about how we handled your information or a request, email support@ohmymori.com with the subject “Privacy grievance”; we aim to respond within 30 days. If you are not satisfied with our response, you may complain to the Data Protection Board of India through the procedure it provides.
The Act requires verifiable parental consent before a child’s personal data is processed once those provisions apply. When they do, account sign-in, usage reporting and sharing features may become unavailable to users under 18 in India unless that consent can be verified; free local practice and journaling continue without an account.
Changes to this policy and contact
We may update this policy as our services or legal obligations change. We will provide appropriate notice of material changes before new processing begins where required and obtain fresh consent when necessary. Contact support@ohmymori.com (Kiwi Tree, Santa Clara, CA) with questions; our postal identity is Kiwi Tree, Santa Clara, CA, United States.