A pregnancy you can share, with the people who matter

It is 9 p.m. and your mother wants to see the bump

You are 28 weeks pregnant. Your mother lives in another city, four hours away by plane, and she has seen you exactly twice this pregnancy. Tonight, after the toddler is finally down, she sends a text: any new photos. You have a phone full of them. Bump shots in front of the bedroom mirror, mostly, taken on Sundays because that is the day you remember. There are 14 weeks of them stacked in a folder you set up in the camera roll the day you saw two lines.

You think about Instagram, briefly. You will not be doing that. You think about texting her one image. That works. But you find yourself wishing for something in between. A small, curated thing. Not a public post. Not a single image stripped of context. Something that says, here is week 28, here is the photo, here is what changed since we last spoke. You want her to see the months passing, not just the moment.

This article is about that in between. It is about what a pregnancy app should let you share, what it should refuse to share, and why the difference is a design choice that has to be made before the first feature ships.

What is already shareable in myCocoon today

The app is not waiting on a future release to give you something to send your mother. Five surfaces ship today.

• A photo bleed share card. Take a bump photo, drop in a week number, hand-write a one-line caption. The app renders a 1080 by 1920 image at full retina resolution, the same shape as a phone screen. You can save it, AirDrop it, send it by message, or post it if you choose to.
• A polaroid chrome. The same photo with a soft white border and a hand-typed caption underneath, finished to look like a small printed object rather than a screenshot.
• A digicam chrome. The early-2000s point-and-shoot frame. Date stamp in the corner, slightly washed colour. The aesthetic your mother will recognise from the photos of you as a child, minus the dust.
• A multi-photo collage. Several bump photos arranged into a single image, week numbers labelled, so a fortnight or a trimester can travel as one picture instead of seven.
• A story PDF. Curated weekly chapters bound into a single document. You pick which chapters to include, the photos that go with them, and the one or two sentences you want each chapter to say. It exports as a PDF you can email, save, or print.

Across all five, a few things are common and worth naming. None of them post to a feed. None of them require your mother to install an app, sign up, or scroll past someone else’s. None of them are auto-published. The app does not, ever, share something on your behalf without you choosing the moment, the photo, the caption, and the recipient.

There is also a direct Instagram Stories handoff, gated on you tapping it. Hand-curated cards can be sent to the Stories composer with one tap, with the image already framed at the right resolution. It exists for the people who do want to post. It is a button, not a default. Most weeks you will not press it.

What is never shareable, by design

The harder list is the one that does not appear anywhere in the export pipeline. Some of these are not visible in the share editor because the app refuses to put them there. Others would require code changes the project has agreed never to make.

• Anything from the Health app. Heart rate, blood pressure, sleep duration, weight, steps. Apple’s HealthKit guidance is explicit: apps must not store this data in iCloud. By the same logic, myCocoon does not put any of it on a share card, ever, even with your consent. The architecture is a dual-cabinet design and the cabinet that holds Health data is the one that never leaves the device. (Apple Developer documentation)
• Mood entries verbatim. The structured triple of mood, emotion word, and association is intimate. A derived single descriptor, the kind a friend might use to describe a week, can occasionally appear on a curated chapter. The raw entry never does.
• Journal entries verbatim. The text you type and the audio you record are for you. Voice recordings never leave the device, full stop. Journal text never appears in a share surface unless you copy it yourself into a caption, in which case it is your choice and your hand.
• Appointments by clinic name. A calendar of titled appointments and locations identifies your obstetric practice and your geography down to a postcode. The share pipeline does not read from the appointment store at all.
• Raw weight. The number itself is medical data. A trend, when one is shown to you, is the most you would ever see in a curated chapter, and only if you toggle it on by hand.
• Symptom logs. The list of what you have flagged is a map of medical conditions and search history. None of it is share-shaped.
• Mental health screener results. The Edinburgh Postnatal Depression Scale, when used postpartum, is designed for clinician handoff. The score is yours and your GP’s. It will never sit on a card next to a bump photo, regardless of how the app is configured. (Clinical Practice Guideline, ACOG, 2023)

The principle running through all of those: a share surface only reads from the cabinet you have curated yourself, never from the cabinet that holds your Health data. This is not a setting you toggle. It is the shape of the app. Even if a future feature wanted to pull a heart-rate reading onto a card, the share screens have no way of reaching the place where that data lives. The shape is the policy. (The architectural decision behind that two-cabinet split is covered in how myCocoon reads what is already on your phone.)

The shape that comes from copying Tinybeans, not Instagram

If you have used another pregnancy app before, the assumption built into most of them is that sharing means feed. There is a community board, a public profile, a discover surface. Every post you make becomes a unit of platform engagement, by default.

There is another shape, older and quieter. Tinybeans, a family-focused journaling app launched in Sydney in 2012, made a different choice and held it for over a decade. Invite-only family circles. Email digests pushed to subscribers, who do not need an account or an app to read. No public search. No way for a stranger to find your photos by typing your name. Distribution is a list of people you trust, not an algorithm. (Tinybeans · Wikipedia)

That shape generalises well to pregnancy. It works because it accepts a smaller, slower truth about what most parents actually want. You are not trying to reach a hundred thousand strangers. You are trying to reach six people, by name. Your partner. Your mother. Your sister. Two close friends. Maybe an aunt who raised you. The right system for that job is push, not pull. Email, message, AirDrop. The user holds the address book.

Flo, the most-downloaded pregnancy and cycle tracker in the world, added an in-app community feature in 2026. Tinybeans has spent fourteen years declining to. Both choices say something. Either could be the right one for you. myCocoon’s choice is the second one, and it shows up in every line of the share pipeline.

The thing that matters is not whether sharing is fast. It is whether sharing is the right shape. A bump photo with a week label sent by AirDrop to your partner standing in the same room is a different object from the same photo posted to a community board. Both are sharing. Only one is what you want at 9 p.m. on a Sunday.

What you have probably noticed in other apps

If you have used another pregnancy app in a previous pregnancy, you have probably noticed the drift. The first weeks were calm. By the middle of the second trimester, the suggested community posts had crept onto the home screen. By the third, the app’s idea of “your week” included content from people you did not follow, on topics you did not choose, framed in a tone you did not pick.

That drift is not random and it is not your imagination. It is a function of how apps in this category make money. The track record, in primary sources, is worth knowing.

In 2021 the United States Federal Trade Commission settled with Flo Health over allegations that the company had shared sensitive user health data, including pregnancy status, with Facebook, Google, AppsFlyer, and Flurry. The settlement required affirmative consent before sharing user health data going forward, and an independent review of the company’s privacy practices. (Federal Trade Commission · Flo Health, Inc.)

In 2020 the California Attorney General reached a settlement with Glow over what the office described as basic security flaws and privacy violations affecting medical and personal data. (California settles with Glow app · WilmerHale)

Mozilla’s “Privacy Not Included” project, which audits the privacy practices of consumer apps, has flagged a long list of pregnancy and period trackers with privacy warnings. The pattern across the audits is consistent: extensive permissions, ad-network integrations, data shared with marketing partners, and policies that change. (Mozilla Foundation · Privacy Not Included) The recommendation in those reviews is rarely to trust the marketing copy. It is to read the architecture.

That last point is worth holding. Privacy is a property of architecture, not a property of marketing. Any app can claim to care about your data. What matters is whether the data lives in a place where the claim becomes possible. myCocoon is built so the most sensitive cabinet does not connect to the cloud at all. The user-curated cabinet that does sync to your iCloud is wired to your account, not the company’s, with no marketing trackers in either direction. The privacy policy on the marketing site is the single source of truth for what is collected and what is not. (myCocoon privacy policy)

None of this makes a system unbreakable. Architecture reduces blast radius. It does not remove risk. The right honest claim is that fewer surfaces hold sensitive data, fewer paths exist for that data to leak, and the user has a smaller list of decisions to track. That is a meaningful difference. It is not a guarantee.

Where this is going

There are three directions the team is exploring for how the curated, private surfaces grow next. None has shipped. All are aspirations being designed against the same principle as the existing five.

A weekly digest email to a private circle. You enter the email addresses of the people who matter once. Each week, you tap to approve a small handful of cards. The app sends them, as a plain HTML email with no JavaScript and no tracking pixels, to the list. Your mother does not need an app. She does not need an account. She gets the digest the way she gets the rest of her email. The closest analog to a Tinybeans circle, applied to pregnancy.

A private link to a single chapter. A short URL with a capability token, generated when you tap to share, expiring after thirty days, revocable from the app. The recipient opens it in a browser and sees one curated chapter. One photo, one caption, the week, the mascot art. No installation. No account. No login. If you change your mind, you revoke the link and the page disappears.

An exportable card with chrome, designed AirDrop-first. The image card pipeline that already ships, with the share affordances reordered. AirDrop becomes the default, because AirDrop never touches a server. Messages second. The system share sheet third. Instagram and other public surfaces become a deliberate choice, never a default. This is mostly a design polish over what already works.

If any of these ship, you will see them. If they do not, you will not. The promise of this article is the five surfaces in section two, all of which are present today. Everything else is the direction, named here so you can hold the team to it.

What this leaves you with

You can send your mother the bump photo tonight. The app will help you frame it, label the week, write a one-line caption, and hand the file to AirDrop or Messages. You can do this every Sunday for the next twelve weeks if you want to. The photos stay on your phone, the captions stay on your phone, and the people who see them are the people you chose, by name.

What the app will not do is build you a public profile, push your photos onto a feed, or send anything that involves your heart rate, your sleep, your mood, your weight, or your appointments. That decision was made in the architecture before any of the share surfaces shipped, which is the only place a decision like that can actually hold.

A pregnancy is a private thing. The app’s job is to make sure it stays one, while still letting you reach the small number of people who deserve to see it.

§