Privacy & cookies
Last updated: 8 November 2026
What we collect, and why. Reading this site requires no account. Four things are optional, and you choose each of them:
- An account, if you open one. Accounts are optional: a trip can be viewed from its private link without one. If you do open one we store your email address; your first and last name; your phone number if you choose to give one; your password as a PBKDF2-SHA256 hash with a random per-account salt and an iteration count, never the password itself; a record of each signed-in session; short-lived tokens for confirming your address (24 hours) and resetting a password (1 hour); and a count of failed sign-in attempts with any lockout time, which is what stops someone guessing their way in. We never see your password, and we cannot tell you what it is, only help you set a new one.
- The booking form. It is not switched on. The booking page exists, but the endpoint behind it refuses every submission for now, so nothing you type there is saved and no booking can be made today. When it does open you will have to be signed in to use it, and what it stores is the choices you make on the page: which package, your start date, how many are walking, how many single rooms, and any extras you tick: extra nights, a Porto airport pickup, the Santiago to Porto bus. Saved beside those choices are the price and deposit we work out here on the server, a booking reference and a private link to the trip. The form does not ask for your name, email address or phone number: those are taken from your account. When you tick the box accepting the booking conditions, we also record which version of them you accepted, the time on our server, and the language of the page, so either of us can show later what the contract said. We also store the IP address and the browser identifier from the moment of acceptance for 13 months, to evidence the contract and to prevent payment fraud (legitimate interest).
- The request form. If you ask us about a trip we keep what you send: your name and email address, your route, dates, number of walkers, room and pace choices and your notes, and, only if you choose to give it, a phone number. The phone is used only to reach you about your request if our email does not reach you; it is never put in an email and never passed to a hotel. We keep the request for as long as it’s relevant to answering you.
- Email you send us. If you write to [email protected] we keep the correspondence for as long as it’s relevant to answering you. The sender, recipients, subject and date of each message (never its text) are also kept in our booking database, linked to your request or booking, for the same time.
Processors. Cloudflare (hosting, the database behind your account, email routing and the form endpoints), Resend (sending confirmation and password-reset email), Zoho (our mailbox, [email protected], where the emails you send us are kept) and Stripe (card payments, once bookings open). All four process data under GDPR-compliant terms. We do not use an email marketing platform.
How long we keep it. Your account stays until you ask us to delete it. Sessions expire after 30 days and the expired and signed-out records are cleared from the database a week later. The token that confirms your address lasts 24 hours and a password-reset token lasts one hour; both stop working when they expire. Email you send us is kept for as long as it is relevant to answering you. Ask us sooner and we delete it sooner.
Sessions, and how to end them. Signing in stores a session on our server and puts a matching token in a cookie. Only a SHA-256 hash of that token is stored, so a copy of our database would not let anyone sign in as you. Sessions expire after 30 days, and signing out revokes the record immediately rather than just clearing the cookie, so it ends on every device using it. Alongside each session we keep a hashed fingerprint of the browser and IP it started from, to spot a stolen session; the raw values are not stored.
Deleting an account. Write to [email protected] and we delete the account, its sessions and its tokens. If you have a booking with us we have to keep the booking records themselves for as long as Portuguese tax and consumer law requires, but they stop being linked to a login. Accounts that are never confirmed are removed after 30 days.
Your rights. Under the GDPR you can ask for access, correction, erasure, restriction, portability, or object to processing: write to [email protected] and we will act within 30 days. You can also complain to the CNPD (Comissão Nacional de Proteção de Dados, cnpd.pt).
Data controller. The operator of this site and data controller is Sherpie Travel, Unipessoal Lda, NIPC 519681126, registered office Rua Francisco da Rocha Soares, n.º 27, Cave, 4050-281 Porto. Contact: [email protected].The operator of this site and data controller is Sherpie Travel, Unipessoal Lda, NIPC 519681126, registered office Rua Francisco da Rocha Soares, n.º 27, Cave, 4050-281 Porto. Contact: [email protected].
Payments
No payment can be taken on this site yet: nothing here charges a card. When bookings do open, cards are handled by Stripe, and this is what that means in practice: you leave this site for Stripe’s own checkout page, you type your card number there and not here, and we never see or store it. Bom Caminho holds only what Stripe hands back: a payment reference, the amount, the currency and whether it succeeded.
What we send Stripe to open a checkout is your email address, the amount, and a description of what you are paying for, plus our own booking reference so the payment can be matched to your trip. We also tell Stripe which version of the booking conditions you accepted, and in which language. Stripe is the data controller for the card details themselves and processes them under its own privacy policy.
Cookies & analytics
One advertising tag. We advertise on Google. If you accept, this site loads the Google Ads tag so that we can tell whether those ads work: it counts a request sent from our form when the visit came from one of our ads. It receives only the page the form was on and the walk asked about, never what you type in the form, and we do not use it to build a profile of you.
Nothing is stored unless you accept. On your first visit a bar at the bottom of the page asks. If you reject, or do not answer, no Google code is loaded at all: nothing is stored on your device and Google receives nothing. If you accept, Google may set its conversion cookies: on this site _gcl_au, _gcl_aw, _gcl_dc, _gcl_gb and _gcl_gs, each kept for 90 days, and on its own domain doubleclick.net IDE (13 months in the EEA and the UK) and test_cookie (15 minutes). Personalised advertising and analytics stay switched off either way. Your choice is kept in your browser’s local storage as bc_consent for six months; then the bar asks again.
Who receives it. The tag is provided by Google Ireland Limited, Dublin. Google may process the data in the United States under the European Commission’s standard contractual clauses. See Google’s privacy policy.
Changing your mind. “Cookie settings” at the bottom of every page opens the bar again, and you can delete the cookies in your browser settings at any time.
Legal basis. The cookies are set only with your consent (Article 6(1)(a) GDPR and Lei n.º 41/2004). The data controller is the one named above: Sherpie Travel, Unipessoal Lda, Porto, [email protected]. The four cookies described next are our own and none of them is for advertising.
This site sets four cookies of its own, none of them for advertising or analytics. bc_csrf is set the moment you LOAD a page carrying a form (the sign-in, registration, password and account pages), not when you sign in; it is a random value your browser mints and sends back with the form, which is how we know the submission came from our page and not somebody else’s. It expires after two hours. The other two arrive only when you actually sign in. __Host-sx is the session itself: it is marked HttpOnly so no script can read it, and Secure so it never leaves over plain HTTP. bc_csrf guards forms against being submitted from another site. bc_in holds the single character 1, so the page knows to show “Account” instead of “Log in”; it identifies nobody. Signing out clears all three.
The fourth, bc_promo, is set only for visitors who arrive through a link from one of the creators we work with. It is a first-party cookie that keeps that link’s promotional code for 30 days, so the 5% discount applies to the request you send. It holds nothing but the code and is not used for tracking or advertising.
External links
Guides may link to other websites for reference. Those sites have their own privacy policies; we have no control over, and receive nothing from, what happens there.