Privacy policy
Last updated 24 October 2026
Nodebook is run by Jareth Gaskin, an individual in New Zealand, who is responsible for the personal information it holds. We follow the New Zealand Privacy Act 2020. This page says what we collect, why, where it is kept and what you can ask us to do with it. Questions go to hello@nodebook.co.nz.
What we collect, and why
- If you request an invite: your email address, whether you want to read, write or both, anything you add in the note, and when you asked. We use it to decide on invites and to reply.
- If you are invited: your email address on the invite list, when you were invited and when you created your account. We check it each time you use Nodebook, because the site is invite-only.
- Your account: your email address and password are held by Firebase Authentication, a Google service. We never see your password. Firebase also records when you signed up and last signed in, and sends the emails that verify your address and reset your password. Our own database holds your display name, your Firebase account number and when you joined.
- Your stories: everything you write, including titles, blurbs, passages, choices and labels, and when you created, changed and published them. Drafts are visible only to you. Published stories are visible to signed-in members, with your display name.
- If you email us: your message and email address, to reply to you.
What we don't collect
We don't record what you read or which choices you make while reading. There are no advertising or tracking cookies, and we don't sell or share personal information for marketing. We don't use your stories to train AI models, or let anyone else do so.
Cookies and technical information
- One cookie,
nodebook_session, keeps you signed in for up to 7 days. Nodebook doesn't work without it. Firebase also keeps your sign-in in your browser's storage. - Our host, Vercel, keeps short-lived logs of requests to the site, such as your IP address, the page asked for and your browser. Our own error messages go into the same logs. We use them only to keep the site running and to fix faults.
- When something breaks, an error report goes to Sentry: what went wrong, where in our code, and the address of the page. We switch off everything else Sentry can collect, such as cookies, form contents, your browser, your IP address and who you are, so a report doesn't say whose it is. An error message can occasionally quote a little of what caused it.
Who else handles it
We use these services to run Nodebook. They hold information for us, not for their own purposes, under their own security and privacy commitments. Some of them keep it outside New Zealand.
- Neon: our database, which holds everything listed above apart from your password. Stored in Sydney, Australia.
- Google Firebase: accounts, passwords and account emails. Google may store this in the United States.
- Vercel: runs the site, in Sydney, and keeps the request logs. Vercel is a United States company.
- Sentry: error reports, kept for 30 days, in the United States.
- Cloudflare and Gmail: email sent to hello@nodebook.co.nz is forwarded by Cloudflare to a Gmail inbox, which is also where feedback goes.
Backups
From time to time we download a copy of the database to our own computer, so Nodebook can be restored if something goes wrong. Up to 12 recent copies are kept, and older ones are deleted. A copy is used only to restore the site.
How long we keep it
- Your account and stories: until you delete them, or ask us to delete your account.
- Invite requests and the invite list: while Nodebook is invite-only. Ask, and we will delete yours sooner.
- When something is deleted, it can stay in a backup until that backup is replaced.
Your rights
You can ask to see the personal information we hold about you, ask us to correct it, or ask us to delete your account and everything in it. Email hello@nodebook.co.nz from the address on your account. We will answer within 20 working days, as the Privacy Act requires. If you are not happy with how we handle it, you can complain to the Office of the Privacy Commissioner.
Keeping it safe
The site only works over an encrypted connection, only Nodebook's server code can reach the database, and passwords are handled by Firebase, never by us. If a privacy breach is likely to cause anyone serious harm, we will tell the people affected and the Privacy Commissioner, as the law requires.
Changes to this policy
When this policy changes, the date at the top changes too. For changes that matter, such as a new kind of information or a new service that handles it, we will email members first.