Where Your Kid's Photos Actually Go (Spoiler: We Can't See Them)

By Durvesh Naik, maker of Everkid · 7 July 2026 · 7 min read

Before you pour four thousand photos of your kid into a memory app, ask the question almost nobody asks: whose computer do those photos end up on?

Because they do end up on a computer, and usually it isn't yours. When an app offers web login, family sharing feeds, printed books, or "access from any device," the photos have to live on the company's servers to make that possible. You take the picture, the app uploads it, and from that moment a copy of your kid's face exists in a database run by a business you know from a screenshot on the App Store.

That isn't sinister. It's just how those features work, and most companies handling family photos are staffed by decent people trying to do the right thing. But it means the safety of your kid's childhood archive now depends on things you can't see: the company's security practices, its staff access policies, what its privacy policy permits this year, and, the one people forget, who buys the company later. Startups get acquired. Databases go with the deal. The privacy policy you agreed to can be rewritten by owners who haven't been hired yet.

None of that should scare you off memory apps. It should just change how you shop for one. Fortunately, there's a 30-second way to see how any app treats your data before you install it.

How to read any app's privacy label in 30 seconds

Since late 2020, Apple has required every app on the App Store to publish a privacy "nutrition label." It's on every app's store page: scroll down past the screenshots and reviews to the section called App Privacy. The developer must declare what data the app collects, and the answers fall into three buckets:

One caveat worth knowing: labels are self-reported by developers. Apple can and does act on false declarations, but the label is a claim, not an audit. Which is why the strongest privacy answer an app can give isn't a promise at all. It's an architecture that makes the promise unnecessary.

Where Everkid puts your photos: nowhere

I built Everkid with a rule that sounds extreme until you have kids: the app must be physically incapable of seeing what you save.

So there are no Everkid servers holding your child's memories. Not "secure servers," not "encrypted servers." None. There are no accounts to create, and no code in the app that can read a photo, a mood or a note. Here is what actually happens to a memory you capture:

• The photo, mood, and note are stored on your iPhone, in Everkid's own database on the device.
• Your iPhone backup covers them like the rest of your phone, inside your personal Apple account. Apple's infrastructure, Apple's terms, our name nowhere in it.
• Nothing is transmitted to us. There's no pipe to send it down. If a court, a hacker, or an acquirer demanded your photos from Everkid tomorrow, we'd have nothing to hand over. Not out of principle. Out of physics.
• Delete the app and the data is gone. No archive of your family lingers in a warehouse because there was never a warehouse.

Two things I will not pretend about. Everkid does measure three ad events: that the app was installed, that a free trial started, and that a subscription started. That goes to a measurement provider called AppsFlyer, it carries a device identifier and no content, and it exists so I can tell which TikTok ad is worth paying for instead of guessing. We do not collect Apple's advertising identifier, which is why Everkid never shows you the "Allow app to track" prompt, and the App Store label says Data used to track you: None. The full list is in the privacy policy. Second, this version does not sync to iCloud, so your memories live on exactly one device until it does.

The trade-offs, honestly

This design costs us features, and you should know which ones before you choose it.

There's no web version; your memories live where your phone is. There's no grandparent feed that updates relatives automatically; sharing a memory means the normal iOS share sheet, deliberately, one moment at a time. This version doesn't sync between your devices either. And the responsibility for backup sits with you in one specific way: keep iPhone Backup turned on (Settings, your name, iCloud, iCloud Backup). Lose your phone with backup off and no company can recover your memories, because no company has them. That sentence is the whole deal, both its cost and its point.

If automatic family feeds matter more to you than server-free storage, a sharing-first option like Tinybeans or FamilyAlbum is a fair choice made with open eyes; I compared them all in the baby journal app roundup. Just make the choice knowingly, on label and architecture, not on screenshot aesthetics.

Five questions to ask any memory app

1. What does the App Privacy label say? Thirty seconds on the store page, before anything else.
2. Where are photos stored: my device, my cloud account, or your servers? If the answer takes more than a sentence, it's servers.
3. What happens to my archive if you shut down or get acquired? Every startup should have an answer it can say out loud.
4. Can I export everything, and does deleting my account actually delete the data?
5. What's the business model? Subscriptions and print orders are you paying for a product. "Free unlimited storage" means the product is being figured out around your photos.

Any decent app clears at least a few of these. The point isn't to find a villain. It's that your kid can't consent to where their childhood gets stored, so the diligence is your job, once, for thirty seconds, before the first photo goes in.