Cookies

We set only the cookies the service needs in order to work, and nothing that tracks you across sites. There are no analytics, advertising or social-media cookies on this website, in the app or on delegates’ phones. Because every cookie below is strictly necessary, we do not ask for consent and do not show a cookie banner.

People who run events (staff)

• Sign-in (a cookie beginning sb- and ending -auth-token, or -auth-token.0, -auth-token.1 and so on when the session is too long for one cookie): keeps you signed in after you use the link we emailed you, for up to 400 days (the sign-in library’s own default) or until you sign out.
• A sign-in link on its way (cookies beginning sb- and ending -code-verifier, -flow- followed by a code and -code-verifier, or -flows-code-verifier): the sign-in library sets them when you ask for a link, so that the link only works in the browser that asked for it. They carry the library’s same 400-day limit. The library removes the first when the link is used, and all of them when you sign out.
• Where to go after sign-in (sy_next): remembers, for thirty minutes, that you came from an invitation, so you land back on it.

Delegates (people who join a session)

• Session identity (sy_ followed by the session’s code): a random code that tells the service which phone is which, so an answer counts once and a phone can carry on after a refresh. It lasts three days.
• Feedback form identity (sy_sv_ followed by the form’s code): the same for a feedback form, so it can be resumed and answered once. It lasts sixty days.
• The phone’s browser storage remembers what that delegate has already answered or asked in the session, so a refresh does not forget it. It stays on the phone and can be cleared in the browser.

Delegates can delete their answers from the “Privacy and your data” link on every session page. Our privacy policy says more about what we keep.