EM Snow: Privacy Policy

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.

Contents

  1. For every EM Snow app and the website
  2. The iPhone app
  3. The Android app
  4. Ski stats you share
  5. Marks you share
  6. Apple Health and Health Connect
  7. The Apple Watch app
  8. The Garmin apps
  9. The website and the flyby
  10. EM-Snow Studio (desktop app)

1. For every EM Snow app and the website

Who we are

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

Rules that apply everywhere

What our server keeps, and for how long

WhatWhat it holdsHow 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 countsHow 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 logThe 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 logWhen 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).

DataWhyLawful basisHow long
Security log, error log, recent requests listKeeping the service secure and workingLegitimate interestsAs in the table above
Watches seen, daily usage countsCounting use, spotting faults, the Pro beta offerLegitimate interestsAs in the table above
Resort lookups, conditions, Next lift, Get me down, routes, ski partyThe feature you usedProviding the service you asked forNot kept beyond the logs above (party: 20 hours)
Your day usage logSeeing which resorts and dates are used, fixing faultsLegitimate interests30 days
Alerts (app and browser)Sending the alerts you choseConsentSee section 2 (at most 400 days)
Ski stats you share (iPhone app)Queues and piste conditions for everyoneConsentSee section 3
Marks you share (iPhone app)Maps of the mountainConsentSee section 3b
Older run summaries (sent by the website and apps before October 2026, and by the Garmin watch app's current alpha)Piste conditions for everyoneLegitimate interests30 days
One-tap piste reportsLive piste conditions and Piste PilotLegitimate interests30 days
Favourites sync (devices paired before October 2026), season codesKeeping your favourites and watched tripsProviding the service you asked forSee section 7 (1 year; season codes no limit yet)
Published days, map-only sharesShowing your day, finding missing runsConsent (you tap Publish or Share)2 years, or until you delete a published day
Synced watch daysOpening your watch day on your phoneProviding the service you asked for1 year
Analytics (website and app)Seeing which parts get usedConsentGoogle's own retention settings
Reports, notes, route answers, flagsBetter maps and conditions, moderationLegitimate interestsSee "Things you tell us" in section 7
Purchases and Pro codesSelling and checking Pro and API keysProviding the service you asked for (a contract)Sales list: latest 500; Studio device codes until you deactivate

Other companies involved

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:

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.

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:

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.

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.

4. Apple Health and Health Connect

5. The Apple Watch app

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)

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:

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:

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

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.

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.