Slid

Slid

Privacy policy

Effective 6 November 2026

This policy covers the app “Slid” (package dev.slid). Slid has no servers of its own, no accounts, no ads and no analytics, and the developer never receives your timeline. The app does talk to outside services, and this page names every one of them, says what each receives and which ones you can turn off.

At a glance

  • Kept on your phone
    The timeline, photo places and steps are stored on the device. The developer never gets them.
  • Outside services see places
    Map tiles are always loaded. Address and transport lookups stay off until you agree; they send coordinates, and you can turn them off.
  • Permissions you can refuse
    Each one is asked for the feature that needs it. Recording needs location and Google Play services.
  • Copies are not encrypted
    A copy in Google Drive or in a backup file holds the whole timeline. Google stores the Drive copy.
  • Deleting has limits
    Uninstalling removes the data on the phone, not copies in Drive or in files.

What data, where it goes, who can see it

DataWhere it is kept or sentWho can see it
Your timeline: locations, activity, steps, years imported from Google, place names, weekly reportsOn your device, in the app’s databaseYou
Your photos’ file names, dates and places (not the pictures)On your device, in the same databaseYou
Watch data from Health ConnectNot stored: read on the fly to show itYou
The map area you look at (always); the satellite area (only with the satellite map)Sent to the map serversCloudflare and OpenFreeMap; Esri
Coordinates of places where you stopped, including imported ones (only after you agree)Sent to address servicesAndroid’s address service, usually Google; Nominatim (OpenStreetMap), only for a place you open or tap
Map squares around your recent trips by vehicle (only after you agree)Sent to transport serversoverpass-api.de; if it fails, overpass.private.coffee
A copy of the whole timeline (only if you connect Drive)Hidden app folder in your Google Drive, not encrypted by the appYou; Google, which stores it
A backup file (only if you save one)Where you save it, not encryptedWhoever has the file
Update check (when you open the app)pegasohlib.github.io and GitHubGitHub, which sees your IP address

What data the app holds

  • Location. While recording is on, the app records the phone’s location, also in the background, through Google Play services, to show where you have been and how you travelled.
  • Physical activity. If you allow it, Android and Google Play services tell the app whether you are walking, cycling or in a vehicle. While recording is on, the app also counts the phone’s own steps hour by hour.
  • Photos and videos. If you allow it, the app reads each file’s name, date, size and the place stored in it, and keeps them in its database to show the photos on the map. The pictures are not copied or sent anywhere. By default a photo without a place gets the place where you were at that time; this can be turned off in the settings. Photos from chat apps, downloads and screenshots are left without such a place; the app guesses that from the folder name, and a place stored in the file itself is still used. The app does not write into your photo files; it can only remove a place that an older version wrote, after Android asks you.
  • Imported files. Google Timeline or Google Takeout files, and a Google Photos export, that you choose are read on the phone.
  • Places. The names you give places and the addresses found for them.
  • Weekly reports (optional): the mood and the words you write about a week.
  • Settings. Language, theme, and, if you give them, your birthday (to show how much of your life the timeline holds), height and weight (for a daily step goal and the length of a step). These are kept on the phone and are not part of copies and backup files.

The timeline, places, photo list, weekly reports and step counts live in one database on the phone. That database is what goes into a Google Drive copy and a backup file.

Permissions the app declares

Slid asks for most of these only when you use the feature. You can refuse or revoke any of them in Android’s settings; the matching feature then stays off.

Internet and network state
Maps, addresses, public transport, Google Drive and updates (see below).
Location: precise, approximate and in the background
To record the timeline, also with the screen off. Recording needs Google Play services.
Physical activity
To tell walking, cycling and vehicles apart. Also the Google Play services version of this permission.
Foreground service (location) and notifications
To keep recording running with a visible notification, and for reminders such as the weekly report.
Start after the phone restarts
To resume recording after a restart or after the app is updated.
Ignore battery optimisation
To ask Android not to stop recording. Android shows its own prompt.
Photos and videos, selected photos, photo locations, and storage on Android 12 and older
To show your gallery photos and their places on the map.
Install apps
To install an update that you confirm. The app is shared outside Google Play.
Health Connect: steps, heart rate, sleep, exercise, exercise routes, older history
To read what your watch app wrote there, only if you allow it. The app never writes to Health Connect.

What goes over the internet

  • Maps (cannot be turned off). Whenever a map is shown, its tiles, style and fonts are loaded through Cloudflare from OpenFreeMap (OpenStreetMap data). Satellite images and the place names on them are loaded from Esri (ArcGIS Location Platform), only while you have the satellite map selected. These servers receive your device’s IP address and the area you look at. Requests to Esri also carry the app’s access key, which is the same for everyone who uses the app; Esri handles them under its privacy statement. Apart from the IP address, nothing that identifies you is sent.
  • Addresses and place names (off until you agree, can be changed in Settings). Once you agree, the coordinates of each place that has no address yet, including places from imported years, are sent in the background to Android’s address service. On most phones this service is Google’s, so Google receives these coordinates; the app cannot change that. Nominatim (nominatim.openstreetmap.org, run by OpenStreetMap) receives only the coordinates of a place you open or tap, once per place and at most about one a second, and never of a place you named yourself or marked as Home, Work or School. It also receives your IP address, the language and the app’s name and version. With the setting off, nothing is sent.
  • Public transport (off until you agree, can be changed in Settings). To tell a bus, tram, train or metro apart, the app asks the Overpass service of OpenStreetMap for rails and stops. This is done only for trips you recorded yourself in the last 60 days that are still marked as a vehicle trip. It sends the coordinates of map squares about 5 km wide around the trip, not the exact route. For a very long trip it sends up to 25 points along the route, and for an underground trip the two ends. The servers are overpass-api.de and, if that one fails, overpass.private.coffee. They also see your IP address and the app’s version. The squares are kept on the phone for about 60 days.
  • Google Play services. Recording uses Google Play services on your phone for location, activity recognition and geofences, and Drive sign-in uses it too. That part is run by Google’s software under Google’s own terms, not by Slid. The app does not send this data to the developer.

Backup to Google Drive (optional)

If you connect Google Drive, you sign in through Google Play services, and the app gets access only to its own hidden folder in your Drive (the drive.appdata permission). It cannot see your other files. It also reads your e-mail address, only to show which account is connected.

What is copied. The whole database, compressed: locations, trips, places, photo file names and places, weekly reports and step counts. The app does not encrypt it. Your birthday, height and weight are not part of it. Watch data is not stored, so it is not in it either.

Who can read it. The copy sits in Google’s storage, so Google stores it and handles it under its own terms. The developer has no access to it.

When. After you connect, a copy is made every 24 hours by default, on Wi-Fi only and when the battery is not low. You can change this or make copies by hand. The file is named after the phone model plus six characters of the phone’s Android ID, and the phone’s name is stored with it, so you can tell your devices apart. Google Drive may keep older versions of the copy for a while, and the app can restore them.

Removing it. Disconnecting stops new copies but does not delete the ones in Drive. In the app you can delete the copies of your other devices, and “Delete my copy from Google Drive” deletes this phone’s copy with its older versions and turns automatic copies off. You can also open Google Drive’s settings, Manage apps, choose Slid and delete its hidden app data. Uninstalling the app does not delete the copy.

The app’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Watch data through Health Connect (optional)

If you allow it, the app reads steps, heart rate, sleep and workouts (with their routes) from Health Connect, written there by watch apps such as Mi Fitness, including history older than 30 days. It only reads this data and never writes to Health Connect. The data is read on the phone only to show it in the Health tab and on the matching day of your timeline; the app does not store it in its database, does not include it in copies and backups and does not send it anywhere. You can revoke the permissions at any time in Health Connect’s settings.

Backup files and safety copies

A backup file is created only when you save one yourself, in the place you choose. It holds the same database as the Drive copy and is not encrypted, so whoever has the file can read your whole timeline. If you save it to a cloud folder, that service stores it.

Before a restore replaces your timeline, the app keeps the previous timeline in its own storage on the phone (the last three), so a wrong restore can be undone. These copies never leave the phone and are removed when you uninstall the app.

Android’s automatic backup of the phone is switched off for Slid, so Google’s phone backup does not include the app’s data.

Export. You can export your timeline to a GPX, KML or CSV file, for a day, a date range or all time. The file is made on the phone and saved where you choose in Android’s file picker. Slid sends nothing, and the file is not encrypted. If you save it to a cloud folder or share it, that service or person has it. Deleting data in Slid does not delete exported files.

Updates

The version of Slid shared on its website checks for a new version when you open the app, at most every 30 minutes. It does not check in the background. For this it reads a small file from pegasohlib.github.io, and when you tap Update it downloads the new version from GitHub. The app compares the download with a checksum from that file, and Android checks that the update is signed with the same key. Like any website, GitHub sees the IP address of your device; no data from the app is sent.

You can turn automatic checks off in Settings. The file is then not read.

GitHub also counts how many times each file has been downloaded. It is only a number, with nothing about who downloaded it; the website shows it as an approximate number of downloads.

Deleting data

Deleting a stay or a trip on the Day screen removes the entry and the points recorded during it. Deleting a trip from the Trips list removes the trip but leaves the points recorded during it.

Uninstalling the app removes everything the app stores on the phone, including safety copies. It does not remove Google Drive copies, backup files you saved, or what outside services already received. Those services keep it under their own rules. If an older version wrote places into your photo files, uninstalling does not remove them: take them out in the app’s settings first.

To delete a Google Drive copy, see “Backup to Google Drive”.

Changes

If this policy changes, the new version will appear on this page with a new date.

Contact

Questions about privacy: support@pegasohlib.com