Privacy Policy
What personal data Tindelog collects, why, who can see it, which companies help us, how long we keep it and your rights.
Last updated October 12, 2026 · What changed
In short
Terris AS is responsible for your data. Questions: [email protected].
We use your data to run Tindelog for you. We do not sell it and we show no ads.
You decide who sees your profile and trips, and whether others see where, when and with what camera your photos were taken.
Download all your data or delete your account at any time under Settings → Your data.
You can complain to the Norwegian Data Protection Authority (Datatilsynet).
Contents
Terris AS runs Tindelog (tindelog.com and the Tindelog app for Android) and is the controller of your personal data under the General Data Protection Regulation (GDPR) and the Norwegian Personal Data Act.
Contact us about your data at [email protected].
Most of it you give us yourself. Some comes from your devices and from services you connect.
| Kind of data | What it is | Where it comes from |
|---|---|---|
Account | What it is Email address (required). Optional: username, first and last name, profile photo, home region. Your privacy, language, notification and photo settings. | Where it comes from You |
Sign-in and security | What it is Sign-in codes and links (stored as a hash, valid 15 minutes) and the email address they were sent to. A password, if you set one (stored only as a bcrypt hash). Passkeys (the public key and device details, never your fingerprint or face). Signed-in sessions: browser and when last used. Sign-in history: what happened, when, and a shortened IP address. | Where it comes from You and your device |
Trips | What it is Tracks (positions, times, heights and any other data in the file, such as heart rate), the original file you uploaded, names, dates, journals, the summits you reached, and the weather for the trip. | Where it comes from You, Strava if you connect it, and weather services |
Photos | What it is The image and its metadata: where and when it was taken and the camera. Captions. | Where it comes from You |
Social | What it is Friends, friend requests, people you have blocked, lists you make or follow, and invitations. | Where it comes from You |
Strava | What it is Your Strava athlete id, username, name and profile picture, access keys, and your activities with tracks, heart rate and other data. | Where it comes from Strava, when you connect it |
Your location | What it is Only if you ask for driving time to a peak and allow your browser to share your position. We use it only for that request and do not save it with your account; like every request, it appears in our server logs. Your browser also uses your position to show where you are on the map and for distances in search without sending it to us; we only store whether you allowed it. | Where it comes from Your device |
Support and reports | What it is Your requests, reports and messages, and our replies. | Where it comes from You |
Technical data | What it is Server logs (IP address, user id, browser, page or action requested, time). Error reports and, for some sessions, a recording of the page with all text and images masked. Visit statistics. | Where it comes from Your device |
Shared map content | What it is Places you add and edits to place descriptions, with your name. | Where it comes from You |
We do not collect payment card details. Paid plans are not open; when they open, payments will be handled by Stripe or Vipps MobilePay, which collect the payment details.
| What we do | Legal basis (GDPR Article 6) |
|---|---|
Run your account and Tindelog: store your trips, find summits, work out progress and statistics, show your content to the people you choose, send sign-in codes and receipts | Legal basis (GDPR Article 6) Contract (6(1)(b)) |
Import from Strava and write summits back to Strava, when you turn that on | Legal basis (GDPR Article 6) Consent (6(1)(a)) — you can withdraw it by disconnecting |
Send friend request emails (you can turn them off under Settings → Notifications) | Legal basis (GDPR Article 6) Contract (6(1)(b)) |
Keep accounts and the service secure: sign-in history, limits against abuse, logs | Legal basis (GDPR Article 6) Legitimate interest (6(1)(f)) in a secure service |
Handle reports and support requests, and keep reports after a decision so it can be reviewed | Legal basis (GDPR Article 6) Legitimate interest (6(1)(f)) in a safe community, and our terms |
Find and fix errors (Sentry) and count visits (Umami) | Legal basis (GDPR Article 6) Legitimate interest (6(1)(f)) in a service that works |
Where we rely on legitimate interest, you can object (see Your rights). You must give us an email address to have an account; everything else is optional. We make no decisions about you by automated means that have legal or similarly significant effects. Tindelog finds summits on your tracks automatically, and people, not algorithms, decide on reports.
Your profile. Under Settings → Privacy you choose Public (everyone, also people who are not signed in, and search engines), Users (signed-in users) or Friends. Search and leaderboards follow that choice.
Your trips. Each trip follows your profile, and you can hide a trip further (for example Only me). Hiding a trip hides its track, journal, photos and summits everywhere. Trips imported from Strava are never more visible than they are on Strava: Followers becomes Friends, and activities you keep to Only you on Strava are not imported.
Your photos. Hide location and camera details (on by default, and set per photo) keeps a photo's position, time and camera details to you: the photo files we show then contain no metadata, and the original file is kept in private storage. When you share them, people who can see the photo can see where and when it was taken, and the photo files we show keep the camera's metadata (position, time and camera). The original of a photo uploaded since October 2026 is kept in private storage either way; for older photos that share their details, it stays next to the files we show.
Friends and blocking. Friends see what you share with friends, and your trips appear in their feed. Someone you block can no longer see your profile, trips or photos while signed in, and their requests never reach you; they are not told. What you share publicly stays public.
Our team. Moderators and administrators can see all content, whatever your privacy settings, for moderation and support. Administrators can also see a photo's hidden position, time and camera details, and email addresses. What staff do is recorded in an audit log.
If you connect Strava, we read your Strava profile (name and picture), your activities and their tracks. We do not read your Strava photos. We write to Strava only if you turn on write-back; then we add the summits you reached to the activity's title and description. Strava access keys are encrypted.
Imported trips are shown to other people according to your privacy settings, and never more widely than on Strava. If you delete an activity on Strava or make it Only you, its copy on Tindelog becomes visible only to you.
When you disconnect under Settings → Connected apps, we remove our access on Strava and delete the access keys. You choose what happens to imported trips: keep them (the default), delete the trips that only came from Strava, or delete every linked trip. If you remove Tindelog on Strava's side instead, we delete the trips that only came from Strava. We keep a record of the connection (your Strava id, username, name and picture) until you delete your account.
We do not sell your data. These providers process data for us, under our instructions:
| Provider | What for | What they receive |
|---|---|---|
Hetzner | What for Our server: database, search index and job queue | What they receive All data stored in Tindelog |
Coolify | What for Manages our server and deployments | What they receive Access to the server |
Backup storage (S3) | What for Daily database backups | What they receive A full copy of the database, kept 30 days |
Cloudflare | What for Network in front of tindelog.com: delivery and protection against attacks | What they receive All traffic to and from Tindelog, including your IP address |
Microsoft Azure Blob Storage | What for File storage | What they receive Photos (originals in private storage), profile photos and uploaded track files |
Postmark | What for Sending email | What they receive Your email address and the content of the emails we send you |
Sentry | What for Error reports and masked session recordings | What they receive Details of the error, performance data for some requests (page and request addresses), your browser and IP address and, if you are signed in, your user id, username and email address |
Umami | What for Visit statistics | What they receive Pages visited and their titles, referring site, browser, screen size, language, device type and country or region (worked out from your IP address). Umami sets no cookies. |
Google (Routes API) | What for Driving time to a peak (Premium) | What they receive Your position, rounded to about 10 metres, and the peak's position |
Strava | What for Import and write-back, if you connect it | What they receive Requests made with your access keys; with write-back, the summit text |
Your browser also loads map tiles directly from OpenFreeMap and, if you choose those maps, Kartverket (Norwegian topo) or Esri (satellite). They receive your IP address and which part of the map you are looking at.
Our server asks MET Norway, Open-Meteo and NVE (seNorge) for weather and snow data. They receive coordinates and dates — of a peak, or of where your trip went — but nothing that identifies you. When you set a password, we check it against Have I Been Pwned by sending only the first five characters of its hash, never the password.
Paid plans are not open. When they open, Stripe (card payments) or Vipps MobilePay will receive what is needed to take payment, such as your email address and payment details.
Some of these providers are based in the United States or may process data there. For transfers outside the EU/EEA we rely on the EU–US Data Privacy Framework and the EU Standard Contractual Clauses, as appropriate. Sentry stores our error reports in its EU region (Germany).
| Data | How long |
|---|---|
Your account, trips, photos, lists and friends | How long Until you delete them or your account |
Signed-in sessions | How long Until you sign out, or 30 days without use, at most 90 days |
Sign-in history and the log of emails we sent you | How long 90 days |
Notifications in the app | How long 90 days after you read them, at most 1 year |
Background job records (may contain ids and file names) | How long 30 days, failed jobs 90 days |
Sign-in codes and links, with the email address they were sent to | How long 7 days after they expire |
Strava update messages and the record of your Strava connection | How long Until you delete your account (update messages also when you disconnect and delete Strava trips) |
Server logs | How long No fixed period set yet |
Support requests and reports | How long Until you delete your account. Some reports are then kept without your name — see Deleting your account |
Staff audit log | How long Kept, to account for staff actions |
Database backups | How long 30 days |
Deleted data can remain in backups until they expire after 30 days.
Delete your account under Settings → Your data. Your account is deleted at once and it cannot be undone; files are removed from storage shortly after. We delete your profile, trips, tracks, summits, photos, lists, friends and blocks, sessions and sign-in details, the log of emails we sent you, and your search entry. We stop any subscription, remove Strava's access and email you a receipt.
Some things stay, without your name:
- places you added to the map and edits to place descriptions
- lists that other people follow
- cover photos of peaks, only if you choose to keep them (without position, time or camera details)
- reports you made that are still open or led to action, so that a review is still possible
Records of sign-in attempts that are not linked to an account (a hashed email address and a shortened IP address) are deleted after 90 days. The staff audit log keeps its record of what staff did with your account.
- Access and portability: download your data under Settings → Your data — a ZIP file with your records as JSON, your tracks as GPX and your photos as you uploaded them. Tracks of trips imported from Strava are not included; download those from Strava.
- Correction: change most of your data in Settings, or ask us.
- Erasure: delete content yourself, or your whole account (see above).
- Restriction and objection: ask us to limit how we use your data, or object to use based on legitimate interest.
- Withdraw consent: for example by disconnecting Strava or turning off write-back.
- Complain: to the Norwegian Data Protection Authority, Datatilsynet, or the authority where you live.
To use a right we cannot offer in Settings, email [email protected]. We answer within one month. If a request is complex, we may need two more months; we tell you within the first month if so.
- every connection uses HTTPS, with strict security headers
- passwords are stored as bcrypt hashes; sign-in codes and links are stored as hashes
- Strava access keys are encrypted (AES-256-GCM)
- photo originals, which contain metadata, are kept in private storage when you hide a photo's details, and for every photo uploaded since October 2026
- passwords, codes and keys are removed from our logs
- staff access depends on their role, and their actions are logged
Tindelog is not meant for children under 16. If you know that a child under 16 has given us personal data, contact [email protected] and we will delete it.
When we change this policy, we update the date at the top and list the change under What changed. If a change is significant, we also tell you directly, for example by email.
Terris AS, [email protected]. You can write in Norwegian or English.
Rewritten in plain language, with a summary and a table of contents.
Corrected: the session cookie lasts 30 days after your last visit (at most 90), not 24 hours of inactivity, and uses SameSite=Lax.
Corrected the list of providers: added Hetzner, Coolify, Cloudflare, Umami, Google (driving time) and the map and weather services; removed Mapbox and OpenTelemetry, which we do not use in production, and Garmin, which Tindelog does not connect to. Sentry stores data in the EU.
Corrected Strava: disconnecting keeps your imported trips unless you choose to delete them. The earlier text said Strava data was deleted within 48 hours of disconnecting.
New: who can see your data, link previews and embeds, photo metadata, all cookies and local storage, a retention table, what happens when you delete your account, data export, and the one-month answer time.
New: sign-in codes and links, with the email address they were sent to, are deleted 7 days after they expire. Until now they were kept until the account was deleted — also for addresses that never became an account.
Earlier version.