Privacy Policy
What we collect when you browse the site, sign in to an account or join the newsletter, how we use it, and the rights you have over it.
Last updated: 2026-11-16
Introduction
The website tour-guide.com, operated under the name Tour Guide, is committed to protecting the privacy of its visitors. This privacy policy describes the data we collect, how we use it, and your rights regarding your personal information.
Data We Collect
We collect a minimal amount of data in the course of operating this site. The information gathered may include:
- Browsing data: anonymised IP address, browser type, pages visited, and visit duration, collected through Cloudflare Web Analytics.
- Technical cookies: small files stored on your device to remember your preferences (such as cookie consent). No advertising or third-party tracking cookies are used.
How We Use Your Data
The collected data is used solely to:
- Understand how visitors use the site in order to improve its content and usability.
- Ensure the proper technical operation of the site.
- Maintain security and prevent abuse.
We do not sell, rent, or share any personal data with third parties for commercial purposes.
Session Analytics
To understand how visitors move through tour-guide.com β
which pages they read, in what order, and where they leave β we run
our own self-hosted, cookieless session analytics. No cookie is set
and no cross-site identifier is used: a random session id is held in
your browser's sessionStorage and is discarded the moment
you close the tab.
For each visit we record the sequence of pages viewed, the time spent
on each page, the country the request comes from (derived from your IP
address, which is then discarded and never stored), your device type,
operating system and browser family (along with the browser's
user-agent string, which those families are derived from and which we
keep to tell real visitors apart from automated traffic), the
referring website (host only, never the full URL), and any campaign
parameters (utm_*) present in the link you arrived
through. This data contains no name, email, or other directly
identifying information, is stored on our own systems, and is never
sold or shared with third parties.
To count unique visitors without a cookie, we also store a daily-rotating one-way signature derived from your IP address, browser, and this site's domain. Only this salted digest is kept β never your raw IP address β and because it is regenerated every day it cannot link your visits from one day to the next.
Third-Party Services
This site uses Cloudflare for hosting, content delivery, and traffic analytics. Cloudflare may collect certain technical data as part of its services. To learn more, see the Cloudflare Privacy Policy .
Your Rights (GDPR)
Under the General Data Protection Regulation (GDPR), you have the following rights:
- Right of access: obtain a copy of the personal data we hold about you.
- Right to rectification: request correction of inaccurate or incomplete data.
- Right to erasure: request deletion of your personal data.
- Right to data portability: receive your data in a structured, machine-readable format.
- Right to object: object to the processing of your data in certain circumstances.
To exercise any of these rights, please contact us at the address below.
Contact
For any questions about this privacy policy or to exercise your rights, you can write to us at: [email protected].
Analytics Providers and Cookies
Alongside the self-hosted session analytics and Cloudflare traffic metrics described above, we use two named third-party analytics services on this site, with different privacy characteristics:
-
Ahrefs Web Analytics gives us anonymous, aggregate traffic statistics β such as page views, referrers, and general browser type. It sets no cookies and does not track you across sites or collect personal information. You can read more in the Ahrefs privacy policy.
-
Google Analytics 4 helps us understand overall audience trends. It is consent-gated: it starts with analytics storage denied, so no Google Analytics cookies are set until you accept the cookie banner. Once you opt in, Google Analytics 4 sets its own cookies and may use them to recognise you across sites and visits; declining or ignoring the banner keeps it switched off. See how Google handles this data in the Google Privacy Policy.
What Your Account Stores
You can read every guide on Tour Guide without an account. If you create one, or confirm a newsletter subscription (which creates a free account for the same address), we keep the following in our own database, hosted on Cloudflare:
- Account details: your email address, a display name if you add one, and the dates the account was created and last changed.
- Profile: your public handle (we generate one when the account is created and you can change it), a short bio and a profile photo if you add them, and whether your profile is public or private.
- Passkeys: for each passkey you register, its credential identifier, its public key, a signature counter, the device type, whether it is backed up, and the ways your device can connect to it. Your fingerprint, face scan or device PIN stays on your device and is never sent to us.
- Sign-in records: for your current session, a random session identifier, its expiry time, and the IP address and browser user-agent string it was started from. When you sign in or sign up with an emailed link, we also keep a record of that link and of the account or address it was sent to; each link stops working after 15 minutes.
- What you save: the guides, destinations and attractions you have saved; the places you mark as visited or as places you want to go; and the trips you build, with their names, stops, order and any notes you write on a stop.
- Browsing-session links: the connection between your account and the analytics sessions you start while signed in, explained in βYour Account and Browsing Historyβ below.
We use this data to sign you in, to show you your saved places and trips, to publish the parts of your profile that are public, and to suggest guides you may like. We never sell it or share it with third parties for commercial purposes.
The Claude Connector
You can add Tour Guide to Claude as a connector, so Claude can answer travel questions from our pages and β if you choose to sign in β read and update the places and trips in your account. Browsing our pages through Claude needs no account and sends us nothing about you. The connector is explained in full on our Claude connector page.
What Claude sends. When you connect your account, Claude signs in through our standard sign-in screen and we issue it a token scoped to your account. After that, Claude only sends the requests you ask it to make β for example to list your trips or save a place. Your Claude conversations are never sent to us; we see only the individual tool requests.
What we store. We keep a record of the permission you granted β which app it is, when you connected it, and when it was last used β so you can review and revoke it. We also keep the tokens that let Claude act on your behalf (the refresh token only as a hashed value). For each tool Claude calls we log the tool name, the outcome and how long it took, so we can keep the connector working and measure it. We never store the arguments of a tool call or the content of what you asked Claude.
Keeping and revoking. The permission lasts until you revoke it or delete your account. You can disconnect at any time under Connected apps on your account page; this takes effect immediately and stops Claude from reading or changing anything. Deleting your account removes the permission, its tokens and the tool-call log along with the rest of your data. Short-lived sign-in codes and expired tokens are purged automatically as they age out.
The Newsletter
When you sign up for the newsletter, we store your email address, the time you asked to subscribe and a random confirmation token, then email you a confirmation link. Until you click it, the request stays pending, and it expires on its own after seven days. Once you have confirmed, we keep your email address, the times you requested and confirmed the subscription, and the account it belongs to: confirming creates a free account for that address if you do not already have one. The subscriber list is kept in Cloudflare's key-value storage, separately from the account database.
The newsletter and your account go together: creating an account also subscribes its email address. You can unsubscribe at any time from your account page; that stops the emails but keeps your account.
Confirmation emails and sign-in links are delivered by our email provider, Resend, which receives your email address in order to send them. To stop automated abuse, the newsletter, sign-up and sign-in forms also keep short-lived counters keyed by your IP address or by the email address entered; each counter expires after ten minutes.
What Other People Can See
Traveler profiles are public by default, as we explain when you sign
up. While your profile is public, anyone can see your handle,
display name, bio and profile photo, along with the guides,
destinations and attractions you have saved, on your profile page at
/travelers/your-handle/. Places you mark as visited can
appear, with your handle and display name, in the list of travelers
who have been there on that place's page. New trips are public too:
anyone with the link to a public trip can see its name and stops.
Your email address is never shown publicly, and neither are the notes you write on trip stops or the places you want to go. You can switch your whole profile to private at any time from your profile and privacy settings, which hides your profile page, saved items, visited places and trips from everyone else, and you can also make an individual trip private. Public profile and trip pages ask search engines not to index them.
Sign-in Cookies
Signing in uses two first-party cookies. They exist only to sign you in and are never used for advertising:
-
__Host-sessionholds the random identifier of your signed-in session. Page scripts cannot read it, it is only sent over HTTPS, and it expires after 7 days, or earlier when you sign out or delete your account. -
tg_auth_returnis set when you reach the sign-in or sign-up page from another page on the site, and remembers where to send you back to afterwards. It lasts 15 minutes.
Keeping and Deleting Your Data
We keep your account data for as long as your account exists. A signed-in session stops working after 7 days, and signing out or signing in again ends it. Your newsletter subscription lasts until you unsubscribe or delete your account.
You can delete your account at any time with the Delete account button on your account page. This permanently deletes your account details, passkeys, sessions, sign-in links, profile, saved items, visited and want-to-go places, trips and trip notes, and the links between your account and your browsing sessions, and it removes your email address from the newsletter list. Deletion cannot be undone.
Two records are not yet removed automatically when you delete your account: a profile photo you uploaded, which stays in our image storage, and the record of an emailed sign-up link, which includes the address it was sent to. To have your photo removed with your account, remove it from your profile settings before deleting the account. In either case you can email us at [email protected] and we will erase it; the same address works for a copy of your data or any other request described under βYour Rightsβ above.
Your Account and Browsing History
If you choose to create an account and sign in, we associate the pages you view while logged in with your account so we can personalise recommendations β for example, suggesting destinations and guides related to the places you have already explored. This linkage happens only while you are signed in; pages you view logged out are never tied to your account.
This connection is stored as first-party data on our own systems and is never sold or shared with third parties. You can delete your account at any time from your account settings, which permanently removes the link between your account and your browsing history.
Deleting your account is thorough and immediate. In the same step we erase your profile and its stored data, remove any profile photo you uploaded from our image storage, and clear the one-time email tokens created when you sign in or register β so none of these records, nor your email address held in them, is left behind.
As part of that same clean-up we also purge any expired sign-in links and registration tokens still waiting to age out, so stale data never lingers on our systems longer than it needs to.
Measuring Newsletter and Account Conversions
To understand how well the newsletter and free account work β without profiling you β we count a small set of server-side conversion moments: when a subscription request is accepted, when the double opt-in email is confirmed, and when an account is created for the first time. Each is recorded on our own systems from the server, never from a script running in your browser.
So we can tell that a later confirmation belongs to the same signup, we generate a random, opaque attribution reference at subscribe time. It is not derived from your email address or your browsing session and identifies nothing about you on its own. The only place this reference is tied to your email is inside the temporary pending-confirmation record, which is deleted the moment you confirm and otherwise expires on its own within seven days. The confirmation link we email you never carries a session identifier.
When you submit the newsletter form, that first server-side event also carries your analytics session id, so we can relate the submission to the browsing session it came from when we study the funnel. That session id stays with our own first-party analytics on the same footing as the browsing measurements described above; it is never written to the pending-confirmation record and never placed in the confirmation link. The aggregate counts and rates we report from these events never expose your email address, account identifier, session id, or IP address. Deleting your account, as described above, removes these associations.