Consumer Health Data Privacy Notice

MeowCouncil · Version 2026-10-26-v2

Scope and contact

Effective date: 26 October 2026. This notice supplements the Privacy Policy for mood, wellbeing and other information that may qualify as consumer health data under applicable law. MeowCouncil is operated by Siddharth Pandey in India. Contact sidpandey12@gmail.com for privacy questions and requests. Not every ordinary mood selection is necessarily health data, but the content and inferences described below can reveal physical or mental health status. Calling the app entertainment or not medical care does not remove applicable data-privacy rights.

Categories and sources

Sources are the information you provide, generated responses and summaries, and labels or patterns derived from that information. Depending on what you submit or save, categories can include moods; wellbeing preferences and reasons for using the app; descriptions of stress, symptoms, health conditions, treatments or medication; reflection answers; generated advice or summaries; and inferred trigger labels or patterns. They can be linked to your Firebase account or otherwise identify you through the text. We do not require medical records, connect to Health Connect or read health sensors in the current app. Reminders are stored locally and can contain health information if you put it in their text.

Purposes and current processing

We use submitted information to generate the response or reflection you request, display it to you, and store the content you explicitly choose to save. Onboarding answers are retained as account preferences. Saved chats currently receive simple trigger labels, and legacy endpoints retain the history-analysis capability described in the Privacy Policy, although the current app does not automatically request it. Content can also be processed as necessary to handle a support or privacy request or protect the service. We do not sell personal information or use journal content for targeted advertising. These descriptions disclose current behavior; they do not establish that every use is necessary or replace consent where the law requires it.

Recipients and disclosures

Google Firebase/Google Cloud process account-linked content for our backend and database. OpenAI receives AI request content and, for legacy history analysis, selected saved evidence. Read What we send to OpenAI and why and OpenAI processing and retention in the Privacy Policy for the scope and limits of that handling. RevenueCat and Google Play receive account/purchase information, and Resend receives transactional email information; we do not deliberately send them your journal text, reflection answers or mood history through those integrations. If you contact support with sensitive information, that information is also handled through the support email service. Local reminder content is passed to your device operating system, and selected exports are passed to recipients or services you choose. Necessary disclosures can also occur as required by law or to protect users and the service. A provider's treatment as a processor or third party depends on the relevant law and actual arrangement, not only its name.

Choices, consent and withdrawal

You may choose not to submit optional personal text, not save generated content, delete reminders and use features that do not require your journal content, such as Vybe. Not saving does not stop processing of an AI request already submitted. Where applicable law requires consent for a purpose, that consent must be specific and affirmative; agreeing to general Terms is not blanket consent to sensitive-data collection or disclosure. Some laws permit processing necessary to provide a service you request without separate consent. This notice does not declare that exception applies to every use or country. There is not currently a dedicated in-app sensitive-data consent or withdrawal switch. Contact sidpandey12@gmail.com to withdraw consent where relied on or request that particular processing stop; we will assess and handle the request under applicable law and explain any lawful limits.

Access, deletion and appeals

Email sidpandey12@gmail.com to request access to covered information, applicable recipient information, deletion, or to challenge a privacy-request decision. We verify ownership without asking you to send passwords or one-time codes. You do not need to create a new account to make a request. Current in-app Delete saved data leaves onboarding answers intact; broader deletion requests can be made by email without requiring account closure. Where Washington's My Health My Data Act applies, rights include access, withdrawal and deletion, requests generally must be handled within 45 days subject to permitted extensions, and a refusal can be appealed. Identify an appeal in your email; where required, our response will explain the outcome and how to complain to the Washington Attorney General. Other applicable rights and deadlines are not limited by this notice.

Retention, security and deletion limits

The Privacy Policy describes account retention, local storage, security and deletion. Covered information is not made anonymous simply by replacing an email with an account identifier. Account deletion processes our account tree and requests RevenueCat deletion, while manual-backup cleanup and relevant provider follow-up require operator action. Deleting our database does not automatically erase provider-held records. We will handle applicable deletion obligations, including required provider notifications, under the law; no universal immediate-erasure guarantee is made. Exported or recipient-held copies and offline device storage cannot all be remotely recalled.

Current controls and changes

Current controls include explicit Save actions, clearing saved data and current-device reminders, account deletion and privacy requests by email. A dedicated Privacy & data menu, comprehensive personal-content erasure without account closure, automatic removal of unused trigger labels, additional consent controls and in-app AI reporting are not made available merely by this notice. Feature-specific disclosures will be updated when corresponding controls are implemented; do not assume a planned control already exists.