Trips by Torotrips.manr.ai

Privacy

The short version: your trips are stored in your browser, there is no account, and there is no server holding them. Below is the longer version, including the exceptions.

What is stored, and where

Everything you enter — trips, stays, transport, costs, travellers, passport numbers, booking references, documents and checklists — is written to your browser’s own storage (IndexedDB) on the device you entered it on. It is not uploaded, and there is no copy of it anywhere else.

There is no account and no sign-up, so there is nothing identifying you attached to any of it. Clearing your browsing data for this site deletes your trips from that browser permanently. We cannot restore them, because we never had them.

What leaves your browser

Three things, and nothing else.

A city name, to OpenStreetMap. To place a pin on the map, the name of a stay’s city — “Kandy”, “Colombo” — is sent to OpenStreetMap’s public geocoding service, and the map itself loads map images from OpenStreetMap. Nothing else about the trip goes with it: no dates, no names, no passport numbers, no amounts. Results are cached in your browser so the same city is not looked up twice.

A message, if you send one. If you use the contact form, your name, your email address and your message are sent to us by email so we can reply. Nothing about your trips is attached.

Ordinary requests for the site itself. Loading any website means your device asks a server for it, and that request carries your IP address. Our server keeps standard web-server logs. Fonts, images and code are served from this site rather than from a third-party network, so loading a page does not tell anyone else that you were here.

Analytics

We use Google Analytics to count visits — how many people arrive and which pages they read. It runs only if you agree to it. You are asked once, with the choice presented plainly, and refusing is a single click.

If you refuse, no cookie is set and no profile is built. Being straight about what refusing does not do: the analytics script still loads, and Google receives an anonymous, cookieless signal that a page was viewed, which it uses only for aggregate counts. It cannot recognise you, link two visits, or follow you to another site. You can change your answer at any time from the “Cookie choice” link in the footer of every page, and withdrawing takes effect immediately.

If you agree, Google receives the ordinary things a web analytics tag receives: the page you are on, roughly where you are in the world, and what kind of device and browser you are using. Your IP address is anonymised before it is stored.

Nothing from your trips is ever included. No names, dates, hotels, costs, passport numbers or booking references — none of it is readable by the analytics script, because none of it is on the page in a form it collects. And the address of a trip page carries an identifier, so that identifier is stripped before the page view is sent — Google is told that someone opened a trip page, never which one.

Advertising

There is no advertising on this site. No ads are served, no advertising cookies are set, and the advertising signals sent to Google are refused for everyone regardless of what you choose above.

We may add advertising later. If we do, you will be asked about it separately and plainly before anything runs — this page will say so first, and consenting to analytics today is not consent to advertising tomorrow.

Advertising will not run on your trip pages. Ads, when they appear, will be on the public pages only — never on the screens where your itinerary, travellers and documents are shown.

Cookies

The site stores three things on your device: your trips, your choice of light or dark theme, and your answer to the analytics question above. Those three stay on the device and are readable only by this site.

If — and only if — you agree to analytics, Google Analytics also sets its own cookies to recognise a returning visit. Refuse, and it sets none.

Files you export, and auto-save

You can export a trip as a file, and you can pick a file for the app to keep in sync automatically. Those files are written by your browser to a location you choose. They are never uploaded.

An exported file is plain and unencrypted, and contains passport numbers. If you put it in a synced folder, it goes wherever that folder goes. Keep it somewhere you would keep the passports themselves. The separate “share a copy” export strips passport numbers, expiry dates, documents, and booking and ticket links — use that one for sending an itinerary to the people travelling with you.

Your rights, and why most of them do not apply

Data protection law gives you rights to access, correct, export and delete the personal data an organisation holds about you. In this case there is nothing to exercise them against: we hold no account, no profile and no copy of your trips. You already have direct access to all of it, you can edit it, the app exports it in a documented format, and deleting it is immediate and permanent.

The one exception is a message you send through the contact form, which arrives as an ordinary email. If you would like that deleted, reply to it and ask.

Children

This is a trip planner and is not directed at children. It collects nothing about anyone because it collects nothing at all.

Changes

If what the app does with data changes, this page changes with it. It describes the current behaviour, not an intention.

Questions about any of this can go through the contact form. See also the terms.