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: 5 September 2026
1. The short version
We use cookies to keep you signed in. 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 |
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 |
Both are first-party, strictly necessary cookies. Neither tells us anything about you beyond the fact that you are signed in.
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. Third parties that may set their own
Listing pages show a map. The map is served by Google Maps, and loading it contacts Google, which can set its own cookies or similar identifiers in your browser under Google’s own terms. We do not control those, we do not receive their contents, and we get no advertising benefit from them.
If you would rather not load Google’s map, you can block third-party cookies for google.com in your browser, or use an extension that blocks the embed. The rest of the listing page works without it.
Payment happens on Paystack’s own checkout, which sets the cookies it needs to process your payment securely. Those are governed by Paystack’s privacy notice.
5. 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.
6. 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.
7. 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.