2.1 Personal & Account Data
What: Full name, display name, email address, date of birth, family role (e.g. Parent, Child, Grandparent), preferred language, and optional phone number.
How: Provided directly by you during account registration or profile setup.
Why: To create and secure your account, personalise your experience, enforce minimum age requirements, and support WhatsApp-based messaging features (phone only).
2.2 Profile Photo
What: An optional profile image you choose to upload.
How: Uploaded voluntarily via the in-app camera or photo library.
Why: To display your identity to members of your family circle.
2.3 Authentication Credentials
What: Hashed password (we never store plaintext passwords), or third-party identity tokens from Apple Sign-In and Google Sign-In, or a one-time magic link token for passwordless sign-in.
How: Generated at sign-up or sign-in and processed through Supabase Auth.
Why: To authenticate you securely and maintain your session.
2.4 Emotional & Mood Data
What: Your daily mood check-in score (numeric rating from 1–5 or equivalent emoji), optional private text notes accompanying a check-in, and your check-in history over time.
How: Submitted actively by you each time you complete a daily check-in.
Why: To display your emotional state to family members, generate AI-powered connection suggestions, and provide insights about family wellbeing over time. Private notes are only used for AI suggestion generation if you choose to include them.
2.5 Family Circle Data
What: Family name, unique family identifier, member list and roles, invite links and QR codes, and family activity timestamps (last check-in, last active).
How: Created when you establish or join a family circle; invite links are generated on demand.
Why: To operate the core family connection functionality — showing family status, enabling moment sharing, and managing circle membership.
2.6 Location Data (Precise GPS)
What: Real-time GPS latitude and longitude, updated at regular intervals while sharing is active.
How: Collected from your device's location services only when you explicitly opt in to Family Map location sharing. Location is transmitted in real time via Supabase Realtime channels.
Why: To display your position on the Family Map to circle members. Location is never stored permanently on our servers — it exists only in the active real-time channel and is discarded when you stop sharing or close the session.
Note: You can disable sharing at any time or activate Ghost Mode to hide your position without fully disabling the feature.
2.7 Voice & Audio Data
What: (a) Voice recordings you create and send as in-app voice notes to family members. (b) Your microphone audio streamed in real time during AI voice conversation sessions.
How: (a) Recorded in-app and stored in Supabase Storage. (b) Streamed to ElevenLabs via their SDK during active voice sessions; Hearth does not retain the raw audio after the session ends.
Why: (a) To deliver voice messages to family members. (b) To enable real-time AI voice conversations via the ElevenLabs platform.
2.8 Moments & Media Content
What: Photos, images, captions, and text you publish to the Family Moments feed.
How: Uploaded voluntarily by you within the app.
Why: To share family memories and updates within your private circle. Moments are visible only to members of your family circle — they are never public.
2.9 AI Interaction Data
What: The subset of mood data (score and optional notes) that you choose to include when requesting an AI connection suggestion; AI-generated suggestion text stored to personalise future recommendations.
How: Transmitted securely to OpenAI's API on your request; suggestions stored in Supabase.
Why: To generate personalised, context-aware connection suggestions to help you stay emotionally connected to your family.
2.10 Device & Technical Data
What: Device model, manufacturer, operating system version, app version, IP address, time zone, locale/language settings, and device push notification token.
How: Automatically collected by the app runtime, Supabase, and Firebase SDKs at app launch and during sessions.
Why: To ensure compatibility, deliver push notifications, troubleshoot crashes, and improve performance across device types.
2.11 Usage & Analytics Data
What: In-app event names (e.g., "check_in_completed", "moment_posted"), screen views, feature interaction counts, session duration, and user flow paths — all without directly identifiable personal details.
How: Automatically collected via Firebase Analytics and processed according to Firebase's privacy standards.
Why: To understand how features are used, prioritise improvements, and measure product health — without tracking individuals.
2.12 Crash & Error Logs
What: Stack traces, error messages, device model, OS version, app version, and an anonymised installation identifier at the time of a crash.
How: Automatically captured by Firebase Crashlytics and Sentry when the app encounters an unexpected error.
Why: To identify, diagnose, and resolve stability issues quickly.
2.13 Subscription & Payment Data
What: Your current subscription tier, subscription status (active/expired/ cancelled), transaction identifiers issued by Apple App Store or Google Play, and a RevenueCat customer identifier linked to your account.
How: Passed from Apple/Google to RevenueCat on purchase; Hearth receives only tier and status — never raw payment card details.
Why: To gate premium features, manage entitlements, and handle billing inquiries.
2.14 Cookies & Tracking Technologies
The Hearth mobile app does not use browser cookies. The Hearth website (hearth.family) uses minimal session cookies required for navigation only. We do not use advertising trackers, third-party pixels, or persistent tracking technologies on the website. Analytics on the website, if any, are limited to privacy-respecting, aggregate-only tools.