1. Scope and contact
XU JUNJIA operates nawacares in an individual capacity and is responsible for the handling of personal information described in this policy. This policy covers the nawacares browser service and public pages at nawacares.com, app.nawacares.com and nawacares.luwork.one. For privacy questions or requests, contact XU JUNJIA at hello@nawacares.com.
The web app addresses use separate browser storage and host-only sign-in cookies. Opening another address does not automatically import writing or sign you in. Linked external apps and websites have their own data practices.
2. Writing saved in your browser
nawacares uses browser storage for chats, journal entries, drafts, mood check-ins, plans, profile details and preferences such as language, appearance and sound. These records can remain after you close the page. They are not an encrypted vault; someone with access to your browser, device or exported files may be able to read them.
Optional account login separates local guest records from records created in each signed-in account. Switching accounts does not silently import guest writing. Chats and journals are not automatically synced to other devices. Exported backups are files you control and may contain private writing.
3. Information sent when you use AI
When you request a conversation reply, discussion starters, a reframe, an action suggestion or another AI feature, the app sends the information needed for that request to the nawacares backend and its AI provider, DeepSeek. Depending on the feature, this can include your text, recent conversation turns, selected feeling and intensity, theme, card or tool context, language and conversation style. If optional memory is enabled, a limited selection of relevant accepted memories may also be included.
The service processes this information to produce the requested response. It does not save a complete cloud chat or journal history in the app database. Providers may process or retain request data under their own terms and policies; browser-local history is not a promise that text you send to an online feature never leaves your device.
XU JUNJIA is responsible for this notice and for the app’s handling of personal information described here. The provider’s direct-service privacy notice is not a substitute for our explanation of this app. We do not claim an upstream zero-retention or no-training arrangement that has not been verified.
AI-generated topics and suggestions are not automatically accepted as facts about you. Proposed memories require review before they become saved memories. Do not send information that you do not want processed by the online feature.
4. Optional accounts
Email/password accounts use Supabase Auth. It processes account information such as email, credentials, verification and recovery requests to provide login. Our backend verifies the account identity and sets secure, HttpOnly session and refresh cookies. Passwords and provider tokens are not stored in the app’s local writing records.
Where Continue with Google is available, choosing it starts the external Google/Supabase authorization flow. It requests basic identity information, not access to your Gmail inbox. Merely reading a public help page does not start Google sign-in.
Confirmation and recovery email delivery uses our configured email service, Resend, through Supabase. Mirror memory starts on for new accounts. Signing in to an existing account keeps its current memory setting. Notifications, microphone access and advertising have separate controls.
5. Optional reviewed memories
You, reflected is separate from chat history. Memory starts on for new accounts and off for guests. While memory is on, the backend can process eligible new conversation text to propose short memories for you to review. Saved memories are stored in Supabase. A verified account is scoped using a hash of its account identifier; guest memory uses a separate browser capability. Signing in does not automatically import guest memories or old transcripts.
The feature supports up to six accepted memories across values, current situations and communication preferences. Sensitive memories require separate consent. You can edit, hide or delete memories and turn recall off. Hidden, expired and unconsented sensitive entries are excluded from recall; at most two relevant accepted memories are supplied to a reply.
Current-situation entries expire from recall after 30 days and remain visible for review until deleted. Other accepted memories remain until you remove them or the profile is removed. Turning recall off is different from deleting saved memories. Use the visible deletion controls when you want to remove them.
6. Voice features
The microphone starts only after an explicit voice action. Browser speech recognition produces a transcript; depending on your browser or operating system, recognition may use that provider’s online service. nawacares does not promise that browser recognition happens entirely on your device.
When a finalized voice turn is sent, its text is processed as conversation input. For requested spoken replies, the backend may send the reply text to Microsoft Azure Speech to return audio. Device speech synthesis is the fallback and may have its own processing rules. The nawacares speech route does not store generated audio as a recording library.
You can pause voice, switch to typing, stop reply playback or revoke microphone permission in your browser. Background sound is a separate saved preference; enabling it does not grant microphone access.
7. Hosting, security and usage information
Vercel hosts the website and backend. Hosting and network services process request information such as IP address, browser/request headers and operational events to deliver and protect the service. The app uses short-lived hashed identifiers for security counters and aggregate request, token-cost and capacity measurements. Hashing is not the same as making information anonymous.
Tool evaluation in the app is limited to local aggregate counts and duration information; it is not private-writing analytics. We do not need journal text or a complete conversation transcript for aggregate capacity reporting. Hosting providers may retain operational logs according to their configured services.
Usage allowances are recorded in Supabase using keyed, pseudonymous account or guest identifiers, daily reply/cost counters and cloud-voice character totals. These records do not contain your messages, journal text, email address or generated audio. A separate keyed network counter limits guest abuse; the hosting platform still receives network information.
Payments and allowances
Paid checkout is currently unavailable. When you make a purchase through Waffo Pancake after checkout opens, Waffo acts as the merchant of record and handles the payment and the contact and billing details you provide at checkout. Waffo uses this information to process orders, manage subscriptions, issue receipts and handle payment support, refunds and disputes. Waffo’s privacy policy explains its processing and retention.
nawacares may receive and retain limited transaction details, such as order or subscription references and payment status, to provide paid access, respond to support requests, prevent fraud and reconcile payments. nawacares does not collect or store full card numbers or send your chats, journals, mood records or memories to Waffo for billing. Waffo and nawacares may retain payment records as needed for these purposes and applicable legal obligations.
9. Your controls and retention
Use Settings → Backup & restore to export local records, restore a backup or clear the supported local history. Individual records and memories have their own management controls. Clearing browser site data can remove additional local preferences and drafts and can end your session; export anything you want to keep first. Removing a local chat does not automatically remove a separately accepted backend memory, and deleting a memory does not delete your local chat.
Local records remain until removed through the app or browser. Backend memory follows the rules described above. Active backend deletion does not establish an immediate purge from provider-managed backups, security logs or data already processed by an external provider. We do not promise a fixed backup purge schedule that has not been configured.
For account deletion, access, correction or another privacy request that is not available through the visible controls, email hello@nawacares.com. We may need information sufficient to verify the request. There is no automatic account-deletion button currently claimed by this notice.
Daily allowance records and one-time cloud-voice trial totals are currently retained in the backend; no automatic purge schedule is claimed. Trial totals help prevent repeated free trials. Contact us for deletion requests; provider-managed backups may retain removed data according to their own settings.
10. External processing and changes
Our hosting, authentication, AI, speech and email providers may process information in countries other than yours under their service arrangements. This notice does not claim that all processing stays in one country. Review the linked provider information before sending material with requirements those services cannot meet.
If service features or data handling change, we will update this page and its date. Any new permission or optional feature still needs its own appropriate action or consent; a policy update does not silently turn on memory, microphone use or ads. Contact hello@nawacares.com with questions.