We build online ordering software for restaurants in the United States. Three things are worth knowing before the detail:
- We do not sell your personal information, and we do not share it for cross-context behavioral advertising. We never have.
- If you are a diner, the restaurant you ordered from is in charge of your data, not us. We hold it on their behalf and under contract with them. Your rights run to them first; §7 explains how we help.
- Our ordering pages carry no advertising pixels, no third-party trackers, and no session recording. They keep your cart in your browser and use a random string, in the tab you have open, to count how many visits become orders. Nothing follows you to other sites.
1. Who this policy covers
This policy is written for four groups, and it says which parts apply to whom:
| Group | Who | Our role |
|---|---|---|
| Visitors | People who visit our marketing website | Controller / “business” |
| Merchants | Restaurant owners and staff with dashboard or tablet-app accounts | Controller / “business” |
| Diners | People who order food through an ordering page we power | Processor / “service provider” to the restaurant |
| Waitlist | People who gave us an email address on our waitlist | Controller / “business” |
TableSpring is offered to restaurants in the United States, and this policy is written for that setting.
The Diner row is the important one. When you place an order, the restaurant decides what to collect, why, and how long to keep it. We are the software they use. This policy tells you what we do with that data as their vendor; the restaurant’s own privacy notice tells you what they do with it. The contract that binds us is our data processing addendum, which restaurants can request from legal@tablespring.com.
2. What we collect
Everything below is a real field in our system, not a hypothetical category.
2.1 From Visitors (marketing website)
| Data | Why |
|---|---|
| Email address, if you signed up for our waitlist or write to us | To send the launch email you asked for, and to reply |
| For waitlist sign-ups, the page or button you signed up from and the referring URL | To understand which content works |
| IP address, browser and device information, request timestamps | Security and abuse prevention; our hosting provider also keeps ordinary request logs |
| A local preference recording that you dismissed the site’s notice banner | So the banner stays dismissed |
| What you type in the contact form, held in your browser tab only until the message is sent | So your text can be put back if sending fails. It is not sent to us until you press send |
We do not require an account, and we run no advertising pixels or analytics service on the marketing site. See the Cookies and Tracking notice for the exact identifiers.
2.2 From Merchants
| Data | Why |
|---|---|
| Name, email address, phone number, profile photo | Your account and how we reach you about your orders |
| Authentication data: password hash, session tokens, and, if you sign in with Google where that is offered, the identifier and email that provider returns | To sign you in |
| Restaurant name, slug, phone, timezone, address, hours, tax settings, branding, menu content and menu photos | To run your ordering page |
| Team membership, role, and the email addresses of people you invite | To enforce who can see what |
| Billing contact and subscription records, once paid Plans are available; card details are held by Stripe, not by us | To charge for paid Plans |
| A log of significant account actions (who did what, when) | Security and dispute resolution |
| Menu files and web addresses you submit for AI import, and the drafts produced from them | To import your menu |
| If you use the Google business lookup during setup: your search text, a short-lived lookup session token, the Place ID you select, and the business details Google returns | To pre-fill your restaurant’s details |
| If you use the merchant tablet app: a device record (device name, platform, app version, when it was last seen, and a random device identifier the app generates for each tablet) and, for printers you add, the printer’s name, model, hardware identifier, and last local network address | To register and recognize the tablet, alert you to orders, show which tablets are connected, and print tickets |
| The text you type to search order history or customers in the dashboard or the tablet app | To provide the Service: it is sent to our servers to return the results. We do not keep a search history. The text travels in the request, so our hosting provider’s ordinary request logs may include it |
| When you use the dashboard’s sign-in, sign-up, password-reset, invitation or resend-email screens, send us a message through the contact form, or sign in to the tablet app: your IP address and browser or device signals, read by Cloudflare’s bot check (Turnstile) | To tell a person from an automated request, and keep bots out of sign-in |
| Emails you send us, and the context you choose to include | To help you |
2.3 From Diners: held for the restaurant
When you place an order, the restaurant collects, through us:
| Data | Notes |
|---|---|
| Name, email address, phone number | All three are required at checkout. Email is the channel your order status is sent on. We do not text you about your order. The only text we send is a one-time rewards code, and only if you ask for one (see “Text messages” below) |
| Delivery address, apartment or unit, delivery instructions, and the Google Place ID of the address you pick | Only when you choose delivery. We keep these on the order so the restaurant can deliver it and answer questions about it. We do not store map coordinates for your address |
| If you choose delivery and use the address box: the text you type, a short-lived lookup session token, and the Place ID of the suggestion you pick | Sent to Google to suggest and confirm the address. Google returns the address and its location; we use the location once to check that the address is inside the restaurant’s delivery area and to work out the distance, and we do not keep it |
| Your order: items, options, quantities, prices, taxes, tip, and any note you add | Notes are free text, up to 500 characters; please don’t put anything sensitive there |
| Fulfillment time, whether the order was scheduled, and its status history | |
| What the restaurant’s staff enter on your order: the estimated ready time when they accept it, the reason if they reject it, and the amount and reason of any refund | Stored with the order and its status history, and visible to the restaurant |
| Payment method and status. We never receive your card number. If you pay by card, you type it into Stripe’s payment form on the ordering page and it goes to Stripe. We store a reference to the payment and, for the receipt, the card brand and last four digits | |
| Your marketing choice. The checkout shows an unchecked box asking whether you want email offers from the restaurant. We record your choice with a timestamp and the version of the wording shown | This is the restaurant’s consent record |
| A customer profile the restaurant keeps: your name, email, phone, order count, date of last order, and whether you opted in to marketing | Kept per restaurant. Ordering from two restaurants creates two separate records that are never combined |
| IP address, briefly, at checkout | Rate limiting and abuse prevention. It is held in memory for that purpose and is not stored with your order; our hosting and database providers may keep ordinary request logs |
| A per-tab random session identifier and a small set of events: menu viewed, item opened, added to cart, checkout started, order placed | Explained in §2.4 |
If you join a restaurant’s rewards or email list, or the restaurant sends you marketing email, it also collects, through us:
| Data | Notes |
|---|---|
Rewards membership: your phone number, the date you joined, and the version of the rewards terms you accepted (currently loyalty-v1) | Joining is optional and never needed to order. A membership belongs to one restaurant: the same number at two restaurants is two memberships that are never combined. It starts as pending and becomes verified when you enter a code we send to your number |
| A verified email address, if you add one to your rewards | Used for the sign-in code if you ask for it by email instead of text, and for a notice if a reward is spent on your account from a device that was not signed in. It is saved only after you enter a code sent to that address, from a device already signed in with your phone. It is never copied from an order |
| Your birthday (month and day only), if you choose to add it | Set once, from a signed-in device. Used only for the restaurant’s birthday reward, if it offers one |
| Your points: a record of points earned, held for a reward, released, reversed, expired or adjusted, with the order each relates to and, if the restaurant adjusts your balance, its note | Your balance is the total of that record, which is never edited after the fact. A restaurant can set points to expire after 6 or 12 months with no earning or spending, or never; an expiry is recorded the same way |
| One-time sign-in codes: a six-digit code sent to your phone by text, or to your verified email | We store only a hash of it, never the code. It works for 10 minutes and allows five tries. If we use a managed verification service for the text, that service holds the code instead (§5) |
| A remembered device: a random session identifier, a coarse label such as “Safari on iPhone”, and when it was created and last used | Keeps you signed in to that restaurant’s rewards, for up to 90 days (or until you close the browser, if you said the device is shared). No IP address or full browser string is stored with it, and you can sign out of every device |
| Your email address, if you sign up on the restaurant’s email join page. That page asks for nothing else | We record your consent: the words shown, their version (currently join-v1) and the time. Until you click the confirmation link in the welcome email, or place an order, you are pending and receive only that welcome email. The page uses Cloudflare Turnstile (§5), and we keep one-way hashes of your address and your IP address for a short time to limit repeat sign-ups |
| Email addresses a restaurant imports from its own list: the address, and a name if the file has one | Email only: phone columns in the file are ignored. The restaurant states that everyone on the list agreed to its marketing email. Each person gets one email asking them to confirm, and nobody who does not is emailed again. An address that has unsubscribed, complained or bounced is never added back |
| Records of the restaurant’s marketing emails to you: which email, when it was sent, and whether it was delivered, bounced, marked as spam, clicked or unsubscribed from; and, if you then order, which email the order is credited to | We do not track whether you open an email. A click is counted by our own link, and an order is credited to an email only if it is placed within five days of the click |
| Offers sent to you: the offer, the short code printed in the email, when it expires, and the order that used it, if any | An offer sent to you is worth nothing to anyone else: using it needs the email or phone on the order to match |
| Groups a restaurant sorts its guests into: new, returning, regulars, lapsed, never ordered, and rewards members | Worked out by us for each restaurant, from that restaurant’s own orders and rewards list only, when the restaurant chooses who receives an email or filters its guest list. They are never combined across restaurants |
Text messages. We send one kind of text: a one-time rewards code. It goes to a number only because the person asked for it: a diner who ticked “join rewards” at checkout gets one text after the order (and another only if they ask for a new code), and a member who taps “Text me a code” to sign in gets the code they asked for. The text contains the code and the restaurant’s name (and, depending on our text provider, “TableSpring”), and the code lasts 10 minutes. Nothing in the Service sends marketing or promotional texts. Message and data rates may apply. Reply STOP to a code text to stop texts from that number, or HELP for help; you can also write to support@tablespring.com. We send these texts only to US and Canadian numbers. We do not share mobile phone numbers or text-messaging consent with third parties for their marketing. Our text providers (§5) receive a number only to deliver the code.
We do not collect from diners: precise geolocation, contact lists, device identifiers, advertising identifiers, biometrics, or anything derived from tracking you across other websites.
2.4 What an ordering page keeps in your browser, in full
This is the part most privacy policies are vague about, so here it is exactly. The Cookies and Tracking notice lists every key.
- A cart. Your cart is kept in your browser’s
localStoragefor that restaurant so it survives a reload. A cart older than seven days is treated as stale and ignored. - An outline of the cart, in a cookie. Our server cannot read
localStorage, so the page also keeps a small cookie for that restaurant (ts_hint_and its name) saying how many items the cart holds and the pickup time you picked, so the page can draw your cart before it has read it. It holds no dishes, no prices and nothing about you, is sent only with that restaurant’s own pages, and is deleted when the order is placed or the cart is emptied (if a pickup time is still chosen then, it is kept until that time instead). - A session identifier. When you open an ordering page, your browser generates a random 16-character string and stores it in
sessionStorageunder the keyts.session. It is 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.- It is not a cookie, and it is not in
localStorage. It exists only in the tab you have open and is destroyed when you close it. - It contains no information about you. It is not derived from your device, your IP, your browser, or anything you typed, and the event records hold item and menu identifiers only, never free text.
- It cannot be linked to a later visit, to another tab, or to another restaurant’s page. It is stored next to the order’s identifier in the “order placed” event, so the restaurant’s funnel can count that visit as a sale; the event holds no name or contact details.
- If your browser blocks storage (private mode, for instance), analytics is simply skipped. The order still works.
- It is not a cookie, and it is not in
- Saving your details on this device. When you place an order, you can tick “Save my details on this device”. It is off unless you turn it on. If you do, your name, email address, phone number and up to five delivery addresses (with the apartment or unit and delivery instructions you entered) are stored in your browser’s local storage, for that restaurant only, so the next order starts filled in. This is storage on your own device that the page uses to do what you asked; it is not sent to us or to anyone else until you place an order, and we do not use it for advertising or to track you. We do not save map coordinates, payment details, or your choice about marketing email. A saved address is checked again with Google each time you use it, so a changed or removed address is not used. Details you have not used for 12 months are removed. To remove them, choose “Clear saved details” at checkout, or clear this site’s data in your browser. If a form is filled in from earlier details and you untick the box when you order, the saved details for that restaurant are removed. Do not tick it on a computer you share.
The rest are named in the notice: the pickup time you picked, an offer code you entered or an offer from an email you opened, which of the restaurant’s emails brought you there, a cookie that hides the join strip once you have joined its list, a sign-in cookie if you sign in to its rewards, the name, email and phone number you type at checkout and the delivery details you enter (kept only in that browser tab while you order, so a reload does not lose them, and cleared when the tab closes or the order is placed), and, only if you ask the page to save them, your contact and delivery details on this device for next time.
There are no advertising pixels, no session-replay or keystroke-capture tools, no chat widgets that forward what you type, no third-party analytics, and no third-party tag managers on ordering pages. This is a deliberate design constraint we intend to keep. The third-party components are Stripe’s payment form at checkout and, on a restaurant’s email sign-up page and on our contact form, Cloudflare Turnstile, which checks that the submission isn’t automated using your IP address and browser signals. Both are described in the Cookies and Tracking notice.
3. Where the data comes from
Directly from you; from your browser and device when you use our sites; from Stripe (payment status, never card numbers); from our email provider (delivery, bounce, and complaint signals) and our text-message provider (whether a code could be delivered, including that a number has opted out); from Google, when a merchant uses the business lookup or a diner chooses delivery and uses the address box; from the person who invited a team member; and from an identity provider if you use social sign-in where we offer it.
4. Why we use it
| Purpose | Data |
|---|---|
| Provide the Service: take orders, send confirmations, show status, alert the restaurant | Merchant and Diner data |
| Run a restaurant’s rewards: confirm a phone number with a one-time code, keep points, and let the restaurant know what was spent | Rewards data |
| Send a restaurant’s marketing email at its instruction, honor unsubscribes, and report results to the restaurant | Email list, offer, and email delivery data |
| Bill for paid Plans | Merchant billing data |
| Security, abuse and fraud prevention, rate limiting | IP, request metadata, bot-check signals, audit log |
| Debug, monitor, and improve reliability | Logs and the ordering-page events in §2.4 |
| Support you | Emails you send us |
| Send merchants service messages: account, team invitations, order alerts, device offline notices, dispute notices | Merchant contact data |
| Send waitlist email about launch | Waitlist email |
| Comply with law, tax, and accounting; establish or defend legal claims | As required |
| AI menu import | Menu files and web addresses you submit |
We never use Diner Data for our own marketing, and we never combine it across restaurants. The only grouping we do is the per-restaurant guest groups in §2.3 (for example, “lapsed” or “regulars”). We work them out from one restaurant’s own records so that restaurant can choose who receives its email, and we do not build profiles of people across restaurants or from outside sources.
5. Who we disclose it to
We use the vendors below to run the Service. Each is bound by contract to protect the data and to use it only to provide their service to us.
| Vendor | What it does | Data it can reach |
|---|---|---|
| Vercel | Hosts our web applications | Anything passing through a request, including request logs |
| Supabase | Managed database and sign-in; scheduled background jobs | All stored data, including account and order data |
| Cloudflare R2 | Stores menu photos (public) and files submitted for AI import (private) | Menu images; the files you upload for import |
| Cloudflare | DNS and edge services for our domains | Request metadata |
| Cloudflare Turnstile | Bot check on the dashboard’s sign-in, sign-up, password-reset, invitation and resend-email forms, the tablet app’s sign-in, a restaurant’s email sign-up page, and our contact form | IP address and browser or device signals, to decide whether a request is automated. It returns a single-use token that we pass to Supabase |
| Stripe | Processes card payments on the restaurant’s own Stripe account | The card details the diner types into Stripe’s form, the amount, and a reference to the order. Funds go directly to the restaurant; Stripe’s relationship with the restaurant is direct |
| Resend | Sends transactional email: order confirmations and status updates to diners, order alerts to restaurant staff, team invitations | Recipient name and email address, order summary, delivery events |
| Resend (a separate account for marketing email) | Sends a restaurant’s marketing email (campaigns, automations and welcome emails) from a TableSpring address on our news subdomain, with the restaurant’s name as the sender and its contact email as the reply-to address. Kept apart from the account that sends order email, and reports delivery, bounce and spam-complaint events back to us | Recipient email address and first name, the message and any offer in it, delivery events |
| Telnyx | Delivers the one-time rewards code by text message | The recipient’s phone number and the text, which holds the code |
| Twilio (Verify) | A managed alternative to the row above: generates, texts and checks the one-time rewards code | The recipient’s phone number and the code |
| Anthropic | AI vendor for menu import | The menu files and text you submit. Receives an opaque identifier for your restaurant, not your name |
| OpenAI | AI vendor for menu import | The menu files and text you submit. We turn off its optional storage of requests |
| Address suggestions and address checks when a diner chooses delivery; business lookup and geocoding of the restaurant’s own address during setup; also an AI vendor for menu import only if we turn that on | The lookup text, session token, and Place ID (for delivery, what the diner types in the address box); the restaurant’s own address, to geocode it; for AI import, the same menu files and text as the other AI vendors |
We do not share mobile phone numbers or text-messaging consent with any vendor for its own marketing. The two text providers above receive a number only to deliver the code.
AI vendors receive menu content, not Diner Data. Their API terms currently provide that they do not train on content sent through their APIs; those terms are theirs, not ours. Menu import produces a draft that you review before anything is published.
We also disclose personal information: to a restaurant, for its own Diner Data (that is the point); to professional advisors under confidentiality; when legally required by valid legal process, where we will give you notice unless prohibited; to protect rights, safety, or investigate fraud; and to a successor in a merger or asset sale, subject to Terms §21.3.
We do not sell personal information and we do not share it for cross-context behavioral advertising, and we have not in the preceding 12 months.
6. How long we keep it
A few short-lived records are deleted automatically by scheduled jobs, as the rows below say. Everything else is kept for the purposes below and removed when an account is deleted or when someone asks us to remove it. For those rows, the periods are what we do, not an automatic deletion.
| Data | Retention |
|---|---|
| Waitlist email | Until you ask us to remove it or we no longer need it to tell you about launch |
| Merchant account, restaurant, menu, and configuration | Life of the account. When the owner asks to delete it, we delete it within 30 days of the request, and they can sign in to export until then |
| Orders and order line items | Life of the restaurant’s account. They are the restaurant’s business record: the restaurant should export what it must keep for tax and accounting before it asks to delete the account. When we delete the account they are deleted with the restaurant, except where the law requires us to keep a record |
| Delivery orders | The address, unit, instructions, the Google Place ID, the name of the delivery area that priced the order, and the distance to the restaurant in whole meters are stored with the order, like the rest of the order, for as long as the order is. Map coordinates for a delivery address are not stored on the order |
| A restaurant’s own location | For delivery areas measured by distance, we look up the restaurant’s coordinates from its address. We keep them for at most 28 days at a time, deleted automatically, and look them up again before then. We keep the Place ID |
| Diner customer profiles | Life of the restaurant’s account, or until the restaurant asks us to delete one |
| Marketing consent records | Life of the restaurant’s account; they are append-only, so a withdrawal is recorded as a new entry |
| Rewards memberships, points records, and birthdays | Life of the restaurant’s account. A member who leaves or is blocked is marked as such and the record stays; the points record is never edited after the fact |
| Offers sent to a guest, and the orders that used them | Life of the restaurant’s account |
| One-time sign-in codes (hashed) | Deleted automatically one day after they are issued, used or not |
| Remembered rewards devices | Until they expire (90 days) or the member signs out. The record is deleted automatically 30 days after that |
| Notices about a reward spent from a device that was not signed in | Deleted automatically 30 days after they are created, once sent |
| A restaurant’s marketing email records | 13 months, then deleted automatically, leaving only the restaurant’s monthly totals with nothing about any person. Delivery events from the email provider are kept 90 days. A link in an email redirects for 60 days. We remember that an address unsubscribed so that we do not email it again |
| Imported email lists | The uploaded rows are scrubbed of addresses and names 90 days after the import is confirmed. An unconfirmed draft is deleted after 24 hours |
| Sign-up and abuse-limit counters | One-way hashes of an address or IP address, deleted automatically after their window (an hour or a day) ends |
| Diner order status links | The link in a diner’s email is a secret; we store only an irreversible hash of it, never the link itself |
| Ordering-page events | Life of the restaurant’s account. They contain no personal data |
| Files uploaded for AI import | Deleted when you start an import over, and in any case by an automatic storage rule 90 days after upload |
| Email delivery events | We store the event type from our email provider, and addresses that bounce or complain are kept on a suppression list so we stop sending to them |
| Billing and tax records | 7 years, as required by law |
| Backups | Point-in-time recovery per our database provider’s retention; deleted data disappears from backups as they age out |
When a merchant account is deleted, restaurants for which that person was the only remaining owner are deleted with it, and everything belonging to them is deleted too. A restaurant with another owner stays open, and only the deleted person’s own access and profile are removed. A paid plan on a restaurant that is deleted is canceled right away, with no refund for the current period.
7. Your rights
7.1 If you are in the United States
Many states now have comprehensive privacy laws, and while the details differ, the rights they give are broadly consistent. We extend the following to every US resident regardless of state, because running a different process for each state is how mistakes happen:
- Know / access: what we hold about you, where it came from, why we have it, and who we gave it to
- Portability: a copy in a portable, machine-readable form
- Correct: fix inaccurate personal information
- Delete: subject to the exceptions the law allows, such as completing a transaction, security, and legal record-keeping (an order you already placed is a business record we and the restaurant must keep)
- Opt out of sale, sharing, and targeted advertising: nothing to opt out of, because we do none of it, but the right is yours and the answer will always be the same
- Opt out of profiling producing legal or similarly significant effects: we do none
- Limit use of sensitive personal information: we do not set out to collect it, and we do not use any for inferring characteristics. Free-text order notes and account credentials can contain sensitive information if someone types it; please don’t put it in notes
- Non-retaliation: we will not deny service, charge a different price, or degrade quality because you exercised a right
- Appeal: if we deny a request, you may appeal by replying to our decision. We will respond within 45 days with a written explanation, and we will tell you how to complain to your state attorney general if you are still unsatisfied
How to exercise them: email privacy@tablespring.com. Merchants can also export their order history and customer list from the dashboard. To delete a merchant account, go to Settings, then Account, then Delete account, in the dashboard or the TableSpring Orders app; open app.tablespring.com/account/delete; or email the same address. We delete the account within 30 days of the request, and the owner can still sign in to export until then. We will verify your identity in proportion to the sensitivity of the request, usually by confirming control of the email address on the account. We respond within 45 days, extendable once by another 45 with notice. An authorized agent may act for you with written permission we can verify.
If you are a diner, send the request to the restaurant you ordered from; they are the business that decides. If you send it to us, we will pass it to the restaurant and help them execute it, and we will tell you we have done so.
Marketing emails from a restaurant. The email offers a diner receives come from the restaurant. To stop them, use the unsubscribe link in any of those emails; order updates still arrive. You can also email privacy@tablespring.com and we will pass your withdrawal to the restaurant and ask it to record it. Restaurant staff can withdraw a guest’s marketing consent from their guest list.
7.2 Global Privacy Control
Our sites run no advertising or analytics scripts, so there is nothing for a Global Privacy Control signal to switch off. 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 separately to the older “Do Not Track” header, because it has no agreed meaning.
7.3 California specifics
- Notice at collection. The categories in §2 and the purposes in §4 are our notice at collection under the CCPA. The statutory categories we handle are: identifiers; customer records information; commercial information (order history); internet or network activity; geolocation only at the coarse level implied by an IP address; and, for merchants, professional information.
- Sensitive personal information. We do not collect it for the purpose of inferring anything about you, and we do not use or disclose personal information for purposes beyond those a service provider may.
- Shine the Light (Civ. Code §1798.83): we do not disclose personal information to third parties for their own direct marketing.
7.4 Outside the United States
TableSpring is offered to restaurants in the United States and is not designed for use elsewhere. If you are elsewhere and want to know what we hold about you, to correct it, or to have it deleted, email privacy@tablespring.com and we will help. Our infrastructure is primarily in the United States.
8. Security
Some of what protects your data, stated concretely because vague security sections are worthless:
- Tenant isolation is enforced in the database, not only in application code. Every table holding restaurant or diner data has row-level security, so a bug in a query cannot return another restaurant’s orders.
- Order status links are never stored. The link emailed to a diner is a bearer credential; we store only an irreversible SHA-256 hash of it, so a stolen database backup cannot be replayed to read someone’s order.
- Dashboard session cookies are HTTP-only, so a script injected into the dashboard cannot read them. On the merchant tablet app, the sign-in session is kept in the device’s secure keychain (the iOS Keychain or Android Keystore), on that device only.
- Order writes go through a single privileged server path that also does the pricing. The browser never holds a credential that can write an order.
- Order history is append-only and cannot be rewritten, including by our own administrative credentials.
- Card numbers never touch our servers. Entry happens in Stripe’s payment form.
- Encryption in transit (TLS); access to production data limited to the people who need it; point-in-time database recovery.
No system is perfectly secure. If we become aware of a breach affecting your personal information, we will notify you and the relevant authorities as the law requires.
9. Children
The Service is not directed to children. We do not knowingly collect personal information from anyone under 13, and merchant accounts require you to be 18 or older. If you believe a child has given us personal information, contact privacy@tablespring.com and we will delete it. Restaurants must not configure the Service to collect information from children.
10. Automated decision-making
We do not make decisions with legal or similarly significant effects about you by automated means. The AI feature in the product generates a draft menu that a human reviews and approves; it does not decide whether you get service, at what price, or on what terms.
11. Changes
We will post any change here with a new “Last updated” date. For material changes affecting merchants we will give at least 30 days’ notice by email and in the dashboard, per Terms §21.1. For changes that expand how we use previously collected personal information in a materially different way, we will obtain consent where the law requires it.
12. Contact
- Privacy questions and rights requests
- privacy@tablespring.com
- Delete a merchant account
- Settings, then Account, then Delete account, or app.tablespring.com/account/delete
- Everything else
- support@tablespring.com
- Postal address
- 10 Eleven Technology LLC
418 Broadway, STE N, Albany, NY 12207, USA