Cookie policy
Short version: TableSpark uses essential browser storage to keep the site working and remember your cookie choices. Optional analytics and marketing storage stay off unless you allow them.
How we use browser storage
TableSpark does not currently load advertising pixels or third-party tracking cookies on the public marketing site. We do use first-party browser storage such as localStorage and sessionStorage for essential preferences, sign-in, optional Journal reading analytics and optional first-party attribution from a Journal call-to-action to signup progress.
Under UK cookie rules, browser storage can still count as storing information on your device. That is why non-essential analytics and marketing storage are off by default and controlled through Cookie Preferences.
What we store on tablespark.uk
| Item | Type | What it does | Category |
|---|---|---|---|
sb-…-auth-token | localStorage | Keeps you signed in to your TableSpark account (your session token). Only set once you sign in; removed on sign-out. | Strictly necessary |
ts_site | localStorage | Remembers which of your restaurant sites you last had open in the dashboard. | Preference |
tablespark_cookie_consent_v1 | localStorage | Records your Cookie Preferences choice, including whether analytics or marketing storage is allowed. | Strictly necessary |
tablespark_journal_visitor_journey_v1:… | sessionStorage | After the relevant consent, holds a random ID scoped to one Journal article context. Reading events use Analytics consent; call-to-action events use Marketing consent. It expires after 24 hours at the latest and is also removed when the relevant consent is withdrawn. | Analytics / Marketing |
tablespark_journal_signup_pending_v1 | localStorage | After Marketing consent and an accepted signup request, temporarily joins that Journal call-to-action to signup completion. It expires after 7 days, is removed after a recorded completion, and is removed when Marketing consent is withdrawn. | Marketing |
Visitors who never sign in may still have their cookie preference stored, so we do not ask the same question on every visit.
For consented Journal measurement, the server receives only an allowlisted signed article/CTA context and a one-way SHA-256 hash of the random journey ID. It does not store the raw journey ID, signed token, email, name, phone, referrer or IP address in the attribution table. These first-party attribution events follow the same 14-month retention limit as our analytics events.
What restaurant sites we host store
| Item | Type | What it does | Category |
|---|---|---|---|
ts_consent | localStorage | Records your Accept / Decline choice on a restaurant's cookie notice, so you aren't asked again. Declining switches the visit counter off. | Strictly necessary |
ts_sid | localStorage | A random identifier for the restaurant's own first-party visit counter (page views, tap-to-call, direction and booking clicks), created only after you accept the site's cookie notice. No IP address, no location, no cross-site tracking. | Analytics |
| Announcement dismissal | sessionStorage | Keeps a dismissed announcement banner closed. Gone when you close the tab. | Preference |
Third-party content
Loading any web page sends your IP address to the servers that deliver it — for our pages that includes our host (Cloudflare) and the font services we use (Google Fonts and Fontshare). None of these set cookies through our pages.
Some restaurant sites choose to embed outside content: a Google map, a YouTube or Vimeo video, an Instagram feed, or an external booking widget. Those providers may set their own cookies once their content loads. We are rolling out click-to-load across all such embeds on hosted restaurant sites, so nothing from a third party loads until you choose to load it — your choice is remembered per site via the consent flag above.
Restaurants can also add photos from Pexels' free library; your browser fetches those images from Pexels' servers like any other image, with no cookies involved.
Withdrawing consent
- On tablespark.uk: use to change your choice at any time.
- On a restaurant site: if you accepted the site's notice and change your mind, clear the site's data in your browser (usually under Settings → Privacy → Site data) — that removes
ts_consentandts_sid, and the notice will ask you again next visit, where you can decline. - Click-to-load embeds: the same site-data reset withdraws your choice to load third-party content.
Anything unclear, or want us to walk you through it? Email hello@tablespark.uk. For how we handle personal data more broadly, see our privacy policy.
The storage described on this page is set by TableSpark Ltd, a company registered in England and Wales under company number 17384916, registered office Studio 9, 50–54 St Paul's Square, Birmingham, England, B3 1QS.