FamilyNest — Privacy Policy
Last updated 2 August 2026
FamilyNest is a shared family calendar published by CJ Designs Ltd. This policy explains what the app stores, who can see it, and what you can do about it. It describes the app as it actually behaves.
Who is responsible
CJ Designs Ltd is the data controller. Contact: support@familynest.es.
What we store
| Data | Why |
|---|---|
| Email address and password | To create and secure your account. Passwords are hashed by our authentication provider and are never visible to us. |
| Display name | So your household can tell who is who. |
| Households you belong to, and your role | To decide what you are allowed to see and do. |
| Calendar events you create — title, times, notes, location, participants, category | The purpose of the app. |
| Managed child profiles you create — a name, and optionally a date of birth and relationship label | So a child can appear on the calendar without needing an account. |
| Files you attach to events | Stored privately; only people who can see the event can open them. |
| Reminders you set | To schedule notifications on your device. |
| An administrative log of household actions | So a household can see that someone was invited, removed or had their role changed. It records user identifiers and never email addresses. |
| Crash diagnostics, stored only on your own device | So a problem can be diagnosed if you choose to report one. See below. |
Crash diagnostics
When something goes wrong, the app writes a short technical record to storage on your own device. Nothing is sent anywhere. There is no crash-reporting service, and we do not receive these records unless you choose to send one to us yourself.
A record holds the time, the app version, your device's operating system version, the type of error and where in the code it happened. Before anything is written, it is put through an automatic filter that removes passwords, access tokens and email addresses. Only the most recent records are kept.
The app does not deliberately put your calendar into a crash record. But a technical error message occasionally quotes the data it was working on, and the filter recognises credentials by their shape rather than understanding what text means — so it cannot guarantee that a fragment of something you typed will never appear. That is why a record is only ever shared if you choose to send it, and why you can read it in full first.
You can read them yourself, copy them, or delete them at any time, under Diagnostics in the app. They are removed when you uninstall.
What we do not do
- We do not sell your data, and we never will.
- We do not show advertising, and we do not share data with advertisers.
- We do not track you across other apps or websites.
- We do not use analytics or behavioural profiling. We do not measure how you use the app.
- We do not send crash reports off your device. See Crash diagnostics.
- We do not read your calendar. Access is enforced by the database, not by staff policy.
- We do not collect your location. The app has no location permission.
- We do not access your device's contacts, photos, camera or microphone.
Who can see your events
You choose, for every event:
- Everyone in the household — every adult and teen member.
- Only chosen people — the people you add to it.
- Private — only you.
A private event does not reveal its title, notes, location, participants, attachments or category to anyone else. This includes household owners and administrators: there is no administrative override. These rules are enforced by the database itself, so they apply to every route into the data.
Children
A child in FamilyNest is a managed profile created and controlled by an adult in the household. A managed profile has no account, no password and no sign-in, and a child does not use the app directly. Only the adults in that household can see it.
We ask for as little as possible: a display name, and optionally a date of birth and a relationship label if the adult chooses to add them.
FamilyNest is not directed at children and we do not knowingly create accounts for anyone under 13.
Notifications
Reminders are scheduled on your own device and are not sent through a server. If you allow notifications, your device shows them at the times you chose. For any event not visible to your whole household, the notification deliberately shows a neutral message rather than the event's title, so a private appointment is not disclosed on a lock screen.
Where data is held
Data is stored with Supabase, our hosting and database provider, in a data centre in the United Kingdom (London region). Data is encrypted in transit and at rest. Some data may be processed elsewhere by Supabase for backups and operational purposes.
How long we keep it
Your data is kept while your account exists. Deleted events are retained briefly so they can be restored, then removed.
Deleting your account
You can delete your account from inside the app, under Delete my account. It is permanent and cannot be undone.
Deleted: your profile and sign-in details, your membership of every household, every private event you created, and your reminders.
Kept: events you shared with your household or with chosen people, and the household's administrative history, which records that actions happened without keeping your name.
We do this so that deleting your account does not erase a shared family calendar that other people still depend on. If you own a household you will be asked to hand it to another adult or delete it first.
Your rights
Under UK GDPR you may request access to your data, correction of it, deletion of it, or a copy of it, and you may object to or restrict processing. Deletion is available immediately in the app. For anything else, write to support@familynest.es and we will respond within 30 days.
Automated data export is not yet available; ask us and we will provide it manually.
If you believe we have handled your data improperly you may complain to the UK Information Commissioner's Office at ico.org.uk.
Security
Access rules are enforced in the database rather than only in the app, so they hold regardless of how a request arrives. Files are stored in private buckets that require a valid, permission-checked request to read. Invitation links are stored only as a one-way hash, so the original link cannot be recovered from our systems.
We should be equally clear about what we do not claim: your calendar is not end-to-end encrypted. It is encrypted in transit and at rest, and access-controlled, but it is technically readable by the database. We say so rather than implying stronger protection than exists.
Files attached to events are not scanned for malware. Only open attachments from people you trust.
Changes
If this policy changes materially we will say so in the app before the change takes effect.