Sipix

This page is a translation provided for information only. Only the French version of these documents is authoritative and prevails in the event of any discrepancy.

Cookie policy

Last updated on 11 November 2026

The Sipix Service uses only cookies and local storage that are strictly necessary for it to work. They are exempt from prior consent under article 5(3) of Directive 2002/58/EC (the ePrivacy Directive) and its French transposition, article 82 of the French Data Protection Act (the “loi Informatique et Libertés”), as clarified by the guidelines of the CNIL, the French data protection authority (deliberation No. 2020-091). As things stand, no consent banner is therefore required.

Cookies used

Session and authentication
keep the Organiser signed in to their dashboard and secure requests (Supabase Auth). Without them, the account could not be accessed. Duration: several months, renewed automatically on each visit, until sign-out or manual deletion from the browser.
Technical preferences
store display settings strictly necessary for a consistent browsing session, including the chosen display language (the “sipix_locale” cookie, kept for twelve months).

Local storage on the guest pages

The guest pages also store, in the browser’s local storage (localStorage), information strictly necessary for the service requested, which is exempt from consent on the same basis:

Verified access code (guest_key_<événement>)
when the Organiser has enabled an access code, this key records on the Guest’s device that the code has been verified, so they do not have to enter it again on every visit. It is specific to the event and stops being valid if the Organiser changes the code.
Resuming an upload
while a photo or video is being uploaded, its progress is stored locally so that an interrupted upload (network drop, page closed) can pick up where it left off. It is erased once the upload is complete.
Reaction identifier (reaction_id_<événement>)
when a Guest adds a “favourite” to a photo or video, a random identifier specific to the event is generated and stored on their device, so that their own reactions can be found again and are not counted twice. It cannot be used to identify the Guest.
Remembered first name (guest_name_<événement>)
if the Guest gives a first name when sending content, it is stored on their device, for that event only, so that it can be suggested the next time they upload. Giving a name is optional.

Bot protection (Cloudflare Turnstile)

When bot protection is active on the organisers’ sign-in and sign-up forms, a component provided by Cloudflare, Inc. (Turnstile) is loaded to tell legitimate visitors apart from automated programs. Verification takes place in the background, with no visible interaction. This component may set technical identifiers strictly necessary for this security purpose, which are exempt from consent under article 82 referred to above. It is not used for advertising or cross-site tracking of any kind. How it works is described in Cloudflare’s privacy policy.

What the Service does not use

The Service uses no advertising cookies and no social media trackers. Its traffic is measured without cookies, through anonymous statistics (Vercel Web Analytics), which are exempt from consent.

Should a tracker requiring consent ever be introduced, a compliant consent banner (where refusing is as easy as accepting) would be put in place and this page updated before any such tracker is set.

Managing cookies

Strictly necessary cookies cannot be disabled without preventing the Service from working. You may nevertheless set your browser to delete or block them. You will then no longer be able to sign in to your account.

Contact

For any question, write to contact@sipix.eu.