tratlas

Privacy

Privacy policy

Last updated October 7, 2026

Tratlas is built by Dandelion Technology LLC. This page explains what we collect when you use Tratlas, why we collect it, and what happens to it if you delete your account. We wrote it the way we'd want to read one: plainly, and without the parts that don't apply to us.

The short version

Tratlas has no analytics, advertising, or crash-reporting tools of its own, and nothing here tracks you across other apps or websites. Mapbox, which draws our maps, collects some usage data of its own (see Mapbox below). The sections below explain exactly what we do collect, who it's shared with, and why.

Signing in

We use Clerk to handle sign-in. Your sign-in credentials live entirely with Clerk and never reach our database. The first time you sign in, we copy your email address and a display name into our own database and use it to identify your account. Your profile photo, if you have one, also stays with Clerk; we never store it ourselves.

If you fill in profile details such as your interests or a home city, we store those too, and we use them to make trip suggestions feel less generic.

Your trips and itineraries

Everything you build in Tratlas (trip titles, dates, budget, who is traveling, destinations, and each itinerary item) is stored in our database, tied to your account.

When you invite someone onto a trip, you give them a role, and that role decides what they can do. An editor can change the trip and its plan. A viewer can read it and suggest things to add, but cannot change it. Either way their access covers that one trip and nothing else of yours.

Photos you add to a trip

You can add photos to a trip from the Tratlas mobile app (the web app is read-only for photos today). Before a photo is uploaded, your phone re-encodes it, and that re-encode drops the metadata your camera embeds, including GPS location. That means the location your camera recorded is not sent to us and not stored.

If you place a photo on the map yourself, we do store the latitude and longitude you chose for it, tied to that photo, because you told us where it goes.

Only the trip owner, its active members, and whoever uploaded a given photo can see or remove it. There is no public link to a photo file; every request for one is checked on our server, not just hidden in the app's screens.

Your location

Your exact location is never sent anywhere, unless you turn on Share map data with Mapbox in the iPhone app (see Mapbox below). On the Today screen, when you tap to use your location, Tratlas reads your phone's GPS locally and compares it against your plans, entirely on your device.

That same tap also names the area you're in. To do that, a rounded version of your location, accurate to about 110 meters rather than your exact position, is sent to Mapbox to look up a neighborhood name. It is used for that one request and is not stored anywhere.

On the web app, we also read an approximate location from your IP address when a page first loads, just to point the globe roughly the right way. It comes from our host as a byproduct of how web requests work, it is city-level at best, and we never store it or treat it as a fact about where you actually are.

Searching for a destination

When you type a place into a search box, whatever you type is sent to OpenStreetMap's Nominatim service to look up matching places. We keep the place it returns (its name and coordinates) in a shared cache so we do not have to ask again, but we do not store the search text itself.

AI-generated suggestions

When you ask Tratlas to suggest things to do, we send your destination, your trip's approximate length and month, and your interests (if you have set any in your profile) to Anthropic, the company that provides the AI model behind this feature. We do not send your name, email address, or exact travel dates. What Anthropic does with that request beyond generating a response is governed by Anthropic's own terms, not this one.

Keeping the service fair

To stop any one account from overwhelming Tratlas or running up an unreasonable AI bill, we count how often you use certain features using Upstash, a Redis-based service. Those counts are keyed to your internal account id, never your IP address, and expire automatically.

Sharing your trips with other people

Inviting someone onto a trip gives them access to that trip's content. If you publish a trip as a public share page, anyone with the link can see it, and it shows your display name; this only happens when you choose to publish a trip.

Reporting and blocking

If you report a person, a trip, a suggested stop or a photo, we keep the report so we can review it: who sent it, what it is about, the reason you chose, and any note you added. Each new report is emailed to us through Resend, and if you delete your account your reports stay but are no longer linked to you.

If you block someone, we keep a record of it so we can keep you apart, and it is removed if either of you deletes your account.

Deleting your account

You can delete your account at any time from your account page. Deleting it removes your identity from our sign-in provider, every trip you own and everything in it (itinerary, photos, members), your membership on trips you do not own, your connections with other people, and every photo you have personally uploaded, even on a trip someone else owns. It signs you out everywhere, and it cannot be undone.

Two things are not part of your account and are not removed with it. Place lookups (the names and coordinates behind a destination search) are a shared cache with no connection to any one person. AI suggestion results are also a shared cache; if your interests were part of a request that generated a cached suggestion, that text stays in that shared cache after your account is gone, on no deletion schedule at all, not even the 30-day window that decides whether a cached suggestion is still fresh to reuse. Neither cache is linked back to your name, email, or account.

Other companies involved

We rely on a small set of other companies to run Tratlas. We do not use any of them to advertise to you.

  • Clerk: sign-in and account identity.
  • Neon: our database, where trip and account content is stored.
  • Vercel: web hosting, and Vercel Blob for storing photo files.
  • Mapbox: map rendering and neighborhood lookups. To show and bill maps, Mapbox always receives map requests, session counts and a random identifier for each copy of the app or browser. On the web, Mapbox's map software also collects its own usage data (map loads and similar, with no location). In the iPhone app, that extra collection is off unless you turn on Share map data with Mapbox in your account. If you do, Mapbox may also collect your location while you use its maps, to improve them.
  • Anthropic: generates AI trip suggestions, as described above.
  • Upstash: rate limiting, as described above.
  • OpenStreetMap (Nominatim): destination search, as described above.
  • Resend: sends report notifications to us.

Changes to this policy

If what we collect or why changes, we will update this page and the date at the top.

Questions

Email us at info@dandeliontechnology.com, or visit our support page. For the rules of using Tratlas, see our terms of service.