Privacy Policy

Tiny Jaunt helps a family decide what to do with a young child today. It is a small personal project run in the United Kingdom, used by one household and the people they invite. This page describes exactly what it collects and — just as importantly — what it deliberately does not keep.

What we collect

• Your account. Your email address, used to sign you in and to send you a code. If you sign in with Google, we also receive your name and profile picture from Google.
• Your household. A postcode and the coordinates we look up from it, any additional places you add, your nap window, and your school term dates.
• Your children. Each child’s name, date of birth and interests. The date of birth is the whole point — the age in months is what decides whether an activity fits. This is personal data about a child, and it is treated as the most sensitive thing here.
• Your ideas and saved links. Anything you add or save: titles, descriptions, venues, addresses, prices, web links, and details extracted from pages you save.
• What you planned and whether you went. Plans, visits, which caregivers and which children were involved, and any reason you gave for missing something.
• Who is free. The weekly hours and one-off exceptions you enter for each caregiver.
• Your phone number, if you choose WhatsApp. Only if you add one. We store the number, the fact you verified it, and when you last messaged us, so we know whether we are allowed to write to you. You can remove it at any time in Settings, which also switches you back to email.
• Basic usage. Page views and feature events, including the page URL, referrer, browser user-agent, and an approximate country and city derived from your connection.
• Billing, if you ever pay. Handled entirely by Stripe. Card numbers never reach us.

Google Calendar

Connecting Google Calendar is optional, per person, and can be undone at any time. Nothing about your calendar is read unless you have connected it yourself.

What we access. With your permission we read the events in your calendars for the next seven days, including their titles. Titles matter because people write intentions into their diary — “swimming?” — and a plain busy block cannot tell that apart from a dentist appointment. We also create a single shared calendar named “Tiny Jaunt” and can add events to it when you ask us to.

What we store. An encrypted copy of the token that lets us keep reading, the email address of the Google account you connected, and any correction you make to how we classified a particular event. That is all.

What we never store. Event titles are never written to our database. They are held in memory for the length of one request, sent once to our AI provider to be classified, and kept in a temporary cache for about fifteen minutes so an unchanged diary is not re-read. Your busy times are worked out fresh each time and are not saved at all. We do not read event locations, attendees, descriptions or organisers.

One honest caveat. The requests we send to our AI provider pass through Cloudflare AI Gateway, which retains request logs. Event titles therefore appear in those logs for as long as Cloudflare retains them, even though they never enter our own database.

Who can see it. Everyone in your household can see when each member is free, and any activity we recognised from a pencilled entry — but never the text of your calendar entries, because we do not keep it.

Disconnecting. Disconnecting deletes your stored token and the corrections derived from your calendar. You can also revoke access from your Google account permissions.

Tiny Jaunt’s use and transfer of information received from Google APIs to any other app adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is never sold, never used for advertising, and never used to train any AI model.

How we use it

To work out what to suggest today: your child’s age against each activity, the weather where you are, your nap window and term dates, who is free, and what you have done recently. To send you a daily digest if you want one, and the codes that sign you in. To keep the product working.

We do not sell your data, we do not share it for advertising, and we do not use it to train AI models.

Who we share it with

Only the services needed to run it:

• Cloudflare — hosting, database, file and cache storage, and the gateway our AI requests pass through.
• Anthropic — writes the daily summary, reads saved pages to pull out event details, and classifies calendar entries. Receives your child’s first name and age, activity details, and calendar event titles.
• Google — sign-in, and calendar access if you connect it.
• Resend — sends your sign-in codes, invitations and digest emails.
• Meta (WhatsApp) — only if you choose WhatsApp delivery. Receives your phone number and the message we send you, which includes your child’s first name and the places you are considering that day. The notification that appears on your lock screen never contains your child’s name. We do not use WhatsApp for marketing, and there is nothing to receive until you add a number yourself.
• Met Office — receives coordinates to return a forecast. No personal detail is sent.
• postcodes.io — turns a postcode into coordinates.
• Stripe — payments, if you ever use a paid plan.

Children’s data

This product exists to plan outings for young children, so it necessarily holds a child’s name, date of birth and interests, and a record of places they have been. That data is entered by a parent or caregiver about their own child, is visible only to the household they belong to, and is never used for advertising, profiling for commercial purposes, or AI training. A child’s first name and age in months are sent to our AI provider to write the daily summary; no date of birth, no address and no location history is.

If you turn on WhatsApp delivery, a daily message containing your child’s first name and the places being suggested is sent to your phone through Meta. We keep the child’s name out of the notification that can appear on a locked screen, and out of any pre-approved template, so it is only readable once your phone is unlocked. WhatsApp delivery is off unless you add and verify a number yourself, and removing the number stops it.

Deleting a household deletes its children and everything recorded about them.

How long we keep it

Your content is kept until you delete it or ask us to delete your account. Calendar titles are kept only for the life of the short cache described above. We do not currently run automatic deletion of old plans and visits — the history is what lets the product avoid suggesting the same place three weeks running.

For WhatsApp we keep your number until you remove it, the date you verified it, and when you last messaged us. We keep a record of any message we failed to deliver, so we can tell whether you missed a day. What you send us is never written to our database: a reply is read, acted on, and discarded. Meta keeps its own copy of the conversation, as it would for any WhatsApp chat.

Storage and security

Data is stored on Cloudflare’s network and encrypted in transit. Calendar tokens and saving tokens are additionally encrypted at rest with keys that are not stored alongside them. Access to production data is limited to the individual who runs this project.

Your rights

You can ask for a copy of your data, ask us to correct it, or ask us to delete it — including all of your children’s data — by emailing the address below. If you are in the UK you can also complain to the Information Commissioner’s Office.

Cookies

A session cookie keeps you signed in. There are no advertising or third-party tracking cookies.

Contact

Privacy questions, or any request about your data: hello@tinyjaunt.co.uk.