Privacy notice

1. Who this is from

PlanTravel is a trip-planning tool operated by PlanTravel ("we", "us"). This notice explains what personal information the tool handles and what we do with it. It covers the website, the trip pages, the PDF and calendar exports and the signed-in editing screens.

2. What we collect

• When you just visit.Our hosting provider keeps ordinary request logs (such as your IP address, browser type and the page asked for). Our own logs record only errors and slow requests: the page path, the result, how long it took and a random reference number. They do not record who you are.
• Trip information.Agents type in trip titles, cities, dates, places, times, notes, estimated prices and map links. This is shown on public pages. Please do not put travellers' names, passport numbers, phone numbers or other personal details into itinerary fields.
• Agent accounts.People who edit sign in with Google. We receive and store their name, email address, profile picture and Google account ID, whether the account is active, and when it was created and last used.
• Edit history.Each change is recorded with the time, the agent's email, what was done (for example "update activity") and the trip and a short title. Notes, booking codes and links are not copied into this history.
• Pocket (bookings and documents).Flights, stays, document details (visa, passport, insurance, booking), reference codes, notes and links to files kept elsewhere. We do not store uploaded files. Pocket is shown only to signed-in agents.
• What you type into searches.The place name an agent searches for, and a trip's saved location for prayer times, are sent to the services listed in section 5.

We do not run advertising, sell personal information, or use analytics or tracking cookies of our own.

3. Who can see what

• Anyone with the address can open trip pages, the client share page, the PDF and the calendar feed. Trip pages are public and there is no password on them.
• Signed-in agents (people on our access list) can edit trips. Every signed-in agent can open the Pocket of every trip.
• Administrators who manage our data storage can see everything in it, including the access list and edit history.

4. Cookies and storage on your device

• tk_sessionKeeps an agent signed in. Signed, not readable by scripts, lasts 7 days, only set after sign-in. Needed for editing.
• tk_oauthShort-lived safety token during Google sign-in. Lasts 10 minutes and is deleted when sign-in finishes.
• pt_welcomeRemembers that you have seen the welcome page so it is not shown on every visit. Lasts 1 year. Contains no personal information.
• Settings kept only in your browserYour chosen season theme and motion level, an unfinished new-trip draft (kept up to a week), packing-checklist ticks and "on time / running late" check-ins for a trip day. These never leave your device.
• Offline copySo trips can be read without signal, the app saves public pages and its own files in your browser. Agent-only screens are not saved, and signing out clears the saved pages.

You can clear all of this in your browser settings at any time. Editing will ask you to sign in again.

5. Services that receive data

PlanTravel relies on other companies. They receive only what is needed for the job below and have their own privacy policies.

• GoogleSign-in (name, email, picture, account ID are given to us). Google also provides the cloud storage where trip data is kept. Google Fonts: when a page loads, your browser asks Google for the typefaces, so Google can see your IP address.
• VercelHosts the website and keeps ordinary request logs.
• Open-MeteoTurns a place name an agent searches for into a location (sent from our server).
• AladhanPrayer times and Qibla direction for a trip's saved location and dates (sent from our server).
• open.er-api.com and jsDelivr (currency data)Your browser fetches exchange rates for the cost views. This shares your IP address with them.
• YouTube (privacy-enhanced mode)Only if you press play on a video on a place. Nothing is loaded from YouTube before that.
• Google Maps, Google Calendar, WhatsAppOnly when you click a link or button that opens them. What you do there is covered by their policies.

6. Why we use data

• To show and edit trips, make PDF and calendar exports, and let you share a trip.
• To keep editing limited to people we have allowed, and to keep a record of changes in case something goes wrong.
• To keep the service running and secure (error and slow-request logs, protection against abuse).

We do not use personal information for marketing and we do not sell it. We share it only with the services in section 5, and where the law requires.

7. How long we keep it

• Trips and Pocket items stay until an agent deletes them. Our storage provider keeps older versions for some time after a deletion.
• Agent accounts and edit history are kept while the person has access and afterwards for accountability. An administrator can disable an account at any time.
• Our error logs are kept for the period set by our hosting plan. Your browser's data stays until you clear it.

8. Keeping it safe

Connections use HTTPS. Editing needs a Google sign-in and a place on the access list, which is checked on every change. Sign-in cookies are signed and hidden from page scripts. Secrets and tokens are kept out of our logs. No system is perfectly secure, so please keep personal details out of public itinerary fields and tell us at once if you think something was exposed.

9. Your choices and rights

Where the law gives you rights, such as the Personal Data Protection Act 2010 in Malaysia or similar laws elsewhere, you can ask us to tell you what we hold about you, correct it, or delete it, and you can withdraw consent where we rely on it. Contact us using the details at the end of this page. You can also clear your browser data and sign out at any time.

10. Changes to this notice

When we change this notice in a meaningful way we update the date at the top. Please check back from time to time.