Last updated: 13 November 2026
Link to this clauseWho we are
7summits.com is a community database tracking 7 Summits finishers, routes, and climbing guides. The site is operated by Harry Kikstra, a private individual based in the Netherlands, who is the data controller for the personal data described in this policy. References to "we", "us", or "the site" mean the 7summits.com service.
Questions about this policy: privacy@7summits.com
Link to this clauseData we collect
Apart from the finisher database (see Climbers in the finisher database below), we only collect what you give us directly:
- Account registration, name, email address, and a hashed password when you create an account.
- Posts, title, body, and any images you upload as part of a trip report or community post.
- Finisher profiles, summit dates, routes, nationality, and other climbing statistics you submit for the finisher database.
- Private messages, the messages you send to other members, who you sent them to, and when.
We do not use advertising networks or any third-party tracking scripts. We do not collect IP addresses beyond what is logged automatically by the hosting infrastructure. The one exception: when you use a sign-up box, we keep a scrambled form of your IP address (a keyed hash that cannot be turned back into the address) for about a day, only to stop one visitor from signing up other people's addresses, and then delete it.
Shop links. A click on a link that leaves this site through /go/ adds one to a daily count per link, per shop and per delivery country (the country shown as “Delivering to” beside the link). It never records who clicked, no account, cookie or IP address. To pick that country we ask our host which country your connection comes from; we use the answer for that page and do not store it. If you change it, your choice is kept in your own browser, and reaches us only inside a shop link you click, as that link’s delivery country.
Page counts. We count page views with Vercel Web Analytics, provided by the company that hosts this site. It sets no cookie and stores nothing on your device. What is recorded is the page address, the page you came from, your rough location (country, region and city) and the kind of browser and device. We see totals only (how many people read which page) and visits by our own team are not counted.
We also measure how quickly pages load for visitors, with Vercel Speed Insights from the same company: your browser reports a few timing figures for the page it loaded (how soon the first text appeared, how quickly it responded to a tap, whether anything jumped) together with the page address, the kind of device and the country. It sets no cookie, stores nothing on your device, and we strip the address of anything that could name you, the same as for the page counts.
What we can never see:
- Your path over time. A visit is recognised only by a code worked out from the request, which Vercel discards after 24 hours. If you come back next week, you count as someone new, there is no "returning visitor" figure.
- Who you are. No name, no account, nothing that links a visit to you or follows you to other sites.
- What you searched for. Search words and any link that contains a code are removed before anything is sent, and your account, messages and notifications pages are not counted at all.
Mailing list. If you sign up to a list, we keep your email address, the sentence you agreed to, when you agreed and when you confirmed. You can leave the list at any time, from your account settings or by writing to privacy@7summits.com.
Link to this clauseHow we use your data
- To authenticate you and maintain your session.
- To display your posts and profile to other users (subject to your visibility settings).
- To send transactional emails you request (e.g. password reset links).
We use your account details to run the account you asked for (Article 6(1)(b) GDPR). We send the mailing list only with your consent (Article 6(1)(a) GDPR), which you can withdraw at any time.
We do not sell or share your personal data with any third party for marketing purposes.
Link to this clauseClimbers in the finisher database
Most records in the finisher database were not given to us by the climber. We put them together from published sources: the Himalayan Database, Eberhard Jurgalski's almanac, expedition reports, news articles, Wikipedia and climbers' own websites. A record holds a name, nationality, year of birth, summit dates and routes, and where we have them a photo, a short biography and links.
Why. The database is a historical and statistical record of who has climbed the 7 summits, and keeping it accurate and public is the reason this site exists. That is our legitimate interest (Article 6(1)(f) GDPR). We keep a record for as long as the site runs.
What we hold back. A climber's page shows the year of birth and ages in whole years, not the full date, unless a Wikipedia article about them already gives it, they choose to show it, or we wrote to tell them and they did not object within ten days. Contact details we find for a climber (an email address or a contact form) are used only to invite them to check their record, and are never shown on the site.
Your say. If you are in the database you can correct your record, hide your year of birth, or object to anything on it being shown: use "Send a message" on your climber page or write to privacy@7summits.com. We remove anything that is not the climbing record itself (photo, biography, links, birth year). Verified summit dates and routes stay, as explained under Your rights. If you hide your age, your place in the age rankings stays, marked "Age known, not shown", so the record stays correct for everyone else.
Link to this clausePrivate messages
Members can send each other private messages. Private means private from other members. It does not mean encrypted, and it does not mean nobody at 7summits can ever read them.
Do not put sensitive information in a message. Never send card or bank details, passwords, passport or identity numbers, or your home address, to us or to another member. We will never ask you for any of these, and anyone who does is not acting for 7summits. Treat a message as a postcard rather than a sealed envelope.
Site administrators can read private messages, and every time they do it is recorded. This is not routine and it is not browsing. An administrator needs a specific reason (investigating a report, a suspected scam or impersonation, a safety concern, or a legal obligation) and each access is logged with who opened it, when, and why.
How long we keep them. We keep messages for as long as the site runs. There is no automatic deletion, and once a message is sent you cannot take it back, neither can the person you sent it to. Please assume anything you send is permanent.
Link to this clauseYour gear shed
Your gear shed (what you own, where it is, and your notes) can be read and changed by you alone. No other account can open it, staff accounts included. It is stored in our database like everything else on the site, and we never look at individual sheds; what we use is anonymous totals, such as how many members own a given kind of item, and a group smaller than five is never shown. When you close your account, your gear shed is deleted with it.
Link to this clauseCookies
This site sets one essential cookie, a session token used to keep you logged in. It is an HttpOnly cookie and cannot be read by JavaScript on the page. It expires when you log out or after a period of inactivity.
Sign-up boxes. Only if you use one of the mailing-list boxes: when you click into its email field, the page loads Cloudflare Turnstile, which checks that the sign-up comes from a person and not a script. For that check, Cloudflare receives your IP address and technical details of your browser and connection. It processes them for us to run the check, and also for its own purpose of improving its bot detection, as its Turnstile privacy policy explains. We receive only a pass or a fail. If you never use a sign-up box, your browser never contacts Cloudflare.
Security checkpoint. Our host, Vercel, may show a short "Security Checkpoint" page to a browser whose traffic looks automated. A browser that passes it gets a strictly necessary cookie that lets it through for one hour. Most visitors never see this check and never get the cookie.
Invisible bot check. On every page, our host Vercel runs a short check in your browser in the background, called BotID, so that a form you send (signing up, writing to us, a mailing-list box or a gift) can be told apart from one sent by a script. For that check your browser sends Vercel technical details about itself. We receive only an answer: person or script. You see nothing, and we store nothing about the check except a daily count of the forms it refused.
No analytics cookies, advertising cookies, or third-party tracking cookies are set, the page counts described above use none. Because the only cookies used are strictly necessary for the site to function, no consent is required under applicable privacy regulations.
Link to this clauseData storage and processors
Data is stored in a PostgreSQL database and object storage provided by Supabase. The application is hosted on Vercel, which also runs the bot checks described under Cookies. A few other companies each do one job for us and receive only what that job needs:
- Stripe takes payments for memberships, company plans and gifts. You pay on Stripe's pages; we never see card or bank details. We keep the invoice, your name, the amount and Stripe's reference. If you choose Apple Pay or Google Pay on Stripe's page, Apple or Google handle that step under their own privacy terms; nothing of theirs loads on 7summits.com.
- AhaSend delivers the emails we send. Migadu hosts our mailboxes, so a message you send to an @7summits.com address is stored there.
- Sentry receives a report when something on the site breaks. Email addresses, links with codes in them and anything you typed are removed before the report leaves our server.
- Anthropic's Claude models read new forum posts to flag possible abuse for a moderator, write suggestions when you press a writing-help button in the trip-report editor, and help us sort messages sent to us. Anthropic does not train its models on this data.
- Cloudflare runs the check on the sign-up boxes (see Cookies).
Each works under its own privacy programme and a data processing agreement. Because we sell or share no personal data, a Global Privacy Control signal from your browser changes nothing here: there is nothing to switch off.
Link to this clauseYour rights
You may request access to or correction of your personal data at any time by emailing privacy@7summits.com. Account holders can also delete their own posts from the account page.
Asking us to remove your data. You can ask us to delete your personal data at any time by emailing privacy@7summits.com, and we will honour it, with three exceptions.
The first is your climbing record. Verified summit dates and routes are the substance of the finisher database, which exists as a public record and is cited elsewhere; that stays.
The second is an open complaint. If there is an unresolved report involving you, we keep what the complaint concerns until it is settled. Otherwise anyone could erase a complaint by asking us to erase them.
The third is an invoice. Tax law requires us to keep invoices for seven years, so an invoice keeps your name and the amount after your account is closed.
Closing your account. We remove your personal details (name, email address, biography, country, photo and links) and the account can never be signed in to again.
Your forum posts and the messages you sent stay, shown as coming from "Removed member". Both reasons are about other people:
- Conversations others took part in would otherwise develop holes, replies to questions that had vanished. They did not ask for their threads to be rewritten because someone else left.
- Someone who used messages to scam, spam, impersonate or harass cannot erase the evidence by closing their account. The person on the receiving end can still report what was sent to them, and we can still act on it.
Backups. Removing something from the live site does not remove it from our backups straight away. Backups are kept on a rolling schedule and are only ever used to restore the site after a failure; deleted data ages out of them as older backups are replaced.
If you are in the EEA or UK you also have the right to lodge a complaint with your local data protection authority.
Link to this clauseChanges to this policy
If we make material changes we will update the “Last updated” date above.


