Privacy should be plain.

1. Who we are

Travelomi is operated by Paul Zammit, trading as Travelomi. The product is in Early Beta. Write to [email protected].

2. What this notice covers

The magazine (guides, build notes, these pages) and the product (the Trip you shape in Chat). When you hand off to a provider to book, that provider’s notice applies to what you do there.

3. What we collect

Only what the product needs to run:

• Account: your Google name and email if you sign in.
• Trip and Chat: what you write, Trip state (Intent, Legs, Stays), and files you attach.
• Search queries sent to travel sources: dates, places, travellers.
• Technical: IP address, user agent and URL, used to host the site and to count pageviews.
• Push: a browser subscription, only if you turn the unfinished-Trip nudge on.
• Magazine: pageviews only. No account. No stored reader profile.

4. What we use it for

To run your Trip, search travel sources, interpret what you write, keep a session, measure how the product is used, keep the service secure, and meet legal duties. We do not sell personal information and we do not run advertising pixels.

5. Who else sees it

Named processors, not a generic list:

• Google — sign-in, and place lookups.
• OpenAI — to interpret a Chat turn and, where needed, to search the web for context. Their API, not the consumer ChatGPT product.
• SerpApi — display-grade Google Flights and Google Hotels searches.
• Open-Meteo — weather for a place on the Trip.
• PostHog Cloud EU — product and magazine analytics. Browser ingest is first-party at tech.travelomi.com. After you sign in we identify you by email. Events carry categories, not message text or Trip titles.
• The hosting operator — ordinary request logs (IP, URL, user agent) to deliver and protect the site.

Paul Zammit can read Chat transcripts and Trip state to operate the product. That access is owner-only.

Not in use today: Duffel, payments, affiliate programmes, advertising, or session replay. If that changes, this page will say so.

6. Cookies and storage

There is no cookie banner because there are no advertising or analytics cookies. The magazine sets none. The product sets one strictly necessary first-party cookie, travelomi_session(HttpOnly; 30 days if you are logged out, 90 days if you are signed in; it slides while you use the product). That cookie is how a logged-out browser owns one Trip.

Analytics is cookieless: PostHog writes no cookie and no browser-storage identifier. A content reader is a daily server-side hash, not a stored profile. Same-day returns stitch; the next day starts again.

The product may keep two first-party preferences in the browser: colour theme, and whether you dismissed the nudge prompt. Neither is used to track you.

7. How long we keep it

• A logged-out Trip left idle is purged after 14 days.
• If you delete a logged-out Trip, access ends at once. The rows are purged after 14 days.
• The session cookie lasts 30 days logged out, 90 days signed in, sliding with use.
• Signed-in work stays until you delete the Trip or the account.
• Daily counts that reconstruct nothing about a traveller are kept.

8. Your rights

You can ask to see, correct, delete or object to personal information we hold. Delete a Trip in the product where that control exists, or write to [email protected]. We will answer.

9. Children

Travelomi is not directed at children under 16. If you believe a child has used it, write to us.

10. Changes

When this notice changes, the date at the top of this page changes.

11. Contact

[email protected] · Terms · How Travelomi works