Privacy
What DreamFlyer records, what it sends, and what stays in your browser. It's written from the game's code.
The short version
- There are no accounts. The game never asks for your name, your email or your device's location. It does let you type the name of a place to fly over.
- It sends play statistics to PostHog, an analytics service: what happened on a visit, how many orbs, flocks and high points, and for how long. They're normally tagged with a random ID kept in your browser, never your name.
- The map comes from Google. If you type a place, Google gets that text so it can find the place.
- Your lifetime totals and best scores stay in your browser and are never sent. What each visit sends is listed below.
- The game sets no cookies of its own.
What we send to PostHog
The game sends events to PostHog's US address (us.i.posthog.com). There are eight kinds, and each kind is sent at most once per page load. A place is always named as Denver, Yosemite, the Grand Canyon, or "custom" for any other place. These five say which place you're flying: loaded, flight_started, link_shared, tell_opened and session_end. A detail is sent only where it applies: for example, there's no flight time if you never swam.
- loaded: the game started and loaded its first place.
- flight_started: your first swim stroke.
- place_switched: you switched place, from which to which (as above), and how: a button, the place list, a key, or typing.
- place_typed: you looked up a typed place, whether it was found, and the status code the lookup reported. The text you typed isn't sent to us.
- city_opened: you reopened the "fly over your city" box, from the place list or a key, and how many orbs you'd caught.
- link_shared: you shared or copied a link. It records:
- whether by share sheet or clipboard
- whether it was a spot or a place
- whether you shared right after clearing a flock
- tell_opened: you pressed "Tell us". It's sent when you press it, before any email exists, and it doesn't record whether you then sent one.
- session_end: sent the first time you leave or switch away from the tab. It sums up the visit up to that moment:
- whether you swam, how many strokes, and, if you swam, the seconds since your first stroke
- orbs caught and flocks cleared
- whether the sound was muted
- the destination's state: none found, found but not seen, seen, or reached; and, if you swam and one was found, how many metres closer you got and how many you reached
- for the first destination at the place you're flying when you leave, if one was found: how far away it was along the ground, whether it was up or down, and which rule picked it
- at that place, the seconds from its start until its first orbs appeared and until its destination was first on screen; and for the whole visit, the seconds from your first arrival to your first catch. Each is sent only if it happened.
Every event also carries:
- "coarse" if your browser reports a touch-style pointer, otherwise "fine"
- your window size
- the product name and this site's address
- an ID: normally the random one described below, or "anon" if your browser blocks storage
The loaded event can also carry two things from the link you arrived by:
- the name of the website that sent you here, if your browser passes one along (the site's name only, never the page)
- a campaign tag (
utm_source), cleaned to letters, numbers and_ . -, and cut to 64 characters
No event contains a coordinate, a typed place, a full web address or an email you wrote.
Like any web request, these reach PostHog from your network address and browser. We don't add those to the event. What PostHog keeps is set by PostHog.
The game sends no PostHog events when the page runs on the address localhost or 127.0.0.1, or in a browser that reports it is under automated control. That keeps our own automated tests out of the numbers.
The random ID
If your browser lets the game use storage, the first time it sends an event it makes a random ID and keeps it as df_id. Later visits from the same browser reuse it. If storage is blocked, nothing is kept and events say "anon" instead. That's how we tell a return visit from a new one. The game never attaches a name or an account to it.
To reset it, clear this site's data in your browser settings. The game makes a new one the next time it sends an event.
What stays in your browser
dreamflyer.progress: orbs caught over all your flights, how many flights you've taken, and for each place both the most orbs and the most high points you've reached in one visit. A custom place is listed by its latitude and longitude rounded to two decimal places (about a kilometre). Never sent.dreamflyer_flock_shape: which orb pattern you saw last, so the next flock looks different. Never sent.df_id: the random ID above. Sent with every event.dreamflyer_google_key: only if the game shows a box asking for a Google Maps key and you type one in. The box appears only when the game has no working map key. A saved key is used only by a copy of the game with no key built in, and then only to call Google: for the map and, if you type a place, to look it up. Such a copy also accepts a key in its web address, used the same way for that visit and not saved. The live site has a key built in, so it never uses a saved one.
The 3D world is Google's Photorealistic 3D Tiles. Your browser loads them from Google for the area you're flying over, so Google receives those requests.
If you type a place to fly over, the game loads Google's Maps JavaScript and asks Google's geocoder to find what you typed. If you never type a place, that part never loads.
When you share or write to us
- Sharing builds a link to where you are. For Denver, Yosemite or the Grand Canyon, if you haven't flown far from the start, that's just the place's address. Otherwise, or for any typed or custom place, the link holds:
- the latitude and longitude, to about a metre
- the place's name
- sometimes a height
utm_source=share, so we can count arrivals from shared links. You choose who gets the link. - "Tell us" asks your device to open an email draft to us. The draft includes the address of the page you're on, which for a shared spot or a typed place includes its coordinates. The email reaches us only if you send it. Pressing the button does send the tell_opened event above.
What the game doesn't do
- It doesn't ask for your device's location.
- It sets no cookies of its own.
- It installs no service worker.
- It loads no ads.
Google, PostHog and our host (Render) run their own servers, and what they record is up to them.
Questions
Write to david@skylarkcreations.com.