Privacy
Last updated: 17 November 2026
Cradle is built so that the questions you ask about your family stay with you. This page explains exactly what happens to your information. It describes how the Cradle software works; whoever runs the copy of Cradle you are using (the "operator", named at the bottom of this page when they have set it) is responsible for their own hosting and should update this page if they change anything.
The short version
- No account needed, no cookies, no analytics, no ads, no trackers. Signing in is optional, and what it syncs is encrypted on your device so the server can't read it — except with email sign-in, where the server holds your key wrapped so a link can sign you in (see below).
- Your history lives in your browser, not on our server. Clear your browser data or press Erase everything in Settings and it is gone. If you sign in, an encrypted copy is kept so your devices can sync; you can delete it at any time.
- To answer a question, it must be sent to an AI model. Your question passes through the Cradle server to the model provider, is used to produce the answer, and is not stored by Cradle.
- Photos you add are sent with that one question and not kept. Your browser shrinks each photo and removes its hidden details (such as location) first; the server passes it to the AI model to answer and keeps nothing. Photos are never saved in your history or synced.
- Children's names never leave your browser. If you tell Cradle about a child or pregnancy, only an age ("2 years 4 months") or weeks of pregnancy is sent with your question.
What is stored, and where
| What | Where | Who can see it |
|---|---|---|
| Household profiles (names/nicknames you choose), on the Household page | Your browser (localStorage) | Anyone using this browser |
| Children and pregnancies (nickname, birthday or due date) | Your browser | Anyone using this browser |
| Your questions, answers and history | Your browser | Anyone using this browser |
| Feeding log (time, amount and type of each feed) | Your browser, never sent to the server | Anyone using this browser |
| Growth measurements (date, weight, length or height, head size) and the chart's boy/girl setting | Your browser | Anyone using this browser |
| Your own model API key and access code, if you enter them | Your browser | Anyone using this browser |
| Which guides each person has read or started, and the section they reached | Your browser, never sent to the server | Anyone using this browser |
| Pregnancy to-dos you tick off on Today | This browser only (not synced), never sent to the server | Anyone using this browser |
| Pages you open, for offline reading | Your browser (offline cache) | Anyone using this browser |
| Photos you add to a question or follow-up | This browser tab only, until you close it (so follow-ups can refer to them); never in history, never synced | Anyone using this tab |
| Theme preference | Your browser | - |
Profiles are a convenience for sharing a device, not a security boundary: anyone who can use the browser can switch profiles. On a shared or public computer, erase your data when you are done.
Unless you sign in, nothing in the table above is stored on the Cradle server. If you do sign in, the server holds an encrypted copy of the shared parts (next section). It can't read that copy if you use a family key; for email sign-in, see Signing in with email below.
What the server keeps if you sign in
| What | Kept for | Readable by the server? |
|---|---|---|
| Your family's encrypted copy, an account number derived from your key, a hash of a sign-in token, and a version number | Until you delete it, or about 13 months after your last sync | No |
| With email sign-in: a one-way keyed hash of your address, and your family key encrypted with the server's secret | Until you turn email off or delete the synced copy, or about 13 months after you last signed in by email | The operator could unlock it with the secret |
| A sign-in link you asked for: your email address and the link's token (hashed) | 15 minutes, or until used | Yes |
| Counters that limit how many sign-in emails can be sent (a hash of your address and of your IP address) | 1 hour | No addresses are kept |
Optional sign-in (sync across devices)
You never need to sign in, and nothing changes for you if you don't. If you want your household's data on more than one device, or shared with a partner, there are two ways in, both on the Sign in page (and as a shortcut on the Household page):
- Email: a one-time link, no password. The most convenient; see the next section for what it means for privacy.
- A family key: 26 letters and digits made in your browser. There is no email, password or name involved, and nobody but you can read your data.
The rest of this section applies to both.
- What syncs: people, children and pregnancies, your questions and answers (with their follow-up conversations), the feeding log, growth measurements and reading marks.
- What never syncs: which person is using a device, your own model API key and access code, the theme and other small preferences, and offline copies of pages.
- End-to-end encrypted. Your browser encrypts everything (AES-256-GCM) with a key derived from
the family key before sending it. The family key itself never leaves your devices; sign-in links
carry it after a
#, which browsers don't send to servers. The server stores an account number, a hash of a sign-in token (both also derived from the family key), a version number and the encrypted data. It cannot read your data, and it cannot recover or reset a lost key. - Where: in the operator's database (Upstash Redis, through Vercel). A family's copy is deleted automatically after about 13 months without any device syncing.
- Who can see it: anyone who has your family key. Share it only within your household.
- Signing out stops a device syncing. You can keep that device's copy or remove it from the browser. Delete the synced copy on the Sign in page removes it from the server at once; every device keeps its own copy and simply stops syncing. Erase everything offers to do both.
Even though the server can't read the data, the hosting provider's request logs (below) record when a device syncs, like any other request.
Signing in with email instead
Where the operator has turned it on, you can sign in with just your email address: Cradle emails you a one-time link, valid for 15 minutes, and opening it signs in the device you open it on, at once. Only open a link you asked for. This is more convenient and lets you back in even if you lose every device, but it is not end-to-end in the same way:
- To let a link sign you in, the server keeps your family key for that address, encrypted with a secret only the server holds. So whoever runs the server could, in principle, unlock that family's data. Families who use only a family key don't have this.
- Your email address itself is not stored: only a one-way keyed hash of it, which is enough to find your family when you ask for a link. The address is kept for the 15 minutes a link is valid, and is passed to the email service (Resend) to send the email, under that service's own privacy policy. Cradle sends no other email: no newsletters, no marketing.
- Adding your address to a family while signed in moves it to that family if it used to open a different one (you have proved both the inbox and the family key).
- Sign in -> Email sign-in -> Turn off deletes the server's copy of the key for every address of your family. Your family key keeps working. Delete the synced copy does the same.
What is sent when you ask for a growth chart explanation
Percentiles are worked out in your browser. Only if you press Explain on the growth chart does your browser send the server a short summary: boy or girl, each measurement's age (in weeks, months or years), value and percentile, the explanation style you picked, and any note you typed. No name and no dates are sent. It is passed to the model like a question and not kept.
What is sent when you ask a question
When you press Get guidance, your browser sends the Cradle server:
- your question, and the plan or claim you pasted (if any);
- the anonymous context line for the child or pregnancy you selected (an age or weeks - no name);
- your model connection, if you added your own (provider, model and API key), or the access code.
The Cradle server then:
- finds relevant passages in its built-in library (this happens on the server; nothing leaves it);
- sends your question, the context line and those passages to the AI model provider - either the one the operator configured, or the one you chose in Settings;
- checks the model's drafts, builds the answer, sends it back to your browser, and discards everything. Each analysis runs in memory and is not written to disk or a database.
Cradle's own logs record only technical metadata (for example which model was called, how long it took, and a one-way hash of the prompt) - never the text of your question or the answer. Your API key is never logged.
The AI model provider
Your question is processed by a third-party AI provider (for example Anthropic, OpenAI, Groq, Google, or a hosted open-model service), which handles it under its own privacy policy and data-retention terms. When no model is configured, Cradle uses a free community model (Pollinations) that needs no key; it is run by a third party with its own terms, and the Ask page says when it is in use. Add your own free key under Settings to choose the provider yourself. If you use your own API key, your agreement with that provider applies. Please avoid including information you would not want that provider to process, such as full names, addresses or medical record numbers. Cradle never needs them.
Hosting and network logs
Like any website, the hosting platform (for example Vercel or a server run by the operator) may keep standard request logs - IP address, time, the page requested - for security and reliability. If the operator limits how many questions can be asked per hour, your IP address is kept in the server's memory for up to an hour to count requests, and then forgotten.
Children
Cradle is intended for adults - parents, expecting parents and caregivers. It is not directed at children and does not knowingly collect information from them, and children should not sign in. Information you enter about your child stays in your browser, except for the anonymous age described above and, if you sign in, the encrypted copy described above.
Your choices
- See everything Cradle has about you: Settings -> Export to a file. (The server's copy, if you sign in, is the same data, encrypted.)
- Change your household: the Household page (people, children and pregnancies).
- Turn off email sign-in: Sign in -> Email sign-in -> Turn off.
- Stop syncing or delete the synced copy: Sign in -> Sign out of this device or Delete the synced copy.
- Delete it: Settings -> Erase everything in this browser (it also clears the offline copies of pages and the small preferences), or clear this site's data in your browser settings. Deleting a single answer: open it and press Delete.
- Keep your question away from the operator's AI provider: add your own key under Settings.
- Contact us: if you email feedback about a guide or an answer, your email address is shared with the operator, as with any email. Cradle itself still collects and stores nothing it can read.
Follow-up conversations
When you keep talking under an answer, the whole conversation (with the original question and answer) is sent with each new message, answered, and forgotten by the server. The conversation itself is saved with the answer in your browser.
Photos
You can add up to four photos to a question or a follow-up: paste one, drop it on the question box, or pick one from your photo library or camera. Before anything is sent, your browser shrinks each photo and saves it again as a plain JPEG, which removes the hidden details phones add to photos (such as where and when it was taken and the phone model). Nothing is uploaded until you send.
When you send, the photos go to Cradle's server with your question, are checked (size and type), passed to the AI model that answers (see The AI model provider above; on this site normally Anthropic's Claude), and discarded. Cradle doesn't write them to a database, a log or any store, and the answer record keeps only how many photos there were. The model provider's own terms apply to what it receives, as for your question; free models on OpenRouter may be run by providers that log or train on what they receive. If the model answering can't see images, the photos are not sent to it, and the answer says so.
Your browser keeps the photos in that tab while it is open, so follow-up questions on the same answer can include them; closing the tab removes them. They are not saved with your history, not included in exports, and not synced when you sign in.
If you share a photo to AskCradle from another app on Android (after installing it), the photo is held on your device until the Ask page opens and picks it up, and is sent only when you ask your question.
Please don't send photos that show anyone's face or other private details unless the question needs it, and never photos of a child's private areas: describe the problem in words and show your child's doctor instead.
Voice input
The mic button listens only while it is switched on. The recording is sent to Cradle's server, forwarded to a transcription service (Groq Whisper, a free AI model on OpenRouter, or OpenAI Whisper) and discarded; only the text comes back, and neither the audio nor the text is kept by Cradle. Free models on OpenRouter may be run by providers that log or train on what they receive. Chrome, Edge and Safari also have their own speech recognition, which may send the audio to the browser maker (for example Google or Apple). Cradle uses it when the server has no transcription service, for a day after the server's transcription has failed on your device (remembered in your browser), and, on desktop, alongside every recording as a backup whose text is only used if the server fails. You can always type instead.
AI assistants
If you add Cradle to an AI assistant as a connector, the assistant sends Cradle's server the search words or message it wants to check. The connector needs no account and no sign-in, and never sees your household or synced data. The server answers from the guides and keeps nothing; the hosting provider's network logs (above) apply as for any page. What you tell the assistant itself is covered by that assistant's own privacy policy, not this one.
Changes
If this changes, the "last updated" date above will change too. Because Cradle keeps no contact details, we cannot notify you directly; check this page.