Fete LabsAll policies

Cookie and Tracking Notice

Every piece of storage FetePass writes on your device, what each one is for, and how to clear it.

Last updated 23 September 2026.

FetePass is in private preview. The software is complete and runs against the real systems it will run against in service — the same database, the same payment rail, the same gate. What is not settled is the company behind it: FetePass is not yet incorporated, holds no money-services licence, and has not taken a real payment. So the registered company name and number, the registered office, the published contact addresses, the fee schedule and some retention periods are marked to be confirmed before launch rather than invented. They will be filled in here, with a new date on this page, before FetePass takes its first real payment.

During the preview: no real money moves — the fiat top-up is switched off in the product, not merely unlinked — and anything you are shown in a demonstration may be reset. Everything on the screen still comes from real data: FetePass does not put invented events, venues, prices or people in front of anyone, so an empty surface is an empty surface rather than a mock-up.

The short version

FetePass sets no advertising cookies and runs no analytics or tracking scripts. Nothing on this page follows you to another site. Everything listed below is storage the app needs to work, kept on your own device — with one thing that has a server side as well, the session described below, which the app cannot work without and which is spelled out rather than buried.

What is stored on your device

Your preferences — fetepass:prefs, in local storage
Your island, colour mode, the role you are viewing as, whether you have pressed past the opening screen, whether identity verification was completed, and the email address you signed in with. This is what makes the app open the way you left it. It never leaves your device on its own — none of it is copied to your account — and signing out clears it.
Your session — fp.auth, in local storage
The token that keeps you signed in, stored by the app on your device. Without it you would be signed out on every page. It is cleared when you sign out.
You get one before you sign in, too. Tapping Guest Mode on the opening screen creates an anonymous account for you on our server and stores its session here. It is strictly necessary rather than a choice we could offer you: our database answers no request that is not attached to some account, so without it the feed and the island tab would be blank. It holds no email address, no phone number and no name you gave us — a placeholder display name and a default island, nothing more — and it becomes your own account if you later sign in. Nothing is stored before that tap — opening the app, following a link straight to a ticket, or reading these notices all leave this entry empty. Clearing this site’s data ends the session on your device; the Privacy Notice covers the row on our side and how to have it deleted.
The offline cache — Cache Storage, written by the service worker
A copy of the app shell, the wallet page and the app’s own script and font files, so the app opens with no signal instead of failing. Nothing from our database is written here, so the pages it restores come back empty until you have a connection. The one exception is a ticket you hold for an event that is running: your phone keeps that ticket’s key while the event is on, so the code can be drawn without a connection. It is a key for that one ticket, it is gone when the event is, and it admits nobody by itself — the gate still checks every code against our servers. Safari clears this kind of storage after seven days without use, and that is fine: nothing here is the only copy of anything.

What is not there

If that changes

If we ever add measurement or advertising, anything that is not strictly necessary will be switched off until you say yes — a real choice, asked before the storage is written, at least for visitors in Guadeloupe, Martinique, Saint-Martin and the EU, where consent is required by law. We would rather ask everyone. What we would use it for, and who would receive it, is to be confirmed before launch because nothing is planned today.

Clearing it

Questions, or something to report

What we do with the data itself, rather than the storage it sits in, is in the Privacy Notice. Everything on this page can also be asked about through Contact.