Legal
Privacy policy
TableSpark builds and hosts websites for restaurants. This policy explains what personal data we handle, why, who we share it with, how long we keep it, and the rights you have — whether you run a restaurant on TableSpark or you're a guest of one.
In short
- We run the platform; each restaurant controls its own guests' data, and we handle it only on their instructions.
- We never sell guest data, never use it for advertising, and never contact guests ourselves.
- Card numbers never reach us — Stripe processes every payment.
- You can ask for a copy or deletion of your data at any time.
1Who we are
TableSpark Ltd ("TableSpark", "we", "us") operates tablespark.uk, a website builder and hosting platform for restaurants. We are a company registered in England and Wales under company number 17384916, with our registered office at Studio 9, 50–54 St Paul's Square, Birmingham, England, B3 1QS. We are registered with the Information Commissioner's Office (ICO) as a data controller, registration number ZC301646. Restaurant websites built with TableSpark are published at addresses like yourname.tablespark.uk or on the restaurant's own domain, but they run on our infrastructure.
That means we wear two hats, and this policy covers both:
- For our customers (restaurant owners and their teams) we are the data controller: we decide how account data is used to provide the service.
- For guests of those restaurants (people who book a table, place an order, send an enquiry or join a mailing list on a restaurant's site) we are a data processor: we store and handle that data strictly on the restaurant's behalf and instructions. The restaurant is the controller — contact them first about data you gave them; we'll help them honour any request. For online orders we store the details you give with the order (name, phone number, optional email, your dishes and any notes) so the restaurant can prepare and confirm it; order contact details are anonymised automatically after 24 months. When you pay online, your card payment is processed by Stripe directly for the restaurant's own Stripe account — TableSpark never receives or stores your card number, only whether the order was paid and a payment reference.
For anything in this policy, you can reach us at hello@tablespark.uk, or write to TableSpark Ltd, Studio 9, 50–54 St Paul's Square, Birmingham, England, B3 1QS.
2What we collect from platform customers
Account data
When you create a TableSpark account we store your email address and, if you provide them, your name and phone number. Sign-in is handled by our authentication provider (Supabase); passwords are stored only as secure hashes and are never visible to us. Account and transactional emails (sign-in confirmations, password resets, team invites) are delivered through Resend, our email provider.
Your restaurant's content
Everything you put into the builder — menus, photos, opening hours, your restaurant's public contact details — is stored so we can publish your site. It's your content; you can edit or delete it at any time, and deleting a site removes its content, leads and analytics with it.
Billing and plan information
We keep a record of which plan your account is on. Subscription payments are processed by Stripe, our payment provider — you enter card details on Stripe's secure checkout and card numbers never touch our servers. We store only your plan and a Stripe customer/subscription reference. Guests who pay a restaurant through its site — for an order, a gift card, a deposit or a no-show guarantee — also pay through Stripe, on that restaurant's own Stripe account; TableSpark keeps the payment reference, amount and status, never card numbers.
Support
If you email us, we keep the correspondence so we can help you and refer back to it. We use it for nothing else.
Menu scan files
If you use the AI menu scan, the images, PDFs, Word documents, text files or spreadsheets you upload are kept in private temporary storage and used only to recognise your menu. The default retention window is up to 24 hours: once the temporary scan task expires, the files are deleted. If deletion is interrupted, our cleanup process automatically retries it. We send the files to OpenAI for menu recognition during this process; OpenAI does not use API data to train its models by default. If you ask us to read the menu page of your existing website, we fetch that public page and handle its visible text the same way, as a text file.
Connected TikTok account
If you connect your restaurant's TikTok account in Promo videos, TikTok asks you to approve the connection and then sends us an access token, a refresh token, your TikTok account ID (open_id), the permissions you approved and when the tokens expire. We store these against your restaurant, together with which team member connected the account and when, so that you can post promo videos to that TikTok account. The tokens stay on our servers and are never shown in your browser. When you post, we read your TikTok display name, avatar and posting options from TikTok to show you before you publish, pass the video and caption you chose straight to TikTok, and then read back whether the post succeeded. We do not keep a copy of the video, the caption or your posting settings, and we never post anything you did not choose to post. Click Disconnect at any time: we ask TikTok to revoke the token and delete everything we stored for the connection. TikTok's handling of your account and posts is covered by TikTok's own privacy policy.
Your team's clock-ins and payroll exports
If your restaurant uses staff clock-in, we keep each team member's name, the times they clock in and out, their breaks, how the time was recorded (their own phone, a shared clock-in device, the till, or entered by a manager) and who approved the hours. Clock-in PINs are stored only as salted one-way hashes, never as the PIN itself. We do not record location or IP addresses for clock-ins. Owners and admins can add hourly pay rates and a payroll ID; team members see only their own hours. The payroll export is a file the owner downloads (names, payroll IDs, hours, hourly rates, gross pay, holiday accrual and tips); TableSpark does not send it anywhere and does not store National Insurance numbers. We hold these records for the restaurant, on its instructions: the restaurant is the controller for its team's data.
Accounting exports and the Xero connection
Accounting exports are files the owner downloads. The daily sales journal holds totals by account (sales, VAT, payments, and tips and service charge held for staff) and no guest or staff names; purchase exports include the supplier details you entered. If you connect Xero, we send each trading day's summary journal to your Xero organisation, and we keep the organisation's name and ID and the connection token on our servers (never in your browser). Disconnect at any time: we revoke the token with Xero and delete it.
Your own card terminal
If you connect the card terminal your restaurant already uses (SumUp, Dojo or Square), the till sends that provider the amount, any tip, a payment reference and a short label. The guest's card is read by the provider's terminal and never reaches TableSpark; we keep the result the provider returns (approved or declined, card type, the last four digits and the authorisation code printed on a merchant slip) so the bill and your end-of-day batch match. The terminal's API key is stored on our servers only and is deleted when you disconnect.
Error monitoring
When something fails on the platform or on a restaurant site, we record what went wrong so we can fix it: the kind of page or request (never its full address), the restaurant's web address and account ID, the browser type, the error status and timing. Before anything is stored, messages are cleaned of email addresses, phone numbers, card-like numbers, postcodes, tokens and query strings. IP addresses and account IDs are used only for a moment to limit repeated requests; neither is kept in these records. Our team receives alerts by email. These records are deleted after 30 days.
Legal basis: we process account, content and billing data because it's necessary to provide the service you signed up for (contract), and support correspondence on the same basis or our legitimate interest in running the service well.
3Journal reading and signup attribution
If you allow Analytics storage, our first-party measurement can record that a Journal article was viewed and, after the stated active-reading and page-progress threshold, engaged with. If you separately allow Marketing storage, it can connect a Journal call-to-action with signup start and signup completion. A Marketing-only choice can measure the signup path without recording Journal reading events.
The attribution record contains an allowlisted, signed article and call-to-action context plus a one-way SHA-256 hash of a random browser journey ID. We do not put the raw journey ID, signed token, email, name, phone, referrer or IP address in that table. Only on signup completion do we attach the authenticated TableSpark account identifier, so one account cannot be counted as more than one new signup completion.
Statistical reading measurement is first-party, needs no advertising pixel and, since the Data (Use and Access) Act 2025 amendments to PECR (19 June 2026), runs on the statistical-purposes basis with a simple objection in Cookie Preferences; attribution that links a Journal article to your signup is based on your consent. You can withdraw either category through Cookie Preferences; the relevant browser attribution state is then removed. Journal attribution events are deleted after 14 months.
4What we process for restaurants' guests
Restaurant sites on TableSpark can take bookings, enquiries, gift-card requests, event RSVPs and newsletter signups. When you submit one of these forms, the details go straight into that restaurant's private inbox on TableSpark. Depending on the form, that can include:
- your name, email address and phone number;
- booking details — date, time, party size, seating preference, occasion and any notes you add;
- allergy or dietary notes, if you choose to share them, so the restaurant can look after you. Please share only what the restaurant needs for your visit;
- for gift cards, the recipient's name and your personal message;
- for newsletters, just your email address.
Only the restaurant you contacted can see these details (plus TableSpark staff where needed to run and support the platform). We never sell guest data, never use it for advertising, and never contact guests ourselves.
Signing in to a restaurant's Guest App
A restaurant can offer a Guest App where you sign in to see your bookings, orders, gift cards and rewards with that restaurant. The name, phone number, delivery address, birthday, pronunciation note and message choices you enter there are stored for that restaurant only, under that restaurant's TableSpark account. Each restaurant is a separate business and a separate controller: if you use the same email address at another restaurant on TableSpark, that restaurant's Guest App starts with your email address alone and asks you for your details itself. What you give one restaurant is not shown to another restaurant, and is not used in another restaurant's messages, rewards or guest list.
Sign-in itself is checked by our authentication provider, Supabase: your email address and a securely hashed password that is never visible to us or to any restaurant, or Sign in with Google if you choose it. There is one sign-in per email address, so the email and password you chose work at each restaurant's Guest App where you decide to sign in. Deleting your details in one restaurant's Guest App removes that restaurant's copy. To remove what another restaurant holds, use that restaurant's Guest App or ask that restaurant; the sign-in is removed once no restaurant holds anything under it.
Online orders, tips and the live order page
When a restaurant offers it, you can order without an account: the order then needs your name, email address and phone number, and is paid online through Stripe. You may see a link to create an account afterwards; no account is created unless you choose to. If you add a tip, it is charged with your order on the restaurant's Stripe account and recorded for the restaurant's team. The live order page is a private link that shows your order's progress, dishes and totals and any refund; it never shows your name, phone number, email or address.
Orders placed on delivery apps
If the restaurant connects HubRise, orders you place on a delivery app reach the restaurant through HubRise. We store what the app passes with the order — your name, phone number, email, delivery address and notes — and a copy of the order as received, so the kitchen and the till can work from it. We send HubRise only the order's status and the restaurant's menu. Once an app order is accepted into the restaurant's orders, its contact details are anonymised after 24 months like any other online order. An app order that is never accepted loses your details, delivery address and notes, including notes on the dishes, after 30 days.
Text messages
If the restaurant switches on text messages, service texts about your own booking, place in the queue or order (confirmed, moved or cancelled, a reminder, your table is ready, your order is ready) are sent to the mobile number you gave, through Twilio. They carry the restaurant's name, the date and time, the party size and a link or order reference, and never offers. Reply STOP to any text and we add your number to an opt-out list that applies to every restaurant on TableSpark; it stays there until you reply START. The list keeps a keyed code made from the number, not the number itself, which is enough to recognise the number when a text is about to be sent. 90 days after a service text or email is sent, the number or address it went to and its content are removed; the record that it was sent stays.
Marketing consent records
When you agree to hear from a restaurant, its records keep the wording you were shown, when you agreed and, for a form on its website, which version of the form it was, so the restaurant can show what you agreed to. We do not store your IP address or browser details with it. It appears in any copy of your data you ask for, and is removed when your details are erased. If you withdraw your agreement, the earlier records are deleted six years later and the record of the withdrawal is kept.
Allergies, and allergy history if the restaurant switches it on
Allergies you tell the restaurant are recorded for that visit so the kitchen is told in writing. A restaurant can choose to switch on allergy history: its team then also sees the allergies recorded at your earlier visits to that restaurant, with the date each was last recorded, as a prompt to ask you again. Staff still ask about allergies at every visit. This is health information the restaurant chooses to keep from one visit to the next; only that restaurant's team sees it, never another restaurant, and it is off unless the restaurant switches it on. When your details are erased, those allergy records are deleted and no longer shown, including those on bookings that carry no email but one of your phone numbers the restaurant holds.
First-party, cookieless analytics
Restaurant sites include a deliberately minimal, first-party visit counter so owners can see how their site is doing. It records the type of action (page view, tap-to-call, directions, booking click), the page path, a coarse traffic source (direct, search, social), device type (mobile or desktop) and a random identifier stored in your browser. It does not record your IP address, your precise location, or what you do on any other website, and it sets no cookies. Restaurants may show a notice letting you decline this measurement.
5Why we use your data, and our legal basis
This table brings together the legal bases set out in the sections above.
| What we use it for | Legal basis |
|---|---|
| Your account, your restaurant's content and billing records — so we can provide the service you signed up for | Contract |
| Support correspondence — so we can help you and refer back to it | Contract, or our legitimate interest in running the service well |
| Statistical measurement of Journal reading | The statistical-purposes basis under PECR as amended by the Data (Use and Access) Act 2025, with a simple objection in Cookie Preferences |
| Linking a Journal article to your signup (attribution) | Your consent, which you can withdraw in Cookie Preferences |
| Error monitoring — so we can find and fix failures | Our legitimate interest in running the service reliably |
| Keeping a number that replied STOP on the text-message opt-out list | Our legitimate interest in honouring that request for every restaurant on TableSpark |
| Bookings, enquiries, orders (including delivery-app orders, tips and the live order page), gift cards, RSVPs and newsletter signups on a restaurant's site, its visit counter, service text messages, consent records, allergy history where the restaurant switches it on, and the restaurant's team clock-ins, accounting exports and card-terminal payments | We process these for the restaurant, strictly on its instructions. The restaurant is the controller |
6How long we keep things
- Account data and site content: for as long as your account is open. Deleting your account, or a site, permanently removes the associated content, leads and analytics.
- Bookings and waitlist entries: kept for the restaurant until the restaurant or the guest asks for deletion, or the restaurant's account or site is deleted.
- Enquiries: deleted 24 months after the restaurant marks them done, and after 36 months in any case.
- Online order contact details (including guest checkout and delivery-app orders accepted into the restaurant's orders): anonymised after 24 months. The order's amounts, tip and payment record stay, because the restaurant must keep its sales records.
- Delivery-app orders never accepted into the restaurant's orders: the guest's details, address and notes are removed after 30 days.
- Texts and emails to guests: 90 days after sending, the address or number is removed, and so is the content of service messages (about a booking, the queue or an order) and loyalty emails; the record that a message was sent stays.
- Private feedback: the name, email and phone number given with it are removed after 24 months; the rating and comment stay with the restaurant.
- Marketing consent records: kept while the restaurant relies on your agreement; six years after you withdraw it, the earlier records are deleted and the withdrawal is kept.
- Card-terminal payments: the last four card digits and the authorisation code are removed after 24 months; the amount stays.
- Team clock-ins and pay records: 37 months after the day worked (three years after a monthly pay period), the team member's name is removed from the hours and the record of edits is deleted; pay rates of people who have left are deleted once no hours inside that period use them.
- Tips records: kept for three years from the date of the tip; then the team member's name is removed and the amounts stay.
- Sickness and absence records: deleted six months after the absence ended once the person has left the team; the restaurant's owner can delete one at any time.
- Leave requests, shift swaps and team-records history: deleted after three years; notices to the team are deleted 90 days after sending.
- Accounting connection records (the daily summaries sent to Xero) and card-terminal batch totals: deleted after six full years.
- Error monitoring records: deleted after 30 days.
- Job applications and CVs: deleted 12 months after they are submitted (see section 12).
- Text-message opt-outs: kept, as a keyed code made from the number, until you reply START from that number.
- Xero and card-terminal connections: the connection token or API key is deleted as soon as the restaurant disconnects.
- Statistical reading events and consented Journal attribution events: deleted after 14 months.
- Connected TikTok account: until you click Disconnect (the token is revoked with TikTok and the stored details are deleted at once), or until TikTok's refresh token expires, whichever comes first. We keep no copy of promo videos or captions.
- Menu scan files: kept in private temporary storage only for menu recognition. The default retention window is up to 24 hours. After the scan task expires, the files are deleted; if deletion is interrupted, cleanup is retried automatically.
7Who we work with
We use a small number of service providers to run TableSpark. They process data only on our instructions:
| Provider | What they do | What they handle |
|---|---|---|
| Cloudflare | Hosting and delivery of the platform and all restaurant sites, and the automated bot check (Turnstile) on some guest forms | All site traffic in transit; short-lived technical logs; for the bot check, your IP address and browser signals |
| Supabase | Database, authentication and media storage | Account data, site content, guest records (bookings, orders, enquiries and mailing-list sign-ups), analytics, consented Journal attribution events, and job applications with their CVs |
| Fontshare | Our marketing pages serve their typeface (Albert Sans) from tablespark.uk, and every restaurant website built with TableSpark serves its template typefaces from the restaurant's own web address through TableSpark (all under the SIL Open Font License) — no font request leaves for Google. Two signed-in app pages load a typeface from Fontshare | On those two app pages your IP address reaches Fontshare to receive the font files (a standard web request; no cookies) |
| Pexels | Free stock photography that restaurants can use on their sites | No personal data is sent by TableSpark. Where a site shows a Pexels photo, your browser loads it from Pexels' image servers (a standard web request) |
| OpenAI | Powers ten AI features for signed-in customers: the AI menu scan, Scan-to-Site generation, the Builder's block and section writer, campaign copy, the SEO title & description writer, the Posts & events writer, the promo video writer, site photo generation, review reply drafts and the area introduction and local guides writer | Menu files for recognition, handled through private temporary storage for up to 24 hours by default, including the text of a menu page on the restaurant's own existing website when the owner asks us to read it; the text a customer asks each feature to work on — page copy, dish names, offers, opening hours, address and menu content; and, for site photos, a short description of the scene and the site's colours. For the area introduction and local guides: the restaurant's name, address, cuisine, dishes and About text, with public facts about the places around it from OpenStreetMap, Wikidata and Wikipedia; the text is written into the restaurant's draft site and reaches guests only when the owner publishes. For a review reply draft, which the restaurant asks for one review at a time: that review's rating and text and the reviewer's first name if given, with the restaurant's own record — its name, contact phone and email, its sign-off, and the kind and date of the visit if the review is linked to one. The draft goes into the owner's editor to be edited and approved; nothing is posted automatically. No other guest data is sent |
| Cloudflare Web Analytics | Cookieless visit counting on our own marketing pages | Your IP address, the page URL and browser type reach Cloudflare's analytics endpoint; it sets no cookie and stores no identifier on your device |
| OpenProvider & Nominet | Registering a domain a restaurant buys through TableSpark | The registrant's name, postal address, email and phone are passed to OpenProvider (our registrar) and, for .uk names, to Nominet (the UK registry), as domain registration rules require |
| Stripe | Processes subscription payments for customers, and the payments guests make on a restaurant's site — online orders, gift cards, deposits and no-show card guarantees — on that restaurant's own connected Stripe account | Card details are entered on Stripe's secure checkout and never touch TableSpark; we store your plan and a Stripe customer/subscription reference, and for guest payments the payment reference, amount and status |
| TikTok | Receives the promo videos a customer chooses to post to the TikTok account they connected | The video, caption and posting settings the customer chose, sent with that account's access token; we hold the connection tokens and TikTok account ID as described above. No guest data is sent |
| Resend | Delivers the emails TableSpark sends: account emails (sign-in, password reset, invites), job application notices and confirmations, and the emails a restaurant sends its guests through TableSpark — booking and order confirmations, reminders, gift cards, review invitations and marketing campaigns | Recipient email address and message content, including any attachment such as a guest's own data copy |
| Sign-in with Google, when a customer or a guest chooses it; address suggestions (Google Places) when a guest types a delivery address or a customer types their restaurant's address; Search Console, to submit each published site's sitemap and verify custom domains; and a typeface the signed-in app pages load from Google Fonts | For sign-in, the Google account's name and email address are confirmed to us by Google; for address suggestions, the address as it is typed, with no name, email or phone number; Search Console receives website addresses only, no personal data; for the typeface, your IP address reaches Google to receive the font files (a standard web request) | |
| Postcodes.io | Checks whether a delivery postcode is inside a restaurant's delivery area | The postcode only, never the address lines, name, phone number or email |
| Apple, Google and Mozilla push services | Deliver Guest App notifications, used only when a guest turns notifications on in a restaurant's Guest App | The device's push address and the notification, which is encrypted so the push service cannot read it |
| Twilio | Sends text messages, used only when a restaurant switches on text messages to its guests | The guest's mobile number and the text of the message, such as a booking or order update |
| HubRise | Passes orders guests place on delivery apps to the restaurant, and the order's status back, used only when a restaurant connects HubRise | The guest's name, phone number, email, delivery address and notes as the delivery app sends them with the order; from TableSpark, only the order's status and the restaurant's menu. HubRise states that it stores personal data within the European Union |
| Xero | Receives a restaurant's daily sales summary in its own Xero organisation, used only when a restaurant connects Xero | Daily totals by account, with no guest or staff names; we hold the Xero organisation's name and the connection token, deleted when the restaurant disconnects |
| SumUp | Takes card payments on the restaurant's own SumUp terminal, used only when a restaurant connects its SumUp terminal | The amount, tip, a payment reference and a short label; the card is read by SumUp and never reaches TableSpark. SumUp's data processing terms state that processing takes place within the European Economic Area and the UK |
| Dojo | Takes card payments on the restaurant's own Dojo terminal, used only when a restaurant connects its Dojo terminal | The amount, tip, a payment reference and a short label; the card is read by Dojo and never reaches TableSpark |
| Square | Takes card payments on the restaurant's own Square terminal, used only when a restaurant connects its Square terminal | The amount, tip, a payment reference and a short label; the card is read by Square and never reaches TableSpark. Square states that it processes and stores information in the United States, Japan, the UK, the EU and other countries, using the UK Addendum to the EU Standard Contractual Clauses or the UK International Data Transfer Agreement for UK transfers |
| Ideal Postcodes | Lists the addresses at a postcode when a guest types a delivery postcode, used only when address lookup is switched on | The postcode only, never the guest's name, phone number or email |
| IndexNow | Tells search engines that pages of a published site have changed, used only when search-engine notification is switched on | Website addresses only, no personal data |
Some restaurant sites also choose to embed third-party content — a Google map, a YouTube video, an external booking widget. Loading those hands a standard web request to that provider; we are moving all such embeds to click-to-load, so nothing loads until you choose it. See our cookie declaration.
Where a provider processes data outside the UK/EEA, transfers are covered by that provider's data-processing agreement and standard contractual clauses.
8International transfers
Our database, sign-in and media storage run on Supabase in its EU (Ireland) region. Where a provider processes data outside the UK/EEA, transfers are covered by that provider's data-processing agreement and standard contractual clauses.
9How we protect your data
- Cyber Essentials certified. TableSpark Ltd holds Cyber Essentials certification for the whole organisation, the UK Government-backed scheme run by the National Cyber Security Centre with IASME, valid to 17 November 2027. View the certificate.
- NCSC Early Warning. Our domain is enrolled in the National Cyber Security Centre’s Early Warning service, which alerts us to potential threats and vulnerabilities it detects on our network.
- Insured. We carry cyber liability insurance, underwritten by AIG UK, with incident response specialists on call if an incident ever occurred.
- Card numbers never reach us. Stripe takes every card on its own checkout or reader.
- Every restaurant walled off. Row-level security in the database keeps each restaurant's records separate.
- HTTPS everywhere. Every page and restaurant site is served over HTTPS.
- Passwords stored only as secure hashes, never visible to us.
The full picture is on our security and data protection page.
10Your rights
Under UK and EU data-protection law you can ask for access to your data, correction, deletion, restriction, portability, and you can object to processing based on legitimate interest. You can also withdraw consent at any time where consent is the basis (for example a newsletter).
- Guests: the restaurant you dealt with is the controller of your booking or enquiry — contacting them directly is usually fastest, and we give them the tools to delete your details. You can always email us at hello@tablespark.uk and we will pass the request on and make sure it's honoured.
- Customers: email hello@tablespark.uk from your account address for a copy, correction or deletion of your account data.
You also have the right to complain to the Information Commissioner's Office (ico.org.uk) or your local EU supervisory authority — though we'd appreciate the chance to sort things out first.
| Your right | How to use it |
|---|---|
| See a copy of your data | Customers: email hello@tablespark.uk from your account address. Guests: ask the restaurant, or email us and we'll pass it on. |
| Correct it | The same way. Customers can also edit their account and site details themselves. |
| Delete it | Customers: delete a site or your whole account in settings, or email us. Guests: ask the restaurant or us — requests made through a restaurant site land in its inbox with a one-click delete. |
| Restrict, port or object | Email hello@tablespark.uk. You can object to any processing based on legitimate interest. |
| Withdraw consent | Journal measurement and attribution: Cookie Preferences. Newsletters: the one-click unsubscribe link in every mailing. |
| Complain | To the Information Commissioner's Office at ico.org.uk, or your local EU supervisory authority. |
11Unsubscribing and deletion, in practice
- Newsletters: every mailing sent through TableSpark will carry a one-click unsubscribe link that works instantly, without a login. Until you unsubscribe, only the restaurant you signed up with can email you through us.
- Booking and enquiry details: ask the restaurant, or us, and the records are deleted from the restaurant's inbox and our database. Deletion requests made through a restaurant site land in the owner's inbox with a one-click delete action. Records at that restaurant that carry no email but one of your phone numbers we hold (a booking taken by phone, an order, an enquiry or feedback) are cleared with them.
- Whole accounts: account deletion removes the profile, its sites, and everything beneath them.
- Text messages: reply STOP to any text and no restaurant on TableSpark texts that number again until you reply START. When your details are erased, the texts and notices sent to your phone number are cleared too.
12Job applicants
When you apply for a role on tablespark.uk/careers, TableSpark Ltd is the controller of your application. We collect the title you choose (if any), your full name, your email address, your CV and the note you add, the role you applied for and the date. We also keep a shortened one-way code made from your IP address, used only to spot repeated abuse of the form; it is not your IP address itself.
We use your application only to consider you for the role you applied for and to reply to you. Your CV is kept in private storage that only TableSpark's platform administrators can open, through a link that expires after a few minutes; it is never attached to an email or shared outside TableSpark. When you apply, we send one email to our careers inbox to say an application has arrived, and one email to you to confirm it; both go through Resend.
Legal basis: the steps you ask us to take before a possible contract of employment, and your agreement, given when you tick the box on the form.
How long we keep it: your application and CV are deleted automatically 12 months after you submit them. You can ask us to delete them sooner, or for a copy, at company@tablespark.uk; the rights in section 10 apply to your application too.
13Changes to this policy
If we change this policy in a way that matters — new processors, new data, new purposes — we'll update this page, revise the date at the top, and for significant changes notify account holders by email. The current version always lives at tablespark.uk/privacy.