TravelSync — Cookie Policy

1.What cookies are and who sets them

1.1Cookies are small files stored on your device by a website; similar technologies such as browser local storage do a similar job. This policy explains which we use on travelsync.cloud, why, and how you control them. Forvosync Ltd, trading as TravelSync (company no. 16960226, registered office 167-169 Great Portland Street, 5th Floor, London W1W 5PF, United Kingdom) is responsible for this site. Privacy questions: privacy@travelsync.cloud.

1.2Under the Privacy and Electronic Communications Regulations 2003 (PECR) we need your consent before storing or reading anything on your device, except where it is strictly necessary to provide a service you have asked for. Our Privacy Notice explains how we use any personal data collected through cookies.

2.The cookies we use

Category A — Strictly necessary (no consent needed). These make the Service work: keeping you logged in after you sign in and remembering your cookie choice. Disabling them breaks the Service.

Category B — Analytics (only with your consent). We use PostHog (EU Cloud, hosted in Frankfurt) to understand how the beta is used: which pages and features are used, where people get stuck, and errors. Data is pseudonymised (a random ID, not your email) and never sold or used for advertising. Analytics cookies are off until you click "Accept analytics" in the banner. [DECISION: see Privacy Notice 5.3. Option B (PostHog in cookieless mode) stores nothing on the device, so PECR consent is not needed — but analytics can never be classed as "strictly necessary", so the implementation must be genuinely storage-free.]

Nothing in this category is stored before you accept analytics. Your choice itself is kept in ts_consent (above); if you later switch analytics off, the PostHog cookie and storage entries are deleted and no further analytics requests are made.

Category C — Marketing / advertising. None in the beta. We do not use advertising or social-media tracking cookies. If we introduce affiliate links to booking partners after the beta, clicking a link takes you to the partner's site, which may set its own cookies under its own policy; we will update this policy first.

Third-party content — Google Maps. The map on a saved trip page is drawn by Google's Maps JavaScript API. Its script is loaded from Google's servers only when you open a saved trip page, never on other pages. When it loads, Google receives your IP address and browser details and may set its own cookies or read device information under Google's privacy policy (policies.google.com/privacy). Place details for your itinerary are looked up on our servers (Places API), so browsing your itinerary without the map involves no Google cookies. The map also loads its font from Google Fonts (fonts.googleapis.com, fonts.gstatic.com) on trip pages only. In our tests no Google cookies were set on this site; if your browser allows third-party cookies, Google may set its own (for example NID) under its cookie policy. [DECISION: the map currently loads without a consent gate as part of the service you asked for (a map of your trip); counsel to confirm whether Google should be listed as strictly necessary on that basis or the map shown only after consent.]

3.How we ask for consent

3.1On your first visit a banner offers two equally prominent buttons: "Accept analytics" and "Reject analytics" (and a link to this policy). No analytics cookie is set until you choose. Closing the banner without choosing, scrolling or continuing to browse is not treated as consent. Your choice is stored in your browser's local storage (ts_consent) for 12 months; after that we ask again. Strictly necessary cookies are set regardless, and the banner says so.

3.2We keep a record of consent (timestamp, choice, policy version) so we can show what you agreed to.

4.How to change your mind or withdraw consent

4.1You can withdraw or change your consent at any time, as easily as you gave it: click "Cookie settings" in the site footer (or Account → Privacy) and switch analytics off. We will stop collecting analytics immediately and delete the analytics cookies; data already collected is handled as described in the Privacy Notice.

4.2You can also block or delete cookies in your browser settings (see your browser's help pages, e.g. Chrome, Safari, Firefox, Edge). Blocking strictly necessary cookies will stop you logging in. Guidance on managing cookies: ico.org.uk/for-the-public/online/cookies.

5.Changes

5.1We will update this policy when the cookies we use change and will ask for consent again if we add a new non-essential category. The effective date at the top shows the current version.