Legal
Privacy notice
What Get Piste stores about you, who processes it on our behalf, how long we keep it and what you can ask us to do.
- Who we are
- What we store
- Why we use it
- Who processes it
- Where it is stored
- How long we keep it
- Your rights
- Changes
Who we are
Get Piste is operated by Little Mesters Ltd, trading as Get Piste, a company registered in England and Wales (company number 17470679) with its registered office at c/o Impelling, Poplars Business Park, Rotherham, S60 5TR, United Kingdom ("we", "us"). We are the data controller for the personal data described here. Contact: hello@crew.getpiste.app.
What we store
Your account
- Email address and display name, and a profile photo if you add one. If you sign in with Apple or Google, the identifier and email they give us (Apple may give a relay address).
- Sign-in records: sign-in links (short-lived), with the IP address and browser or device they were requested from, the devices you have signed in on, and the time of each sign-in.
- Your private forwarding address token, and a push-notification token for each device that has allowed notifications.
- Your preferences: snow sport, home currency, units, and which notifications you want.
- Your entitlement (Free, Pro, trial, trip pass) and the store or Stripe reference for it. We never see card numbers.
Your trips
- Trip name, type, dates, destination and base currency; a header photo fetched from an open image source, with its attribution.
- Plan items: what was booked, where, when, the confirmation reference, the cost, and who is sharing it. This is the content of your bookings.
- Members and their roles, invite links, and guest rows for people who have not signed up: a name and, if the organiser gave one, an email address.
- Attachments you upload (PDFs, images) and files extracted from forwarded emails.
- Places you add, the coordinates we resolve for them, and route legs between consecutive stops.
- Suggestions generated for the trip and whether you accepted or rejected them.
Forwarded emails
- When you forward a booking, we store the raw email (headers, body and attachments) so it can be parsed and, if parsing fails, retried or checked by you. The subject, sender, size and processing status are shown in the app.
- The body is sent to Anthropic's Claude to extract the booking as structured data. Only the email you forwarded is sent. There is no mailbox connection to grant: we never have access to your inbox and never ask for it.
Recorded days and location
- When you record a day on the mountain, the phone sends GPS fixes (time, position, altitude, speed, accuracy and heading). We keep those fixes and the runs, lift rides and statistics we work out from them, matched to the resort's runs and lifts. Days you import as GPX files are stored the same way. Recorded days are yours and are deleted with your account.
- The app asks for your precise location. If you allow only approximate location, it still records with the approximate fixes your phone gives, and they are stored and shared in the same way.
- If you switch on Share my live location for a trip, your latest fix is shown to the other members of that trip while you are recording. Your tripmates stop seeing it fifteen minutes after your last fix. It is deleted when the recording is finished or you switch sharing off; if a recording is never finished (the phone dies mid-day, say), your last position stays stored, hidden, until that day is finished (when you next record, at the latest). Sharing is off by default.
- A meeting pin you drop (a position, an optional label and an arrival time) is visible to the members of that trip. It is deleted when you arrive, take it down or drop another; once it is twenty minutes past the time you gave, it is deleted the next time the trip's pins are loaded in the app.
- We do not track your location outside recording, and the app never records in the background unless you have pressed Record (or Track on the piste map).
Money
- Costs, splits, payments and settlements you record in a trip: amounts, currencies, the exchange rate used, who paid and who confirmed. These are records of what you told us, not transactions — no money moves through Get Piste and we hold no bank or card details.
Technical
- Server logs (IP address, user agent, request path and time) kept briefly for security and debugging.
- A record of changes, kept for support and to resolve disputes. When your profile, a trip, its members, its plans and costs, a payment or settlement, a recorded day, a meeting pin, or your subscription, trial or trip pass is added, changed or removed, we note what changed, keeping the old and the new values, and which account made the change, where one did. The plans we create from a booking you forward are noted as your change. It is not shown in the app, to you or to your tripmates; only we can look at it. Each entry is kept for 365 days, then deleted.
- Crash reports from the phone and web app: technical details of the failure and of the device, such as the device model, operating system version, language and time zone settings, free memory and storage, the app version, the screen that failed and the steps in the app that led up to it (the screens opened and the buttons pressed, by their internal names). They are linked to your account by its account id (a random identifier, not your name or email). On a phone, a report sent while you are not signed in carries a random id for that copy of the app instead. The app also reports when each session starts and whether it ended normally or crashed, with the same id. A report reaches Sentry, our crash-reporting provider, from your IP address, as any internet request does; Sentry is set not to store that address. It may still work out an approximate location (country, region and city) from the address and keep that with the report. Apart from the time zone setting, a report carries no location from your phone, and no trip content.
- This website (getpiste.app) sets no cookies and runs no analytics; the only thing it keeps in your browser is your theme preference, in local storage. The web app keeps your sign-in, your settings and a copy of the account and trip data it has loaded in your browser's local storage (the copy is removed when you sign out), and its maps add the Mapbox identifier described below and keep a cache of the map tiles you have viewed.
Why we use it
| Purpose | Lawful basis (UK GDPR) |
|---|---|
| Running the service you signed up for — trips, timeline, ledger, weather, maps, imports, recording your days | Performance of a contract |
| Sending sign-in links, trip invitations and the notifications you have turned on | Performance of a contract |
| Showing your position to a trip's members while you record, and, in the phone app, sharing anonymous map usage with Mapbox: both off until you switch them on | Consent. Switch either off at any time: Share my live location on the trip's Tracking page, Share anonymous map usage with Mapbox on You. Switching off does not affect what was shared before. |
| Billing, trials and refunds | Performance of a contract; legal obligation (tax records) |
| Keeping the service secure, preventing abuse, and fixing faults | Legitimate interests |
| Answering your support requests | Legitimate interests |
| Keeping a record of changes for support and disputes | Legitimate interests |
We do not sell personal data, do not use it for advertising, and do not use your content to train models.
Who processes it on our behalf
| Vendor | What they do | What they see |
|---|---|---|
| Cloudflare | DNS, this website, routing forwarded emails to our servers, and the storage for forwarded emails, attachments and photos (EU region) | Traffic to getpiste.app; forwarded emails in transit; the files above at rest |
| Postmark | Sends our emails (sign-in links, invitations, alerts) | Your email address and the message content |
| Anthropic (Claude) | Extracts bookings from forwarded emails; ranks activity suggestions | The email you forwarded; the trip's destination, dates and place names |
| Mapbox | Map tiles, terrain, place search, driving, walking and cycling directions between stops, and offline map packs in the phone app | The map areas you view, what you type into a place search and the place or pin you choose, and the stops we route between. In the Android and iOS apps, Mapbox's optional anonymous usage and location telemetry is sent only if you switch it on in Settings; it is off by default. On the web there is no such switch: when a map is shown, your browser sends Mapbox the requests and usage events its map software uses to load, serve and count the map. These include your IP address, what a browser normally sends, and a random identifier kept in your browser's local storage. We have turned off Mapbox's optional performance reporting. |
| Geoapify | Turning place names and addresses on your trip into coordinates when an item has no pin (mostly bookings you import); public-transport directions between stops; finding places near your trip for activity suggestions | Place names, addresses and coordinates on your trip |
| Open-Meteo | Weather and snow forecasts | Destination coordinates and elevations |
| AeroDataBox | Flight status | Flight number and date |
| Frankfurter | Exchange rates | Currency pairs and dates only |
| Wikipedia and Wikimedia Commons, Openverse, Pexels, Unsplash | Trip header photos | The destination's name and coordinates, the ski area's name, and the text in the photo search box when you search (it starts as the destination's name, or the trip's name if there is none) |
| Sentry | Crash reporting for the app, and error reports from our servers | Technical details of an error. From the app: also the device (including its language and time zone settings) and when each app session starts and ends, linked to your account id; Sentry sees the IP address a report arrives from, is set not to store it, and may keep an approximate location (country, region and city) worked out from it. From our servers: the error's type, where in our code it happened, and the first line of its message with email addresses, sign-in details and everything in a web address after the site's name taken out; the API route without the values in it; the app's version and platform; and your account id if you were signed in. Not a request's content, your IP address or a sign-in token. Apart from the time zone setting, no location from your phone and no trip content. |
| RevenueCat; Apple App Store; Google Play | Subscriptions and trip passes on iOS and Android | Your account id (a random identifier, not your name or email) and your purchases and their status |
| Stripe | Subscriptions and trip passes bought on the web | Your email address and payment details (held by Stripe, not us) |
| Expo | Delivering push notifications | Device push token and notification content |
| Sign in with Google, if you use it; delivering push notifications to Android phones (Firebase Cloud Messaging, which Expo sends them through) | When you sign in with Google: that you are signing in to Get Piste. Google gives us your Google account's identifier, its email address and whether Google has verified it, your name and your profile picture. For push: the Android device's push token and the notification content. Purchases on Google Play are in the RevenueCat row above. | |
| Gravatar | Your profile picture, if you have not added a photo and your Apple or Google sign-in gives none | A one-way hash of your email address, sent by the phone or browser showing your picture (yours or a tripmate's) to fetch it |
Runs and lifts on the piste map come from OpenSkiMap and OpenStreetMap contributors; that is public map data, and nothing about you is sent to them.
Each vendor is bound by its own terms and, where required, a data-processing agreement. Where a vendor is outside the UK or EU, transfers rely on the vendor's standard contractual clauses with the UK addendum, or an adequacy decision where one applies.
Where it is stored
The API and database run on servers in the United Kingdom; forwarded emails, attachments and photos are stored in the EU. Some vendors above, notably Anthropic, Postmark, RevenueCat, Stripe, Expo, Mapbox, Sentry, Gravatar and Google, process data in the United States.
How long we keep it
- Account, trips and recorded days: for as long as your account exists. When you delete your account it is signed out and its forwarding address stops working at once, but nothing is destroyed for 60 days so that signing in again can restore it. After 60 days (or immediately, if you chose Delete permanently) your personal data, recorded days and forwarded emails are permanently deleted and their files removed from storage. A trip you were the only organiser of is archived for everyone on it when you delete your account, and the other members are told; it comes back for everyone if you restore your account; otherwise it is permanently deleted along with your data, for everyone on it, with its plans, costs and ledger. Trips that have another organiser remain for the other members, and the name you used on the trip stays on them, even after your account is permanently deleted, so that the costs and balances you were part of still add up. When your account is permanently deleted, the email address your account put on a trip is removed from it. A guest row an organiser added for you by email keeps the address they gave, as part of their trip.
- Forwarded emails: the raw email is kept until 60 days after the trip ends, so a failed import can be retried or checked, then deleted; the plan items created from it remain on the trip.
- Live position: deleted when the recording is finished or you switch sharing off, and hidden from tripmates fifteen minutes after your last fix; if a recording is never finished, the last position is kept, hidden, until that day is finished (when you next record, at the latest). Meeting pins: deleted on arrival, when you take the pin down or drop another, or, once twenty minutes past the time you gave, the next time the trip's pins are loaded in the app.
- Ledger records: kept for the life of the trip, because the group's balances depend on them.
- Billing records: as long as tax law requires.
- Server logs: up to 30 days, then deleted.
- Crash and error reports: kept by Sentry for up to 90 days.
- Attachments: kept with their trip for as long as it exists. One you remove is deleted at once, file and all. The attachments of a plan item or a trip that is deleted stay with it, and their files are removed when the trip is permanently deleted.
- Push tokens: kept for each device until you sign out on it or sign it out from Signed-in devices, and deleted at once when you delete your account.
- Record of changes: each entry is kept for 365 days, then deleted. When your account is permanently deleted, we delete at once the entries about you, the entries for the changes you made (including the plans we created from bookings you forwarded), and every entry about the trips deleted with it. On trips that carry on without you, the entries for changes other members made are kept until their 365 days are up. They can mention you, as the trip itself does.
- Sign-in links: valid for 15 minutes, single-use; deleted within 3 hours.
Your rights
Under UK GDPR you can ask us to access, correct, delete or export your personal data, to restrict or object to certain processing, and to withdraw consent where we rely on it. You can edit your profile and preferences in the app and delete your account from You → Delete account (Settings in the side bar on a wide screen; see the 60-day window above). For an export of your data, email support@crew.getpiste.app from your sign-in address and we will send it promptly. You also have the right to complain to the Information Commissioner's Office (ico.org.uk).
Get Piste is not intended for children under 13, and we do not knowingly collect their data.
Changes
We will post changes here and, for anything material, tell you in the app or by email before it takes effect.
Version 1.3. In force from . Last updated .