Privacy Policy

Effective October 13, 2026

LullaRoute plans calm driving routes so your baby can sleep. This policy explains exactly what data the app handles. In summary, LullaRoute has no accounts and no trackers, and we do not sell data. Trip coordinates go to our routing server to compute your route, and opening Discover sends where you are so we can look up family events and the weather near you. The only ads are small partner markers on the map, always labeled “Ad” and chosen by place and time of day (near you or along your route), never by who you are.

What we process

When you plan a trip, the app sends your chosen origin, destination, any intermediate stops, and your routing preferences (slider values, target duration) to our routing server. This is required to calculate routes. These requests are not stored after the route is computed, beyond short-lived technical logs (IP address, timestamp) kept for abuse prevention and deleted on rotation.

Discover

When you open Discover, the app sends the point your trip starts from (your current location, unless you have picked a different start) to our server, so it can find family events near you and fetch current conditions from the US National Weather Service. Two outside services see a location as part of that: weather.gov, and Ticketmaster, which is one of the sources we search for family events. Both receive a coarsened point, rounded to roughly a 5 km cell. That is enough to say which town you are near and not enough to say which street. They never receive your exact position or anything that identifies you or the device. Library and community event feeds are queried by town, not by coordinates. When you tap a junction to ban a turn there, that junction’s coordinates go to our server so it can read which roads meet at it. None of this carries an account or an identifier, and none of it is kept beyond the same short-lived technical logs described above.

Location

Your device location is used on-device to show where you are on the map and to set trip starting points. Location permission is optional; you can plan trips by searching addresses instead. Background location is used only during an active drive to keep navigation working.

Search and map data

On iPhone, address search, autocomplete, and points of interest are provided by Apple Maps on your device under Apple’s privacy policy; those queries do not go to our servers. That covers the search bar, the autocomplete, the calm places in Discover and the “What’s on my way” results.

On Android there is no equivalent on-device service, so those searches go through our server instead. When you type an address, the text you type goes to our server together with a position rounded to about a kilometre, so that the results are near you rather than in another state. Our server asks two outside geocoders: Photon, run by komoot, and the United States Census Bureau’s address geocoder. The “What’s on my way” list and the calm places in Discover send the route, or that rounded position, to OpenStreetMap’s Overpass service. None of it carries an account or an identifier. We do not keep what you typed: it is held in memory for a few minutes so that repeating a search does not send it out twice, and it is never written to disk and never written to our logs.

The events listed in Discover are different. They come from our server, as described above. Route calculation uses OpenStreetMap data hosted on our own server.

Partner markers (ads)

Local businesses can pay to show a small marker on the LullaRoute map near their location: their logo, always labeled “Ad”. Markers appear on your phone: on the map at home, in the trip preview and on the drive screen. They never appear on a car screen (CarPlay or Android Auto). Everyone sees them, LullaRoute+ subscribers included.

To find markers, the app sends our server the squares of map around where you are, along your route and wherever you move the map, each about 4 km across. It never sends your exact position or anything that identifies you or your device. The server answers with the markers in those squares, and your phone picks which to show from the date, the time of day and each business’s opening hours. The squares are not written to our logs.

When a marker has been on your screen for at least a second, the app counts one view of it, at most once an hour for each marker, and notes the map it was on: browsing it, planning a trip, or driving. It also counts taps on a marker, or on the business in the trip preview’s list, and when someone uses its card to drive there, add it as a stop, call the business or open its website. It sends those counts to our server in small batches, with no location, no account and no identifier. We keep only the totals, for each marker and hour, to charge the business and to show it how its marker is doing. The network address the counts arrive from is used, in memory only, to stop anyone inflating them, and is not stored with them.

The ⋮ beside “Ad” says why you are seeing a marker and lets you report or hide it. “Report ad” sends us the marker and the reason you chose, and we review it. “Hide this ad” stops that business’s markers from showing on your phone; the choice stays on your phone and is never sent to us, and Settings → Privacy & data shows hidden ads again.

A business’s card can carry its website and phone number. Tapping the website opens it in your browser, where that business’s own privacy policy applies, and tapping the number opens it in your phone app. The app counts that it happened, as above, and nothing more.

The businesses see totals only: views and the map they were on, taps and those actions, by day, by location and by hour of the week, and what they spent. They see nothing about who saw their marker. Markers are chosen by place and time alone: no profile of you, your trips or your interests is used, and nothing about you is shared with the businesses or anyone else. If you advertise a business on LullaRoute, the partner terms describe what we keep about your partner account.

Google Business Profile. If a business connects a Google account in the partner portal, LullaRoute reads the Business Profile locations that account manages (names, addresses, map positions, opening hours, phone numbers, websites and categories) to fill in and keep up to date the locations the business links. We keep the email address of the connected Google account, a token that lets us read those locations (encrypted), the listings as last read, and which location is linked to which. We use this data only to show the business’s own locations in LullaRoute: never for advertising, never sold or shared, and never to train AI models. We never post or change anything on Google. Disconnecting Google in the portal deletes the token and the listings. LullaRoute’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Route reports and trip ratings you choose to send

If you tap “Report this route”, or rate a drive with stars when it ends, the app sends that trip’s request (coordinates and preferences), the route shown, your star rating if you gave one, and any comment you add. We keep these to fix and improve routing quality. Do not include personal information in comments. Skipping the rating (“Not now”) sends nothing.

Anonymous trip timing (optional)

To make arrival estimates accurate, the app can report, after a drive ends, how long the drive actually took compared with the plan, along with the route it followed and your routing preferences. The first and last 300 metres are removed on your phone before anything is sent, so where you set off from and where you arrived are never uploaded, and drives too short to trim that way are not sent at all. There is no account and no identifier: nothing links a trip to you or your device. This is on by default and can be turned off any time in Settings → “Help improve time estimates”.

The same report also carries how long each stretch of the road took, as a small number of “at this distance along the route, this many seconds had passed” readings, trimmed by the same 300 metres at both ends. This is what lets the app learn that a particular road is slow at five on a weekday, so it can plan a drive that lasts as long as you asked. Our server turns those readings into an average for each road at each hour and keeps only the average: the order you drove them in is never written down, so what is stored describes the road and not your journey. It is controlled by the same switch, and is not sent when that switch is off.

Reporting a bad route is deliberately handled differently. When you tap the flag to tell us a route was wrong, the exact trip is sent untrimmed, because replaying it against the routing engine is the only way to fix it. That happens only when you choose to report.

Email addresses we hold, and feedback you send

You do not have to give us anything to use LullaRoute: it downloads from the App Store and Google Play without an address, and the app has no account. Before the app was released, some people left a name and email to be sent an early build, plus anything they wrote in the optional note. We still hold those entries, and they are the only place LullaRoute holds personal contact details. We use them for nothing else. They are not used for a newsletter or for advertising, and they are never shared or sold. Ask us at support@lullaroute.com and we will delete your entry.

If you send feedback from inside the app (Settings → Send feedback), we store your message, the app version and your device model. Your email is included only if you choose to type one so we can reply. No location or trip data is attached.

Push notifications (optional)

LullaRoute may send occasional push notifications about new features and local events, and a reminder after an extended period without use. During initial setup the app shows a dedicated page that describes these notifications. The setting on that page is enabled by default and can be switched off before continuing; if it remains enabled, your device then asks for permission to display notifications. On installations that did not show this page, push notifications stay disabled until you enable them in the app’s settings. You can disable them there at any time.

While push notifications are enabled, your device provides a push token: an address issued by Apple or Google through which a notification can reach that device. Together with the token we store the app version, the app’s language, your time zone, whether LullaRoute+ is active, and the date the app was last opened. This information is used only to send each notification to the devices it is intended for (for example, an update notice to older versions, or a reminder after several weeks without use) and only during daytime hours in your time zone. No location, trip data or name is stored with the token.

Notifications are delivered through the Apple Push Notification service on iPhone and through Google’s Firebase Cloud Messaging on Android; these services process the token and the message in order to deliver it. We do not use the token for advertising or to identify you, and we do not share it. Disabling push notifications deletes the token and all information stored with it from our server immediately. If the app is deleted, the next delivery attempt is rejected by Apple or Google and the token is deleted at that point.

What we do not do

LullaRoute has no user accounts. It uses no advertising or analytics SDKs and no advertising identifier: the partner markers come from our own server and are chosen by place and time alone. We do not sell your data, and we share nothing about you with anyone for advertising, profiling or any purpose of their own; a business sees only the totals for its own markers, described above. The one thing about you that does leave our server is the coarsened location (about 5 km) described under Discover, sent to weather.gov and Ticketmaster purely to answer “what is on near here”. No identifier travels with it. We do not store your trip history on our servers beyond the route reports and ratings you choose to send, and the trimmed, unidentified trip timings described above, which you can turn off in Settings.

Data on your device

Your settings, home address, and recent searches are stored only on your device and can be removed in the app (or by deleting the app).

Deleting your data

LullaRoute has no account, so there is nothing to close and no profile to erase. How data is deleted depends on where it is stored.

On your phone. Your settings, home address, saved loops, saved events, banned turns, recent searches and the nap log never leave the device. Remove any of them inside the app (the home address has a “Remove home address” button, and saved items can be deleted individually), or delete the app, which removes all of it. We cannot see any of this and cannot delete it for you.

Data you chose to send us. Route reports, star ratings and the anonymous trip timings carry no account and no device identifier, so they cannot be traced back to a person, either by us or by anyone reading them. This is deliberate, and it means we cannot find your reports on request. If you want a specific report removed, email us the approximate date and route and we will find and delete it.

Push notifications. Disabling push notifications in the app’s settings deletes the push token, and all information stored with it, from our server immediately.

Data linked to your name or email address. If you left a name and email to be sent an early build, we hold those and anything in the optional note. If you sent feedback from inside the app, we hold your message, the app version, your device model, and your email only if you typed one. Email support@lullaroute.com from that address, ask for deletion, and we will delete it and confirm. There is no form to fill in and no waiting period beyond the time it takes us to read the message.

Short-lived technical logs (IP address and timestamp, kept for abuse prevention) are deleted on rotation and are not searchable by person.

Contact

LullaRoute is made and operated by Steixner Digital LLC, which is responsible for the data described in this policy.

Questions or deletion requests: support@lullaroute.com