Privacy Policy
Last updated 31 October 2026
- You can browse, edit and download itineraries without an account. Your edits stay in your browser.
- If you sign in we keep your email address; if you subscribe, Stripe handles your card and we never see it.
- We don’t sell your data, and we don’t use advertising or analytics cookies.
- Email support@travelitinerarytemplate.app to see, export or delete your data.
1. Who we are
travelitinerarytemplate.app (“we”, “us”) is operated by Travel Itinerary Template. We are the controller of the personal data described here. Contact us at support@travelitinerarytemplate.app.
2. What we collect
When you just browse
Itineraries you edit, and the blank itineraries you fill in, live in your browser tab. We don’t receive them unless you use AI chat or export a file. To enforce daily limits we store a salted, one-way hash of your IP address with a timestamp; we can’t turn the hash back into your IP. Our host keeps standard server logs (IP address, browser, pages requested) for security and debugging.
When you use AI chat
The itinerary on screen and your last ten chat messages are sent to our AI provider to produce a reply. We don’t store the text of your conversation. For each message we record the destination, the model used, token counts, cost and time taken, linked to your account or IP hash, so we can count your daily allowance and watch our costs. Don’t put sensitive personal information in chat.
When you sign in
Your email address, and if you use Google, the basic profile Google shares (name and email). Sign-in links and sessions are handled by our authentication provider.
When you subscribe to Pro
Stripe collects your payment details and billing address. We receive and store your Stripe customer ID, subscription status, price and renewal date, never your full card number.
When you publish a story
The story, title, destination, travel month and the author name you choose are public. We also store your account ID and IP hash with it to prevent spam.
When you export
Exports are created on request. If you are signed in, the file may be kept in cloud storage so we can give you a download link.
3. Cookies and local storage
| Name | Purpose | Kept for |
|---|---|---|
| sb-* (Supabase) | Keeps you signed in. Strictly necessary. | Until you sign out or the session expires |
| currency | Remembers the currency you picked. | 1 year |
We don’t set advertising or analytics cookies. If we add analytics later, we will update this page and ask for consent where the law requires it.
4. How we use it, and why we’re allowed to
- To provide the service you asked for: sign-in, AI chat, exports, Pro features, publishing stories (performance of a contract).
- To bill you and keep tax and accounting records (contract and legal obligation).
- To prevent abuse, enforce daily limits and keep costs under control (legitimate interests).
- To answer you when you write to us (legitimate interests).
We don’t sell or rent personal data, and we don’t use it for advertising or automated decisions with legal effects.
5. Who processes it for us
| Provider | What for | Data involved |
|---|---|---|
| Vercel | Hosting | Requests, server logs |
| Supabase | Database and sign-in | Account, subscription, stories, usage records |
| Stripe | Payments | Payment and billing details |
| Anthropic | AI chat replies | Itinerary and recent chat messages |
| Cloudflare (R2) | Export file storage | Exported itineraries of signed-in users |
| Sign in with Google; web fonts | Profile if you choose Google; IP address when fonts load | |
| Wikimedia | Place photos load from upload.wikimedia.org | Your browser’s IP address |
| Geoapify, Mapbox, Google Places | Matching place names to real places | Place names only, no personal data |
Some of these providers are in the United States. Where data leaves the EU, UK or Switzerland, we rely on the providers’ Standard Contractual Clauses or an adequacy framework. We may also disclose data if the law requires it.
6. How long we keep it
- Account and stories: until you delete your account or ask us to remove them.
- Subscription and payment records: as long as tax and accounting law requires, typically up to 10 years.
- Usage records for limits and cost tracking: up to 12 months.
- Export files: deleted when no longer needed for the download link.
7. Your rights
Depending on where you live (for example the EU, UK or California), you can ask to access, correct, delete or export your data, and object to or restrict how we use it. Email support@travelitinerarytemplate.app from the address on your account; we answer within 30 days. Deleting your account cancels any Pro subscription. If you’re unhappy with our answer, you can complain to your local data protection authority.
8. Children
The service isn’t meant for children under 16, and we don’t knowingly collect their data. If you think a child has signed up, tell us and we will delete the account.
9. Security
Data is encrypted in transit, database access is restricted, and IP addresses are stored only as salted hashes. No system is perfectly secure; if a breach affects you, we will tell you as the law requires.
10. Changes
We will post changes here and update the date at the top. For significant changes we will also tell signed-in users by email. See also our Terms of Service.