Privacy Policy

The short version

In the Natkhat Android and iPhone apps: no account or phone number is required. Your baby's photo is processed entirely on your phone and is never uploaded to our servers. Their name and exact date of birth stay on your phone. Limited analytics, including their age in completed weeks and months and their gender, are described below.

On the natkhat.app website: your baby's photo works exactly the same way — processed in your own browser, never uploaded. After your photo is ready, we optionally ask if you'd like to share your name, phone number, your baby's age, and your city so we can follow up. This is entirely optional, always skippable, and never required to download your photo — see "Information you choose to share" below for the full detail.

The setup details are stored on your device. Limited age, gender and activity properties are sent to Firebase, alongside usage analytics that help us understand which features people use and whether our ads are working; the analytics section explains what is sent.

What we collect

During first setup the Android app asks for your baby's first name and gender, and offers an optional birthday. These details personalize your photos and milestone stickers and are stored on your phone. The name and exact date of birth are never sent to us. Firebase receives the selected gender and age derived from the birthday, as described in the analytics section.

The iPhone app asks for your baby's first name, birthday and gender during first setup, and you can edit them later in Settings. They personalize your photos, milestone timeline, stickers and reminders and are stored on your iPhone. The name and exact date of birth are never sent to us; Firebase receives the selected gender and the age derived from the birthday, as described in the analytics section.

The Android and iPhone apps do not ask for a phone number, an email address, or any other contact details, and there's no account to create.

On the web app, your baby's date of birth, if you enter it, is stored only in your browser.

We never collect your baby's photo, on either platform. It stays on your device or in your browser.

The one exception is the optional contact details you can choose to share on the website after your photo is created — see the next section.

Information you choose to share (website only)

After you finish creating a photo on natkhat.app, you may see a short, clearly optional form asking for your name, mobile number, your baby's age, and your city. Every field is skippable — a visible "Skip" is always available, and downloading your photo never requires filling it in.

We use this only to follow up with you about Natkhat — for example, letting you know about new themes. If you tick the separate consent checkbox, we may also contact you about offers on WhatsApp or SMS; leaving it unticked means we won't. We never sign you up for marketing without that explicit, separate opt-in.

Alongside whatever you enter, we also store which page and theme you were viewing, any campaign tracking (UTM) parameters, the time of submission, and basic technical information (like your browser's user agent) so we can understand which pages are working.

This is submitted to our servers and stored in our database — unlike your baby's photo, which never leaves your browser. It is never sold, and is only used as described above.

This form does not exist in the Android or iPhone apps. Nothing you type into it is linked to any photo, cutout, or image — we hold no photos of your baby on our servers regardless of whether you use this form.

To have this information deleted, write to hello@oyechilli.com with the phone number or name you submitted — see also our Data Deletion page.

Photos on your phone

The Android app asks for permission to read photos on your device so you can pick your baby's photo from your gallery, and so the app can show a grid of your recent photos to choose from. The app reads only the photo you select in order to process it on your device. It does not scan, index, catalogue, or upload your photo library, and photos are never transmitted anywhere.

You are in full control of this. On Android 14 and later you can choose "Select photos" instead of allowing access to everything, and Natkhat will only ever see the photos you hand-pick — the app is built to work that way, not to nag you out of it. You can also decline the permission entirely and still use Natkhat: the "Choose from Gallery" button uses Android's own photo picker, which needs no permission at all.

The iPhone app works the same way. It can show your recent photos if you allow access, and you can allow only selected photos, or decline and use the system photo picker ("Browse Gallery"), which needs no access. The camera is used only when you choose to take a photo. If you allow it, Natkhat can also add the finished pictures you save to your photo library; this permission only lets it add photos, not read them. Photos are read only when you pick them, and are never uploaded.

Your baby's photo never leaves your device

This is the core design of Natkhat, not just a promise: the web app removes your baby's background using a machine-learning model (U2NetP) and detects pose landmarks (MediaPipe), both running entirely inside your browser via WebAssembly. The Android app does the same using Google's on-device ML Kit, and the iPhone app uses Apple's on-device Vision framework. Neither ever sends your photo to any server — there is no upload endpoint in the app for photos at all.

Themes, stickers, and other artwork ARE downloaded to your device (from our content delivery network) so they can be composited with your photo locally. Only your baby's photo is exempt from ever being transmitted.

Where your data is stored

Web: your photo and edits are kept in your browser's local storage for the duration of your session, and are cleared if you clear your browser's site data. If you choose to submit the optional contact form described above, that information (name, phone, baby age, city) is stored on our servers — it's the one thing on the website that isn't purely local.

Android: your photo's processed cutout, chosen theme, and edits are stored in the app's private storage on your phone. Finished keepsakes you save go to your phone's Pictures/Natkhat folder like any other photo you take. Your photos are never backed up to our servers.

iPhone: your photo's cutout, the pictures you save, your baby's profile and growth log are stored in the app's private storage on your iPhone, protected by your device's file protection. Pictures you choose to save are added to your Photos library. In Settings, "Delete my data" removes all of this from your iPhone.

Price

Natkhat is currently free to use, with no in-app purchases and no subscription. If we introduce a paid feature later, we'll say so clearly in the app before you're asked to pay, and update this policy to describe how payments are handled.

Analytics and how we measure our ads

The Android app includes two analytics tools: Google Analytics for Firebase, and the Meta (Facebook) SDK. They record how the app is used — which screens you open, which themes you pick, whether photo processing succeeded or failed, and how long it took — together with technical information about your device (model, operating system version, language, country, and your device's resettable advertising identifier).

We use this for two things: finding and fixing problems (for example, spotting that photo processing fails more often on a particular phone), and understanding whether the ads we run actually bring people who enjoy the app. Meta uses the events sent from the app to attribute installs to our ad campaigns and to improve who those campaigns are shown to.

These events describe actions, not content. They never include your baby's photo, name, or date of birth.

Google Analytics for Firebase also receives user properties: the number of saved creations made with your own photos, the number of personal photo cutouts, whether you have saved a personal creation, and whether you have created a WhatsApp sticker pack. If you enter a birthday, Firebase receives the baby's age in completed weeks and 30-day months. It also receives the selected gender if you provide one. These properties update as your profile or activity changes; removing the birthday clears the age properties. These properties are not sent to Meta, and never contain the baby's name, exact date of birth, or photos.

You can limit this: Android's Settings › Privacy › Ads lets you delete or opt out of your advertising ID, which stops it being used for ad measurement.

The iPhone app uses Google Analytics for Firebase in a configuration that does not use your advertising identifier (IDFA). It records the same kinds of actions as above, with your iPhone model and iOS version, plus a random installation identifier created by Firebase. The same user properties (counts of saved creations and cutouts, baby age in completed weeks and months, and gender) are sent to Firebase. The name, exact date of birth and photos are never sent. You can switch analytics off at any time in Settings › Share usage analytics.

On iPhone, Meta ad measurement works only if you allow it. After you save your first picture, the app shows Apple's tracking prompt. If you tap "Allow", the Meta (Facebook) SDK starts and Meta receives the same short list of actions described above (completing setup, opening a theme, saving, sharing or downloading a picture, and creating a sticker pack, with the theme ID where relevant), together with your iPhone's advertising identifier and technical device information, so Meta can attribute installs to our ads. If you tap "Ask App Not to Track", the Meta SDK is never started and nothing is sent to Meta; everything else in the app works the same. You can change this at any time in iOS Settings › Privacy & Security › Tracking. Meta never receives your baby's photo, name, date of birth, age or gender.

Website analytics

The natkhat.app website uses Google Analytics 4 to count how the site is used: which pages are visited, which theme or collection is opened, and whether a photo is created or downloaded. Each event carries the page you were on, the theme or collection involved, and any campaign tags (UTM parameters) from the link you arrived through.

Google Analytics sets cookies in your browser to recognise a returning visit, and Google derives approximate location and device type (browser, operating system, screen size) from the request; Google Analytics 4 does not store IP addresses. The website stores the page and campaign tags of your first visit in your browser so we can tell which links bring people to Natkhat.

These events describe actions, not content. They never include your baby's photo, name or date of birth, and they never include anything you type into the optional contact form.

You can limit this by blocking cookies or analytics in your browser, using Google's Analytics opt-out browser add-on, or clearing your browser's site data, which resets the identifier.

Crash reporting

The Android and iPhone apps report crashes to Firebase Crashlytics so we can fix them. A crash report contains the technical state of the app at the moment it failed — the error, the code path, and your device model and OS version. It does not include your photos or profile information.

Ratings and feedback (Android and iPhone apps)

After you've saved a few creations, the Android app may ask you to rate it. If you give a rating, we receive the star rating and, if you choose to type one, your comment, together with the app version, your phone model and Android version, and how many creations you've saved. We store this to understand what to improve. It is not linked to your name, your baby's details, or your photos, and a comment you type is the only free text we collect — please don't include personal details in it.

If you give 5 stars, the app also opens our Google Play page so you can leave a public review there; that review is governed by Google Play, not by us.

The iPhone app can ask for an App Store rating using Apple's own review prompt, which Apple controls. Separately, Settings has a feedback form: if you send one, we receive your star rating and the comment you type, together with the app version, your iPhone model and iOS version, and how many pictures you've saved. It is not linked to your name, your baby's details or your photos. If you are offline, the feedback waits on your iPhone and is sent later.

Notifications

Milestone reminders and the welcome message are created on your phone using your baby's name and birthday, and are scheduled by your phone itself; that information is not sent to us to produce them. Campaign notifications about new themes and festivals are sent through Firebase Cloud Messaging (on iPhone, via Apple's push notification service), which means your phone's push registration token is held by Firebase so a message can reach it. Notifications are optional: you can allow or stop them in the app's Settings or in your phone's settings.

Diagnostics

If the on-device photo processing fails, the web app sends a single, small diagnostic message (the failure reason, your browser's user agent, and a timestamp) so we can improve reliability. This message never includes your photo or any other personal data.

Third-party services we use

Google Fonts, to load the app's typeface (this is a standard font request to Google's servers).

Firebase (Storage and Firestore), to serve our theme and sticker catalog — this never carries your photos or personal data, only our own artwork.

Google Analytics 4, for anonymous usage counts on the natkhat.app website, as described under "Website analytics".

Google Analytics for Firebase and Firebase Crashlytics, for usage analytics and crash reporting in the Android app, as described above.

Meta Platforms (the Facebook SDK), to measure our advertising in the Android app and, only if you allow tracking, in the iPhone app, as described above.

Google Play Services, which provides the on-device machine-learning models (ML Kit) the Android app uses to cut your baby out of the photo. The models run on your phone; your photo is not sent to Google.

Apple's Vision framework, built into iOS, which the iPhone app uses on your iPhone to cut your baby out of the photo. It runs on your device; your photo is not sent to Apple or to us.

Firebase Cloud Messaging and Apple's push notification service, to deliver campaign notifications as described under "Notifications".

WhatsApp, only if you choose to add a sticker pack: the app hands the pack to WhatsApp on your phone. We do not receive it.

Vercel, to host the web app, which keeps standard server access logs like any web host.

Children's data

Natkhat is made for parents and guardians — adults creating keepsakes of their own children. It is not directed at children, is not intended for anyone under 18 to use, and we don't knowingly collect information directly from children. All profile information described above is entered by the parent or guardian using the app.

The photograph you edit is of your own child, and it never leaves your device. We never receive it, so we hold no images of children at all.

Your rights

Your baby's photos, name and exact date of birth stay on your device: uninstalling the app or clearing your browser's site data removes that local data. Firebase age, gender and activity properties are analytics data; deleting the local data does not automatically delete previously collected analytics data.

If you submitted the optional web contact form, that's the one piece of information we do hold on our side — write to us at the address below with your name or phone number and we'll delete it. If you'd like the apps' device-linked analytics data deleted too, include that in the same email. On iPhone you can also open Settings › Delete my data to remove everything stored by the app on your phone at once. Website analytics is tied to a random browser identifier rather than to you; clearing your browser's cookies and site data resets it.

Changes to this policy

This policy was last updated on 13 October 2026. If we make material changes, we'll update this page and the "last updated" date above.

Contact

Questions about this policy? Write to us at hello@oyechilli.com.