Travyxo — Cookie Policy
Effective date: {{EFFECTIVE_DATE}} Last updated: {{LAST_UPDATED_DATE}} Version: 1.0-draft
Plain-English summary. Travyxo uses a small number of cookies that are strictly necessary to sign you in, keep you signed in, and keep the Service secure, plus one functional cookie for your theme preference. We do not use analytics or advertising cookies. This policy explains what types of cookies we use, why, and how to manage them.
Status. This is a draft pending legal review.
1. What cookies are
Cookies are small text files placed on your device when you visit a website. Similar technologies — such as browser local storage — work in comparable ways and are covered by this policy where relevant.
2. How we use cookies on Travyxo
Travyxo uses cookies (and a small amount of local storage) for two purposes:
- Strictly necessary — to sign you in, keep you signed in, route requests correctly, and keep the Service secure.
- Functional — to remember your dark / light theme preference.
Travyxo does not use analytics, advertising, or cross-site tracking cookies. If that ever changes, we will update this policy and obtain your consent before setting any non-essential cookie (in regions where consent is required).
3. Cookies we use
The tables below describe the cookies and similar technologies set on the Travyxo marketing site, the Travyxo app, and where applicable on third-party domains you may interact with as part of using the Service.
3.1 Strictly necessary
| Cookie / Technology | Provider | Purpose | Duration | Type |
|---|---|---|---|---|
| Authentication session cookies | Clerk | Sign you in, maintain your active session, synchronise your session across browser tabs, and handle token refresh. For the full list of cookies Clerk sets, see Clerk's privacy notice. | Session to ~1 year | 1st-party, HttpOnly |
| Client Portal session cookie | Travyxo | Links your browser to an authenticated Client Portal session for users of the /portal area. Set on login and cleared on logout. |
30 days | 1st-party, HttpOnly, Secure, SameSite=Lax |
| Application routing cookies | Vercel | Manage request routing and, where applicable, preview-environment access. Set by our hosting provider. | Session to 1 year | 1st-party |
| CDN security cookies | Cloudflare | Security checks and load balancing for asset delivery. Set by our CDN provider on the asset-delivery domain. | Up to 30 days | 3rd-party (on asset domain) |
| Checkout session cookies | Stripe | Required for the Checkout payment session. Only set when a Customer initiates a subscription checkout. | Session | 3rd-party (on checkout.stripe.com) |
These cookies do not require consent under the GDPR (Recital 30) or the UK PECR exemption for cookies "strictly necessary" for a service that the user has requested. Disabling them will prevent the Service from working.
3.2 Functional
| Cookie / Technology | Provider | Purpose | Duration | Type |
|---|---|---|---|---|
| Theme preference cookie | Travyxo | Remembers your chosen dark, light, or system colour scheme so it is applied on your next visit. | 1 year | 1st-party, SameSite=Lax, Secure |
| Interface preference (local storage) | Travyxo | Remembers which section of the package builder you were last using, so you return to the same view on your next visit. Stored in browser local storage — not a traditional cookie, but subject to the same principles. | Persistent (until cleared) | 1st-party local storage |
Functional cookies are not strictly necessary, but they improve the experience by remembering preferences. Where consent is required in your region, we ask for it before setting these.
3.3 Analytics
Travyxo does not currently use analytics cookies. If we add an analytics tool, we will update this section, list the cookies involved, and obtain your consent in regions where consent is required.
3.4 Marketing / Advertising
Travyxo does not currently use marketing or advertising cookies, and we do not engage in cross-site behavioural tracking. If that changes, we will update this section and obtain consent in regions where consent is required.
4. Third-party cookies
Some cookies are set by third parties when you interact with their features through Travyxo. The relevant providers and links to their policies are:
- Clerk (authentication) — see Clerk's cookie and privacy notices at https://clerk.com/legal/privacy.
- Stripe (payments, only when you enter the checkout flow) — see https://stripe.com/cookie-settings.
- Cloudflare (asset delivery) — see https://www.cloudflare.com/cookie-policy/.
- Google Maps Platform (geocoding and mapping, where embedded) — see https://policies.google.com/privacy.
- Vercel (hosting; routing and preview-environment cookies) — see https://vercel.com/legal/privacy-policy.
If any of these providers changes the cookies they set, we will reflect the change in §3 within a reasonable time.
5. How to manage cookies
You can control cookies through your browser settings:
- Chrome: https://support.google.com/chrome/answer/95647
- Firefox: https://support.mozilla.org/kb/cookies-information-websites-store-on-your-computer
- Safari (macOS): https://support.apple.com/guide/safari/manage-cookies-sfri11471/mac
- Edge: https://support.microsoft.com/microsoft-edge/delete-cookies-in-microsoft-edge-63947406-40ac-c3b8-57b9-2a946a29ae09
If Travyxo provides an in-app cookie banner or preferences centre, you can change your choices for non-essential cookies there.
Disabling strictly necessary cookies will prevent core features from working — most importantly, you will not be able to sign in.
6. Consent
In the EEA and the UK, strictly necessary cookies are exempt from consent. Before non-essential cookies are set in those regions, Travyxo will present an in-app consent mechanism through which you can accept or reject functional, analytics, or advertising cookies. Where the consent mechanism is not yet available at the time you visit, Travyxo limits its use of non-essential cookies in the EEA / UK accordingly. You will be able to withdraw consent at any time through your browser settings or, once available, through the in-app cookie preferences.
In other regions, your local law applies. Many regions follow an "opt-out" model — if that is true for you, you can opt out through your browser settings or via the controls described in §5.
7. Changes to this policy
We may update this policy, for example when we add or remove a cookie or when a third-party provider changes its cookies. Material changes will be notified in-app and (for Customers) by email to the contact on file. The "Last updated" date at the top reflects the most recent revision.
8. Contact
If you have any questions about cookies or this policy, email {{PRIVACY_EMAIL}}.