COOKIE POLICY PRIVATE BETA - PUBLICATION COPY Document Code TRP-CK-001 Version 1.0 Effective Date 29 August 2026 Operator Duru Naz Akkaya and Yigit Efe Karabulut - Milan, Italy
This Cookie Policy explains how Tripivor uses cookies and similar technologies on tripivor.com during its private beta. It should be read together with the Tripivor Privacy Policy & GDPR Notice. This Policy applies to the website, account and authentication flows, AI travel-planning interface, saved itineraries and related beta functionality.
1. Who We Are
Tripivor is a pre-incorporation private beta operated jointly by Duru Naz Akkaya and Yigit Efe Karabulut from Milan, Italy. Contact: info@tripivor.com. Website: https://tripivor.com.
2. What Cookies and Similar Technologies Are
Cookies are small text files stored on or accessed from a user device. Similar technologies may include local storage, session storage, software development kits, pixels and comparable identifiers. These technologies may be used to maintain sessions, authenticate users, remember choices, secure the Service, display maps and, where the user has consented, measure use of the beta.
3. Categories Used by Tripivor
3.1. Strictly Necessary Technologies
Tripivor may use strictly necessary technologies to provide functions expressly requested by the user, including account authentication, email/password login, Google Sign-In, session management, security, fraud or abuse prevention, load balancing and storage of privacy choices. These technologies are not used for advertising and, where permitted by applicable law, do not require optional consent because the requested service cannot operate properly without them.
3.2. Analytics Technologies
Tripivor uses Google Analytics to understand how invited beta users interact with the Service, identify technical or usability issues and improve the beta. Analytics may involve device/browser information, page and feature interactions, session information, referral information and approximate network-derived information. Where consent is required, Google Analytics will remain disabled until the user affirmatively accepts analytics technologies.
3.3. Google Sign-In and Google Maps
Tripivor may use Google Sign-In for authentication and Google Maps for mapping and location-display functionality. These services may use or access storage technologies necessary to provide their functionality and may process technical information in accordance with Google's applicable terms and privacy documentation. Tripivor does not use Google Maps to request continuous live GPS access during the current beta.
3.4. Advertising and Profiling
Tripivor does not currently use advertising cookies, cross-site behavioural advertising pixels or third-party advertising profiles as part of the private beta. If this changes, this Policy and the consent interface will be updated before such technologies are activated.
4. Consent and Your Choices
Where required by applicable law, non-essential analytics technologies are disabled by default. The cookie interface must offer a genuine choice to accept analytics, reject optional technologies or manage preferences. Refusing optional analytics does not prevent ordinary use of the Tripivor beta. Users may change or withdraw their optional choices at any time through the Cookie Settings control made available on the website.
5. Current Technology Register
The following is the complete list of cookies and browser-storage technologies actually used by Tripivor. Name / Provider / Purpose / Category / Duration / Party. 1) tripivor_consent - Tripivor (first-party cookie) - stores your cookie choice so the banner is not shown again - strictly necessary - 12 months - first-party. 2) tripivor_language - Tripivor (first-party cookie) - remembers the interface language (EN/TR/IT) - strictly necessary - 6 months - first-party. 3) tripivor_currency - Tripivor (first-party cookie) - remembers your preferred currency - preferences/functional (set only after preference consent) - 6 months - first-party. 4) sb-<project>-auth-token - Supabase (first-party local storage) - keeps you signed in - strictly necessary - until sign-out or token expiry - first-party. 5) postAuthRedirect - Tripivor (first-party session storage) - returns you to the page you were on after sign-in - strictly necessary - session - first-party. 6) tripivor:onboarded - Tripivor (first-party local storage) - records that the quick survey was completed - strictly necessary - persistent until cleared - first-party. 7) tripivor:trip, tripivor:searchPrefill, tripivor:itinerary-plan, tripivor:itinerary-meta - Tripivor (first-party local storage) - working state of the trip you are currently planning so it survives a page refresh - strictly necessary - persistent until replaced or cleared - first-party. 8) tripivor_preferences and tripivor:prefs-draft - Tripivor (first-party local storage) - long-term travel preferences such as travel style, budget level, pace, interests, accommodation type, dietary notes, home city/airport, preferred currency and usual number of travellers - preferences/functional (written only after preference consent) - approximately 6 months - first-party. 9) guideVoiceId and guideLanguage - Tripivor (first-party local storage) - remember the audio-guide voice and language you selected - preferences/functional - approximately 6 months - first-party. 10) sidebar:state - Tripivor (first-party cookie) - remembers whether the sidebar is expanded - strictly necessary interface state - 7 days - first-party. 11) _ga, _gid, _gat - Google Analytics (third-party cookies) - anonymous measurement of beta usage - analytics - up to 24 months - third-party. These are created only after analytics consent is granted; if analytics consent is refused or withdrawn, the Google Analytics script is not loaded and any existing analytics cookies are deleted. 12) Google Maps - Google (third-party) - storage technologies necessary to display maps when a map is loaded - functional/service-related - Google-controlled - third-party. Signed-in users additionally have their long-term travel preferences stored in their Tripivor account database record rather than only in the browser. No fingerprinting, advertising or cross-site tracking technologies are used.
6. Third-Party Travel Websites
When a user follows a link from Tripivor to Booking.com, Skyscanner, Hotels.com, Uber or another independent provider, the destination service may set its own cookies or similar technologies. Those technologies are controlled by the relevant third party and are governed by that third party's own privacy and cookie information. Tripivor does not control cookies placed after the user leaves Tripivor.
7. Changes to this Policy
Tripivor may update this Cookie Policy where technologies, providers, legal requirements or beta functionality change. The effective date at the top of this document identifies the current version. Material changes will be reflected on the website or otherwise communicated where appropriate.
8. Contact
Questions about cookies, tracking or privacy may be sent to info@tripivor.com. Implementation note: the categories above describe the technologies intentionally used for the beta. Tripivor will keep the live cookie configuration aligned with this Policy and will update the register if the production deployment introduces additional storage or tracking technologies.