What we keep, and what we never see.

The heart of this app runs entirely in your browser. The following are not transmitted to us, and we could not read them if we wanted to:

• Your selected peaksWhich mountains you have summited, how many times you have climbed each, and the EXP and rank calculated from them. These are held in your browser’s session storage and are discarded when you close the tab. The one exception is if you press Publish these climbs on the summary page, which is covered under your public page.
• Your theme choiceLight or dark, remembered in your browser’s local storage so the page does not flash the wrong one.
• Your share cardThe image you can download from the summary page is drawn inside your browser. It is never uploaded to us, and we never see it.
• An offline copy of the pages you visitIf you install the app to your home screen — or simply keep using it — a service worker keeps a copy of the pages, images and fonts you have already loaded in your browser’s cache storage, so the app still opens without a signal. It is a copy of what we already sent you, it stays on your device, and pages that need your account are never cached.

Clearing your browser’s site data removes all of this immediately.

An account is entirely optional — every other part of the app works without one, and signing in does not by itself back up or sync your climbs. If you create one, we store:

• First and last nameAs you enter them.
• Email addressUsed to sign you in and to reach you about your account. We do not send marketing email.
• Profile photoOptional. Resized and re-encoded in your browser before it is uploaded, so the original file never leaves your device — only the small square version does.
• A public handleGenerated from your name plus a few random characters, for the address of your public page.
• The date you joinedSet once, automatically.
• A climb log, only if you publish onePressing Publish these climbs on the summary page stores the peaks you selected and how many times you climbed each, plus the EXP and rank worked out from them. Nothing is stored until you press it, and pressing Take my climbs off my page deletes the record outright rather than hiding it.

Your password is handled by our authentication provider and is stored only in hashed form. Nobody, including us, can read it back.

You can review and change all of it at any time on your profile page.

Every account has a page at a public address, which anyone with the link can open without signing in. It shows your name, your photo, and the month you joined, plus your climbs, EXP, hiker rank, and earned badges if — and only if — you have published them. Badges are not stored anywhere: they are worked out from that same published peak list each time the page is loaded, so publishing nothing publishes no badges either.

That page is meant to be shared, so treat anything on it as public: search engines can index it, and posting the link to Facebook generates a preview card carrying your name, rank, and climb totals.

Publishing a climb log also makes it findable without the link. If your EXP is among the 100 highest, your name, photo, EXP, and rank appear on the leaderboard, which anyone can open. Taking your climbs down removes you from it; an account with no published log is never listed.

Your email address is never shown there, and it is not merely hidden — the page reads from a restricted view of the database that does not contain it at all. You can remove your climb log yourself at any time from the summary page. If you would rather have no public page at all, ask us to delete your account.

If you use the feedback form, we store what you submitted: the topic, your message, and an optional rating, plus your name and email address if you chose to give them. We also record which page you were on and your browser’s user-agent string, which is what tells us whether a reported bug is specific to one browser.

Name and email are optional there. Leave them blank and the message reaches us with nothing identifying attached.

If you use the add-a-mountain form, we store what you filled in about each peak — its name, difficulty, elevation, province, island group, trail class and description — along with the email address on your account, so we can come back to you with a question before the peak goes into the catalogue. That address is stored with the submission and is never shown on your public page or to other hikers.

This is the one part of the tracker that needs an account, because a contribution is attributed. Every submission arrives marked pending and is reviewed before anything is added; there is a limit on how many peaks one account can send per hour, which is there to keep the queue usable.

We use privacy-friendly page analytics to see which pages get visited and roughly where visitors come from. It does not use cookies, does not follow you to other websites, and does not build a profile of you. We see counts and trends, not people.

Our host also keeps standard server logs, which include IP addresses, for a short period. These exist to keep the site running and to investigate abuse — they are not used to identify you.

This site loads its typefaces from Google Fonts. That means your browser makes a request to Google’s servers, which reveals your IP address to them, as it would on any site using the same service. No cookie is set by it.

Beyond that, the only companies involved are the ones that run the site for us: our hosting provider, and the provider that runs our database, sign-in, and file storage. They process this data on our instructions in order to operate the service, and for no purpose of their own.

There is no cookie banner on this site because there is nothing to consent to: we set no advertising or tracking cookies.

• Sign-in cookiesSet only after you sign in, and only so the site knows it is still you on the next page. Signing out clears them.
• Local storageYour theme preference.
• Session storageYour selected peaks, and a note that this tab has already seen the opening screen. Both are discarded when the tab closes.

We do not sell your personal information, and we do not share it for advertising. The only parties who ever hold it are the service providers described above, who need it to run the site.

We would disclose information if we were legally required to, and we would tell you unless we were prohibited from doing so.

• Account detailsUntil you ask us to delete them.
• A published climb logUntil you take it down, which removes it immediately, or until your account is deleted, which removes it too.
• Feedback messagesKept while they are still useful for improving the app. Ask us and we will remove yours.
• Contributed peaksKept as a record of where a catalogue entry came from, including after it is approved. Ask us and we will remove your address from it.
• Anything on your deviceEntirely under your control — clearing your site data erases it at once.

Under the Philippine Data Privacy Act of 2012 (Republic Act No. 10173) — and comparable laws elsewhere — you may ask to see the personal data we hold about you, to have it corrected, or to have it erased. You may also object to how we use it and ask for a copy of it.

Correcting your details is immediate: edit them yourself on your profile page, and delete a published climb log yourself from the summary page.

Deleting an account is not yet self-service. Send the request through the feedback form from the address on your account and we will remove your profile, your photo, and your public page. We will confirm when it is done.

If you believe we have mishandled your data, you may complain to the National Privacy Commission at privacy.gov.ph.

SummitStack PH is not aimed at children, and we do not knowingly collect personal data from anyone under 13. If you believe a child has created an account, tell us and we will remove it.

If we change what we collect, we will update this page and move the date at the top. Where a change is significant, we will say so plainly rather than expecting you to spot the difference.

Questions about any of this, or a request about your data, can go through the feedback form. Choose the “General” topic, include your email address so we can reply, and we will come back to you.