Privacy Policy

1 overview

roamly is a self-hosted, open-source location tracking application. this privacy policy explains how your data is handled when using a roamly instance.

2 data collection

roamly collects only the data you explicitly provide:

account information: username and password (hashed) for authentication.
location data: gps coordinates, timestamps, altitude, speed, and battery level sent from your tracking device.
adventure data: adventure names, dates, day notes, and associated places you create.

3 data storage

all data is stored on the server where this roamly instance is hosted.
no data is sent to roamly developers or any third party by the application itself.
the instance operator is responsible for securing the server and database.

4 what leaves your server

roamly is self-hosted, so almost everything stays on hardware you control. these are the exceptions — every network request the app can make to somewhere that isn't your own server, and what it carries.

goes to	what is sent	when
map tile providers carto, esri, optionally mapbox	the map tiles you are looking at — which implies your approximate location — plus your browser's ip address	on by default. every time you open a map
overpass api mirrors openstreetmap data	bounding boxes covering areas users of this instance have travelled through, and the names of towns they have visited	when road, subway or place data is downloaded (admin-controlled; enabled by default)
your chosen ai provider whichever you configure	your location history, visits, and — if you allow it — your journal entries. this is the largest disclosure the app can make, and it goes wherever you point it	opt-in, off by default. only if you enable ai ask or summary emails
cloudflare turnstile captcha	your ip address and browser characteristics	only if the instance admin turns on the captcha
github	your server's ip address (not yours)	when the server checks for an android app update
zepp / amazfit	your zepp credentials and the health data they return	opt-in, off by default. only if you connect a zepp account
your s3 provider whichever you configure	a complete backup of your data, and optionally your photos	opt-in, off by default. only if you configure automatic backups
your smtp provider	email addresses and the contents of any mail the app sends you	only if the instance admin has configured email

reverse geocoding is fully offline. turning coordinates into city, state and country names happens entirely on your own server, using bundled us census boundary data and an offline place database. no coordinate is ever sent anywhere to be named. earlier versions of this policy said otherwise; they were describing an approach roamly no longer uses.

the web app loads no third-party javascript at all — fonts and the map library are served from your own server, not a cdn.

5 data control

you have full control over your data:

export all your data at any time in csv or gpx format.
delete individual location records or your entire account.
the application does not prevent you from accessing or removing your data.

6 cookies

roamly uses session cookies for authentication only. no tracking cookies or analytics are used by the application.

7 self-hosted instances

since roamly is self-hosted, the privacy practices of each instance depend on its operator. this policy covers the application's default behavior. instance operators may have additional policies.

8 changes to this policy

this policy may be updated as the application evolves. changes will be reflected in the "last updated" date above.

9 contact

for privacy concerns, please open an issue on the github repository or contact the operator of this instance.