Privacy Policy
Last updated 28 September 2026
This site does not require an account and does not store your personal data on any server. Favorites, saved trips, and recent searches stay in your browser's local storage on your device. Clearing browser data erases them.
This policy explains, in plain language, what happens to information when you use TravellerSeed (travellerseed.com), which third parties are involved, and what control you have. If anything here is unclear, email [email protected].
1. Who we are
TravellerSeed is a free travel information website built and maintained by Telly Jameson at My Startup ("TravellerSeed", "we", "us"). For the purposes of data protection law, we are the controller of the small amount of information described below. You can reach us at [email protected].
2. The short version
- No sign-up, no accounts, no passwords, no profiles.
- No tracking or advertising cookies, and no ad networks.
- Your saved trips, routes and favorites live only in your own browser.
- We count affiliate clicks in aggregate — never who clicked.
- We never sell, rent or trade personal data.
3. What we collect
Anonymous usage statistics
What we collect: Cloudflare Web Analytics records anonymized page views, referrer, country, device type, and browser. No tracking cookies. No profiles. No data sales. Cloudflare Web Analytics does not use cookies or local storage to identify you and does not fingerprint visitors; we only see aggregated totals such as "page views from mobile devices this week".
Technical data processed by our host
The site runs on Cloudflare's network. Like any web host, Cloudflare necessarily processes your IP address and basic request details (such as the page requested, time, and browser type) to deliver pages, protect the site against abuse and attacks, and keep it running. We do not build logs of individual visitors. Our own server code briefly holds a request count per IP address in memory for about one minute to prevent abuse of our data endpoints; this is never written to storage.
Aggregated feature events
To learn which parts of the site are useful, our server records a small, anonymous event when you do one of these things: search (and whether the search found nothing), view a country, airport or route page, use the trip builder, save or remove a saved item, or click a link marked "Partner" (which passes through a short redirect on our site, /out/…).
Each event contains only: the event name, the type of page it happened on, a short item key (an airport, country or route code, a partner name, or — for searches — the search text, lower-cased and cut to 60 characters), and the country Cloudflare reports for the request. It contains no IP address, cookie, device identifier, user ID or session ID, so events cannot be linked to each other or to you. They are stored in Cloudflare Workers Analytics Engine and deleted automatically after three months. Please don't type personal information into the search box.
Emails you send us
If you email us, we receive your email address and whatever you choose to include. We use it only to reply and to fix any data errors you report, and we delete correspondence when it is no longer needed.
What we do not collect
We do not collect names, postal addresses, phone numbers, payment details, passport information or precise location. Search suggestions are worked out in your browser; only the final search text is sent as an anonymous aggregated event, as described above.
4. Data stored on your device
To remember things between visits without an account, TravellerSeed uses your browser's local storage. This data never leaves your device unless you export it yourself. We use these keys:
| Key | What it holds |
|---|---|
tr:favorites | Countries and airports you starred |
tr:routes | Routes you saved |
tr:trips | Trips you built in the trip builder |
tr:recent | Your last few searches |
tr:theme | Your light/dark mode choice |
You can export, import or erase all of it on the Settings page, or by clearing this site's data in your browser settings. Because this data is only on your device, we cannot see it, recover it, or delete it for you.
5. Cookies
TravellerSeed does not set cookies of its own. Cloudflare may set a strictly necessary security cookie (such as __cf_bm) if it needs to tell humans from bots during an attack; this is used only for security and expires quickly. Partner websites set their own cookies once you leave our site — see section 7.
6. Third-party services
APIs we call: Open-Meteo, Frankfurter and Wikipedia (plus the fallback rate source listed on Sources). Public holidays and country facts are bundled into the site when it is built, so no request is made for them. All requests are proxied through our Cloudflare Worker; your IP does not reach them directly. Partner logos are fetched and cached the same way.
Some page resources are loaded directly by your browser from other providers, which means those providers receive your IP address and standard browser information when the page loads:
- Unsplash (images.unsplash.com) — photographs. Unsplash privacy policy.
- OpenStreetMap tile servers — maps on airport and route pages. OSMF privacy policy.
- Flag images (flagcdn.com) — country flags.
- Cloudflare — hosting, security and analytics. Cloudflare privacy policy.
We choose providers that do not require us to run advertising or tracking code, and we will keep this list up to date.
7. Affiliate links and partner sites
Third parties: When you click an affiliate link (marked "Partner"), the destination site sets its own cookies and receives standard referral info per its own privacy policy. We receive an aggregated click count in Cloudflare KV — never who clicked.
If you book or buy something on a partner's site, that partner (and the affiliate network that tracks the referral, such as FlexOffers) handles your personal and payment details under their own privacy policy, not this one. We may later receive a commission report from the network; these reports show sales totals and do not identify you to us.
8. Why we process data (legal bases)
Where data protection laws such as the EU and UK GDPR, the Nigeria Data Protection Act 2023, or US state privacy laws apply, we rely on our legitimate interests in running a secure, reliable website and understanding its use in aggregate (hosting, security, analytics and click counts), and on your request when you email us. We do not use personal data for automated decision-making or profiling.
9. International transfers
Cloudflare and the other providers listed above operate worldwide, so technical data may be processed outside your country. These providers use recognised safeguards, such as standard contractual clauses, for international transfers.
10. How long we keep data
- Aggregated analytics — kept by Cloudflare in aggregated form under its retention settings.
- Aggregated feature events, including partner clicks — deleted automatically after three months.
- Emails — deleted once the conversation is resolved and no longer needed.
- Data in your browser — kept until you erase it.
11. Your rights
Your rights: because we store no personal data, there is nothing to access or delete on our end. Clear this site's browser storage or use the "Erase everything" button in Settings to remove local data.
Depending on where you live, you may have the right to ask what personal data we hold about you, to correct or delete it, to object to processing, and to complain to your data protection authority. If you have emailed us and want that correspondence deleted, or you have any privacy question, write to [email protected] and we will reply within 30 days. We do not sell or "share" personal data for cross-context advertising, so there is nothing to opt out of.
12. Children
TravellerSeed is a general-audience travel reference and is not directed at children. We do not knowingly collect personal data from anyone under 16. If you believe a child has emailed us personal information, contact us and we will delete it.
13. Security
The site is served only over HTTPS, and we keep the amount of data we handle to a minimum — the best protection is not holding personal data at all. Remember that anyone with access to your device can see the data saved in your browser.
14. Changes to this policy
If we change how we handle data — for example, by adding a new provider — we will update this page and the "Last updated" date above.
15. Contact
Contact: [email protected]