Mompanian Privacy Policy

Effective date: October 14, 2026

Last updated: October 14, 2026

1. Who we are

Mompanian is a voice-first companion and family-operations app for mothers and caregivers. It is operated by Mompanian, LLC, an Idaho limited liability company (in formation) ("Mompanian," "we," "us").

For any privacy question or request, contact us at mompanian@gmail.com.

This policy covers the Mompanian app (web and mobile), the marketing site, and related services. Mompanian is for adults. Children do not use Mompanian. Section 7 explains how we handle information you choose to add about your children.

2. The short version

• You talk to Mompanian; she remembers what you tell her so she can help carry your day. That memory can include sensitive things: your family, your children, health notes, your voice transcripts, your places.
• We do not store the audio of your conversations. Audio is processed in real time to understand you; we keep the text, not the recording. The one exception is a name recording you choose to make (Section 3.3).
• We never sell your data. Ever, to anyone.
• The most sensitive free-text fields (medical details, personal notes, care-log narratives) are encrypted at rest.
• Everything is private by default. Nothing you record is visible to anyone else unless you explicitly share it, person by person, and the other person must explicitly accept before they see anything.
• You can delete anything you've added at any time in the app, and your whole account and everything in it by writing to us. Deletion is real: after a 30-day grace period (or immediately, on request) your data is permanently purged.
• The usage statistics we keep to improve Mompanian are anonymous (hashed IDs, no names, no message content), and you can opt out.

The rest of this policy spells that out precisely.

3. What we collect

We collect only what you give us or what is needed to run the service.

3.1 Account and settings

• Account identity: your email address, name, and optional avatar, managed through our authentication provider (Supabase Auth), including sign-in with Google where you choose it.
• Preferences: timezone, country, language(s), notification and voice settings, and your data-retention choice.
• Invitations: if you joined Mompanian through a friend's invite, we record who invited you, so we can understand how Mompanian grows. We do not expose your activity to the person who invited you.

3.2 What you tell Mompanian (your content)

• Tasks, reminders, calendar events, shopping lists, and notes you create by voice, text, or upload.
• Family member profiles you create, including, if you choose, profiles of your children: name, relationship, birth date, and free-text notes (notes are encrypted at rest).
• School information you add about a family member: school, grade, teacher and teacher contact, and notes (encrypted at rest).
• Medical information you add about yourself or a family member: conditions, allergies, medications, appointments, vaccination records, blood type, and provider details. The title and details fields are encrypted at rest. This is the most sensitive data we hold, and Section 6 describes the extra protection it gets.
• Schedules and contacts for family members (for example, activity schedules, or a teacher's or coach's contact details). Where you add another person's contact details, you are responsible for having the right to share them.
• Care logs (see Section 6): structured care events (diapers, feeds, nursing, sleep, medications and doses, temperatures, symptoms, potty training, milestones) about a child, another family member, a pet, or yourself, plus growth measurements (weight, height, head circumference).
• Places: saved places and addresses you add, such as home or school.
• Uploads: photos and files (images, PDFs, Word documents) you send Mompanian to read, such as a school flyer. Before a photo is read, we remove its location and camera details. We extract the text (OCR) and suggest tasks and events, which you review. When you confirm, the file you uploaded is deleted at once. We keep the text and, for a photo, a small preview image (no larger than 256 pixels, with location and camera details removed) for up to one year. If you don't confirm, the upload is deleted after 7 days; if you discard it, at once (Section 9). Rash photos in a care log are different: we never read or process them, and they follow their own rules (Section 6.4).
• Your "what you carry" profile: the standing responsibilities, paid-work weekly hours, an optional note about your work (encrypted at rest), and an optional exercise/movement profile you choose to record. This is used only to recognize what you carry; it is private to you and never shared with your family or anyone else.

3.3 Voice

When you talk to Mompanian:

• Your audio is streamed in real time to our speech and AI providers (OpenAI, Google Gemini, and Deepgram; see Section 8) so Mompanian can understand and respond.
• We do not store the audio of your conversations. What we keep is the text transcript of the conversation and short summaries generated from it, so Mompanian can remember context across sessions.
• Transcripts can contain anything you say, including health details about you or your family, and are treated accordingly (Sections 6 and 10).
• Name recordings. You can record yourself saying a family member's name, so Mompanian says it right and recognizes it when you say it. This is the one recording of your voice we keep. Only the person who runs the family circle (you, in your own circle) can play it; other members of the circle can't. When you save it, Deepgram transcribes it once, under no-training terms, to help match the name (Section 8). It is kept until you delete it, that family member's profile, or your account.
• In some jurisdictions, voice data is treated as a biometric identifier. We treat your voice data with that level of seriousness regardless of where you live.

3.4 Calendar (optional)

If you connect Google Calendar, we ask Google for two permissions: read-only access to your list of calendars (calendar.calendarlist.readonly) and access to events (calendar.events). We read events from the calendars you select, and create, update, and delete events Mompanian makes for you only on the calendars you choose to write to. We store the OAuth tokens needed to do this, protected as credentials. We never read events from calendars you have not selected, and you can disconnect at any time, which revokes our access.

Mompanian's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We do not use Google user data to train AI models, we do not sell it, and we do not transfer it to others except as needed to provide the features you asked for.

3.5 Notifications

To send you reminders and updates you ask for, we store push-notification tokens (Expo push tokens on mobile; web-push endpoints in the browser).

3.6 Anonymous usage analytics

To improve Mompanian we keep anonymous, aggregated usage statistics: which kinds of requests succeed or fail, response times, session lengths, stress-level categories at session start and end, and similar measures. This data is engineered to be non-identifying:

• User IDs are hashed (SHA-256) with a salt that rotates monthly, so even the anonymous IDs cannot be correlated across months.
• No names, emails, addresses, or message/transcript content are ever stored in analytics. Any text value longer than 50 characters is rejected automatically, and only fields on an explicit allow-list can be stored at all. Care-log labels and details are never included.
• Raw analytics events are kept 30 days; diagnostic snapshots 14 days; only aggregate daily metrics persist beyond that.
• You can opt out at any time by writing to mompanian@gmail.com. Once you do, opt-out is enforced at the point of collection.

If you submit an in-app bug report, anonymous diagnostic context is attached and you receive a reference code (for example, MOM-A3F7K2). Bug reports follow the same no-PII rules.

3.7 Free tools on the marketing site (no account)

Some tools on mompanian.com, currently the Invisible Load Receipt (mompanian.com/receipt) and Schedule Snap (mompanian.com/school), work without an account:

• Process-and-discard. The text you type or speak (Receipt), or the school documents you upload (Snap), are processed once to generate your result and then discarded. We do not store them, associate them with any account or identifier, or use them to train AI. They pass through our AI providers (Section 8) for that single processing step, under the same no-training terms.
• Client-side personalization. Optional inputs like your name and the number of children you care for are used in your browser only and are never transmitted to our servers.
• Anonymous counts only. We retain non-identifying counters (for example, the number of receipts generated, or the number of line items) under the analytics rules of Section 3.6.
• Waitlist. If you choose to join the waitlist, we store the email address you provide, solely to contact you about access.

3.8 What we do NOT collect

• We do not collect data from children (Section 7).
• We do not store the audio of your conversations. The only voice audio we keep is a name recording you choose to make (Section 3.3).
• We do not collect precise device location in the background. Places exist in Mompanian only because you typed or spoke them.
• We do not buy data about you from anyone, and we do not sell or rent your data to anyone.
• We do not use your content to train AI models, and our AI providers are configured not to either (Section 8).

4. Why we collect it (purposes)

1. To run the service you asked for: understand your requests, create and manage your tasks, reminders, events, notes and care logs, remember context across sessions, and respond with care.
2. To support and protect you: answer support requests, investigate bugs, secure accounts, and meet legal obligations.
3. To improve Mompanian: only in the anonymized, aggregate form described in Section 3.6.

We do not use your data for advertising, and we do not build advertising profiles.

5. Legal bases

• Performance of the service you requested (for example, GDPR Art. 6(1)(b)) for core functionality: your tasks, reminders, calendar, notes.
• Consent (for example, GDPR Art. 6(1)(a)) for optional features and analytics.
• Explicit consent for health and other special-category data (for example, GDPR Art. 9(2)(a); Taiwan PDPA Art. 6 written consent). For information about your children, your consent is given in your capacity as the holder of parental responsibility (Sections 6 and 7). We ask for this consent separately; it is never bundled into general onboarding.
• Legitimate interests, narrowly, for service security and abuse prevention.

You may withdraw consent at any time (Section 11); withdrawal does not affect processing that already happened.

6. Health and care data (including children's health data)

This is the heart of Mompanian and the data we protect hardest.

6.1 What it includes

Medical profiles (conditions, allergies, medications, appointments, vaccinations, blood type), care logs (feeds, sleep, diapers, medication doses, temperatures, symptoms, including where on the body a rash is and what it looks like, potty training, milestones), rash photos you add (Section 6.4), growth measurements, and any health details you speak or type. Much of it describes your children, entered by you, under your authority as their parent or guardian.

6.2 How we protect it

• Separate, explicit consent. Before you first use health and care features, we ask for a distinct, recorded consent specifically for health data. Taiwan users receive the PDPA Article 6 written-consent version. You can use the rest of Mompanian without it.
• Encryption at rest for free-text medical details, care-log narratives, growth notes, and profile notes. Structured fields needed to answer your questions (for example, the medication name, so Mompanian can answer "when was the last Tylenol?") are stored queryably, inside our encrypted, access-controlled database.
• Private by default. No one, not even members of your care circle, can see any of it unless you explicitly share it (Section 6.3).
• Never used for analytics, advertising, or AI training. Health details, medication names, and care-log content never enter our analytics tables, logs, or diagnostics.
• Minimized AI processing. When Mompanian composes a summary (for example, a pediatrician summary), she works from structured fields (types, times, amounts), not your encrypted narratives, unless you explicitly ask for a specific entry's text.

6.3 Sharing care logs (person-to-person grants)

You can share a care-log book (for example, your child's log) with a specific person, such as a partner, grandparent, or nanny, with read or co-write access. How that works:

• A grant goes to one named person, never to a group automatically. Being in your care circle by itself grants zero visibility.
• Nothing is visible until the other person explicitly accepts the share. Acceptance is recorded.
• A share covers only that log book (its entries and growth records). It never exposes the medical card, vaccination records, school information, schedules, contacts, or anything else about the child.
• You can mark individual entries private even inside a shared book.
• You can change or revoke a share at any time, effective immediately. (Honestly: revoking stops all future access, but it can't un-see what someone already saw while the share was active.)
• Entries record who logged them. If a co-writer later deletes their Mompanian account, their entries remain in your book with the attribution anonymized to "a former member."

6.4 Rash photos

You can add up to six photos to a rash entry about your own child (a child in your family, not one you are looking after for someone else) — for example, to show your pediatrician how it has changed.

• Only you can see them. Even if you share that log book with someone, they don't see the photos, or even how many there are. No one at Mompanian looks at them unless you ask us to or the law requires it.
• No AI, ever. We never send them to any AI, image-recognition or text-reading service — ours or anyone else's — and we never use them for analytics, advertising or training.
• What we keep. When you add a photo, we save a new copy with the location, camera and other hidden details (EXIF metadata) removed, and no larger than 2,560 pixels on its longest side. The file you uploaded is discarded. Photos are kept in a private storage area. Each time you open one, the app gets a link that stops working within 5 minutes.
• How long. Until you delete the photo, the rash entry, your child's profile, or your account. Deleting removes the photo from our storage straight away (for your account: when it is purged — after the 30-day grace period, or at once if you ask). Diaper-area photos are also deleted automatically 30 days after you mark the rash cleared; until then they stay, because they are what you are tracking.
• Backups. Our backups never hold the photos themselves, so a deleted photo cannot be brought back. A record that a photo existed (not the photo) may remain in our encrypted database backups for up to 7 days after you delete it, and then it is gone.
• If someone you share with deletes the entry. A person you've given co-write access can delete the entries they wrote. If one of those entries has your photos, the photos are not deleted: we keep them for you, and only you get a note in your Inbox. Choose Keep to bring the entry back with its photos, or Delete photos to delete them for good. They stay until you choose, except that diaper-area photos are still deleted 30 days after the rash was marked cleared. The person who deleted the entry is never told that it had photos.
• Your own copies. Choosing a photo in Mompanian doesn't change the original in your phone's photo library, and deleting it in Mompanian doesn't delete that copy. If you share a photo — for example with your pediatrician — using your device's share options, that copy leaves Mompanian and is handled by whoever or whatever you sent it to.

7. Children

Mompanian is an adult-only service. You must be at least 18 to create an account. Children do not use Mompanian: they never log in, never speak to it, and never provide information to it. We do not knowingly collect personal information from anyone under 18, and we do not direct any part of the service to children. If we learn that a child has created an account, we will delete it.

What Mompanian does hold is information about your children that you, their parent or guardian, choose to enter (profiles, school details, health and care records) so the app can help you care for them. By entering information about your child, you confirm that you are the child's parent or legal guardian and that the information is yours to share. That information receives our highest protection tier (Section 6), is private to you by default, and is deleted when you delete it, the child's profile, or your account.

8. Who processes your data (sub-processors)

We never sell your data. To run Mompanian, these service providers process data on our instructions:

When you speak or type something that includes health details, that content necessarily passes through our AI providers (OpenAI and Google) for transcription and response, and structured care-log fields may be used to compose summaries you request. We configure our AI providers so that your content is not used to train their models. Providers keep it only as long as needed to run the conversation and, for a limited period, to detect abuse, under their terms.

International transfers. Our application is hosted in Singapore (Vercel) and our providers may process data in the United States. Where required (for example, for EU users), we rely on appropriate safeguards such as Standard Contractual Clauses.

9. How long we keep it (retention)

Soft-deleted items (for example, a care-log entry you removed) are permanently purged when you delete the related profile or your account. The one exception is rash photos: when you delete the entry, its photos are deleted for good straight away. When someone you share with deletes it, the photos wait for your choice instead (Section 6.4).

10. Security

• Encryption in transit (TLS) everywhere; encryption at rest for the database and stored files, and additionally field-level encryption for sensitive free-text (medical details, personal notes, care-log narratives, work note).
• Files you keep with us are held in private storage. The app opens them with links that stop working within 5 minutes.
• Anonymized analytics by construction (hashing, allow-lists, length caps).
• Access controls: your data is scoped to your account; shared data is enforced at the data-access layer, not just the interface.
• We are a small team and we say this honestly: no system is perfectly secure. If a breach affects your data, we will notify you and the relevant authorities as required by law (including Taiwan PDPA and GDPR breach-notification rules).

11. Your rights

Wherever you live, we give you the same core rights:

• Access and portability: see your data in the app; request a copy by emailing mompanian@gmail.com.
• Correction: edit anything in the app.
• Deletion: delete any item or any family member profile in the app, and your entire account by emailing us. Account deletion permanently purges everything after a 30-day grace period, or immediately on request.
• Consent withdrawal: withdraw health-data consent (in Settings, or by email); care and health features stop, and you can have the health data deleted.
• Analytics opt-out: email mompanian@gmail.com.
• Complaint: you can complain to your data-protection authority (Taiwan: the Personal Data Protection Commission; EU: your national supervisory authority).

California residents (CCPA/CPRA): we do not sell or share your personal information as those terms are defined in the CCPA, and we have not done so in the preceding 12 months. We honor the access, deletion, correction, and non-discrimination rights described above.

Taiwan residents (PDPA): you have the rights of inquiry and review, copies, supplementation or correction, cessation of collection, processing or use, and deletion (PDPA Art. 3). For health data, we collect only with your separate written (electronic) consent, which you may withdraw at any time.

EU/EEA residents (GDPR): the rights above implement Arts. 15–21 (access, rectification, erasure, restriction, portability, objection). Our legal bases are in Section 5.

12. Changes to this policy

If we change this policy in any meaningful way, we will tell you in the app before the change takes effect and ask for fresh consent where the law requires it. Each version is dated and archived; your consent is recorded against the specific version you accepted.

13. Contact

Mompanian, LLC (Idaho, in formation)

Privacy requests: mompanian@gmail.com

Support: support@mompanian.com