LAST UPDATED 15 NOVEMBER 2026
Privacy policy
The short version. trails.city turns trips people really took into trails other people can follow. Your trails are link-only unless you choose otherwise. We don't sell your data, show ads or use tracking cookies. Photos are stored without their hidden location data, and the exact place you stayed never appears on a trail. When you make a trail, your words and photos go to our AI provider to build it, and nowhere else.
Who we are
trails.city ("trails.city", "we", "us") runs the website at trails.city. For anything in this policy, contact privacy@trails.city.
What we collect
- Your account. When you sign in with Google, we receive your name, email address and Google account ID. We don't receive your Google password or anything else from your Google account. You also choose a handle, which appears in your trail links (trails.city/@handle).
- Invites. trails.city is invite-only, so we record whose invite link you joined with. For the invite links you make, we store only a scrambled (hashed) version, when each was used and by whom.
- Your trails. What you say or type to make a trail, kept as text, and the trail itself: its stops, titles, times, notes, who can see it, and any copies of it.
- Your photos. We store a resized copy of each photo you add, with its embedded data (EXIF, XMP and IPTC, which can include location and camera details) removed. We refuse a file that still carries it. Separately, your browser reads the photo's capture time, camera model and location, when the photo has them, and sends them to us. We keep these privately to put your stops in order and match them to places, and never show them on a trail.
- Technical data. Our hosting provider keeps short-term logs of requests (such as IP address, browser and time) for security and to fix problems. We count page views with Cloudflare Web Analytics, which doesn't use cookies or identify you.
Cookies
We use only essential cookies: one keeps you signed in (for 30 days), one exists for a few minutes while you sign in with Google, and one remembers an invite link you opened (for up to 14 days) so it still works after Google sends you back. We don't use advertising, analytics or third-party tracking cookies.
How we use it
- To run trails.city: build your trails, show them to the people you choose, and let them make their own copies.
- To provide the AI features you use (see below).
- To keep the service secure, prevent abuse and apply usage limits.
- To contact you about your account or important changes.
We don't sell your information, use it for advertising, or use it to train AI models.
Who can see your trails
- Link-only, the default: anyone with the link. It isn't listed anywhere.
- Public: anyone, and it's listed on the pages of the places it passes through.
- Private: only you.
Anyone who can see a link-only or public trail can make their own copy ("make it yours"). The copy credits you, links to your trail and shows your photos with credit. If you later make your trail private or delete it, copies keep their text and the credit but lose your photos and the link.
A trail shows your first name and handle, its stops and times, the words of yours it quotes, and your photos. It never shows where your photos were taken, the exact place you stayed (only the town), your email address, or anything you said that isn't part of a stop. People you mention appear by their role ("our driver") unless you record that they agreed to be named. Please ask people before you name them or add photos in which they can be recognised.
AI features
When you make or fix a trail, we send what you said or typed and your photos to Anthropic's Claude API, to read the photos and draft the stops and any questions. Anthropic processes them and returns the result to us. Under Anthropic's commercial terms, data sent through its API isn't used to train its models. Nothing is sent to an AI provider unless you make or fix a trail.
Speech
The mic button uses your browser's built-in speech recognition. Depending on your browser, your voice may be processed by the browser's maker (for example Google for Chrome, or Apple for Safari) under their own privacy terms. trails.city only receives the resulting text, never the audio.
Place lookup
To match your stops to real places, we may send a stop's place name and its city or rough area to a place-lookup service (Google Places or Foursquare). We don't send your name, email address or photos.
Who we share it with
- Service providers that run trails.city for us: Cloudflare (hosting, database, photo storage, logs and page-view counts), Google (sign-in, and place lookup if we use Google Places), Anthropic (AI features) and, if we use it for place lookup, Foursquare. They may only use your data to provide their service to us.
- The people your trail settings allow, as described above.
- When required by law, or to protect the rights, safety and security of our users and service.
Where it's stored
Your data is stored with Cloudflare. Our providers may process it in other countries, including the United States, with appropriate safeguards.
How long we keep it
We keep your data while you have an account. A draft trail you never approve is deleted after 30 days, with its photos. To delete a trail or your whole account, email privacy@trails.city from the address you sign in with, and we'll do it within 30 days. Hosting logs are kept only briefly.
Your rights
You can see, correct, export or delete your data, or object to how we use it. Depending on where you live (for example under the GDPR, UK GDPR or California law), you may have further rights, including complaining to your data protection authority. Email privacy@trails.city and we'll respond within 30 days.
Security
All traffic uses HTTPS. Sign-in sessions and invite links are stored only in hashed form, and every request is checked so that people only see the trails they're allowed to. No system is perfectly secure, so if you believe your account has been compromised, contact us straight away.
Children
trails.city isn't intended for anyone under 16, and we don't knowingly collect data from them.
Changes
If we change this policy, we'll update the date at the top. If a change is significant, we'll tell you on trails.city or by email before it takes effect.