Privacy policy.

Euxie Atlas (“Atlas”) is run by Euxie, which is James Argarin, an individual based in the Philippines. It is not a company and carries no advertising. It does keep two kinds of record: the ones the features below need, and a usage telemetry trail described in § 04.

Your account (email and password hash, handled by Supabase Auth), your trips — days, stops, notes, costs, booking references — the files you upload (booking documents and photos, including the date and location your camera wrote into a photo), your chats with the planner, and a log of AI calls (token counts and timings, never the text of a prompt).

Files live in a private storage bucket. They are served through short-lived signed links, never public URLs.

When you use an AI feature, the relevant content is sent to Google’s Gemini API under this app’s key: the chat sends your messages and what it looks up to answer them — the itinerary of the trip you are in or, in the app-wide chat, of the trips you ask about, and the details read from your booking documents (references and traveller names included) when you ask about bookings; the paste reader sends what you pasted; booking parsing sends that document; the journal writer sends a day’s stop names and photo captions. Generating a trip draft sends your destination, dates, pace, interests, travel constraints, travel mode, currency and optional budget. Suggested venue names and the destination are then searched through Google Places. An uncreated draft is kept only in the current page; AI usage counts and quota records are still stored. Google’s API terms apply to that processing. No AI call happens in the background — each one is something you clicked.

Place searches are forwarded to Google Places and route lookups to OpenRouteService from our server, so your IP address is not shared with them. Map tiles are fetched by your browser from MapTiler, which therefore sees your IP address, as any map host does.

To understand how Atlas is used, it also records what you do here as telemetry. This is a second copy of your content, keyed to a device identifier in your browser and, while you are signed in, linked to your account as well, and read by the maintainer. Specifically:

A trip is visible to its owner and the people invited to it. Invites are bound to an email address. A public link, if you create one, shows a read-only page — itinerary, day notes and photos — to anyone who has the link; it never shows costs, booking references, documents, collaborators or chats, and you can revoke it at any time. Public pages are marked not to be indexed by search engines.

Deleting a trip deletes its days, stops, files, chats and share links, for everyone. Deleting your account deletes every trip you own the same way, removes you from trips shared with you, deletes the rest of Atlas’s data about you, and signs you out. Your hive sign-in itself stays, because it is shared with the other apps on this site. Photos you added to someone else’s trip remain with that trip. There is no soft-delete and no backup. The log of AI calls and the daily allowance counts (§ 02: token counts and timings, never what was asked) stay with your hive sign-in, so deleting your data does not reset the daily limits. Usage telemetry (§ 04) is unlinked from your account by this but not removed — ask for that through the contact below.

When you create an account, Atlas records which version of the terms of use you agreed to and when, and whether you asked for product news and offers by email. That box starts unticked; you can change your answer under Account at any time. Deleting your account turns promotional email off; the record of what you agreed to is kept with your sign-in.

The sign-in, sign-up, password-reset and account forms run Cloudflare Turnstile, a check that the visitor is a person and not a script. It runs in a frame served by Cloudflare, which reads your network address and technical details of your browser to decide, and tells this site only whether the check passed. Cloudflare states that it uses those signals to detect and block bots, not to identify or profile anyone; its Turnstile privacy policy describes them.

Questions go through the feedback button in the app’s header, which emails the maintainer directly.