Privacy
Last updated 16 November 2026 (Cloudflare added to the services we rely on)
My Dream Peaks is a personal, non-commercial project for climbers. There are no ads and no tracking, and we don't sell or share your data. This page explains exactly what we keep and why. Questions? Write to [email protected].
The short version
- You can browse the whole site without an account. Like any website, our web server keeps a standard access log for 30 days; nothing else about you is stored.
- With an account, we keep what you give us — your name, email, profile and climbs — to run the site for you.
- You decide who sees your climbs: only you, your connections, or everyone.
- No advertising, no tracking scripts or cookies, no data sales. We count visits only from our own server log, in aggregate.
- You can download everything we hold about you, or delete your account, at any time from your account settings.
What we store
Your account
- Email address, name and handle — to sign you in, show your profile, and send account emails (confirmation, password reset, and notifications you turn on).
- Your password, if you set one — stored only as an Argon2 hash, never in readable form.
- Two-factor sign-in, if you turn it on — the secret your authenticator app uses.
- Profile details you choose to add — tagline, bio, website, social links, home country and a photo (we remove location data from uploaded photos).
- Sex, if you add it — private, never shown to anyone; used only to pick the right formula for training load.
Your climbs and activity on the site
- Summits, attempts, routes, dates, notes, ratings, stars, lists, connections, climbing partners you tag, and your notifications.
- Answers you give about summits found in your GPS tracks, and any marks such as “GPS was wrong” — these also help us improve how summits are recognised.
If you sign in with Google
Google tells us your Google account ID, name and email address, and that the email is verified. That's all — we don't get your contacts, files or anything else from your Google account, and we don't post anything to it.
If you connect Garmin
- Your Garmin personal API key, stored encrypted.
- Your activities and a copy of the original files: GPS track, altitude, heart rate and the summary Garmin provides (for example calories and training load). We keep the copy so improving the summit finder never means downloading again.
- What we work out from them: summits, near misses, and the statistics on your climb pages.
Disconnect Garmin on the import page at any time; tick “Also delete the downloaded Garmin data” to remove the activities, files and the climbs they added.
If you add photos
You can upload photos from your device, or import them from another service: an Immich album you share with us, or Google Photos.
- Uploads from your device: from each photo we read the time it was taken and, if the photo has one, the position where it was taken — only to put it on the right day and at that spot on your trip's map (the position is shown only where the photo itself is shown). We keep a web-size copy and a thumbnail with all other metadata removed (camera, original file details), never the original file. Each member can keep up to 3,000 photos.
- Immich: you paste the link of an album you shared on your own Immich server (and its password, if it has one). We read only that album, copy a web-size version of the photos taken during your trip's days with their time and position, and forget the link and the password as soon as the import ends. Nothing is sent to your server but these requests.
- Google Photos: you connect Google Photos with Google's own consent screen, with any Google account (it can be a different one from the account you sign in with). We keep a token that lets us open Google's photo picker for you, stored encrypted. It gives no access to your library: Google shows you the picker, and we receive only the photos you choose there.
- For the photos you choose we copy a web-size version and a thumbnail (no originals), with the time each was taken and its file name. We use the time only to place each photo on the right day of your trip and on your own GPS track; we don't keep the photo's location or camera details.
- New photos are hidden until you choose to show them; shown photos follow the trip's own privacy setting. We use them for nothing else — no advertising, no training, no sharing.
Delete a photo in Manage photos and our copies are deleted. Disconnect Google Photos there at any time (your copied photos stay until you remove them), or revoke the access in your Google account's security settings. Deleting your account deletes all of it. Our use of data from Google follows the Google API Services User Data Policy, including its Limited Use requirements.
If you make API keys
- An API key lets a program you choose — an AI agent or your own script — use the site as you. We show the key once and keep only a fingerprint of it, with the name, access (read only, or read and write) and expiry you chose.
- A key sees exactly what you see on the site: your own data, what other members share with you, and the public catalogue — never anyone's email address. What the program then does with that data is up to you and the program.
- When you connect an AI app (Claude, ChatGPT and others) with “Sign in with My Dream Peaks”, it works like a key you approved on our page: listed on Account → API keys as a connected app, with the access you chose. The app gets short-lived tokens (we keep only fingerprints of them); disconnecting it ends them at once.
- We log every request a key makes (time, what was asked or changed, the result, the address and program it came from) so you can check it on Account → API keys. Suspend or revoke a key there at any time.
If you invite friends — or someone invites you
- When you invite someone, we keep their email address only to send the invitation, with your name and an optional note. If they don't join, we erase the address after 90 days and keep only a one-way fingerprint of it, so the limits that stop invitation spam keep working. Your own email address is never shown to them.
- Every invitation email has a link to stop invitations; we then keep only that fingerprint, never to email it again.
- If you join through an invitation, we record who invited you, and you're connected with them (you can remove the connection).
To keep the site safe
- Reports you send about a profile, climb or list — what you reported, why, and that it was you. The member you report isn't told who reported them.
- Your sign-in sessions (device type and IP address).
- Sign-in, sign-up and password-reset attempts, to stop password guessing and spam.
- A short history of account changes (for example “password changed”), with the IP address it came from.
Web server access log
For every request, our web server records the time, the page asked for, the response, how long it took, the referring page, your browser's description of itself (user agent) and your IP address. We use it to keep the site secure, find broken links and errors, and count visits in aggregate: how many people visit, which pages and which countries, and how much traffic comes from search engines and other crawlers. Those counts are made on our own server, with IP addresses anonymised and countries looked up locally; they are visible only to the site's administrators. No log data is shared, and no script, pixel or cookie is used for this.
Who can see what
- Your profile and climbs follow your visibility setting — only you, your connections or everyone — and you can override it for each climb. Hidden climbs are visible only to you.
- Public profiles can appear in search engines; profiles that aren't public ask search engines not to index them.
- When others can see a climb with a GPS track, they see only the climb itself: the track is trimmed away from where the activity started and ended, which can be your home.
- You can add more email addresses to your account. Each is confirmed by a link sent to it (unconfirmed ones are deleted after 7 days). A confirmed one lets you sign in, and an invitation to it isn't sent (the inviter sees only that it was skipped, as for any address we don't mail).
- Your email address, sex, Garmin data you haven't shared, and your answers are never shown to other members.
- Moderators — members we trust to keep the community safe — can open members' accounts and private profiles, climbs and lists when looking into a report or a problem. Every time they open private content it is recorded, and admins review those records. They can hide content that breaks the rules (you'll see what and why) and block accounts.
- The people who run the site can access the database to operate and fix it, and don't look at personal data otherwise. They get a short email when someone joins (name, handle, email address and how they joined), to welcome new members and spot spam sign-ups.
Services we rely on
Like any website, these services see your IP address when they're involved.
- Akamai (Linode) — hosts our server, in New Jersey, United States. All the data on this page lives there.
- Cloudflare — every visit passes through Cloudflare's network on the way to our server (since 16 November 2026): it protects the site from abusive automated traffic and delivers pages faster. It sees your IP address, browser and the page you ask for; it keeps no account data of ours.
- Resend — sends our emails, so it handles your email address and the message.
- Google — only when you choose “Sign in with Google”, or connect Google Photos to add trip photos. Your browser also loads our fonts from Google Fonts.
- Tigris — object storage where we keep copies of Garmin files and of the trip photos you add.
- Garmin — only if you connect it: we fetch your activities from Garmin using your key.
- OpenTopography — when a track's altitude is garbled, we fetch the terrain heights for the area it covers (a map rectangle, nothing that identifies you).
- Gravatar — if you haven't uploaded a photo, your browser asks Gravatar for the picture that matches a one-way hash of your email.
- Maps and photos — your browser loads map tiles from OpenStreetMap and OpenTopoMap, the map code from cdnjs (Cloudflare), and mountain photos from Wikimedia Commons.
Peak and climber information comes from public sources such as Wikidata and Wikipedia; the climbers described there are public figures, not members of this site.
Cookies and storage in your browser
mdp_session— keeps you signed in (30 days).mdp_csrf— protects forms from being submitted by other sites.mdp_goauth— exists for ten minutes while you sign in with Google.mdp_invite— remembers the invitation you followed until you join (up to 30 days).- The map remembers where you last looked, in your browser's local storage.
That's all: no analytics, advertising or tracking cookies.
How long we keep things
- Your account, profile and climbs — until you delete them or your account.
- Garmin data — until you disconnect Garmin with “delete the downloaded data”, or delete your account.
- Sign-in attempt records — 30 days.
- Web server access log — 30 days; the aggregate visit counts made from it keep only anonymised data, for 30 days.
- IP addresses in the account history — 90 days; the history itself — 12 months (90 days after an account is deleted).
- Reports — 12 months after a moderator has dealt with them.
- API key activity — 12 months; the IP addresses in it — 90 days. Revoked keys stay listed (without the key) with their activity.
- Invitations — a non-member's address 90 days; the record of invitations 12 months.
- Expired sign-in sessions and used email links — removed daily.
- Backups — daily database backups are kept for 7 days, and our host keeps machine backups for a few weeks, so deleted data disappears from backups within about three weeks.
Your choices
- See and download everything: download your data as a JSON file.
- Correct it: edit your profile and climbs at any time in account settings.
- Limit it: change who can see your profile and climbs, hide climbs, or disconnect Google and Garmin.
- Delete it: delete your account in account settings. This removes your profile, climbs, stars, lists, connections, Garmin key, downloaded Garmin data and the climbs it added.
- For anything else — including questions about your rights under the GDPR or other privacy laws — email [email protected]. We reply within 30 days.
Security
The whole site uses HTTPS. Passwords are hashed with Argon2, and API keys you give us are stored encrypted. You can turn on two-factor sign-in in your account settings; it is required for editors and admins.
Children
My Dream Peaks isn't meant for children under 16, and we don't knowingly keep accounts for them. If you believe a child has an account, let us know and we'll delete it.
Changes
If we change this policy, we'll update the date at the top; for significant changes we'll also email members.