← Back to Inukshuk
Inukshuk — Privacy Policy
Last updated: 18 November 2026
Inukshuk is a free app for offline trail navigation: it displays georeferenced PDF maps with
your GPS position and records your routes as GPX files. This policy explains what the app does
and does not do with your data. The short version:
your data stays on your device.
Who we are
Inukshuk is developed by Marc-André Vigneault. For any privacy question, contact:
marc-andre.vigneault@mvxtechnologies.com.
Data the app uses
-
Location (GPS). With your permission, the app reads your device location
while it is open to show where you are on the map and, when you start a recording, to build
your trail. Your location is never used for advertising or analytics, and your recorded
trails stay on your device. A few features send a position off the device, always for that
feature alone; they are listed in the next point.
-
When a position leaves your device. Naming a saved recording sends its
first recorded point to your device's built-in geocoder (Google Play services on
Android, Apple on iOS). Searching for a place, and the weather fields of the info strip,
send your position rounded to about 1 km. Drawing a route in Trails or Roads mode
sends the points you tapped. Downloading an offline area sends that area's centre. If you
use an external GNSS receiver with RTK corrections and turn on
Send my position to the caster, your precise position goes, encrypted, to the
correction service (NTRIP caster) you chose. Team mode shares your position with your
teammates, end-to-end encrypted. Uploading an outing to Strava sends its route. Each case is
described under "Network connections", "External GNSS receiver" and "Team mode over the
internet" below.
-
Files you import and create. PDF maps you import, the GPX tracks you
record, and the activity files you import (FIT, TCX, GPX, or a Strava or Garmin export zip)
are stored locally on your device, inside the app's private storage.
Imported files are read and converted into trails on your device; nothing about them is sent
anywhere. We never upload them, and the only way one leaves your device is if you choose to
share or export it yourself — or upload an outing to Strava, if you have connected an
account. You can delete any map or track inside the app at any time, and uninstalling the
app removes all of them.
-
Automatic backup to your own folder. If you choose a backup folder
(Settings → Privacy & data → Backup), the app copies your trails, maps, photos and
settings into an Inukshuk Backup folder inside it, so you can restore them after
reinstalling the app. The backup stays in the folder you chose — on your phone, or in iCloud
Drive or another storage app you picked, which then keeps it under its own terms. It is
never sent to us. Passwords, sign-in tokens, team data and downloaded map tiles are never
written to it, and neither are trails imported from Apple Health or Health Connect: they
stay on your phone only. You can stop the backup or delete the folder at any time.
-
Activities you import from Strava, Apple Health or Health Connect. If you
connect Strava or allow access to Apple Health (iOS) or Health Connect (Android), the app
can import your past activities as trails. What is read, and how, is described under
"Strava" and "Apple Health and Health Connect" below. The imported trails are stored on your
device and shown only to you. Trails imported from Strava are copied into your backup folder
like your other trails, if you chose one; trails imported from Apple Health or Health
Connect never are.
Data we collect
Inukshuk has no user accounts, no analytics and no advertising, and it never
sells data. Your maps, trails, waypoints, photos, imported activities and health data stay on
your device; if you turn backup on, a copy of all but the health data also goes to the folder
you chose. The app does send some data off your device, each time only for the feature that
needs it. Most of it is optional:
-
Email address: only if you use "I already donated" (below), or if you type
it as the user name of an RTK correction service (some ask for one).
-
Name, town or region, and the store receipt numbers of your tips: only if
you ask to appear on the donors list (below).
-
Approximate location (about 1 km) and what you type in place search: for
weather fields and place search.
-
Precise location: for the cases listed under "When a position leaves your
device".
-
Error reports and device diagnostics: on by default, and you can turn them
off (below).
-
A random installation identifier: sent to Expo's update service when the
app checks for updates.
For Google Play's Data safety section, the location and search text sent to public weather,
geocoding, search and routing services count as shared with those services.
Everything else goes only to us or to the providers that run our services for us: Cloudflare,
Resend, GitHub and Expo.
Requests that reach servers of ours (run on Cloudflare):
- map tiles, the Explore catalogue and long-distance trails;
- the points of a route you draw in Trails or Roads mode;
- place searches, with their text and a position rounded to about 1 km;
- error reports;
- the optional donor submission and "I already donated" steps;
- if you connect Strava, the sign-in tokens on their way to Strava.
None of them carry an account. Our server keeps no request logs: it keeps only what each
section below says it keeps. A team with the internet on also uses our relay, which only ever
sees encrypted data (see "Team mode over the internet" below).
Tips. An optional tip (Settings → Support Inukshuk) is processed entirely by
Apple or Google; we receive no payment details. That screen also downloads the public
support page's figures from our website, which carries nothing about
you.
Donors list (optional). After a generous gift, the app offers to add your
name to the public "Prominent donors" list. Only if you choose to, it sends the display name
you type, an optional town or region, your platform (iOS or Android) and the store receipt
numbers of your tips, so we can check the gift before publishing. This form asks for no email
and no account. After our check, the name and place are shown publicly in the app and on the
support page. To have your name removed, or an unpublished
submission deleted, write to
marc-andre.vigneault@mvxtechnologies.com.
"I already donated" (optional). If you gave some other way, the Support
screen can hide the tip button on your device for a year. It asks for an email address and
sends a one-time code to it through our email provider (Resend). The address is used only to
send that code and is never shared. Our server does not store the address: it keeps only a
salted hash of it with the code, which expires after 15 minutes and is deleted once used, or
within a day at most (it is kept that long only to limit repeated requests). We do not check
whether you donated.
Apart from these optional steps, the one place we ask for anything is the Android beta signup
on our website, which is optional and separate from the app — see below.
Joining the Android beta
Android testing is invitation-only while the app is in closed testing, so joining means giving
us an email address. That address is used for one thing: sending you the link to join the
test, and the occasional note about the beta itself. We do not sell it, share it, or use it to
advertise to you, and it is not connected to anything you do inside the app.
Signing up is handled by Google, so your address is stored in Google's systems and is subject
to Google's privacy policy as well as this
one. Joining the test also means Google Play knows you are a tester, which is how the app
reaches your device.
You can leave at any time: unsubscribe from the list, or ask us to remove your address by
emailing
marc-andre.vigneault@mvxtechnologies.com. Once the app is published publicly on Google Play, the list has served its purpose and will
be deleted.
Error reports
When the app hits an error, it records a report and — if error reporting is enabled — sends it
automatically so the problem can be fixed. A report contains only technical details: the error
message and stack trace, the app version, the operating-system version and device model, and a
short list of the actions the app took just before the failure. It contains
no location, no map or trail content, and nothing that identifies you.
Error reporting is on by default. Reports go to our server (on Cloudflare), which files them
as issues in the app's private GitHub repository, accessible to authorized project
collaborators. Before a report leaves your phone, file paths, quoted text, coordinates, IP
addresses and team identifiers are removed. Each report is linked to a random fingerprint of
the error, not to you or your device. You can turn this off at any time:
Settings → Privacy → Automatic error reporting. With it off, nothing is sent.
Network connections
Inukshuk works offline, but a few features fetch data over HTTPS — from our own tile server
and directly from third-party servers. In each case that server receives your device's IP
address and the map area or tile coordinates being requested — the normal information any web
request carries. None of them receive an account or identity (the app has none), and the PDF
maps you import are rendered entirely offline with no network connection. All of these
connections are encrypted (HTTPS), and so is the connection to an NTRIP correction service
(see "External GNSS receiver").
-
Our tile server. The default base map, its contour lines, named peaks and
the map's label font come from our own tile server, which runs on
Cloudflare. The map data is from
OpenStreetMap (built by Protomaps), and the contour lines are drawn from the open "Terrain
Tiles" elevation dataset. A request carries only the tile being asked for and your IP
address: no identity, and no location beyond the map area on your screen. Our server keeps
no logs of its own and stores nothing about you; it only caches the map tiles themselves.
The requests are processed by Cloudflare, which hosts the server, under Cloudflare's privacy
policy.
-
Snapping a drawn route to trails or roads. When you draw a route on the map
in Trails or Roads mode, each stretch between two points you placed is
sent to our tile server, which asks a routing service for the path along real trails or
roads: BRouter (brouter.de) for trails,
and the FOSSGIS e.V. Valhalla
server (valhalla1.openstreetmap.de) for roads. What is sent is only the coordinates of the
two points you tapped (rounded to about a metre) and the mode — not your GPS position, no
identity, and nothing else about your trails. The routing service sees our server's address,
not yours, but it may keep those coordinates in its logs for a short time (BRouter states
two weeks). Our server keeps the answer in Cloudflare's cache for up to 7 days, under a
fingerprint of the request, so that the same stretch is not asked twice; it keeps no log of
who asked. Freehand mode sends nothing: its straight lines are drawn on your
device. Routes come from OpenStreetMap data (© OpenStreetMap contributors).
-
Other base maps. The satellite and relief base maps, the map draped over
the 3D terrain view, and the maps you make for printing load image tiles from
Esri / ArcGIS Online.
-
Elevation data. The shaded relief on the map and the 3D terrain view
download public elevation tiles hosted on Amazon Web Services (the open "Terrain Tiles"
dataset).
-
Naming a downloaded map area. When you download an offline map area, the
app asks OpenStreetMap's
Nominatim service for the name
of the nearest place, so the download can be labelled something memorable ("Sainte-Adèle")
instead of a set of coordinates. That request sends the centre coordinates of the area you
chose to download — not your own position, and only at the moment you start a download. If
Nominatim does not answer, the app falls back to your device's own built-in geocoder (Apple
on iOS, Google Play services on Android), which receives the same coordinates.
-
Naming a saved recording. When a recording is saved, the app asks your
device's built-in geocoder (Apple on iOS, Google Play services on Android) for the place
name at the recording's first recorded point, so the outing can be titled
"Sainte-Adèle — morning" instead of a timestamp. Unlike the map-area case above, these
coordinates are a position you actually visited — the place you started. The
request goes to your device's operating system, which handles it under
Apple's or
Google's own privacy policy; it is not
sent to us. If the geocoder does not answer within five seconds the app gives up and names
the outing by time of day instead.
-
Long-distance trails. Explore downloads a list of long-distance trails
(built from OpenStreetMap data) from
our own tile server, and, when you open a trail, that trail's route. Only the trail's id is
requested — never your identity or your location; which trails are near you is worked out on
your phone.
-
Searching for a place. When you type a place name into the map's
Search places box, the app sends what you typed, your phone's language (English or
French), and an approximate location — your position, or the map's centre if the app has no
position, rounded to about 1 km — to our own tile server, so nearby places come
first. Our server passes the same three things on to
Photon, an OpenStreetMap place search run by
komoot, which answers with matching places;
Photon sees our server's address, not yours. Answers are cached on our server for a day so
repeated searches do not reach Photon again, and our server counts requests per IP address
for a minute to prevent abuse; nothing is logged or kept beyond that. Coordinates you type
into the box are never sent anywhere. With no connection, nothing is sent: the box searches
your own trails, waypoints and maps on the device. The last ten places you picked are kept
on your phone only, and Clear in the search box removes them.
-
Weather in the info strip. When you place a weather field in the info strip
(Temperature, Wind, Humidity, Dew point, or
Sun info with its UV index), the app asks a public weather service for the current
conditions, or today's UV index, at your position (or at the map's centre if the app has no
position), rounded to about 1 km. Depending on the place and the source you choose,
that service is Environment and Climate Change Canada (
api.weather.gc.ca, which
receives a box of about two degrees around that point), MET Norway
(api.met.no), the U.S. National Weather Service (api.weather.gov,
which is then asked for the latest observation of its station nearest that point), or, when
the app offers it as a source, Open-Meteo through our relay on our tile server
(tiles.mvxtechnologies.com). The service receives those coordinates, your
device's IP address, and the app's name and version; no identity. For Open-Meteo, the app
sends our relay only the centre of the grid cell about 5 km wide (0.05°) that contains that
point; the relay passes that cell centre on to Open-Meteo
(customer-api.open-meteo.com), which never sees your IP address. The relay
keeps Open-Meteo's answer for up to an hour to answer nearby phones, and keeps no log of
coordinates or IP addresses. The Weather extension's forecasts (hour by hour, at altitude,
or several models compared) go through the same relay the same way: the app sends only that
cell centre, the models' names, for a comparison the one quantity compared (temperature,
rain, wind or gusts), and a code that every copy of the app carries (it names the app, not
you). The relay keeps each of those forecasts until the model's next run is out, at most 6
hours, and when Open-Meteo cannot answer, or when our allowance of Open-Meteo calls is used
up, it may answer with the last copy it kept, at most 6 hours old. The app asks again at
most every 15 minutes for the weather and every 30 minutes for the UV index, or after you
move about 5 km, never for every GPS fix. With no weather field in the strip, nothing is
sent.
-
Tides. With the Tide stations extension installed, the map shows
tide stations. Their positions come from our tile server, except Canada's: the app downloads
the list of Canadian stations from Fisheries and Oceans Canada
(
api-iwls.dfo-mpo.gc.ca), a request that carries no location, and refreshes it
at most once a week. When the app shows a station's water level, its next high and low or
its curve (on the map's level labels, on the station's card, or in the info strip's tide
fields), it asks the agency that runs that station: Fisheries and Oceans Canada for Canadian
stations, NOAA Tides & Currents (api.tidesandcurrents.noaa.gov) for U.S.
stations, and the Norwegian Mapping Authority, Kartverket
(vannstand.kartverket.no), for Norwegian stations. Those requests name the
station (its id, or for Kartverket the station's coordinates) and a time window, never your
position: the info strip's nearest station is worked out on your phone. The agency receives
your device's IP address. Observed levels are asked for at most every 10 minutes;
predictions once a day, and they are kept on your phone.
-
Explore (the map catalogue). The Explore tab downloads a catalogue of free
public maps, and the lists of activities, terrain and collections it is sorted by, from our
own site (
inukshuk.mvxtechnologies.com). That request carries no location and
no identity; maps "near you" are picked on your device. When you then download a map, the
file comes directly from the publisher that hosts it — the U.S. Geological Survey, Natural
Resources Canada, the U.S. Forest Service, Geoscience Australia or Cartes Plein-air
(cartespleinair.org) — and that publisher's server sees your IP address and
which map sheet you asked for. The Parcs Québec collection opens the park's page on
sepaq.com in your browser, where Sépaq's own privacy
policy applies.
-
Strava (only if you connect it). Described in its own section below. If you
never connect a Strava account, the app never contacts Strava.
-
App updates. On launch the app asks
Expo's update service (EAS Update) whether newer app
code is available. That request carries basic technical details: the app version, the
platform, and a random identifier the update library creates when the app is installed (Expo
uses it to count installations). It carries no location and no personal data. The app also
asks its store whether a newer version is out. On iPhone it asks Apple's App Store
(
itunes.apple.com), at most once an hour, with the app's identifier; Apple
receives that and your device's IP address, under
Apple's privacy policy. On Android it
asks the Play Store app on your device, on each launch, which answers under
Google's privacy policy. Neither is sent
to us.
-
Error reports. If automatic error reporting is on, technical error reports
are sent to our server, which files them on GitHub, as described above. They are queued on
your device while you are offline and sent when a connection returns.
Team mode over the internet
When a team admin turns on the internet for a team, its members' phones find each other
through a small relay service of ours, run on Cloudflare (Cloudflare acts as our processor).
Positions, messages and everything else a team shares are end-to-end encrypted between the
members' phones: the relay cannot read them.
The relay sees the IP address of each phone that connects, when it connects and how much it
sends. It keeps nothing: no storage, no logs. Phones meet in rooms named by a code that
changes every day and that only team members can work out, so the relay cannot tell which team
is which.
When two phones can reach each other directly, they connect phone to phone, and each one sees
the other's IP address. "Always use the relay", in a team's Connection screen, sends
everything through the relay instead (Cloudflare's TURN service), so teammates never see your
IP address.
Someone removed from a team keeps what their phone already received; they receive nothing new.
Strava
Connecting Strava is optional, from
Settings → Connections. It opens Strava's own sign-in page in your browser, where you
choose what to allow: uploading activities, reading your activities, or both. We never see
your Strava password.
-
Sign-in tokens. Strava requires the app's secret key to complete a sign-in,
and that key must not be built into the app. So the one-time authorization code from the
sign-in, and later the refresh token used to renew access, pass
through our tile server, which adds the key and forwards the request to
Strava. Strava's answer goes straight back to the app. Our server does not store or cache
any of it. The resulting tokens are stored on your device only.
-
Importing your activities. If you allow reading your activities, the app
reads your Strava activity list and, for each activity it imports, its recorded streams —
position, time, altitude and heart rate — to save it as a trail on your device. You can run
an import yourself, and by default the app also imports new activities automatically when
you open it (at most every 15 minutes); you can turn that off with
Import new activities automatically. Imported Strava data is stored only on your
device and shown only to you. It is never sent to us or to anyone else.
-
Uploading outings. If you allow uploads, you can send an outing you choose
to Strava. Doing so sends that outing's route and statistics to Strava under your Strava
account. Nothing is uploaded unless you ask for it.
-
Disconnecting. Disconnect revokes the app's access on Strava's
side, deletes the tokens from your device, and can also delete every trail that was imported
from Strava. You can also remove Inukshuk from your Strava settings at any time.
What Strava does with your data on its side is governed by Strava's privacy policy. Inukshuk
does not connect to Garmin: the Connections screen only explains how to link Garmin Connect to
Strava, so your Garmin activities can reach Inukshuk through Strava.
External GNSS receiver (RTK corrections)
With the External GNSS receiver extension, you can connect to an RTK correction
service (an NTRIP caster) that you choose, such as Centipede or Point One Polaris. The app
then sends that service the user name and password you entered. If you turn on
Send my position to the caster, it also sends your receiver's precise position about
every 10 seconds, which some services need. This goes straight from your phone to the service
you picked, never to us, under that service's own privacy policy. The connection is always
encrypted (TLS); casters without encryption, such as RTK2go, are not supported. Your password
is kept in your device's secure storage. Without the extension, or without a correction
profile, nothing is sent.
Apple Health and Health Connect
On iOS, Inukshuk can read from Apple Health; on Android, from Health Connect. Both are
optional, and the app reads nothing until you allow it in the system's own permission screen.
-
What is read. Apple Health: your workouts and their routes. Health Connect:
your exercise sessions, their exercise routes, and distance, plus access to that history
beyond the last 30 days so older workouts can be imported. Nothing else — no heart rate,
sleep, body measurements or any other health data.
-
Why. Only to import those workouts as trails on your device, so you can see
them on your maps. The access is read-only: Inukshuk never writes to Apple Health or Health
Connect.
-
Where it goes. Nowhere. Health data and the trails imported from it stay on
your device. They are never sent to us or to any third party, and never used for
advertising, marketing, data mining or any purpose other than showing you your own trails.
The app does not store health data in iCloud, and never writes it, or the trails imported
from it, to the backup folder you may choose (even one in iCloud Drive); like the rest of
the app's data on your phone, imported trails can be part of your device's own backup if you
have turned device backups on. An imported trail leaves your device only if you yourself
share or export it, or send it to Strava.
-
Stopping it. You can revoke access at any time — in the Health app or
Settings → Health → Data Access & Devices on iOS, or in Health Connect's
settings on Android — and delete imported trails in the app.
Permissions
-
Location (while using the app): to show your position and record trails.
-
Location (in the background, optional): used only while you record a trail,
or while you share your position with your team using Share my position · Always.
It keeps either one going when the screen turns off or you switch apps. A notification shows
whenever it is active, and it stops when you stop the recording, set sharing back to
Recording or App open, or turn off Share my position. Recorded
positions go into your GPX track on your device. Shared positions go only to your teammates,
end-to-end encrypted. If you decline this permission, recording and sharing still work while
the app is open on screen.
-
Apple Health (iOS, optional): read access to workouts and workout routes,
to import them as trails on your device. Inukshuk asks for no write access and never saves
anything to Health.
-
Health Connect (Android, optional): read exercise sessions, read exercise
routes, read distance, and read data older than 30 days — to import your workouts, with
their routes, as trails on your device. All four are read-only.
Children
Inukshuk is a general-audience utility and is not directed at children under 13.
Your control and rights
Because all of your maps and tracks live only on your device, you are in full control: delete
individual items in the app, revoke the location permission in your device settings, revoke
Apple Health or Health Connect access in the Health app or Health Connect settings, disconnect
Strava in Settings → Connections (optionally deleting the trails imported from it),
turn off automatic error reporting in Settings, export a copy of everything from
Settings → Your data → Download your data, or uninstall the app to erase everything.
What we hold on our side, and how to have it deleted, is under "Deleting your data" below.
Deleting your data
Everything on your phone is deleted when you delete it in the app or uninstall Inukshuk. For
what reaches us, email
marc-andre.vigneault@mvxtechnologies.com
and we will delete it within 30 days: your donor entry (published or pending), or the error
reports that came from your device (tell us the app version and roughly when). Some data
deletes itself: "I already donated" codes and their hashes within a day, search and route
caches within 1 and 7 days. We keep no account or history that ties anything else to you.
Changes to this policy
If this policy changes, the updated version will be posted at this URL with a new "last
updated" date.