Effective 15 October 2026, updated 11 November 2026 · Extreme Media (extreme-media.co.uk)
This one page covers everything EM Snow makes: the website, the iPhone app, the Android app, the Apple Watch app, our three Garmin apps and the EM-Snow Studio desktop app. Section 1 holds the rules that apply to all of them. Each later section only adds what is different for that app or feature.
EM Snow is made by Extreme Media (extreme-media.co.uk). Extreme Media is not a company: it is the name one independent developer uses for hobby projects, and that developer decides how the data described here is used (in data protection terms, the "controller"). There is no office or postal address; email is the way to reach us, and we answer every privacy request: [email protected].
The short version
No accounts. There is no sign-up and no login. We never ask for your name to use any app.
No adverts and no advertising IDs. None of our apps or pages show ads or read your phone's advertising identifier.
We do not sell your data, and we do not share it with anyone for their own purposes.
Your recorded tracks stay on your device unless you choose to publish or sync a day.
Rules that apply everywhere
Finding your resort. Apps need to know your resort to show its snow, lifts and pistes. Where we can, this is worked out on your own device. When a position has to be sent to our server, it is used to find the nearest resort. Unless a section says otherwise, a point sent only to find a resort is rounded to about 1 km. Each section says what its app sends.
The security log. Every request to the website or an app passes through Cloudflare to our server and appears in the security log with your IP address (see the table below). Some requests carry a position in the web address, so it is in the log too. Other sections only say "see section 1" for this.
Analytics need your consent. Google Analytics (website) and Firebase Analytics (apps) record nothing until you choose Allow. Declining is remembered and the site works identically.
Heart rate is never sent to us, unless you choose to send us a Your day file that has it in (see Helping test EM Snow).
What our server keeps, and for how long
What
What it holds
How long
Web server security log (every request to the website and the apps)
Your IP address, the time, and the full web address asked for (which can include a position, a resort, or an app's random code). Not what you sent in the body of a request.
About two weeks, then deleted
Recent requests list (for the resort conditions the website and watch apps load)
The position sent with the request, the resort, the time, which app asked, and the watch's random code if it is a watch. No IP address.
The latest 5,000 requests only, and nothing older than 90 days. Positions in this short record are rounded to about 1 km.
Weekly origin counts (where interest in a resort comes from)
We also keep weekly counts of how many requests each resort gets from each country and from each broad area (squares of about 100 km). To count how many different watches are behind those requests we pass a scrambled form of the watch code through a counter that keeps only an estimate, not the codes. No exact position is kept.
About two years
Daily usage counts
How many requests each app made, and how many different watches used it, counted from scrambled watch codes. No positions.
120 days
Watches seen (Garmin and Apple Watch apps)
The watch's random code, which app and version, when it was first and last seen, how many requests, the last feature used and the last resort.
Deleted 90 days after the watch was last seen. A scrambled (hashed) form of the watch's code, with the app and the date it was first seen, is kept until 1 July 2027 to check who used our watch apps early, for the Pro beta offer.
Your day usage log
The hour of your request (UTC), the point sent to find the resort (rounded to about 1 km, two decimal places), the resort found, and the ski date you opened. Nothing else: no IP address, no rider code, no device or app ID.
30 days. Each day's file is deleted at the start of the 31st day. It is kept outside our nightly backup.
Error log
When a request goes wrong, our server notes the error and may note the web address asked for. No IP address.
About two weeks, then deleted
Other records (alerts, published days, shared ski stats, synced watch days, purchases) are described with the feature they belong to.
Why we use your data, and on what legal basis
UK law calls the reason we are allowed to use data a "lawful basis". Ours are: your consent (you switched it on, and can switch it off); providing the service you asked for (the feature cannot work without it, or you bought something); and our legitimate interests (a fair reason of our own that we have weighed against your privacy).
Data
Why
Lawful basis
How long
Security log, error log, recent requests list
Keeping the service secure and working
Legitimate interests
As in the table above
Watches seen, daily usage counts
Counting use, spotting faults, the Pro beta offer
Legitimate interests
As in the table above
Resort lookups, conditions, Next lift, Get me down, routes, ski party
The feature you used
Providing the service you asked for
Not kept beyond the logs above (party: 20 hours)
Your day usage log
Seeing which resorts and dates are used, fixing faults
Sales list: latest 500; Studio device codes until you deactivate
Other companies involved
Cloudflare sits in front of our website and our server (snow.extreme-media.co.uk and snow.0-21.co.uk). It sees your IP address and the address asked for, and keeps its own logs under its own terms. This includes requests from Your day.
Hostinger provides the server our website and apps run on, so everything our server receives and keeps, including the Your day usage log, is stored on its machine.
Google Firebase is used in the iPhone and Android apps only, and only for two things you switch on yourself: anonymous analytics (if you tap Allow) and push alerts (if you turn alerts on).
Google Analytics is used on the website only after you choose Allow.
Map and imagery services. When a page shows a map or a 3D view, your browser fetches map pictures straight from the map provider, so that provider sees your IP address and which area of map is being shown. Depending on the view this is Esri (satellite imagery), EOX (Sentinel-2 imagery), OpenTopoMap, Thunderforest or OpenSnowMap (maps), or a national mapping service such as the Swiss federal geoportal (geo.admin.ch), basemap.at (Austria) or IGN Géoplateforme (France). Map layers on the resort page also come from Waymarked Trails (trails), Amazon Web Services (terrain shading tiles), NASA GIBS (snow cover pictures) and RainViewer (rain radar), each only when that layer is shown. Resort photos load from Wikimedia, and some pages load webcam views from Windy.
Code hosts. A few page libraries load from a public code host (unpkg), which sees your IP address like any website.
Garmin. Our Garmin apps reach the internet through the Garmin Connect app on your phone.
Stripe handles payment when you buy a Pro code or an API key. Stripe receives your card details and email address; we never see your card. Stripe tells us your email address, what you bought, the amount and a payment reference. We send the code to you by email. A copy of each sale (email address, product and code) goes to our own private alerts channel, for us only, so we can send it, and we keep a list of the latest 500 sales.
Companies that handle data for us are bound to protect it at least as well as this policy does. Cloudflare, Google and Stripe may handle data outside the UK, including in the United States. Where they do, they rely on safeguards recognised under UK law, such as UK adequacy regulations or the UK International Data Transfer Agreement or Addendum. Ask us if you would like more detail.
Your rights
Under UK data protection law (UK GDPR) you can:
ask for a copy of the data we hold about you,
ask us to correct it or delete it,
withdraw your consent at any time, for anything you switched on (ski stats, analytics, alerts, day sync). Withdrawing does not affect what was done before,
object to how we use your data where we rely on legitimate interests,
ask us to restrict (pause) using your data, for example while we check a concern you raised,
ask for data you gave us in a common computer format, to take elsewhere (data portability). This applies where we use it with your consent or to provide a service you asked for,
complain to the Information Commissioner's Office (ICO) at ico.org.uk. We would like the chance to put things right first, so please contact us too.
Because there are no accounts, we usually cannot tell which data is yours from your name or email. To help us find it, send whatever the app shows you: your rider code (iPhone app Settings), the link to a published day, a season code, or a Pro code. We will reply within one month.
Synced Garmin days can be deleted from a linked phone. If you have lost the keys on both your watch and your phone (for example after reinstalling both apps), we cannot pick your days out from anyone else's, so they are deleted automatically after a year. To ask for deletion of anything else, email [email protected]. Much of the data above also deletes itself on the timetable shown.
Changes
If we change what an app collects, we update this page first. The date at the top shows the latest version.
2. The iPhone app
Sections 2 and 2b cover the iPhone and Android apps together.
Recording. The app uses your precise location only from when you tap Start until you tap Stop. It never starts by itself and does not use your location in the background at any other time. Your full track stays on your phone.
Finding the resort. The app carries its own list of resorts (refreshed from our server at most once a day) and finds your resort on the phone, so normally no position leaves it. Only when the list knows no resort within 15 km does it send one point: the middle of your day's track, rounded to about 1 km. The same applies to the first position of a recording and to "Near me" in the resort picker. This happens for every saved day whatever your ski stats setting, because the app needs it to name your runs. The point is used only to find the resort, is not kept with your days, and carries no rider code or app ID. It appears in the security log (section 1).
Replaying a day in the flyby. The app sends the middle of the day's track to find the resort (rounded to about 1 km) and to look up the weather (rounded to about 110 m, with the date). Not kept beyond the security log.
Piste Pilot. The resort is found as above. To work out your route, the app sends your current position (not rounded) with the resort. With no signal it uses the piste map saved on the phone and sends nothing. Not kept beyond the security log. (Before app build 81, the position was also sent unrounded to find the resort.)
Publishing a day ("ghosts"). Nothing is published unless you tap Publish in the flyby replay and type a display name; the app tells you the day will be public. A published day holds up to 2,500 points of your track (position, height and time), a summary of each run (piste name, top speed, time, drop and the way the slope faces), the day's totals and the name you typed. We keep top speeds but do not show them for a single published day. It stays public until you delete it, and is deleted automatically 2 years after publishing. Deleting needs the delete key saved on your phone; if you delete the app or clear its data that key is lost, so email us the day's link. Publishing is separate from sharing ski stats.
Ski party. Only if you join a party with its code. While you are recording at a resort (not paused, and not with ski stats turned off), the app sends your chosen name and position to the party about every 30 seconds, with a random party ID made only for this (not your rider code). It stops when you pause, tap Stop, tap Leave or turn sharing off. Friends with the code see your name, where you are and which piste. Kept as in Ski party (section 7): dropped after an hour quiet, the whole party deleted within 20 hours.
Lift names. The app may ask if a lift you rode has the right name; we keep only the lift and your answer, nothing about you.
The Resort tab shows our live website inside the app, so the website rules in section 7 apply, including how it uses your location. Try a sample day is made up, never saved among your days and never uploaded.
Alerts are off until you turn them on, and are delivered through Google Firebase Cloud Messaging. For each phone with alerts on, we keep: the push token, the resorts you follow (up to 50), any trips you are watching (dates and alerts chosen), the app and phone software description (user agent), and the time it last registered. It is deleted when you turn alerts off, when Firebase says the token no longer works, or 400 days after the app last registered, whichever comes first.
Anonymous analytics are off unless you tap Allow on the first-run question or turn them on in Settings. Google Firebase Analytics then records which screens and features are used, and never receives your movement data. There are no other analytics or crash tools.
2b. The Android app
The Android app works like the iPhone app (section 2) and sends the same things, only when you use the feature. None of these requests (resort lookup, flyby replay, Piste Pilot, Resort tab) carries a name, a rider code or an app ID. The Resort tab uses your position only if the app already has location permission. The differences:
Recording starts only when you tap Start, with the app open. Android shows an "EM Snow recording" notification, which lets it carry on with the screen locked, and it stops when you tap Stop. The app does not ask for "Allow all the time" (background location), does not start with the phone and never records on its own.
Your rider code stays on this phone. The app does not back up to your Google account. If you uninstall it or clear its data, your rider code and the delete key for a published day go with it. To have shared ski stats or a published day deleted then, email [email protected] with your rider code (shown in Settings, so note it down) or the day's link.
Analytics are off until you allow them (changeable in Settings). Alerts use Firebase Cloud Messaging; the app holds a push token only while alerts are on, and turning them off removes it from our server and the phone.
The app does not read Health Connect or any other health data.
3. Ski stats you share
Your runs, lift waits and the pistes you rode help everyone see queues and how the pistes are skiing. The app asks you once ("Share your ski stats?"). Nothing is shared until you say yes. Your consent is our legal basis, and you can withdraw it at any time.
We send: each run and lift ride (start times rounded to 15 minutes, lengths to 10 seconds, speed, height, piste or lift name, wait), the resort, and a random rider code.
We never send: your track, your name, your email, or your heart rate.
We keep the detail until the day is 30 days old (or a week after we receive it if that is later, for older files), then only totals that can't be traced to you. Turn it off or delete what you shared any time in Settings.
Your rider code is a random code made on your phone. It links your shared days together until you change or delete it. It is not linked to your name, email or phone.
Totals made from many riders cannot be traced back to anyone, and are kept for up to 3 seasons.
Settings: "Share my ski stats" turns sharing on or off. "Delete my shared data" deletes everything you have shared (totals already made stay). "New rider code" starts a new code, and can delete what you shared first.
If you lose your phone without a backup, the app can no longer prove which data is yours. Email us your rider code (shown in Settings) and we will delete it. If you don't have it, everything you shared is deleted automatically within 30 days anyway. (After that, a small receipt that a day was received keeps your rider code for up to 30 more days, so a late re-send is not stored twice. It holds no stats.)
The website sends no ski stats yet. Files you drop into its flyby will get their own, separate ask first (see section 7).
3b. Marks you share
Only if you say yes ("Share my marks", asked when you first drop a mark and switched on or off in Settings; separate from ski stats). Our legal basis is your consent.
We send, for every mark (plain marks, photo spots, powder stashes, saved runs, falls, favourite lines, meeting points and filming marks): its kind and position rounded to about 20-30 metres; the resort and date; your random rider code with its secret (a password made on your phone that proves the code is yours; we keep only a scrambled copy); an upload code; which version of this text you agreed to; and, for a Garmin day, a code linking it to your synced day so it is counted once (Garmin days are described in section 6). We never send the time of a mark, your name, a device id or a filming clip number.
How we use them. Marks are pseudonymous: linked to your rider code so you can delete them, not to your name. Each night we count how many different riders marked the same kind of place in the same area (about 500 metres) in a season. Once at least 3 riders have (5 for falls and meeting points), the count becomes part of our maps and stays, holding only the kind of place, area, season and number of riders. Places fewer riders marked are never kept as counts. Nothing is shown for a resort until at least 10 riders there have shared marks that season, and never with a date or one rider's mark. To pick the places most worth showing, we compare them with how many riders passed that way, using the totals from shared ski stats (no new location data, and never one person's stats). We keep your own marks for this season and the last.
Falls and meeting points. A fall mark is never used to work out injuries or health; if we ever wanted to, we would ask you separately first. A meeting point is a place you suggest, not a record of who met or when. Both are shown only as counts for an area.
Turning it off, or "Delete my shared data", deletes your own marks when your phone next connects; places several riders marked stay in our maps. We keep a record of each yes or no (the answer, the date and the version of this text, nothing else) for 3 years after your last answer, to show you agreed. Deleted marks can stay in our encrypted backups for up to 6 months, used only to recover from a failure; a separate deletions list is re-applied if a backup is ever restored.
4. Apple Health and Health Connect
What the iPhone app reads: only downhill skiing and snowboarding workouts and their routes: type, start and end time, distance, energy burned, which app saved it, pauses and workout events, and extra details (for our Apple Watch app, the marks you added and turns per run); for each route point, the time, position, height, speed and direction. It does not read heart rate, sleep, steps or any other health data. It asks permission first, and you can change this in the Health app at any time.
On Android (Health Connect): if you turn on Health, EM Snow reads your skiing and snowboarding sessions and their routes from Health Connect, only to add those days on your phone. It reads nothing else from Health Connect, writes nothing to it, and sends none of it anywhere unless you share your ski stats (Ski stats you share).
What the Apple Watch app writes: when you record on the watch and tap Save, it writes the workout and route to Apple Health, with your permission. It stays in Apple Health on your own devices.
Nothing raw leaves your phone. Workouts and routes become a ski day on your phone, and the resort is found as for a recorded day (section 2). Only derived ski stats leave it, and only if you share them (Ski stats you share). Workouts without a route (for example from Garmin Connect) only make a day card on your phone.
Health data is never used for advertising or marketing, never sold, and never shared with anyone else.
5. The Apple Watch app
Its own random code, made the first time it runs and sent with every request so we can count watches. It is not linked to you, your Apple ID or your phone (see "Watches seen" in section 1).
Conditions, lifts, sun, avalanche and plans use your chosen resort (set on the phone) and its own position, not yours.
Next lift: only while that page is open, and with the watch's location permission, the watch sends your position (to about 1 metre) to find the nearest lifts, and again only after you move 150 m or more. Get me down: your position is sent once when you ask for a route. The server does not store these positions; they appear only in the security log (section 1).
Recording writes the workout and route to Apple Health (Apple Health) and sends nothing to us. Your iPhone app then imports it like any other Health workout.
6. The Garmin apps
We make three Connect IQ apps: the EM-Snow Field data field, the LESnow widget and the EM-Snow watch app. They talk to our server (snow.0-21.co.uk) through the Garmin Connect app on your phone. Data they send is submitted to us, Extreme Media, not to Garmin, which has no responsibility or liability for it. Positions are sent as the watch has them (not rounded) unless stated.
The watch's code. Each app sends an identifier Garmin creates for it on your watch, not your Garmin account, name or email. We use it to count users and for the watch app's optional features. What we keep against it is under "Watches seen" and "Recent requests" in section 1.
EM-Snow Field (data field)
To look up conditions for the nearest resort it sends the watch's code, the app version and the resort ID (only if you set the resort override), plus your position. In the current version that is the watch's last GPS fix, sent in the background without asking. In the next version nothing about where you are is sent until you choose a location source (the watch's GPS, or the location your phone gives Garmin for weather); if you choose a resort, only its ID is sent.
When you stop the activity timer, the current version also tries to send that day's total descent and maximum speed, with the watch's code and the last resort's ID (no position), kept for 12 hours. The next version sends no day totals. FIT recording stays in your own Garmin Connect activity and is not sent to us.
LESnow (widget)
To show conditions for the nearest resort, when you open it (and in the background if you set a refresh rate) the widget sends the watch's code, the app version and name, your resort override if you set one, and a position. In the current version (1.8.3) that is, without asking, the location your phone gives Garmin for weather (unless you turn that off), otherwise the watch's GPS. In the next version nothing about where you are is sent until you choose: the weather location (then the watch's GPS if none), the watch's GPS, or a resort code (then no position). The widget records nothing and sends no ski days.
EM-Snow (watch app)
Conditions and safety: sends your position and chosen resort, with the watch's code and version, for conditions, avalanche danger and forecast. In the current alpha this happens without asking, including once an hour in the background. In the next version nothing about where you are is sent until you choose a location source; with a resort code, the watch sends that resort's own position for the avalanche lookup, never yours.
Choose resort, Next lift (to about 1 metre, while that screen is open) and Get me down (once, when you ask) send your position. In the next version they (with Take me home and Guide to a friend) send it only if you chose Watch GPS or Garmin weather, and only while you use them. With a resort code, or before you choose, Choose resort uses the list on the watch and sends nothing, and Next lift and Get me down ask "Use your watch GPS?" each time; your position is sent only if you say yes, for that use only. The Next lift card after each run shows only when you picked Watch GPS or Garmin weather.
Ski party: only if you join with its code, shows friends' positions shared on the website (section 7).
Day sync. Days you record stay on the watch. Nothing is sent until you open "Link phone" (or turn on "Sync days to phone"). In the current alpha, opening "Link phone" switches sync on as soon as the code appears, even if you never scan it, and stored days are then sent; the next version asks first. Once on, each saved day goes to our server so you can open it on your phone (in the next version also in small parts while you record): track, runs, lifts, totals, any marks you added, and the watch model name. A synced day always carries its track, whatever your location choice, because sending the day is what you said yes to. Synced days are kept for 1 year. The watch makes its own random secret key, sent privately (never in a web address); we keep only a scrambled version. A linked phone can delete a synced day; if you have lost the keys see Your rights.
Run summaries (current alpha only): after you save a day, it sends a summary of each run (start time, length, height dropped, top speed, smoothness score) with the resort, date and watch's code, without asking, and no track or position. Kept 30 days. Removed in the next version; Garmin days will then be shared only if you say yes.
QR codes: the watch fetches the QR picture through Garmin's image service, so Garmin sees that link. A code for opening your day on your phone lasts 24 hours.
Pro for the Garmin apps
Paid Pro is not switched on yet; we will update this page first. When it is: the watch shows a short code (valid 30 minutes) that you take to our Pro page; you pay through Stripe (section 1); we email you a purchase code; you type it on up to 2 watches (6 app installs in all). We will keep the purchase (email address, payment references, which watch codes it is on, and a history of changes). Your email address is removed 1 year after your Pro ends, and watch codes on a purchase are replaced with scrambled versions 90 days after it ends.
7. The website and the flyby
Analytics
The EM Snow website (snow.extreme-media.co.uk and snow.0-21.co.uk) asks before using Google Analytics to count page visits, so we can see which parts of the site get used. Most pages load Google's script at once so the tag can be verified (a flyby or Snow Globe opened from Your day loads it only after you choose Allow), so Google sees your IP address like any website. Until you choose Allow, Consent Mode stops it recording anything: no events and no cookies. When allowed, analytics cover page views and a count of runs opened from Your day in the flyby or in 3D (with the resort only). They never see your GPS tracks, videos, or anything else you do inside the flyby or the Studio app.
If our code is copied
If our code is copied onto another website, it tells us that website's address (never anything about its visitors), so we can ask for it to be taken down.
Your location on the EM Snow website
The website never asks for your location when a page opens. Your browser only asks when you tap something that needs it, such as "near me", "Where am I" in the Snow Globe, or Piste Pilot's guidance. What is sent to our server is:
If you have already allowed this site to know your location, the resort page sends your position, rounded to about 1 km, with each resort it loads. We use it to see roughly where our visitors are looking from (a map for us, not for anyone else). We never ask for your location for this: if you have not allowed it, nothing is sent and the resort's own position is used instead.
When you ask for the resort nearest you ("near me"), your position (to about 10 metres) is sent so we can find it.
When you ask for a route from where you are (Piste Pilot, or "From where I am" in the Snow Globe), that point is sent so the route can be worked out. It is not kept.
Positions that come with a resort request go into the recent requests list (see section 1), which holds no name, email or IP address. The dot that shows where you are in the Snow Globe, and any track you replay there, stay on your phone or computer and are not sent to us. To stop your position being sent at all, take back the site's location permission in your browser's settings.
Files you drop into the flyby
Track and video files (GPX, FIT, TCX, KML and others) are read in your browser. The file is not uploaded, and your whole track only leaves your browser if you publish or share it (below). To build the replay, the page asks our server for:
the resort and the weather, using the middle of your track (rounded to about 1 km and about 110 m) and the date;
sun and shade for each run, using up to 16 run middle points (rounded to about 110 m) with the sun's direction at the time, which stands for the time of each run;
in the older GPX tool, the start and end point and start time of up to 60 runs, and the middle of your track, to add weather and piste names.
These are not stored, apart from the security log (for requests that carry them in the web address) and a weather answer cached for 30 minutes.
Ski stats: the website sends no ski stats. The flyby, the older GPX tool and the browser recorder used to send piste speed summaries unless you opted out; that stopped on 15 October 2026, and older summaries are deleted after 30 days. A new, separate ask, shown before any stats are shared, is being built (see Ski stats you share).
If you answer one of the one-tap questions about the snow on your day, your answer is kept with the resort, the date and the same browser code (the latest 200 answers per resort).
Your day
The file you drop on Your day is read in your browser and is not uploaded, unless you choose to send it to us (see "Helping test EM Snow" below). To show the weather, snow, avalanche rating and lift counts for your day, the page sends one point from your track (its middle, rounded to about 1 km) and the ski date to our server in the body of a request, not in the web address. We use it to find the nearest resort within 25 km and answer from that resort's records. If a resort is found we add one line to the Your day usage log (see section 1), so we can see how the page is used; if none is found we keep nothing. The point is not used for anything else and is not stored with your track, because we never receive your track. The request itself still reaches our server through Cloudflare, so Cloudflare and our security log see your IP address and the page address, but not the point or the date. Our server is hosted by Hostinger. Your track, heart rate and file name are never sent, unless you choose to send the file (see "Helping test EM Snow" below). Legal basis: providing the service you asked for for the lookup, and legitimate interests for the usage log (seeing which resorts and dates are used, and fixing faults).
Heart rate on Your day: if your file has heart rate in it, the page first asks how old you are, then whether you want it shown. Heart rate is health information, so it is only read if you say you are 13 or over and then say yes. It is worked out in your browser only: your heart rate, your heart-rate zones and any maximum heart rate you type in are never sent to us or anyone else. The one exception is a file you choose to send us yourself (see "Helping test EM Snow" below): it goes as it is, with any heart rate in it. Your answer, and the maximum heart rate if you give one, is kept in this browser's storage, not on our server, so we do not ask every time. "Stop using heart rate" on the page removes heart rate from the page at once and forgets your yes; clearing this site's data in your browser removes the answer too. Because the answer is kept in your browser, we cannot see it, and on a browser several people share it cannot show which of them gave it. Legal basis: your explicit consent, which you can withdraw at any time.
A run in the flyby or in 3D: if you press "Fly it" or "In 3D" on a run, the points of your day (position, height, time and speed; never heart rate, the file name or your marks) are saved in this browser's own storage so the flyby or the Snow Globe can replay them, and it opens at that run. The last 5 days saved this way stay in this browser until you clear this site's data; they are not sent to us. The code for your day travels in the part of the web address that browsers never send to a server, and is taken out of the address before anything else loads. If you have allowed analytics (see Analytics), Google Analytics counts that a run was opened in the flyby or in 3D and at which resort, as it counts other visits; it never receives your day, your track or that code. The flyby then works as it does for a file you drop on it: it asks our server for that day's weather and the terrain for sun and shade, and your browser fetches map pictures around your day from the map providers in section 1. To show the "In 3D" button, the page asks our server for the list of resorts that have a Snow Globe; that list is the same for everyone and says nothing about your day.
Downloading your day: "Download your day" makes a GPX file (your track and your marks) or a CSV file (your runs and lift rides) in your browser and saves it on your device. Nothing is sent to us. Heart rate goes into either file only if you tick "Include heart rate". The GPX file shows exactly where you went, including where your day started and ended, so think about who you share it with.
Helping test EM Snow: after you open your own day (never the sample day), the page offers to send that day's file to the developer. Nothing is sent unless you tick "I'm happy to send this file" and press "Send this file". Then the page sends the file you chose, exactly as it is, with the resort the page found and the file's format; not your name, email address or anything else, and our server does not keep your IP address with it. The file holds everything your device recorded, including your whole track and times, and heart rate if your device recorded it. We use it only to test and tune the maps for that resort. It is kept on our server only (hosted by Hostinger), never shared, and deleted after 90 days. You get a reference such as ABCD-1234: to have the file deleted sooner, email [email protected] with that reference. Legal basis: your consent.
Publishing a day
Publishing from the flyby works as for the iPhone app. A published day is also stored with a random code kept in your browser, so one person cannot fill a leaderboard or a map check with many copies of the same day. It is never shown.
Map-only share (the older GPX tool): only if you use its separate "share for the map" option, up to 2,500 points of your track (position, height and time), your runs and speeds, the resort, the date and a random code kept in your browser are sent. It is never shown publicly; we use it to find runs missing from the map. It is deleted after 2 years.
Things you tell us
Resort reports: your words, condition tags and a 1 to 5 rating are shown publicly on the resort page. We keep the latest 60 per resort.
"What is off here?" notes in the 3D view: your words, what the note is about, and the spot you pointed at or were looking at (rounded). No IP address or device code. We keep the latest 500.
Route answers in the Snow Globe: your answer about a route, any words you add, and the route asked about. We keep the latest 2,000. If you tick the box, after we have read it we may post it as a public note on OpenStreetMap, at that place.
One-tap piste reports: if you tap how a piste is skiing (closed, icy, moguls, powder or groomed), we keep the resort, the piste, your answer and a random code kept in your browser (so one person counts once). They show as live piste conditions and help Piste Pilot avoid bad pistes. Kept for 30 days.
Flags on published days: to count how many different people flagged a day, we keep a scrambled form of your IP address (mixed with a secret value so it cannot simply be looked up). It is deleted when the day is deleted.
Notes and route answers are also sent to our private alerts channel so we read them.
Favourites and season codes
Season codes: on My mountains you can save your favourite resorts and watched trips under a code, to get them back on another device. We keep the code with the resorts and trip dates and alert choices you saved. There is no time limit yet: email us the code and we will delete it.
Favourites sync (devices paired before October 2026): pairing new devices has closed, but devices already paired still share their favourites. We keep the favourites and the random codes of the paired devices for 1 year after they were last used. To let your browser get its favourites back if it clears its storage, our server sets one cookie (emsnow_did) that holds your device's random code. It lasts 1 year and is only sent to the favourites part of our server. It is not used for analytics or anything else.
Ski party
If you start or join a ski party, your chosen name and position are shared with everyone who has the party's code. A member who goes quiet for an hour is dropped, and the whole party is deleted within 20 hours.
Alerts in your browser
Your browser's own push service delivers them. We keep the same details as for the app's alerts (section 2), for up to 400 days or until you turn them off.
8. EM-Snow Studio (desktop app)
EM-Snow Studio is a desktop application for creating ski videos with telemetry overlays. Your video files and your GPS/FIT track files are never uploaded from your computer. Videos, tracks, projects and exported clips are processed and stored on your machine only. The app contains no analytics, tracking or advertising SDKs, and collects no names, email addresses, viewing habits or usage statistics. The free tier works without any account or code. A further feature, "3D flyby transitions", is planned but not available in this version: its control is shown disabled, it makes no network requests and caches nothing today.
What the app sends over the network
Studio's requests to our server pass through Cloudflare and appear in the security log (see section 1). In this version the app makes no requests to any third-party service on your behalf.
Licence verification (automatic; only once you enter a Pro code): the app sends the code and a device code to snow.0-21.co.uk, when you enter it and periodically to re-verify. The device code is made from your computer's name and hardware ID with a one-way scramble. It cannot be turned back into those details, but it stays the same for your computer, so it identifies your machine to us. We keep it against your Pro code only to enforce the limit of 5 devices per code, and delete it when you deactivate the device (Settings, any time), which removes its fingerprint from our server.
Weather and resort conditions (automatic): when you preview or export a clip that has a track, the app sends the middle point of the track, rounded to about 1 km, and the day of the track to snow.0-21.co.uk. Our server answers with the weather for that day, the resort's time zone and its conditions, for the clock and weather parts of your overlay. The rounded point goes into the recent requests list (see section 1). Answers are cached on your machine so the same track and day are not asked for again.
Name my runs (optional, off until you click Name runs): the app fetches the resort's piste map from our server to label your runs with real piste names. This sends your track's approximate area (a rounded latitude/longitude) so we can find the right resort, nothing else, and nothing is stored on our server. If you never click it, no piste data is requested. The piste map is cached locally on your machine (an application-wide cache, reused across projects for the same area).
3D flyby transitions (planned, not in this version). When it ships, and only if you turn it on (it will be off by default), the app will download map imagery and terrain for the area around your route to render a short 3D flyover between clips. The imagery will come from Esri World Imagery (Esri, Maxar and Earthstar Geographics) and the terrain elevation from our own DEM tile service at snow.0-21.co.uk. These services will receive the tile locations for the area around your route and view. Tile locations are grid references, not your exact track, but they do reveal the general area you skied. They will also receive normal network information such as your IP address, and nothing else. Your video and GPX/FIT file will not be uploaded. Downloaded tiles will be cached locally. If tiles fail to load, Studio will fall back to a plain chapter card. Esri's terms are at esri.com/legal and its privacy policy at esri.com/privacy; the DEM tile service is our own, covered by this policy.
If a future version enables 3D flyby transitions or adds further online features, this policy will be updated first and the feature will disclose what it sends. The only location Studio sends is the rounded track point described above (for the website's use of your location, see section 7).
Questions or data requests: [email protected]. This page replaces the separate Studio privacy note (19 July 2026) and the per-app notes.