Privacy
Staying Home Sucks is a trading name of La Quenta Por Favor Ltd, registered in England and Wales, company number 17525464. Registered office: 38 Doudney Court, Bedminster, Bristol, England, BS3 4AP. We are the data controller for what this page describes. Write to us at contact@stayinghomesucks.com.
No accounts, and the only personal data we keep is what you send with our contact form. We set no cookies of our own unless you ask us not to count your visits (below), and we do not store IP addresses or browser details, apart from the request log our host keeps for 7 days (below). Our host sets no cookies for visitors either (below).
If you press the moon button at the top for dark mode (or back to light), your browser keeps that one choice on your device so the next page opens the same way. It is never sent to us. Without a press, the site follows your device's own setting and keeps nothing.
Three more choices stay on your device the same way, only if you make them, and are never sent to us. On a place with a local name, the "Name in …" button keeps whether you see English or local names first (kept as names). On a map, the Airports switch keeps whether it shows airports (kept as shs-map-airports). The currency switch at the top keeps the currency you picked for prices (kept as currency); without it, prices are in your start point's currency. The site works the same without them.
The home page also keeps your last search on your device (the sports, dates, where and filters you picked, and a start point you chose over the nearest one), so it opens as you left it. It is not a cookie. It goes to us only as a search: when you press "Let's go", or just before (below). It is forgotten after 30 days.
The spots list keeps, on your device too, the top ten spots of each search you run and their scores, so the same search next time can say what changed since you looked. They go to us only with that same search from the home page, when it is sent (below), and we keep nothing of them. They are forgotten after 30 days.
So the results are ready sooner, the home page sends your search to our server before you press "Let's go": when the page opens with a sport ticked, and again a moment after you change it, four times at most. The spots list does the same after you change its search, before you press "Show spots". It sends the same search the button would, nothing more. Our server makes the results page from it and keeps that page until the forecast next refreshes, a few hours at most, for anyone who asks for the same search. We log nothing from it: a search is logged only when you press the button and open its results. Your browser does not send it if it asks sites to save data.
To fill in "From", we use the rough location of your connection (the city Cloudflare, our host, guesses from it) to pick the nearest start point. We do not store that location. We keep only the start point it picked, with your search, as with any search (below). You can change "From" to anywhere on the list.
To count unique searches we keep a hash of your connection's address and your browser's name, made with a secret that changes every day and deleted within 48 hours, so it cannot be linked across days or traced back to you. The address itself is not kept. If your browser sends Global Privacy Control, or you press "Don't count my visits" (below), we log nothing at all.
Under the same daily hash we log which of our pages you open, in order, so we can see which pages lead people on and which they leave from: the page's address without anything you typed, the kind of page, the name of the site that sent you (such as google.com, never the page you were on there), whether you are on a phone or a computer, and your browser's and system's names, a word each (such as Chrome and iOS, never the full name your browser sends or its version). Nothing else about you or your browser. After the day it cannot be joined to any other day.
Each page our server answers is also counted, with no hash and no id, by who asked (a person's browser, a search engine or another robot, or a script), the browser's or robot's name and system as above, the page, the country Cloudflare guesses and the name of the site that sent the visit. Cloudflare keeps these counts for three months. Not with Global Privacy Control or after "Don't count my visits".
Cookies
We set no cookies of our own unless you press "Don't count my visits" (below). Then we set one, named count-visits, which holds only the word "no" and tells our server not to log you. It is there only because you asked, so there is nothing to accept. Our pages load no script from a travel partner or an advertiser.
Cloudflare, our host, sets no cookies for visitors. It sets one, CF_Authorization, only for the people who run the site, when they sign in to its admin pages with a code emailed to them. It keeps them signed in for up to 24 hours. Visitors never meet it.
What your browser keeps for us is the dark mode, names, airports and currency choices, the last search and the spots you last saw (above), all on your device and none of them a cookie, and "Don't count my visits" if you press it. Of these, only the last search and the spots you last saw are ever sent to us, as part of a search.
A booking button goes through our own address first. Our server adds our partner code to the link, where the partner has given us one, and sends you on. For some partners the link then passes through an affiliate network, Travelpayouts (tp.media) or Awin (awin1.com), which tells the partner the visit came from us. That network may set its own cookies as you pass through, under its own privacy policy. Once you are on the partner's site, it may set its own cookies, under its own privacy policy.
Counting visits
We count page visits with Cloudflare Web Analytics, so we know which pages are used and can improve them. Your browser fetches its script from Cloudflare (static.cloudflareinsights.com), then tells Cloudflare the page you opened, the site that sent you, your browser's name and how fast the page loaded. It sets no cookies and keeps nothing on your device. It does not load if your browser sends Global Privacy Control.
To stop us counting your visits on this browser, press the button below. We then log no searches, pages or booking clicks from it, and Cloudflare Web Analytics does not load, just as with Global Privacy Control. Your browser keeps the choice, and sends it to our server as the count-visits cookie. Press it again to be counted, and the cookie is deleted.
What we keep, and for how long
| Searches (sport, week, start point, what we showed) | 90 days |
| Pages opened (which of our pages, the site you came from, phone or computer) | 90 days |
| Booking-button clicks | 13 months |
| Saved trips: saved, sent, reminder added, opened again | 13 months |
| Daily totals | 2 years |
| Forecast scores per run | 30 days |
| Contact form messages, with your email and name if you give them | 1 year |
Searches, pages opened, clicks and saved-trip events hold no name, email or IP address. We keep them to see how the site is used, to make it better and to know which partners earn us money. The law calls this our legitimate interests. Older rows are deleted once a day.
Photos
The photos of places come from Wikimedia Commons (credits). Every photo loads from our own domain. When we have no copy of a photo yet, our server fetches it from Wikimedia and passes it on, so your browser never contacts Wikimedia and Wikimedia sets no cookie.
Maps
Town, area, place and results pages have a map. It loads only when you scroll near it. Its background comes from OpenFreeMap (openfreemap.org), drawn from OpenStreetMap: your browser fetches those pieces of map from OpenFreeMap's servers, which see your connection as any website does. OpenFreeMap sets no cookies, and we tell it nothing about you or the page you are on. A map of ski resorts, mountain bike or climbing areas also shades the hills, from Mapterhorn (mapterhorn.com): your browser fetches those pieces from Mapterhorn's servers in the same way, and we tell Mapterhorn nothing either. The map never asks where you are. The pins on it are our own data. A "Google Maps" or "Directions" link opens Google Maps with the place's position, under Google's own privacy policy, only when you click it.
Live webcams
Some place pages offer a live webcam run by someone else (a tourist office, a resort, YouTube). Nothing from the webcam's site loads until you press "Show live webcam". Only then does your browser fetch the webcam from that site, which sees your connection and may set its own cookies, under its own privacy policy. We tell it nothing about you or the page you are on. YouTube streams play through YouTube's privacy-enhanced player (youtube-nocookie.com), which is told only that it plays on stayinghome.sucks, as it needs to. If you never press the button, the webcam's site never hears from you.
Booking and sponsor links
When you click one, we log which button, for which place, and the search it came from. For some partners we also add a random click number to the link, and keep it with the click, so the partner can tell us if a booking followed. It holds nothing about you. The partner's own site then has its own privacy policy and cookies (above).
Saved trips
"Save this trip" makes a link that holds the trip itself: the town or place, the dates, where you start and your level. We store no copy of it and set no cookie, so anyone with the link sees the same trip. We count when a trip is saved, sent, added to a calendar or opened again through its link, and nothing about you. "Email it" opens your own email app; we send nothing. "Remind me to book" is a calendar file your device keeps.
Who handles it for us, and where
These companies handle data for us. None may use it for anything but running our service.
- Cloudflare hosts the site, keeps contact form messages, sends our emails, counts visits, runs Turnstile on the contact form and keeps a log of each request for 7 days, so we can find faults. That log can hold your connection's address, the page you asked for and your browser's name. It also runs the sign-in to our admin pages, for the people who run the site. Cloudflare runs from data centres around the world, including outside the UK.
- Supabase holds our database: searches, clicks and saved-trip events, in its London (UK) region.
- Fasthosts, a UK company, holds our email inbox, where contact form messages arrive.
Cloudflare and Supabase are US companies, so your data may be handled outside the UK. When it is, it is covered by the safeguards each of them offers for data sent from the UK, in its contract with us. You can ask us for a copy.
Your rights
You can ask us for a copy of what we hold about you, and ask us to correct it, delete it, limit how we use it, or send it to you to take elsewhere. You can object to our use of it for our legitimate interests. Most of what we keep cannot be linked to you, so for searches and clicks there may be nothing we can find. Write to contact@stayinghomesucks.com; we answer within a month.
Complaints
If you are unhappy with how we handle your data, tell us first at contact@stayinghomesucks.com. We will reply within 30 days to say we have your complaint, then look into it and tell you what we found and what we did.
If you are still unhappy, you can complain to the Information Commissioner's Office (ico.org.uk), the UK's data protection regulator.
Contact
Questions about privacy go to contact@stayinghomesucks.com. If you email us, we keep the email only as long as we need to answer it.
If you use our contact form, we keep your message, the page it was about, and your email and name if you give them, for one year, then delete them; our weekly backups, kept 8 weeks, drop them after that. Each message is also emailed to our inbox at Fasthosts, where we keep it while we need it to answer you and deal with what you raised; ask us and we delete it there too. We use them only to read and answer you. The law calls this our legitimate interests. To stop scripts, we count messages from each connection for one minute, by its address, and keep no record of it; Cloudflare Turnstile checks that a person sent it: it runs in your browser, and we pass it your connection's address once to check the answer.
Last changed 31 October 2026.