Privacy Policy

Effective October 6, 2026

PreggyAI ("we", "us", "our") is a pregnancy companion app. This policy explains what information the app collects, how it is used and protected, how long it is kept, and the choices and rights you have. It applies to the PreggyAI mobile app and this website. Questions any time: support@preggyai.online.

The short version: we collect only what the app needs to work, we encrypt the sensitive parts, we never sell your data, we show no ads and use no advertising or analytics trackers, and you can delete your account and remove your personal content from our active systems from inside the app at any time.

1. Information we collect

Account information. You sign in with Apple or Google. We receive a unique account identifier and, depending on the provider and your choices, your name, email address, and profile picture. We do not receive your password.

Account email and communication choices. We may use the email address from your sign-in provider to send service-related account messages, such as a material Terms or privacy change, a non-promotional change to an App feature, a PRO welcome, or another necessary account notice. Each message includes an unsubscribe link. If you unsubscribe, we keep the fact and time of that choice so future account-email campaigns exclude you. For each campaign we also keep a short delivery record containing your internal account identifier, the campaign identifier, whether the send was accepted or failed, and the relevant times; it does not store the email body or a second copy of your email address. A bounded campaign-coordination record keeps the campaign identifier, audience and purpose, recipient count, preparation status and relevant times, and a one-way hash of the content. While preparation is incomplete it also holds a one-way hash of the initial recipient set; that recipient-set hash is removed before sending begins. The record does not contain the email body or an email address.

Profile information you provide. Your chosen name, due date, your baby's nickname, your partner's name (if you enter one), your time zone, the country and state/province you tell us you live in (asked once at setup, unverified, and used to honour where the app is offered — see section 8 — and to pick which measurement units your app starts out in, which you can change at any time in Settings, and to show a persistent AI-identity notice in chat for users who select California, New York, or Oregon), and app preferences such as your measurement units, notification settings and the baby's personality style.

Your adult-eligibility confirmation. PreggyAI is for adults, and at setup we ask you to confirm that you are at least 18 and have reached the age of majority where you live. We record only that you confirmed and when — we do not ask for or store your date of birth, and we do not verify your age against any document or external service. The confirmation is kept with your profile until you delete your account.

Your health-data consent record. Before creating a pregnancy profile, we ask you separately to consent to the sensitive-data collection and use described in this policy and our Consumer Health Data Privacy Policy. We record the version you accepted and the server time of acceptance so we can demonstrate the choice you made. We keep this bounded record with your profile until you delete your account.

Health information you choose to enter. Symptoms, moods, weight entries, kick counts, contraction timings, appointment details, notebook entries (for example a birth plan), bump photos, and the messages you exchange with the AI baby character. This is sensitive information, and we treat it that way — see sections 3 and 4.

Activity data from a connected health app (optional). If you choose to connect Apple Health or Health Connect, we import daily activity summaries only — daily step totals and workout sessions (type and duration) — from the categories you authorize. We keep a rolling window of the most recent 14 days; older entries are replaced automatically on each sync. Raw sensor samples, heart rate, and locations are never read or collected. Imported activity data is used only for the activity-aware features described in section 2, and disconnecting the health app in Settings deletes our copy.

AI-generated summaries and memories. To personalize your experience, the app creates short summaries, memories, and contextual inferences from conversations (for example, remembering your baby's nickname or a health or mood detail you shared). They can refer to your baby, partner, or other people you mention. They are personalization aids, not clinical findings, and can be wrong. They are stored encrypted, used only to provide the service, and queued for deletion with your account subject to the recovery limits in section 6.

Purchase information. If you buy the optional PRO plan, the purchase is made through Apple's App Store or Google Play. We never see or store your payment card details. We do receive, and store against your account, the fact that a purchase is active, which product it was, and when it expires or renews, so the app knows to unlock PRO. To manage this we use RevenueCat (see section 10): your PreggyAI account identifier is sent to them, and they hold your purchase history against it. Deleting your PreggyAI account does not automatically erase store or RevenueCat purchase records; see sections 6 and 8. If you redeem a promotional code instead, we store the code you used and the access it granted.

Technical information. A push-notification token for your device (if you enable notifications), your app version, and operational logs needed to run, debug and secure the service — see section 6 for what these contain and how long we keep them. We do not collect advertising identifiers, and the app contains no advertising or third-party analytics SDKs.

Usage records. Our own servers keep a few counters and times about how you use the app, stored with your account: when you last opened it and how many times you have, when you last sent a chat message and how many you have sent, and when you last used each feature (for example the kick counter, the notebook, or passing a message to a partner). Our operational logs also note a handful of account milestones — that an account was created, sent its first chat message, reached a free-plan limit, or started PRO — against the internal account identifier. None of these contain what you wrote or logged, and they are produced by our own servers, not by an analytics company or by software in the app.

Feedback and bug reports (optional). When you send feedback or report a bug from Settings, we receive your message along with your account identifier and app version. You can also choose to attach diagnostic information by leaving the "Include diagnostic info" checkbox ticked. That attachment is a technical snapshot of the app on your device — app version and build, device platform and operating-system version, your settings and feature flags, your plan and trial status, and the number and scheduled times of any queued notifications — together with the names of the last 10 actions you performed in the app, meaning the screens you opened and the buttons you tapped. It does not include your name, your due date, or the contents of your messages, notes, photos, or notifications. Clear the checkbox before sending and none of it is collected. We use these reports only to reply to you and to diagnose and fix problems.

Reports about a particular AI response (optional). Tap an AI message to reveal its Report action. A report includes that AI response, the reason you choose, your account identifier and app version, and any note you add. The form can also show the nearest preceding message you sent, which may contain pregnancy or health information, but its separate Include my preceding message checkbox is off by default and we receive that message only if you check it. This report does not attach the general diagnostic snapshot. Before sending, the form shows which message content will and will not be included. We use the report only to investigate and fix safety and quality problems and to reply where appropriate.

2. How we use information

We use your information only to provide the app's features: powering the AI conversation, showing your week-by-week progress, storing the entries you make, sending the notifications you have enabled, enabling Partner Mode sharing you have chosen, powering activity-aware features when you connect a health app (for example, the AI baby celebrating your steps and workouts, or gentle activity-related suggestions to you — imported activity data is not shared with a partner you have linked), applying fair-use limits, understanding in aggregate how the app is used (for example how many people start chatting, reach a free-plan limit, or choose PRO) so we can improve it, sending the service-related account emails described above, replying to feedback and bug reports you send us, investigating the AI responses you choose to report, fixing the problems they describe, and keeping the service secure and reliable.

We do not sell or rent your personal information, share it with data brokers or advertisers, or use it for advertising of any kind. We do not use your personal content to train AI models.

3. AI processing

The AI conversation is powered by large language models running on Amazon Web Services (AWS), through Amazon Bedrock and its managed model platform. Some of these models are developed by AWS; others are developed by third parties (for example, OpenAI) but run on AWS's own infrastructure rather than the developer's. In every case your messages and relevant context (such as your pregnancy week and the memories described above) are processed within AWS to generate each reply: your content is not sent to, or shared with, the third-party model developers, and under the AWS terms that apply to this processing it is not used to train any model. AWS may briefly retain request content solely to detect and prevent abuse of its own service, under strict access controls and without sharing it with the model developers; we have not enabled any setting that would share your content with a model provider. The app attempts to ground answers to health questions in published guidance from public health sources, but not every answer is based on a source, and a source link shown next to an answer is chosen automatically by the AI and may be inaccurate or mismatched — see sections 4 and 5 of the Terms of Use. The app is designed and offered for general information, companionship, and self-tracking—not for diagnosis, treatment, clinical monitoring, or clinical decision-making—and does not provide medical advice.

4. How your information is protected

All communication between the app and our servers is encrypted in transit (TLS). Data stored on our servers is encrypted at rest, and the most sensitive content — your chat messages, your notebook entries, the text you enter when you log a symptom, an appointment or a weight (including the clinician and place for an appointment), the activity data imported from a connected health app, the AI-generated summaries described in section 1, the concerns one parent's baby chat queues for the other described in section 7, and the contents of notifications we generate for you — is additionally encrypted at the field level with a dedicated managed key, bound to your account. Photos are stored privately and served only through short-lived, expiring links.

On your device, the app keeps a local copy of recent content — chat messages, your profile, tracker and notebook data — so it opens quickly and works offline. That local copy is not separately encrypted by us. It is held in the app's private storage, which the operating system keeps isolated from other apps, and it is protected by your device passcode or biometrics and by our optional app lock (Face ID / fingerprint / PIN). On Android we exclude it from Google's cloud backup, so it is not copied to your Google account. If you back your device up yourself, or use your platform's device backup, that backup may include this local copy — how it is protected is governed by your device and your backup provider's settings, not by us.

No system is perfectly secure. If we learn of a breach of security affecting your personal information, we will notify you and the relevant authorities without unreasonable delay, and no later than 60 days after we discover it.

5. Where your information is stored

PreggyAI is offered in Canada and the United States. If you are in Canada or the United States, your information is stored and processed in the United States — the Amazon Web Services servers that hold your information and the AI that generates replies both run there.

If you live in Canada (where PreggyAI is based), your information is therefore transferred to and processed in the U.S., which may have different data-protection laws than your country.

Wherever your information is processed, the same protections described in this policy apply. Where your information is stored is never used to decide what protections or rights you get.

6. How long we keep information

Entries have built-in retention limits, after which they are automatically deleted from our systems:

• Chat messages: 240 days
• Imported activity data (daily steps and workouts): rolling 14 days, replaced on each sync
• Symptoms, kick sessions, and contraction timings: 1 year
• Moods: 400 days
• Concerns queued between linked parents (section 7): 7 days, or sooner if either of you withdraws, unlinks, or the baby has already checked in about it. Automatic clean-up can lag by up to two days after that, so a row may sit unreadable for a little longer than the seven-day rule allows — it is never delivered past seven days.
• Appointments: 2 years after the appointment date
• Weight entries: 3 years
• Profile: kept until you delete your account
• Usage counters and last-used times (section 1): kept with your profile until you delete your account. The account milestones are part of our operational logs, below
• Health-data consent record (accepted version and server timestamp): kept with your profile until you delete your account
• Account-email unsubscribe choice: kept until you delete your account
• Account-email delivery records (campaign identifier, outcome, and times, but no email body or second copy of your email address): 400 days
• Account-email campaign-coordination records (campaign identifier, audience, purpose, recipient count, preparation status and times, a one-way content hash, and a recipient-set hash only while preparation remains incomplete): 400 days
• Notebook entries and photos on your phone: kept until you delete them or your account. We do not delete anything on your device.
• Notebook entries and photos backed up to the cloud — backing up is a PRO feature. If your PRO subscription ends and you do not renew, those cloud copies become eligible for removal from active cloud storage 30 days after your PRO access ends. A daily deletion sweep normally removes them on or shortly after day 30, although a retry or processing backlog can make active-system removal finish later. Bounded disaster-recovery copies may remain for the periods explained below. This does not touch your phone: the App downloads a copy of every backed-up photo and note onto your device and keeps it there, and it goes on doing so after your subscription ends, so what the App shows you is unchanged. The App tells you before this happens and counts down the 30-day grace period
• Notification history — a record of which notifications we sent you and when, including the message text. Some of those messages refer to things you logged, such as a symptom or a kick session, so the text is stored encrypted: 1 year
• Device notification tokens — the address your phone gives us so notifications can reach it. It does not identify you by name and is refreshed each time you open the App: 60 days
• Operational logs: up to 12 months
• Housekeeping position markers — when our routine tidy-up jobs work through accounts in batches, they save their place so the next run continues instead of starting over. A saved place is a single internal account identifier and nothing else: no name, no email address, and none of your content: 2 days
• Account deletion records — when you delete your account we keep one small record so that any device still signed in to it is refused rather than served. It holds an internal account identifier, the date of deletion, and a marker that the account is closed. It contains none of your content, and no name or email address: 370 days
• Feedback, bug reports, and AI-response reports (including any diagnostic or message context you chose to attach): kept in our support records while we work on them and deleted once they are no longer needed

When you delete your account (section 8), we revoke access and queue removal of the account's content from our active systems rather than waiting for the limits above. The deletion runs in the background and is retried if part of it fails. Four limited categories can remain: the operational logs described just below; the account deletion record described above, which exists precisely because the account is gone and expires after 370 days; feedback, bug, and AI-response reports you already sent, which sit in our support records; and bounded disaster-recovery copies. The same bounded recovery systems apply when cloud content is removed after a PRO lapse. Database point-in-time recovery can retain an older copy for up to 35 days, and deleted or replaced cloud-photo versions are configured to expire after 30 days. Those recovery copies are not available through the app and are not used to restore a deleted account for you. Email us to request deletion of an existing support report. Apple, Google, and RevenueCat may retain purchase, subscription, and entitlement records under their own store, fraud-prevention, reporting, and legal-retention rules. We do not automatically delete those records when you delete the app account because doing so can interfere with subscription administration and restoration of a qualifying purchase. You may email our Privacy Officer for a specific RevenueCat access or deletion request; we verify the request, explain any restoration impact, and send an applicable request to RevenueCat manually. Apple and Google provide their own account and purchase privacy controls.

About operational logs. These are the records our servers keep of system events — which request was made, when, how long it took, and whether it succeeded — so that we can keep the service running, investigate faults, and detect abuse. They are keyed to an internal account identifier rather than to your name or email address, and they do not contain your messages, your notes, or the contents of anything you log. They are not deleted account by account: when you delete your account we delete your data, after which that internal identifier no longer corresponds to any account, and the log entries themselves are automatically deleted within 12 months. We keep them for that long so that a security, reliability or billing question can be investigated across a full year rather than only the last few weeks.

7. Partner Mode — sharing you control

What your partner can see. If you choose to link a partner, they can see information associated with your pregnancy in their own copy of the app: your baby's nickname, due date and week, symptoms and moods you log, upcoming appointments, kick counts and weight trends, notes, and — with the PRO plan — your synced bump photos and notebook. The AI may also share context it has learned from your conversations with your partner's baby character, so it can help them support you.

What your partner is actively notified about, without you asking. Some things do not just become visible — we send your partner a notification about them, in the baby's voice, so they can be there for you at the time it matters. These are: a symptom you log at moderate severity or above (at most once every 12 hours); a low, anxious or overwhelmed mood (at most once a day); a kick session you save; a note you add to the notebook, including what kind of note it is; a bump photo you add; an appointment you create; and that you have begun timing contractions.

Messages you choose to pass on. Separately, you can ask the baby to pass a short message to your partner, and it may sometimes offer to pass something on for you — an offer we only act on if you tap yes. Either way you are shown the message that was sent.

What the baby may raise with you, from your partner's chat. Everything above describes information travelling from you to your linked partner. This describes the other direction.

Your baby is one baby, and it talks to both of you. If your partner tells it something it judges worth raising with you — how you have been, or news to share in — it may bring that up with you the next time you open the app, naming which parent mentioned it. So if your partner tells the baby you fell, the baby may later ask you how you are; if they tell it they have bought a car for the family, it may mention that instead. The reverse also applies.

Some specifics worth being exact about. What crosses between your accounts is a short line the baby writes itself, together with which of you raised it and when. Your messages never cross, and nothing else either of you wrote crosses. No PreggyAI user other than the two of you ever receives it; like everything else in the app it is processed by us and the service providers listed in section 10 in order to produce that message. What is worth raising, and which of you it is raised with, are decided by the AI from what was said, and that judgement can be wrong — including bringing up something the other parent would rather have told you themselves. At most three are held at a time, they expire after seven days, and they are delivered only when you open the app, never as a notification. The person who mentioned it is not told that anything was queued.

Asking the baby to keep something to itself may not work as intended. It shares conversation summaries between the two of you, and a later instruction not to mention something may not carry across. Unlinking deletes anything still waiting.

This is part of linking rather than a separate switch: you both agree to it on the sharing sheet shown before a partner is linked, and it requires an active PRO or partner-trial plan. Unlinking turns it off — immediately, in both directions, deleting both agreements and anything still waiting. It is never a substitute for urgent care: if something needs attention now, the baby says so in the conversation at the time, and that is unchanged by any of this.

Linking is entirely your choice, requires an invite code you generate, and you can unlink at any time, which stops all future sharing.

8. Your choices and rights

Delete your account. In the app: Profile → Settings → Delete account. This immediately revokes access and queues permanent removal of your profile, messages, summaries, symptoms, appointments, weights, kick sessions, notebook, photos, account-email preferences and delivery records, per-account usage counters, and sign-in mapping from our active systems. The bounded account-email campaign-coordination record is not keyed by account and expires within 400 days as described in section 6. Bounded disaster-recovery copies expire as described in section 6. Feedback, bug reports, and AI-response reports you sent us are held in our support records rather than in the app's database, so they are not removed automatically — email us and we will delete them. Store and RevenueCat purchase records are also not removed automatically; email our Privacy Officer if you want us to review and pass on a specific RevenueCat request. Deleting those records does not cancel a store subscription and may affect later purchase restoration.

Clear your chat history. In the app: Profile → Settings → Privacy & Security → Clear chat history. This deletes your whole conversation with the baby from our servers and from the app on that phone, together with the memories and summaries built from it, anything waiting to be raised between you and a linked partner that came from a chat, and — if you are the parent carrying the pregnancy — the baby's memories about itself (which also resets them for a linked partner). A partner clearing their chat leaves those baby memories in place. It does not touch your trackers, notes, photos, or account, or your partner's own chat, and another phone signed in to your account keeps its own copy until you clear it there too. Usage counters are not reset.

Delete specific entries. You can delete individual symptoms, weight entries, kick sessions, contraction timings, appointments, notebook entries, and bump photos in the app, and disconnecting a connected health app deletes our copy of its data. For anything you cannot delete yourself — for example a single mood entry — email privacy@preggyai.online. A summary of every deletion option is at preggyai.online/delete-account.html.

Access and correction. Almost everything we hold is visible and editable directly in the app. For anything else, email us and we will help.

Notifications. Fully controllable in the app's settings, per category, or off entirely.

Account email. Every account email includes a signed unsubscribe link. The confirmation page records your choice immediately, and later campaigns exclude your account.

Withdraw consent. You can withdraw consent to our processing at any time by disconnecting your health app in Settings (for imported activity data — this deletes our copy), unlinking your partner (for sharing), deleting your account (for everything), or contacting our Privacy Officer about the broader health-data consent recorded at setup. Withdrawing consent required for the core pregnancy experience means the affected features may no longer be available.

Canada. We comply with the Personal Information Protection and Electronic Documents Act (PIPEDA). You may contact us with any privacy concern, and you have the right to complain to the Office of the Privacy Commissioner of Canada. Because we operate from British Columbia, BC's Personal Information Protection Act (PIPA) also applies to us, and BC residents may complain to the Office of the Information and Privacy Commissioner for British Columbia. The person accountable for personal information at PreggyAI is identified in section 14.

Quebec. PreggyAI is not offered to residents of Quebec at this time. We ask where you live when you set up the app and do not create a pregnancy profile when you tell us you live in Quebec. This is our own decision while we complete the French-language and privacy work that offering the app in Quebec properly requires; we intend to open Quebec later. We do not verify what you tell us, so to be unambiguous: if you are in Quebec and use PreggyAI anyway, everything in this policy applies to you in full and you keep every right Quebec law gives you — including the rights to access, correct, delete, and port your information, to withdraw consent, and to complain to the Commission d'accès à l'information du Québec. Not being offered the app is never a reason we would give you less protection.

United States. Depending on your state, you may have rights to access, delete, or obtain a copy of your personal information, and to be free from discrimination for exercising them. The deletion and access mechanisms above satisfy these requests; email us for anything additional.

Europe/UK. PreggyAI is offered only in Canada and the United States. It is not offered in the European Union or the United Kingdom and is not intended for use there.

9. Consumer health data

This section supplements the above for laws that specifically protect consumer health data (such as Washington's My Health My Data Act). The categories of health data we collect are direct entries such as pregnancy status and due date, symptoms, weight, fetal movement (kick) counts, appointment details, health-related notes, and health topics discussed in chat; optional activity summaries from a health platform you connect; information supplied through a partner you deliberately link; and summaries, memories, calculated pregnancy context, or other inferences generated from those inputs. AI-generated inferences are not clinical findings and can be wrong. We collect and generate this information to provide the app's features described in section 2. We do not sell consumer health data. We do not share it with third parties except: the service providers in section 10 (who process it only on our instructions); a partner you have linked (section 7); and where valid legal process compels us to, subject to the safeguards in section 11. You can withdraw consent or delete this data as described in section 8.

Washington's My Health My Data Act requires this content to be published as a separate document, so the full version — including the categories of sources we collect from and each recipient by name — is our Consumer Health Data Privacy Policy. Where the two differ on consumer health data, that document governs.

10. Service providers

We use a small number of providers to run PreggyAI, each processing only what is needed:

• Amazon Web Services — cloud hosting, storage, encryption, account-email delivery (Amazon SES), and AI processing (Amazon Bedrock), in the United States
• Expo — push-notification delivery and app updates. When the app opens it checks Expo's update service for a newer version of the app's code, which gives Expo your device's IP address, platform, app version, and a random identifier for that installation; no account or health information is sent. Expo also receives the title and text of each notification we send you. That text can name something you logged — for example a symptom, in a check-in from your baby asking how it has been since, or in a note passed to a partner you have linked.
• Apple / Google — sign-in, app distribution, and payment processing for the optional PRO plan. They also operate the push-notification networks (APNs and FCM) that carry our notifications to your device, so the text of a notification passes through them too, and that text may refer to something you logged.
• RevenueCat — subscription management: receives your account identifier and the purchase records associated with it, so we can tell whether PRO is active, along with basic technical details its software collects (a device identifier, your language, country, and app and operating-system version). We do not send it chat messages, tracker entries, due date, baby name, or other profile details. Its records do identify use of PreggyAI, and the Pregnancy Pass product name or purchase can support an inference about a pregnancy.

We have no advertising, analytics, or data-broker relationships.

If you would rather notification text never mentioned a specific entry, you can turn off the notification categories you do not want in Settings.

11. Legal requests

We may be required by law to disclose information — and because this app holds pregnancy data, we think you are entitled to know exactly how we handle that rather than to find a silence where the answer should be.

• We disclose your information to a government or law-enforcement agency only when valid, binding legal process compels it — a subpoena, court order, or warrant properly served on us. We do not act on informal requests.
• We review every request we receive, and we challenge or narrow those that are overbroad, defective, or that reach further than the law allows.
• We tell you before we disclose anything, so you have the chance to object — unless a court order or statute forbids us from telling you, in which case we notify you as soon as that restriction lifts.
• We give the minimum the process actually requires. We do not hand over a whole account because one record was asked for.

Legal process should be served on our privacy contact at support@preggyai.online, which is monitored for this purpose.

12. Children

PreggyAI is for adults. You must be at least 18 years old (or the age of majority where you live, if higher) to use it. We do not knowingly collect information from children.

13. Changes to this policy

If we make material changes, we will tell you at least 15 days before they take effect, by email to the address associated with your account or through a notice in the app. When they take effect, we will update the effective date above and ask you to review and agree again in the app before continuing. A material change may take effect sooner where it is required by law, where it is needed to protect the safety or security of users or the app, or where it only benefits you; we will still ask you to review and agree to it before you continue. The current version is always at https://preggyai.online/privacy.html.

14. Contact and accountability

Privacy questions, requests, or concerns: privacy@preggyai.online. PreggyAI is operated by Injoy AI Solutions Inc., registered in British Columbia, Canada.

Person accountable for personal information. Injoy AI Solutions Inc. has designated a Privacy Officer, responsible for our compliance with privacy law — including PIPEDA and, for anyone in Quebec, the Act respecting the protection of personal information in the private sector as amended by Law 25. Contact the Privacy Officer at privacy@preggyai.online to exercise any right in section 8, to ask how your information is handled, or to complain. We answer privacy requests within 30 days. The identity of the individual currently holding this role is recorded internally and will be provided on request.