Who we are

Ready Teddy is a New Zealand platform that connects early childhood education centres with relief teachers (relievers). We are a platform only. We do not employ relievers and we never pay wages.

This draft explains how we handle personal information. It is not legal advice. A lawyer still needs to review it before launch.

What we collect

From relievers: name, email, mobile number, suburb, a home location used only to work out travel time, qualification, Teaching Council number if you have one, minimum rate, weekly availability, compliance documents (photo ID, Police vet, first aid, and Teaching Council certificate if qualified), bookings, timesheets and messages we send you.

From centre staff: name, email, the centre’s street address, suburb, city, phone, rooms, the centre card (parking, sign-in, who to report to), people you invite, billing details held by Stripe, bookings, timesheets and messages we send the centre.

We collect this so we can run the service: match people, send requests, keep a record of shifts, charge the centre’s platform fee, and meet our own legal duties.

What centres never see

A reliever’s home address and exact coordinates are never shown to a centre. Centres only see suburb and travel minutes.

We never store children’s personal information. Do not type children’s names, dates of birth or other child details into Ready Teddy.

Who we share information with

Centres see the reliever details they need to request and host a shift: first name, suburb, travel minutes, qualification, rate, reliability and rating, and the centre card the reliever reads when they arrive.

Relievers see the centre name, suburb, street address on a booking, room, hours, pay and the centre card.

We use other companies to run the service: Clerk (sign-in), Supabase in Sydney (database and private document storage), Stripe (centre billing), Twilio (SMS), Resend (email), Google Maps (travel time), Inngest (scheduled jobs), Sentry (error tracking) and PostHog (product analytics). Each only gets what they need to do that job.

Sentry receives technical error reports. We scrub emails, phone numbers, addresses, cookies, auth headers, request bodies and query strings before sending, and we do not send uploaded document contents. PostHog receives product usage events identified only by an internal id and role (and centre id for centre users) — not names, emails, phones, addresses or pay rates of named people. Analytics are not collected in the demo product.

We may share information if the law requires it, or with an adviser who is bound to keep it confidential.

Privacy Act 2020

We aim to follow the information privacy principles in the Privacy Act 2020: collect only what we need, be open about why, keep it accurate and secure, use it for the reason we collected it, and let you access and correct it.

You can ask for a copy of the personal information we hold about you, and ask us to correct it. Email the address on this site or use the in-app profile screens where you can already edit your own details.

If you are not happy with how we have handled your information, you can complain to the Office of the Privacy Commissioner (privacy.org.nz).

How we store and keep it

Compliance documents sit in a private storage bucket and are only opened through a short-lived signed link. Sign-in is handled by Clerk. Database access from the app uses the server, not the browser.

We keep information while your account is open and for a reasonable time after, so we can complete bookings, payroll exports, billing and any dispute. We then delete or de-identify it unless the law says we must keep it.

Overseas storage

Our database and document storage are in Sydney, Australia. Clerk, Stripe, Twilio, Resend, Google, Inngest, Sentry and PostHog may also store or process information outside New Zealand. We only use them to provide this service.