Privacy Policy for OutdoorX
Last updated: 15 October 2026
OutdoorX is an app for planning outdoor activities around the weather. It has no user accounts, and
your spots, routes and settings are kept on your device. Its only server is a data relay, described below,
which stores nothing. This policy explains
what leaves your device, who receives it and why.
Who is responsible
Marcos Candela Boti, the developer of OutdoorX, is the controller of the data described here.
Contact: hello@outdoorx.app (or Settings → Support in the app)
What stays on your device
- The spots you save, the routes (GPX files) you import and the plans you make for them.
- Your settings, chosen activity and notification preferences.
- The forecasts, warnings and bulletins downloaded for your spots and routes, kept so the app works offline.
- Your device location, if you allow it: it is used only to keep a "current location" spot up to date,
and is stored on your device.
Notifications (the weekly digest, route reminders and spot alerts) are worked out on your device.
There is no push server, and we never store your routes, your location or anything about your spots.
The analytics described below record that a spot was added or opened, but not its name or where it is.
The data relay
Forecast requests, the request for the list of nearby webcams and, while Photon is in use, place searches do
not go to MET Norway, Windy or Photon straight from your device. They pass through a relay we run on Cloudflare Workers
(Cloudflare, Inc.), which forwards them, so those services see Cloudflare's address instead of yours. The relay receives your IP address and the coordinates or search text in the
request, as any server must to answer it. We have request logging turned off. The relay keeps a copy of each forecast in
Cloudflare's cache for up to about half an hour, so that others asking about the same point are answered
without asking MET Norway again; that copy contains the point and its forecast, but nothing about who asked.
Cloudflare processes these requests on our behalf, in its data centre nearest to you, under its data
processing terms; it may process data outside the EU under the EU standard contractual clauses.
Services the app contacts
To show forecasts, maps and conditions, the app asks the services below from your device.
Like any internet request, each one receives your device's IP address, along with what the
request contains. Where a request contains the coordinates of a spot, a route point or your
current location, that is noted below. Each service handles this under its own privacy policy.
- MET Norway (api.met.no), the Norwegian Meteorological Institute: weather forecasts,
through the relay above. Receives the coordinates of each spot and route point (rounded to within about
10–100 m) and, for route points, their height, but not your IP address. MET Norway stores the coordinates
in its access logs, in its data centre in Oslo, Norway. If the relay ever fails, the app may be switched
back to asking MET Norway directly, and MET Norway then receives your IP address as well.
- Photon by komoot (photon.komoot.io): a standby for MapTiler, used only while we have switched it on because MapTiler
is not working, and by older versions of the app. Place search, and naming new spots and the area where an imported route starts, through the relay above.
Receives what you type in the search box, the coordinates of the spots and route starts being named (rounded to within about 10 m) and,
if you have turned on the current-location spot, the area you are in (rounded to within about 10 km) so that nearby places are listed first,
but not your IP address. The relay keeps each answer for up to an hour, with nothing about who asked.
- MapTiler (api.maptiler.com), MapTiler AG (Switzerland): place search, the naming of new spots and route starts,
and the contour lines and weather layers on the map. These go to MapTiler straight from your device, not through the relay, so
MapTiler receives your IP address along with what you type, the coordinates of the spots and route starts being named (rounded to
within about 10 m), if you have turned on the current-location spot, the area you are in (rounded to within about 10 km), and,
through the map tiles requested, which area you are looking at.
- Windy.com (api.windy.com): webcams near a spot. The list of webcams is fetched through the
relay above, so Windy receives the spot's coordinates (rounded to within about 10 m) but not your IP address;
the relay keeps each list for up to 15 minutes. The webcam images and the player then load directly from Windy,
which sees your IP address when they do. The player is Windy's own page, may show Windy's advertising, and is
covered by Windy's privacy policy.
- Map tiles from OpenFreeMap (tiles.openfreemap.org) and AWS Terrain Tiles (s3.amazonaws.com):
the map and the height of the ground. The tiles requested show which area you are looking at.
- Weather warnings from MeteoAlarm (feeds.meteoalarm.org), and avalanche bulletins
from the European avalanche warning services: avalanche.report / EAWS, SLF (Switzerland),
lawinen-warnung.eu, lauegi.report, AINEVA (Italy) and ICGC (Catalonia). These are downloaded as whole
country or region files and receive no coordinates.
Analytics, crash reports and purchases
- Google Firebase Analytics and Performance Monitoring, only if you agree:
the app asks once, when you first open it, and you can change your answer at any time under
Settings → Privacy → Share usage statistics. Until you agree, nothing is sent and no identifier is stored
for them. If you agree, they receive which screens and features are used and how fast they load, an
app-instance identifier, device model, operating system and app version, and a rough location (country or
region) derived from the IP address. Events record what was done, such as adding, opening, renaming or
deleting a spot or opening a webcam, but not what it was done to: they do not include spot names, webcam
titles, your routes, the coordinates of your spots or your precise location. Turning the setting off stops
the sending and deletes the analytics identifier on your device; it does not undo what was already sent.
- Google Firebase Crashlytics: when the app crashes, a report of what it was doing (the
code that failed, device model, operating system and app version, and an installation identifier). It is
on by default, and you can turn it off under Settings → Privacy → Send crash reports.
- Google Firebase Remote Config: a few settings we can change without an app update, such
as where forecasts are fetched from and the oldest version still allowed to run.
- For all Firebase services, see
firebase.google.com/support/privacy.
- RevenueCat, with Google Play or the Apple App Store:
OutdoorX Pro subscriptions and purchases. RevenueCat receives an anonymous app user ID and your purchase
history, and uses them to confirm whether Pro is active. Payment is handled entirely by Google or Apple;
we never see your payment details. See
revenuecat.com/privacy.
Why, and on what legal basis
- Sending coordinates to weather, map and search services is needed to provide what you ask the app
for (Art. 6(1)(b) GDPR).
- Handling purchases is needed to provide OutdoorX Pro (Art. 6(1)(b) GDPR).
- Usage analytics and performance data are collected only with your consent (Art. 6(1)(a) GDPR, and
§ 25(1) TDDDG for storing and reading the identifier on your device). You can withdraw it at any time in
Settings; withdrawing does not affect what was sent before.
- Crash reports are needed to keep the app working and fix the faults that stop it doing what you ask
(Art. 6(1)(f) GDPR, legitimate interest, and § 25(2) No. 2 TDDDG). You can turn them off in Settings.
- Remote Config is needed to keep the app working, for example to move forecasts to another source when
one fails (Art. 6(1)(f) GDPR, legitimate interest).
We do not sell your data, show advertising of our own, or build profiles about you.
How long data is kept
Data on your device stays until you delete it in the app or uninstall the app. Firebase keeps analytics
data for at most 14 months and crash reports for 90 days. RevenueCat keeps purchase records for as long
as the store transaction exists. The services listed above keep their access logs according to their own
policies.
Your rights
Under the GDPR you may ask for access to, correction or deletion of your personal data, restrict or object
to its processing, and ask for a copy of it. Because we hold no account or server-side record of you, most
requests can be met by deleting spots and routes in the app or uninstalling it. For data held by Firebase or
RevenueCat, write to the contact address above and include the user ID shown under Settings. You also have
the right to complain to a data protection authority, for example the Bavarian Data Protection Authority
(BayLDA) or the authority where you live.
Children
OutdoorX is not directed at children under 16, and we do not knowingly collect data from them.
Changes
If this policy changes, the new version will be included in an app update and the date at the top will change.