Cookie Policy
Every cookie we set, what it does, and how long it lasts. There are not many, and none of them are for advertising.
Last updated: 7 November 2026
1. The short version
We use cookies to keep you signed in, and to let you back into a trip page that has an access code. That is the whole of it. We do not run advertising cookies, we do not use tracking pixels, and we do not share cookie data with data brokers or ad networks.
Because our own cookies are strictly necessary to provide a service you asked for, UK and EU law does not require us to ask your permission for them, and we do not show you a consent banner for something you cannot meaningfully refuse. If that changes — if we ever add analytics or marketing cookies — we will ask first, and this page will say so.
2. What a cookie is
A cookie is a small file a website asks your browser to store, and which your browser sends back on the next request. It is how a site remembers that the person loading this page is the person who signed in a minute ago. Some cookies vanish when you close the browser; others last a set period.
3. The cookies we set
| Cookie | What it does | How long | Can you refuse it? |
|---|---|---|---|
sb-<project>-auth-token | Holds your signed-in session, issued by Supabase, our authentication provider. Split across several numbered cookies when the session is large. | Until it expires or you sign out | Not while staying signed in — this cookie is the sign-in |
y3_trip_page_<address> | Set only when you enter the access code for someone's published trip page, so you are not asked for it again. Only sent back to that one trip page. | 30 days | Yes — without it you type the code each visit |
sb-<project>-auth-token-code-verifier | A short-lived value used to complete a secure sign-in or password reset. Deleted as soon as the sign-in finishes. | Minutes | No — without it, sign-in cannot be completed securely |
All of these are first-party, strictly necessary cookies. None of them tells us anything about you beyond the fact that you are signed in or have entered a trip page’s code.
We also rely on a short-lived record, keyed on your IP address, to rate-limit sign-up and contact forms against automated abuse. That is not a cookie — nothing is stored on your device — but we mention it here because people reasonably ask about it. It is covered in the Privacy Policy.
4. What we keep in your browser
A few things are saved in your own browser’s storage rather than in a cookie. They are never sent to us on their own, and clearing your browser’s site data removes them.
| What | Why | How long |
|---|---|---|
| A trip you start before signing in | So your plan is still there when you sign in to save it | Until you save it or clear it |
| Phrases you save on the Translate page | So your phrasebook is there next time | Until you remove them |
| Whether you collapsed the dashboard sidebar | A display preference | Until you change it |
| A half-finished business application, or a plan being built | So you do not lose your place if the page reloads | Until you close the tab |
5. Third parties that may set their own
Maps on Y3NKO are Google Maps: listing pages, the browse maps and the map hosts use to pin their place. Opening a page with a map loads it from Google, which sees your IP address and which part of the map you look at, and may set or read its own cookies under Google’s privacy policy, especially if you are signed in to a Google account in the same browser. Pages without a map load nothing from Google.
The “Get directions” and “Open in Google Maps” buttons are ordinary links that take you to Google Maps itself, where Google’s own terms apply.
If you sign in with Google or Apple, you go to their sign-in page, which sets its own cookies under their privacy notices. When online booking opens, payment will happen on Paystack’s own checkout, which sets the cookies it needs under Paystack’s privacy notice.
6. What we do not do
- No advertising or retargeting cookies.
- No social media tracking pixels.
- No cross-site behavioural profiling.
- No selling or sharing of cookie data with anyone.
- No analytics cookies. We do count page views and how pages are used (clicks, scrolling, load speed), using PostHog, but it runs without cookies, writes nothing to your browser's storage, and has no identifier that follows you between visits. That is why this page has nothing to ask your permission for.
7. Controlling cookies yourself
Every browser lets you see the cookies a site has set, delete them, and block future ones. It is usually under Settings, then Privacy.
If you block or delete our authentication cookies you will be signed out and will not be able to sign back in until you allow them again. Browsing listings without an account works fine either way.
8. Changes, and questions
If we add a cookie, this page changes before the cookie ships, and the date at the top moves. If the new cookie is not strictly necessary, we will ask for your consent first.
Questions: contact@y3nko.travel.
Who you are dealing with
Y3NKO is a trading name. The operating company is being registered in Ghana. We will publish the registered name, company number and registered office here as soon as registration completes, and we will tell existing account holders by email when we do.
Until then, contact us at contact@y3nko.travel. We operate from Accra, Ghana.