Skip to content
Say Cheese

Last updated 30 July 2026

Cookie policy

TechKnowlogy Consulting Ltd · SC-COOK-001 · v1.0

Say Cheese uses four cookies. All four are strictly necessary to make the service work and to keep it secure. We do not use advertising cookies, we do not use tracking cookies, and we do not run third-party analytics. That is why you are not asked to accept cookies when you arrive.

1 About This Policy

This policy explains the cookies and similar technologies we use across the Say Cheese website, host dashboard, guest upload experience and live screen. Read it alongside our Privacy Policy (SC-PRIV-001).

  • Published by: TechKnowlogy Consulting Ltd, trading as Say Cheese, company number 15308472
  • Contact: [email protected]
  • Version: 1.0 · effective 30 July 2026

2 What Cookies Are

A cookie is a small text file a website asks your browser to store and send back on the next request. It is how a site remembers that you are signed in, or that you have entered an event code. Cookies set by another company, usually to follow you between sites, are third-party cookies. We use none of those.

3 The Cookies We Use

All four use HttpOnly where the browser need not read them, SameSite=Lax so another site cannot use them, and Secure in production so they travel only over an encrypted connection.

3 The Cookies We Use
NameWho gets itWhat it doesHow long it lasts
sc_sessionEvent HostsKeeps you signed in. Holds a random token only, never your name, email or password. Revocable from your account at any time.Until you sign out or the session expires
csrf_tokenEvent HostsProtects against cross-site request forgery, where another site tries to act on your behalf while you are signed in. Checked against a matching header on every change you make.The browser session
sc_guest_entryGuestsSet once you enter the correct event access code. Records, in encrypted form, which event you were admitted to, so later screens do not ask again.20 minutes
sc_guestGuestsYour guest session for one event. Lets you upload, see the gallery and return later without entering the code again. Holds a random token only, tied to a single event.Ends with the event, and in any case within 30 days

4 Why You Are Not Asked To Accept Cookies

UK law requires consent for cookies except where they are strictly necessary for the service you asked for. All four of ours are in that category: without them you could not sign in, could not stay in an event after entering the code, and would lose protection against a known class of attack. There is nothing optional to consent to.

If we ever add an optional cookie, for analytics or anything else, we will ask for your consent before setting it and update this policy.

5 Device Recognition

As well as cookies we use a technique called device recognition on the guest entry screen. An open-source library reads characteristics your browser already exposes, such as screen size, installed fonts and how your device draws graphics, and combines them into an identifier for that browser.

We use it for one purpose: enforcing bans. If an Event Host bans someone for abusive uploads, that person can clear their cookies and come straight back. The device identifier lets the safety check recognise them and keep them out. It is checked before the event access code is verified, so a banned person never gets in.

  • The library runs entirely in your browser. Nothing is sent to the company that publishes it, and we do not use its commercial service.
  • The identifier is sent only to our own servers, and only as part of entering an event.
  • We do not use it for advertising, profiling or tracking you across other websites.
  • If it fails to run, for example because you use an ad blocker or privacy browser, you are not penalised. You can still join the event normally.
  • It is stored against the event's safety records and deleted when no longer needed to protect events from repeat abuse.

6 What We Do Not Use

  • No advertising or retargeting cookies
  • No third-party analytics such as Google Analytics
  • No social media tracking pixels
  • No cross-site tracking of any kind
  • No sale or sharing of any identifier with data brokers

7 Managing Cookies

You can delete cookies or block them entirely in your browser settings, usually under Privacy or Site Settings. Because ours are strictly necessary, blocking them has consequences: you will not be able to sign in as a host, and as a guest you will be asked for the event code repeatedly and may be unable to upload.

Clearing your cookies signs you out and ends your guest session. It does not delete photographs you have already uploaded. To have those removed, contact us or the Event Host as described in our Privacy Policy.

8 Changes And Contact

We will update this policy if we add or remove a cookie, or change what an existing one does. The version number and effective date are shown in section 1.

  • Questions about this policy: [email protected]
  • Postal address: TechKnowlogy Consulting Ltd, 4 Moonshine Way, Stevenage, Hertfordshire
  • Related documents: Privacy Policy (SC-PRIV-001) and Terms & Conditions (SC-TC-001), both at www.say-cheese.io
  • Complaints: Information Commissioner's Office · 0303 123 1113 · www.ico.org.uk