Last updated 29 October 2026
The short version. NestDays stores one calendar for one family on a server we control. There are no analytics scripts, no advertising pixels, no third-party trackers, and nothing is sold or shared.
Parent names, the child's first name, the parenting pattern, exchange time, calendar events, imported school and shift data, swap requests, and the night-by-night ledger. Account email and a salted password hash are stored for sign-in. The co-parent signs in through a private link and has no password.
The account holder and anyone holding the co-parent invite link. Calendar feed links are read-only and can be revoked by generating new links. Server access is limited to the operator.
If you connect a private .ics address (for example a Homebase shift feed routed through your calendar), the server fetches it periodically and stores a copy of the events so the calendar works offline. Removing the source deletes those events.
Data stays until the account is deleted. Write to support and the instance will be removed, including its database file. Ledger history is append-only inside the app so a record cannot be quietly rewritten; deleting the account deletes it entirely.
support@nestdays.io