This notice lists every cookie and browser-storage key our surfaces use. It is deliberately specific, naming keys and lifetimes, because a vague tracking disclosure is worth nothing, and because on ordering pages it is also our best evidence if someone claims we tracked a diner we did not track.
We have five surfaces and they behave very differently. Find yours:
- The ordering pages we host for restaurants, at addresses on order.menunearby.co (for example,
your-restaurant.)order.menunearby.co - The merchant dashboard:
app.tablespring.com - The merchant tablet app
- This marketing website: tablespring.com
- Stripe’s payment form, shown at checkout when a diner pays by card
Across all of them: no advertising or social pixels, no product-analytics service, no session replay, and no error-tracking service.
1. Ordering pages
These are the pages diners order from, at addresses on order.menunearby.co, such as your-restaurant.. This surface sets three cookies, and none of them is for advertising, analytics or tracking: one that lets a page draw your cart before it has read it, one that remembers you joined a restaurant’s list, and one that keeps you signed in to a restaurant’s rewards if you sign in. Everything else is in your browser’s storage. Every key below ends with the restaurant’s name from its address, and is only ever read for that restaurant. On a restaurant’s own address, its cookies reach only that restaurant’s pages. Where several restaurants share one address (a preview, for instance), the cart outline is still sent only with its own restaurant’s pages, while the join and sign-in cookies are sent with every restaurant’s pages on that address and are read only for the restaurant named in the cookie.
| Name | Type | Purpose | Lifetime | Third party? |
|---|---|---|---|---|
ts_hint_ followed by the restaurant’s name | Cookie: SameSite=Lax, readable by scripts (the page’s own script sets it), Secure | The outline of your cart, so the page can draw it before it has read the cart itself: how many lines and items it has, which of the first five carry options or a note, and the pickup time you picked. It holds no dishes, no prices and nothing about you, and only our server reads it, to draw that restaurant’s page. It is sent only with that restaurant’s pages | Seven days after your cart last changed. Deleted when the order is placed, or when the cart is emptied, unless a pickup time is still chosen: then it is kept until that time, and deleted then | No |
ts_join_ followed by the restaurant’s name | Cookie: SameSite=Lax, readable by scripts | Hides the “join” strip on that restaurant’s menu once you have joined its list, or confirmed from one of its emails that you want to stay on it. Holds the word joined and nothing else. It goes with every page request on the address, and is read only for the restaurant in its name | 1 year | No |
ts_rw_ followed by the restaurant’s name | Cookie: HttpOnly, SameSite=Lax, Secure | Keeps you signed in to that restaurant’s rewards after you confirm your phone number. Set only if you sign in. Holds a random, signed session identifier; your phone number is not in it. It goes with every request on the address (the rewards calls included), and is read only for the restaurant in its name | 90 days, or until you close the browser if you said the device is shared; removed when you sign out | No |
ts.cart. followed by the restaurant’s name | localStorage | Your cart for that restaurant: items, options, quantities, and any note you added to an item | Kept until you clear it or place the order; a cart older than 7 days is ignored | No |
ts.when. followed by the restaurant’s name | localStorage | The pickup or delivery time you picked | Removed when you place the order; a time that has passed is ignored | No |
ts.offer. followed by the restaurant’s name | localStorage | A promo code you typed, or the offer from a restaurant email you opened, so it stays on your order | A typed code 24 hours, an email’s offer 30 days; removed when the order is placed | No |
ts.offer.auto-off. followed by the restaurant’s name | localStorage | That you took an automatic offer off this cart, so it is not added back | Removed when the cart is emptied or the order is placed | No |
ts.attr. followed by the restaurant’s name | localStorage | Which of the restaurant’s marketing emails you clicked through from, so the restaurant can see that the email led to an order. It names the email, not you | 5 days | No |
ts.checkoutKey. followed by the restaurant’s name | localStorage | A random one-time key, so pressing Place order twice, or in two tabs, places one order | Removed when the order is placed or the cart is emptied | No |
ts.diner. followed by the restaurant’s name | localStorage | Only if you tick “Save my details on this device”: your name, email, phone number and up to five delivery addresses with their instructions, so the next order is quicker | Until you choose “Not you?” or place an order with the box unticked; an address unused for 12 months is dropped | No |
ts.rewards.row. followed by the restaurant’s name and cart or checkout | localStorage | How tall the rewards row was, in pixels, the last time this device was signed in to that restaurant’s rewards, so the next page holds that room and nothing jumps. Only a height: never a balance, a reward or a phone number | Removed, for both layouts, when you sign out of that restaurant’s rewards on this device or its server reports that the device is no longer signed in; otherwise it stays until you clear site data | No |
ts_rw_skip: followed by a code | localStorage | That you chose “Not now” when an order’s status page asked you to confirm your number for rewards. The code is worked out from the order’s link, not the link itself | Until you clear site data | No |
ts.session | sessionStorage, not a cookie | A random 16-character string attached to five events (menu viewed, item opened, added to cart, checkout started, order placed) so the restaurant can see how many visits became orders | Destroyed when you close the browser tab | No |
ts.item-from-app | sessionStorage | A short-lived mark that you reached an item page from inside the ordering pages, so the Back button returns you to the menu | Used within 30 seconds; gone when the tab closes | No |
ts.delivery. followed by the restaurant’s name | sessionStorage | Delivery or pickup, and for delivery the address, unit and instructions you entered, with our server’s signed confirmation that the address is in the delivery area (which includes its map position) | Gone when the tab closes; the address is removed after the order unless you saved your details | No |
ts.checkout-contact. followed by the restaurant’s name | sessionStorage | The name, email and phone number you are typing at checkout, so a reload does not lose them | Gone when the tab closes or the order is placed | No |
ts.pendingsave. followed by the restaurant’s name | sessionStorage | While a card payment leaves the page for your bank’s check: whether you ticked “Save my details on this device” and, if you did, the details to save | Removed when you come back to the page; gone when the tab closes | No |
That is the complete list.
What is not here
Stated as commitments, not as an accident of the current build:
- No advertising or social pixels. No Meta pixel, no TikTok pixel, no Google Ads tag, no conversion tags of any kind.
- No session replay, heatmapping, or keystroke capture. Nothing records what you type, where you move your mouse, or how you scroll.
- No third-party tag manager, so no third party can be added to this page without a code change that goes through review.
- No chat widget that forwards what you type to a third party.
- No cross-site tracking, no fingerprinting, no advertising identifiers, no precise geolocation.
- No product analytics vendor. The five events above go to our own database and nowhere else.
Why ts.session cannot identify you
- It lives in
sessionStorage, which is scoped to a single tab and cleared when that tab closes. It is not a cookie and is never sent as a request header. - It is randomly generated. It is not derived from your IP address, device, browser, screen, fonts, or anything you typed.
- It cannot be linked to a later visit, to another tab, or to another restaurant’s ordering page. When you place an order, the “order placed” event stores the session string next to the order’s identifier so the restaurant can count the visit as a sale. The event holds no name or contact details.
- Analytics event payloads accept only item and menu identifiers, capped in size on the server. Free text is rejected, so nothing you type can end up in an analytics record.
- If your browser blocks storage (private browsing, for instance), the identifier is simply not created and analytics is skipped. Ordering still works. Analytics is the first thing we give up.
During checkout
Placing an order is a normal web request, so your browser sends your IP address, which our server uses transiently for rate limiting and abuse prevention and does not store as part of the order. Our hosting and database providers may keep ordinary request logs.
If you pay by card, Stripe’s payment form is a third-party component. See §5.
A restaurant’s email sign-up page and our contact form run Cloudflare Turnstile, a bot check that receives your IP address and browser signals to tell people from automated submissions. Cloudflare is a third party and controls what it stores.
2. Merchant dashboard: app.tablespring.com
Signing in requires cookies. The first two are strictly necessary; the dashboard cannot function without them. The rest are preferences.
| Name | Type | Purpose | Lifetime | Third party? |
|---|---|---|---|---|
sb-*-auth-token (and its numbered parts) | Cookie: HttpOnly, SameSite=Lax, Secure | Keeps you signed in | Session, or 30 days if you check “keep me signed in” | Set on our domain by our authentication provider’s library |
ts-persist | Cookie: HttpOnly, SameSite=Lax, Secure | Records whether you chose “keep me signed in”, so a token refresh does not silently extend a session you wanted to be temporary. Contains no secret and no personal data | Session, or 30 days if you chose to stay signed in | No |
ts_restaurant | Cookie: SameSite=Lax, readable by scripts | Which of your locations you were last working in. Contains the location’s identifier | 1 year | No |
ts_sidebar_collapsed | Cookie: SameSite=Lax, readable by scripts | Whether you collapsed the side navigation | 1 year | No |
ts_orders_sound | localStorage | Whether this browser has been armed to play the new-order alert sound. It is per device, not per account | Until you change it or clear site data | No |
tablespring.menu.view | localStorage | Whether you prefer the card or table view of the menu manager | Until you change it or clear site data | No |
tablespring:setup-draft: followed by your user ID | sessionStorage | Keeps an unfinished restaurant setup form while you move between setup steps. May hold the restaurant details you typed or picked from Google (name, address, phone, hours, website, price range, timezone, Place ID) | Destroyed when you close the browser tab | No |
The sign-in cookies are HttpOnly. The dashboard talks to the database only from the server, so session tokens are never readable by scripts on the page: a cross-site scripting bug could not steal your session.
Signing out clears the sign-in cookies and revokes the session on the server.
The sign-in (by password or by emailed link), sign-up, password reset, invitation and resend-email screens, and our contact form, also run Cloudflare Turnstile, a bot check, loaded from challenges.cloudflare.com. Cloudflare is a third party: it receives your IP address and browser signals to decide whether the request is automated, and controls anything the check stores in your browser. We cannot read it and have not listed names here. The check returns a single-use token. On the sign-in and account screens we pass it to our authentication provider; on the contact form it goes to our own server, which asks Cloudflare to confirm it.
3. Merchant tablet app
The tablet app (iOS and Android) sets no cookies of its own. All of its screens are native; it does not show the dashboard in an embedded web view. Its one web view is the bot check on the sign-in screen, described below. It stores the following on the device.
| Name | Where | Purpose | Lifetime |
|---|---|---|---|
Sign-in session: sb-*-auth-token, and the sign-in keys that go with it (-user, -code-verifier, -flows-code-verifier) | Device secure keychain (the iOS Keychain or Android Keystore), on this device only: not in backups and not copied to a new device | Keeps the tablet signed in | Until you sign out, or the tablet’s access is revoked by an owner. Reinstalling the app starts signed out |
ts.deviceId | Device secure keychain | A random identifier for this tablet, shown to owners under Settings so they can revoke it | Kept across app updates; replaced if the tablet is revoked and signs in again |
ts.restaurant | App storage | The location this tablet is set up for, and who set it up | Until it is changed or cleared in the app, or you remove the app |
ts.deviceName | App storage | The tablet’s name | Until you change it or remove the app |
ts.soundOn | App storage | Whether the new-order alert sound is on | Until you change it |
ts.lastEta. followed by a location’s identifier | App storage | The “ready in” time last chosen when accepting an order at that location on this tablet, so the next accept starts on it | Until you choose another or remove the app |
ts.installed | App storage | A flag that this install has already cleared any sign-in an earlier install left in the keychain, so a reinstall starts signed out | Until you remove the app |
ts.keychainV2 and ts.deviceId.parked | App storage | Used once, when the tablet’s identifier is moved into the keychain with this device-only setting: a flag that it was, and the identifier held here for the moment between removing the old item and adding the new one | The flag until you remove the app; the held identifier is deleted as soon as the move completes |
ts.signOutQueue | Device secure keychain | A sign-out that could not reach the server yet, retried when the tablet is back online. It holds a sign-in credential until the sign-out completes | Until the sign-out completes |
ts.printLedger | App storage | What this tablet has already printed, so a restart does not print a ticket twice | Until the app is removed |
The app also tells our server the tablet’s name, platform, app version, its random device identifier (ts.deviceId above), and when it was last seen. Signing in to the app loads the same Cloudflare Turnstile bot check, in a small web view that shares no cookies with the rest of the app, as described in §2. It asks for local-network access so it can find receipt printers, and uses Bluetooth or USB for printers connected that way. It does not use location, the camera, or the microphone.
4. Marketing website: tablespring.com
| Name | Type | Purpose | Lifetime | Third party? |
|---|---|---|---|---|
ts-migration-banner-dismissed | localStorage | Remembers that you closed the notice banner so it does not return | Until you clear site data | No |
ts-contact-draft | sessionStorage | What you typed in the contact form (name, email, restaurant, topic and message), copied when you press send so it can be put back if sending fails | Removed as soon as the message is sent; otherwise gone when the tab closes | No |
This site sets no cookies and loads no analytics or advertising scripts. Fonts are served from our own domain.
If we ever add retargeting or analytics to the marketing site, this notice will be updated first, a consent banner will be added for the jurisdictions that require one, and the ordering pages in §1 will remain untouched.
5. Stripe’s payment form
When a diner chooses to pay by card, the ordering page loads Stripe’s payment form from js.stripe.com. Stripe is a third party and controls what that form stores. Stripe may set cookies and similar identifiers on the diner’s browser, which it describes as being for fraud prevention and to process the payment. We cannot read them and we have not listed names here because they are Stripe’s to define. Stripe’s cookie policy is at stripe.com/cookies-policy/legal.
Stripe’s form loads only when a card payment is chosen. Paying cash does not load it.
6. Global Privacy Control and Do Not Track
We do not sell personal information or share it for cross-context behavioral advertising, and our sites run no advertising or analytics scripts, so there is nothing for a Global Privacy Control signal to stop. We treat the signal as a valid request to opt out of sale and sharing, which we do not do in any case. We do not respond to the older, unstandardized “Do Not Track” browser header, because there is no agreed meaning for it.
7. How to control this yourself
- Ordering pages: close the tab and the session identifier is gone. Clear site data to remove the cart, its outline cookie and anything you saved. Private browsing prevents the identifier being created at all.
- All surfaces: your browser can block or delete cookies and site storage (see its privacy settings). Blocking cookies on the dashboard will sign you out and keep you out; blocking storage on ordering pages costs you your saved cart, and blocking cookies there costs a cart that is drawn a moment later and a rewards sign-in, not your ability to order.
- Tablet app: signing out ends the session and clears it from the keychain; reinstalling the app always starts signed out. Removing the app removes what it kept in its own storage.
8. Changes
We will update this notice whenever a cookie or tracker is added, removed, or changes purpose. Because this notice is also the disclosure our diner-facing legal position rests on, adding any third-party script to an ordering page requires updating §1 first; that is an internal rule as well as a promise here.
- Questions
- privacy@tablespring.com