Komorebi · Character chat, voice & games
Privacy Policy
Updated 25 October 2026
This policy explains how Komorebi handles information in its web app and iOS application when released. For questions or privacy requests, contact komorebi-support@googlegroups.com.
Information we use
- Account information: the identity and verified email supplied through sign-in, your nickname and age-eligibility confirmation. We do not receive your Google password.
- Conversations: messages, AI replies, saved memory notes and call transcripts when synchronized.
- Usage: check-ins, daily allowances, product events and referral information associated with those events.
- Billing: customer, transaction and subscription references and payment status when billing is used. Full card details are handled by the payment provider.
- Security: login sessions, short-lived rate-limit records and basic request information processed by our infrastructure.
Why we use it
We use information to sign you in, generate replies, preserve conversations, apply allowances, deliver voice features, manage membership, respond to support requests and protect the service. Conversations and memory notes are private account records, not public posts. Conversation content is not sent to our website analytics service.
Sign-in and service providers
Google, Apple and Supabase Auth provide the sign-in methods available in each client. The iOS app keeps an opaque session token in the device Keychain. Apple authorization tokens are encrypted server-side so we can revoke authorization when an Apple-login account is deleted. Sites and Cloudflare provide hosting and app storage. Some existing test accounts may use ChatGPT sign-in.
DeepSeek receives the current text-chat request, character instructions, nickname, memory note and recent conversation context to generate a reply. Fish Audio receives text you choose to play aloud. Its call service also processes microphone audio, transcripts and character conversation context using the speech and conversation services it operates. Calls use a pseudonymous account reference rather than your Google email.
Providers process requests under their applicable terms and may process information outside your country. The configured free voice-playback tier may use requests to improve its models. We do not promise zero retention by every provider. Contact us if you have questions before using a feature.
Paddle or Freemius, as identified in the checkout and receipt, handles payment details, receipts and subscription records when payments are enabled. For Freemius checkout, we use the verified email from your Google sign-in to associate a purchase with your app account. Conversation text, memory notes and call audio are not sent to the payment provider. Payment status is checked server-side, with a cache of up to 60 seconds. See Paddle’s Privacy Policy or Freemius’ Privacy Policy for the provider handling your purchase.
iOS purchases and account deletion
For Apple in-app purchases, Apple handles payment details and receipts. We use account-bound purchase identifiers to verify subscription access with Apple, including expiry and refunds; chat content and microphone audio are not sent to Apple for billing. Use in-app Restore Purchases after signing into the same Komorebi account used at purchase. The iOS app offers deletion of your login account and private product data. Necessary financial reconciliation references may be retained. Apple subscription renewal must be canceled separately. App-local preferences include character-blocking choices and display settings. The native app has no advertising identifier integration.
Microphone and calls
You choose whether to allow microphone access. Calls stream audio while connected; you can mute or hang up, and closing the call panel ends the call. We disable call-audio recording and do not retain original call audio in the app. The call provider keeps metadata and transcripts under its policies. Final call text is synchronized to chat history when available; a connection issue may delay this.
Optional browser dictation uses speech-recognition support from your browser or device. Typed messages remain available instead.
Cookies, preferences and analytics
Secure cookies keep you signed in; a login session can last up to 30 days. Your browser stores preferences such as character, sound and motion settings. Cloudflare Web Analytics measures visits, page views, referrals and performance. We do not send chat text, voice text, memory notes or account identifiers to that analytics service.
Retention and your choices
Chat history, memory notes and product records remain associated with your account until deleted or deletion is requested, subject to billing and other records we must retain. Use Delete my chat and account data in account settings for accounts without linked billing; end an active call first. For billing-linked accounts or deletion of the underlying sign-in identity, contact support. Provider records and backups may have separate retention periods.
You can ask about access, correction, deletion or other rights that apply to you. Use your account email where possible; we may need to verify ownership. Do not email passwords, card numbers or identity documents unless an appropriate secure process has been arranged.
Eligibility and contact
The service’s eligibility rule is explained in the Terms. If you believe an ineligible person’s information has been submitted or have a privacy concern, contact komorebi-support@googlegroups.com.
Android application and Google Play
When released, the Android app uses the existing Google sign-in flow in your browser. An opaque login session is encrypted using Android Keystore and app backups are disabled. Conversations are associated with your Komorebi account on our backend, not solely stored on your phone. Playing a voice reply sends its text to our voice service; microphone permission is requested only for a call. Calls do not save raw recordings, but live audio is transmitted to the voice provider for processing and available transcripts may be saved.
Google Play processes Android in-app payments. We receive and store encrypted purchase tokens, an opaque app-account identifier, subscription status and expiry to verify membership and prevent one purchase being claimed by multiple accounts. We do not receive full payment card details. This app contains no advertising SDK or advertising-ID collection. Public website pages may use Cloudflare analytics as described above. See account deletion instructions for the in-app and external request pathways. Necessary financial records may remain after deletion, separately from removed conversations.