Privacy Policy

Last updated 5 October 2026. This policy applies to the LittleHop landing site and supported LittleHop app builds. Where behaviour depends on whether a feature is configured or offered, the relevant section says so.

No account required

You can plan without an account. LittleHop does not need your name, email, or device location to make a plan. Google sign-in is optional and is used only for cloud trip backup where that feature is configured and available.

Plans and family details

Your child's age and routine, nap times, wishlists, priorities, and generated plans are stored on your device and processed there. Clearing browser or app storage removes them. They are not uploaded unless you choose the optional cloud backup and confirm the backup in the app.

Optional cloud trip backup

When available, Google sign-in through Supabase stores your account email and account ID. A cloud backup is sent only after you request it and confirm the summary shown in the app. It contains trip dates, cities and trip labels, plus the base and place labels you entered, selected Google Place IDs, priorities, visit lengths, and booked times. It does not include your child's age, routine, naps or meals, map coordinates, a searched city's map area, Google suggestion display names, or the generated schedule. Backups are separate snapshots associated with your account. Restoring shows a preview before you choose to add or replace trips; restored places need to be selected from Maps again before rebuilding. You can export trips, sign out, or request deletion of the cloud account and its backups in Settings.

Place suggestions and transit estimates

If you use Google place suggestions, city search, or place details, the text or selected Google Place ID and city information needed for that request are sent through LittleHop's server to Google Maps Platform. A place details request returns location coordinates. The current app uses on-device straight-line distance and estimates; it does not request Google Routes directions. These requests do not include your child's profile, nap routine, priorities, or generated plan. LittleHop uses a random installation ID and short-lived rate-limit counters to limit abuse; the ID is not sent to Google as an account identifier. Google processes requests under its own privacy policy. Picked Google Place IDs and the labels you entered may be stored on-device; coordinates and searched-city area expire from use after 30 days.

Sharing

A shared plan is encoded in the link you create. Anyone who receives that link can read the snapshot and its place names and times. The link is read-only and does not update when you later change your plan.

Subscriptions and service providers

If a purchase offer is available and you choose to subscribe, Paddle processes web payments as Merchant of Record. RevenueCat helps confirm subscription access and receives a pseudonymous app user ID and purchase status. When you build a Plus day, the app sends that ID and the day's random ID to LittleHop's server for entitlement verification; it does not send place names or family details in that check. Paddle receives the payment information you enter at checkout, including your email. Provider privacy policies also apply. If a build has no purchase offer, it does not collect checkout or payment details.

Cookies and analytics

The LittleHop landing page does not use third-party advertising trackers or collect information through forms. The web app may use cookieless Cloudflare Web Analytics to count page views without tracking you across sites; plan contents and place names are not included. Our hosting provider may process standard technical request data to deliver and protect the site.

Your choices and contact

Your plans can be removed from device storage in LittleHop settings or by clearing the browser/app data. For privacy questions, email hello@littlehop.app.