Cookie Policy — Plan Trip

Plan Trip does not set its own cookies. The app uses the browser's localStorage — a technology distinct from cookies, never automatically transmitted to remote servers. Third-party cookies may be set by Google exclusively if you choose to enable cloud synchronisation.

1 What are cookies

Cookies are small text files stored in the browser. Unlike localStorage, cookies are automatically sent to the server with every HTTP request and can have an expiry date set by the site.

2 Cookies set by Plan Trip

Plan Trip does not set any first-party cookies.
No cookies are created by the application code.

3 Local storage (localStorage)

Plan Trip uses the browser's localStorage, distinct from cookies: data is never automatically transmitted to remote servers and stays on your device.

plantrip_trips

Trip list

Names and dates of created trips · Persistent

plantrip_data_*

Itinerary data

Cities, accommodations, activities and tips · Persistent

pt-theme

Theme preference

Light / dark · Persistent

pt-lang

Language preference

Italian / English · Persistent

plantrip_cookie_consent

Cookie consent

Records acceptance of this policy · Persistent

plantrip_google_session

Google session (only if connected)

Email, name and OAuth2 access token · Until logout

To delete this data: Developer tools → Application → Local Storage → Clear all.

3b Local storage — Firebase

If you enable real-time collaboration, the Firebase SDK automatically saves the following localStorage keys to manage the authentication session:

firebase:authUser:*

Firebase Auth session

Authenticated user data (UID, email, token) · Until logout

These keys are automatically removed on Firebase logout. You can also manually delete them from the same Local Storage panel in your browser.

4 Third-party cookies — Google

Google scripts are loaded only after your explicit consent, when you click "Accept & sign in" in the app's cookie consent popup. They are not loaded on app startup.

If you choose to sign in with Google Drive or use real-time collaboration, the browser loads the following scripts:

https://accounts.google.com/gsi/client — Google Identity Services
https://apis.google.com/js/api.js — Google API Client
https://www.gstatic.com/firebasejs/* — Firebase SDK (authentication and real-time database)

These scripts may set the following technical cookies:

Cookie	Domain	Type	Purpose	Duration
`SIDSCC`, `__Secure-1PSID`	accounts.google.com	Technical	Google auth session	2 years
`NID`	google.com	Technical	Google user preferences	6 months
`1P_JAR`	google.com	Statistical	Aggregate Google stats	30 days

Exact cookies may vary. Full list: policies.google.com/technologies/cookies

5 Third-party cookies — CARTO

When an interactive map is displayed, the browser contacts CARTO (basemaps.cartocdn.com) for map tiles. CARTO may set technical performance cookies. Details: carto.com/privacy.

6 Managing and disabling cookies

ChromeSettings → Privacy and security → Cookies

FirefoxSettings → Privacy → Cookies and data

SafariPreferences → Privacy → Cookies

EdgeSettings → Cookies and permissions

Blocking third-party cookies may prevent Google Drive synchronisation from working. The app's core features (itineraries, maps) do not require cookies.

7 Consent

Under the ePrivacy Directive and GDPR:

Strictly technical cookies do not require prior consent.
Google scripts are loaded only on explicit user request via the cookie consent popup — not on automatic app loading.
Consent is saved in localStorage (plantrip_cookie_consent) and will not be requested again on future visits.

To revoke: delete the plantrip_cookie_consent key from localStorage or revoke access at myaccount.google.com/permissions.

8 Contact and complaints

For any questions: plan.trip.support@gmail.com

Supervisory authority: you may lodge a complaint with your national data protection authority.