Privacy policy

Last updated: 29 September 2026 · Version 1.0

1. In short

Lullabean is a shared logbook for two parents caring for one baby. To do that, it has to hold information about your baby's feeds, nappies, sleep, temperature and growth. That is health information about a child, and we treat it accordingly.

The short version:

We collect what the app needs to work, and nothing else.
We do not sell your data, share it with advertisers, or use it to profile you.
There are no advertising SDKs and no cross-app tracking in Lullabean.
Your data is stored in the European Economic Area.
You can export everything you have logged, and you can delete your account and everything in it from inside the app.

The rest of this document is the detail that UK data protection law requires us to give you.

2. Who we are

Eelavan Ltd is the data controller for the personal information described in this policy. That means we decide what is collected and why, and we are responsible to you and to the regulator for how it is handled.


Company	Eelavan Ltd
Registered in	England and Wales, company number 09892770
Registered office	86-90 Paul Street, London, United Kingdom, EC2A 4NE
ICO registration	ZC236426
Contact for privacy questions	`privacy@lullabean.co.uk
General support	support@lullabean.co.uk

We are a very small company and we do not have a statutory Data Protection Officer. Privacy questions go to the address above and are answered by a person, not a ticket queue.

3. Who this policy covers

Three groups of people appear in Lullabean's data:

You, the account holder. An adult with parental responsibility for the baby, or someone that adult has invited to share the record.

The other parent or carer. The second member of your family group, who joined using your invite code. They see everything you log and you see everything they log. That is the point of the app.

Your baby. Your baby does not use Lullabean and does not have an account, but the app holds information about them and they are a data subject with rights of their own. Until they are old enough to exercise those rights themselves, you exercise them on their behalf as the holder of parental responsibility.

Lullabean is for adults. You must be 18 or over to create an account.

4. What we collect

Data	Why
Email address	To create and sign in to your account, and to send you account and security messages
Password	Stored only as a salted hash; we never see or hold your password
Display name	So each entry can show who logged it, and so the app can say "synced with Sam"
Invite code use	To link the second parent to the right family

4.2 Information about your baby

Data	Why
First name or nickname	So the app can use your baby's name rather than "the baby"
Date of birth, and gestational age if born preterm	Age drives nearly everything interpretive in the app: temperature thresholds, nappy guidance, feed amounts, and corrected age on the growth charts
Sex recorded at birth	Growth centiles are computed from separate UK-WHO reference tables for girls and boys; without it we cannot plot a centile

4.3 The care record

Everything you log. Depending on which trackers you have enabled, this may include feeds (type, side, duration, volume, time), nappies (contents, size, colour), sleep, temperature readings and the band they fell into, weight, length, head circumference and the computed centiles, vitamin D doses, and any free-text notes you add to an entry.

This is health data about your baby. Under UK data protection law it is "special category" data and gets the highest level of protection. We ask for your explicit consent before you can log any of it, and you can withdraw that consent at any time (see §8).

Free-text notes are yours to write, so please be aware that whatever you type into them is stored with the rest of the entry and is visible to the other member of your family group.

4.4 Information collected automatically

Data	Why
Push notification token	An anonymous identifier issued by Apple or Google that lets us send feed and vitamin D reminders to your phone. Only stored if you turn notifications on
Timezone	Reminders are computed in your local time, including across British Summer Time changes
Device and app version, sign-in timestamps, error logs	Security, fraud prevention, and diagnosing crashes

[IF YOU ADD CRASH REPORTING OR ANALYTICS — e.g. Sentry, PostHog, Firebase — IT MUST BE LISTED HERE AND IN §7. If there is none, say so explicitly: "Lullabean contains no analytics or crash-reporting SDK."]

4.5 What we do not collect

We do not collect your location. We do not access your contacts, photos, camera or microphone. We do not use advertising identifiers. We do not track you across other apps or websites. Lullabean contains no advertising SDK of any kind.

5. Why we are allowed to process it

UK data protection law requires a lawful basis for ordinary personal data, and a second, separate condition for health data. Ours are:

What	Lawful basis (UK GDPR Art. 6)	Additional condition for health data (Art. 9)
Creating and running your account	Performance of our contract with you	—
Storing and syncing the care record	Performance of our contract with you	Your explicit consent, Art. 9(2)(a)
Computing centiles, temperature bands and feed suggestions	Performance of our contract with you	Your explicit consent, Art. 9(2)(a)
Sending reminders you have turned on	Performance of our contract with you	Your explicit consent where the reminder concerns health data
Security, abuse prevention, keeping the service running	Our legitimate interest in operating a secure service	—
Responding to your support messages	Performance of our contract, and our legitimate interest in supporting our users	Your explicit consent, where you send us health details
Marketing emails, if we ever send any	Your consent	—

On consent. Because the care record is health data about a child, consent is the honest basis and we ask for it plainly during onboarding rather than burying it in this document. Withdrawing it is not a penalty box: you withdraw by deleting the relevant entries or your account, and we stop.

This is the part most policies handle badly, so it gets its own section.

A family group is created by one person. Anyone else joins by entering that family's invite code, which is a six-character code created with the family and shown in Settings to every member.

Every member of a family group has the same access, and it is the whole record: every entry, including entries made before they joined, growth measurements and centiles, the complete history, export and settings. Any member can edit or delete any entry, including yours, and you can edit or delete theirs.

Each entry keeps a permanent record of who originally created it, which does not change when someone else edits it.

Things worth understanding:

The invite code is the door. Anyone who has it can join your family and see your baby's record, including everything logged before they joined. The code does not expire, it is not limited to a single use, and it is visible in Settings to everyone already in the family. At present there is no way to change the code, and no way to remove someone who has joined. Please share it only with someone you would give a key to your house.
There is no limit on how many people can join. A family group is built for two parents sharing one baby, but nothing in the app stops a third or any later person joining with the same code.
Leaving. There is currently no way to leave a family group. If you no longer want access to a shared record, you can delete your account, which is described below.
What they logged stays. Entries made by a member remain in the record and remain attributed to them. Deleting them would tear holes in a history the family may need.
We cannot take sides. If members of a family group fall out, we are not able to arbitrate about who may see or delete what.
If one member deletes their account, the record survives for the others. Entries they made stay in the history but are re-attributed to "a parent" rather than being deleted.
If the last member of a family deletes their account, the family, the baby's record and every entry in it are permanently deleted.

7. Who else your data reaches

We use a small number of service providers, each of which is contractually a processor acting on our instructions. None of them is permitted to use your data for their own purposes.

Provider	What they do	Where	Safeguard
Supabase Inc.	Database, authentication and realtime sync — this is where the care record lives	Hosted on AWS in the EEA (Ireland)	UK adequacy for EEA storage; EU Standard Contractual Clauses plus the UK International Data Transfer Addendum cover any support access from the US
Amazon Web Services	Underlying infrastructure for Supabase	EEA	Sub-processor to Supabase; AWS's UK GDPR Addendum applies
Expo (650 Industries, Inc.)	Delivers push notifications to your device	United States	EU SCCs and the UK Addendum
Resend (Plus Five Five, Inc.)	Sends the emails the account needs — confirming your address, and resetting your password	United States	EU SCCs and the UK Addendum; the only personal data sent is your email address and a one-time code
Apple, Google	App distribution, and the push delivery networks that carry notifications to your phone	Global	Their own published terms; we receive no personal data from them beyond what is needed to distribute the app
RevenueCat, Inc.	Records and verifies purchases of the paid Growth features, and tells our server when one succeeds	United States	EU SCCs and the UK Addendum; the only personal data sent is your Lullabean account identifier and the purchase receipt, never your email address, your name or anything from the care record

We also disclose personal data where we are legally obliged to — a court order, or a regulator exercising its powers. If that ever happens and we are permitted to tell you, we will.

We do not sell personal data. We do not share it with advertisers, data brokers, or analytics companies. If Eelavan Ltd were ever acquired or its assets transferred, your data would be part of that transfer, and we would tell you before it happened and give you the chance to export and delete first.

8. International transfers

Your baby's record is stored in the European Economic Area. The UK Government has decided that EEA countries provide an adequate level of data protection, so storing it there needs no further safeguard.

Two of our providers are US companies, and their staff may access data from the US to keep the service running or to provide support. Those transfers are covered by the European Commission's Standard Contractual Clauses together with the UK International Data Transfer Addendum issued by the Information Commissioner. You may request a copy of the relevant clauses from privacy@lullabean.co.uk.

9. How long we keep it

Data	Retention
Account and care record	For as long as your account exists
Everything, after you delete your account	Removed from live systems immediately; purged from encrypted backups within 30 days
Support correspondence	24 months from the last message
Security and access logs	12 months
Records we are legally required to keep (e.g. transaction records if you ever buy something)	6 years, as UK tax law requires

We do not keep your baby's record "just in case". If you stop using Lullabean and later delete your account, it goes.

10. Deleting your account and your data

This section is the account deletion policy referred to from our App Store and Google Play listings. Permanent link: https://lullabean.co.uk/privacy-policy#deletion

You can delete your Lullabean account from inside the app: Settings → Account → Delete account. You will be asked to confirm, and then:

Your account, email address and display name are deleted.
If you are the last member of your family group, the family group, the baby's record and every entry in it are permanently deleted with it.
If another member remains, the record stays with them and your past entries are re-attributed to "a parent". Your own personal details are still deleted.
Deleting your account is the only way to leave a family group. There is no way to remove another member, and no way to leave without deleting your account.
Everything is removed from our live systems straight away and purged from backups within 30 days.
Deletion is permanent. We cannot restore a deleted account, so export your data first if you want to keep it.

If you have bought the paid Growth features, there is nothing to cancel. It is a one-off purchase rather than a subscription, so no further payment is ever taken. Deleting your account does not refund it, and we cannot refund it for you: purchases are made through Apple or Google and refunds are theirs to give, under their own terms.

You can also request deletion by emailing privacy@lullabean.co.uk from the address on your account. We will action it within 30 days.

Exporting first. Settings → Export gives you a CSV of everything you have logged. Do this before deleting if you want to keep the record.

11. Your rights

Under the UK GDPR you have the right to:

Access a copy of the personal data we hold about you
Rectify anything inaccurate — most of this you can do yourself by editing entries in the app
Erase your data (§10)
Restrict or object to our processing
Portability — receive your data in a machine-readable format, which is what the CSV export is for
Withdraw consent at any time, without affecting anything done before you withdrew it
Not be subject to decisions made solely by automated means with legal or similarly significant effects. Lullabean makes no such decisions; it displays information and thresholds for you to interpret

You exercise your baby's rights on their behalf while they are too young to do so themselves.

To exercise any of these, email privacy@lullabean.co.uk. We respond within one month. It is free unless a request is manifestly unfounded or excessive.

Complaints. We would rather hear from you first, but you can complain to the Information Commissioner's Office at any time: ico.org.uk/make-a-complaint, or 0303 123 1113.

12. How we protect your data

All traffic between the app and our servers uses TLS. Data is encrypted at rest by our hosting provider.
Access to each family's data is enforced in the database itself using row-level security, not only in the app. A query from one family's account cannot return another family's rows even if the app has a bug.
The app on your phone holds no privileged database credential. It can only ever see what your account is entitled to see.
Passwords are stored as salted hashes. We cannot read them and cannot tell you what yours is.
Access to production systems is limited to 1 people and protected by two-factor authentication.

No system is perfectly secure. If a breach happens that is likely to result in a high risk to your rights, we will tell you directly and without undue delay, and we will report it to the ICO within 72 hours as the law requires.

13. Children

Lullabean is designed for adults. It is not directed at children, is not marketed to children, and children do not create accounts.

Your baby's information is in the app because you put it there. We treat it as special category data about a child, which means: no profiling, no advertising, no use for any purpose beyond running the service for you, no sharing beyond the processors listed in §7, and deletion when you ask.

14. Changes to this policy

If we change how we handle your data, we will update this page and change the date at the top. For anything significant — a new processor, a new purpose, a change of lawful basis — we will tell you in the app or by email before it takes effect, and where the change requires your consent we will ask for it rather than assume it.

Previous versions are available on request.

15. Contact

privacy@lullabean.co.uk Eelavan Ltd, 86-90 Paul Street, London, United Kingdom, EC2A 4NE