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

Cookie policy

Last updated: 1 August 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 loi “Informatique et Libertés”, as clarified by the guidelines of the CNIL, the French data protection authority (délibération n° 2020-091). No consent banner is therefore required as things stand.

Cookies used

Session and authentication: keep the Organiser signed in to their dashboard and secure requests (Supabase Auth). Without them, access to the account would be impossible. 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 browsing continuity, 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, 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.
Upload resume: while a photo or video is being uploaded, its progress is stored locally so that an interrupted upload (network drop, page closed) can resume 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 does not make it possible to identify the Guest.
Remembered first name (guest_name_<événement>): if the Guest enters a first name when sending content, it is stored on their device so it can be suggested for a later upload, specific to the event. It is not compulsory.

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 in order to distinguish legitimate visitors 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, exempt from consent under article 82 referred to above; it is not used for any advertising or cross-site tracking purpose. How it works is described in Cloudflare’s privacy policy.

What the Service does not use

The Service uses no advertising cookies, no social media trackers and no third-party audience measurement tools.

Should an audience measurement tool or a non-exempt tracker ever be introduced, a compliant consent banner (with refusal as easy as acceptance) would be put in place and this page updated before anything is set.

Managing cookies

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

Contact

For any question: contact@sipix.eu.