Data Processing Addendum
How Shop & Table processes personal data on a client’s behalf.
Updated November 7, 2026 · Version 2026-11-05
1. About this addendum
This Data Processing Addendum ("DPA") is part of the agreement between Shop & Table LLC ("Shop & Table," "we") and the business client named in it ("Client," "you"). That agreement is the Platform Services Agreement, the terms accepted at self-serve sign-up, or another signed agreement, together with any order form (the "Agreement"). Section 6.26 of the Platform Services Agreement incorporates it. It applies automatically when the Agreement takes effect, without a separate signature, and lasts as long as we process Client Personal Data.
Signed copy. You sign this DPA in the same electronic-signature flow as the Platform Services Agreement and Mutual NDA. We countersign automatically and email you signed copies of all three. They stay available to download from the Portal (Settings, Legal), along with every version you've accepted. You can also ask for them at privacy@shopandtable.com. This DPA binds both of us from the start of the Agreement, even if a signed copy isn't delivered.
Order of precedence. For the handling of personal data, this DPA controls over the Agreement. A law that requires different terms controls over both.
Definitions. Words not defined here have the meaning in the Agreement or in Privacy Laws.
| Term | Meaning |
|---|---|
| Client Personal Data | Personal data that we process on your behalf in providing the Services, mainly about your guests, customers, job applicants and staff |
| Privacy Laws | Every US federal and state law on personal data that applies to the processing. This includes the Connecticut Data Privacy Act (CTDPA); the California Consumer Privacy Act as amended (CCPA) and its regulations; the comprehensive privacy laws of Colorado, Virginia, Utah, Texas, Oregon, Montana, Iowa, Delaware, New Hampshire, New Jersey, Nebraska, Tennessee, Minnesota, Maryland, Indiana, Kentucky and Rhode Island; health-data laws such as Washington's My Health My Data Act; data-breach notification laws; and the GLBA, COPPA and TCPA where they apply |
| Processor and service provider | We are a "processor" under the CTDPA and similar laws, and a "service provider" under the CCPA |
| Controller and business | You are the "controller" under the CTDPA and similar laws, and the "business" under the CCPA |
| Subprocessor | A company we engage that processes Client Personal Data |
| Security Incident | A confirmed breach of security leading to the accidental or unlawful destruction, loss, alteration, or unauthorized disclosure of or access to Client Personal Data |
| De-identified Data | Data that can't reasonably be linked to a person or household, and that we hold under the safeguards required by CCPA § 1798.140(m) and the CTDPA's definition of de-identified data |
2. Roles and instructions
You decide; we act for you. For Client Personal Data, you are the controller and we are your processor and service provider. We process it only on your documented instructions. Those instructions are the Agreement, this DPA, the settings and features you choose in the platform, and other written instructions you give that are consistent with them. If we believe an instruction breaks a Privacy Law, we'll tell you, and we may decline to follow it.
When we're a controller. We are an independent controller for:
- information about you and your team as our customer: account, billing, support, sales and security records
- data we must handle for our own legal obligations, fraud prevention and security of the platform
- our own website and marketing
Our Privacy Policy covers that information, not this DPA.
Your responsibilities. You confirm, and will keep true, that:
- Notice. You give guests and other people the notices Privacy Laws require. That includes a privacy policy on your sites and apps that describes your use of our Services. We provide a template, but it's your responsibility.
- Lawful basis and consent. You have every consent and right needed for us to process Client Personal Data as you instruct. That includes prior express written consent for marketing texts and calls, consent for any contacts you upload, and consent for sensitive data where a law requires it.
- Opt-outs and rights. You honor opt-outs, including universal opt-out signals such as Global Privacy Control, and answer guests' requests within the legal deadlines. The platform's tools help you do both.
- Settings are your choices. Choices you make in the platform are your instructions and your responsibility. Examples include turning on advertising measurement, uploading contacts, setting retention, using hiring tools, or switching on automated features such as auto-send answers, standing post approval or order-issue rules.
- No prohibited data. You don't send us data the Services aren't built for, such as Social Security numbers, full payment card numbers outside the payment fields, bank account details, medical records, biometric data, precise location for marketing, or data about children under 13, except through features designed for that purpose.
- Your own processors. You're responsible for apps, agencies and other services you connect or invite, other than our Subprocessors.
You will compensate us for claims, fines and losses caused by your breach of this section, as the indemnity in the Agreement provides.
3. Our commitments
Purpose. We process Client Personal Data only for the business purposes in Annex A, to provide, secure, support and improve the Services for you, and as the law requires.
We will not :
- sell Client Personal Data, or share it for cross-context behavioral advertising (targeted advertising) on our own behalf
- keep, use or disclose it for any purpose other than the business purposes in this DPA, including any commercial purpose of our own, or outside our direct business relationship with you
- combine it with personal data we receive from or on behalf of another client, or that we collect from our own dealings with a person, except as CCPA regulations § 7050(a) allow, for example to detect security incidents or fraud. Even then, we never use one client's records for decisions about a guest at another client
- use it to train, fine-tune or improve AI models. Our AI providers are contractually barred from training on it
- attempt to re-identify De-identified Data
Advertising measurement on your instruction. If you turn on advertising measurement, we send conversion events for guests who agreed to marketing cookies to your own ad accounts, as our Privacy Policy describes. Those events include the order value and items, and the guest's email, phone and name, hashed before they reach the ad platform. You instruct this, and it's your disclosure to your ad platforms. We never send events for guests who opted out of sale or sharing, or whose browser sends Global Privacy Control or Do Not Track. Each client's events go only to that client's accounts.
Confidentiality. Everyone we authorize to process Client Personal Data is bound by a duty of confidentiality and gets access only as their role needs.
Same protection. We give Client Personal Data the level of privacy protection Privacy Laws require of you, and we'll tell you within 5 business days if we decide we can no longer meet our obligations. You may then take reasonable and appropriate steps to stop and fix any unauthorized processing, including suspending the affected processing.
Help with compliance. We'll give you the information you reasonably need to show compliance with Privacy Laws, and help you with data protection assessments where processing calls for one.
What we may do with data, within these limits. As Privacy Laws allow a processor or service provider, we may use Client Personal Data to:
- keep the Services secure and prevent fraud, abuse and illegal activity, using each client's records separately
- debug and repair the Services
- build and improve the Services, without building profiles of individuals for another client or ourselves
- create De-identified Data and aggregated statistics from many clients, such as pooled benchmarks of at least 5 businesses, never split by city. These never identify a person or a client. You can opt out of pooled benchmarks in Settings; you then neither contribute nor receive them
- comply with the law, legal process and our legal obligations
Sensitive data. The platform handles certain sensitive data only through features built for it:
- A guest's saved diet and allergy preferences are stored only with the guest's separate consent, encrypted, unreadable by you or your staff, and never used for marketing or targeting.
- Per-order allergy notes go only to the kitchen and are deleted 30 days after the order.
- Precise location is used only for the purpose the guest tapped it for.
- Drivers' location is shared only during a delivery.
Hiring tools. If you use our hiring tools, you're the employer and the decision-maker. Scores and summaries assist a person at your business. They never decide alone. You're responsible for notices, consent and audits that hiring laws require of employers, such as New York City's Local Law 144, Illinois' amended Human Rights Act, California's automated-decision regulations and Colorado's AI Act.
4. Security and incidents
Safeguards. We keep administrative, technical and physical safeguards appropriate to the risk, including those in Annex B. We review them at least once a year, and may update them as long as protection doesn't decrease. You're responsible for your side: secure sign-ins, two-step sign-in, removing staff who leave, and the devices and networks you use.
Security Incidents. If we confirm a Security Incident, we will:
- tell you promptly after discovering it, as Conn. Gen. Stat. § 36a-701b requires of a business that holds data for another, and in any event within 72 hours of confirming it, at your account's legal-notice email
- tell you what we know: what happened, what data and how many people are likely affected, what we're doing, and who to contact. We'll add details as we learn them
- take reasonable steps to contain it, investigate and reduce harm
- help you meet your own notice duties, for example by providing the facts you need for notices to people, regulators or the Connecticut Attorney General
Unless the law requires otherwise, you decide whether and how to notify affected people and regulators, and we won't name you publicly without your consent. If we're the one notifying, we'll coordinate the wording with you. Our notice of an incident isn't an admission of fault.
Costs. If an incident is caused by our breach of this DPA, we'll reimburse your reasonable, documented costs of the notices the law requires and of credit monitoring where the law or regulators require it, within the liability terms of Section 7. Otherwise each party bears its own costs.
Incidents on your side. This section covers incidents originating in systems under our control. Incidents arising from your staff, credentials, devices, accounts, connected apps, or data after it is exported are yours to handle, as Section 6.17 of the Platform Services Agreement provides. We'll still cooperate reasonably.
Unsuccessful attempts don't count as incidents. These include pings, scans, blocked sign-ins and denial-of-service attempts that don't compromise data.
5. Subprocessors
You authorize us to use the Subprocessors listed here and on our AI & Vendor Disclosure, which is kept current. We sign a written contract with each one that is at least as protective as this DPA for the data it handles, and we remain responsible to you for their work.
| Purpose | Subprocessors | Data location |
|---|---|---|
| Database, storage, hosting, background jobs | Supabase, Vercel, Inngest | US (production database in Ohio) |
| Purpose | Subprocessors | Data location |
|---|---|---|
| Security and bot checks | Cloudflare (Turnstile), Google (Web Risk) | US / global edge |
| Product analytics | PostHog | US |
| Payments (in your own accounts) | Square; Stripe (backup payments); Shopify (if connected) | US |
| Texting and calls | Telnyx (with Deepgram for speech), Twilio (backup), Amazon SNS | US |
| Resend, Amazon SES | US | |
| Push notifications and app builds | Google Firebase, Expo | US |
| AI features | Anthropic, OpenAI, Google (Gemini, paid tier), via Vercel AI Gateway | US |
| Delivery and shipping | Shipday and its couriers (DoorDash, Uber, Grubhub, Roadie, Stuart, Zifty); KitchenHub; Shippo and its carriers | US |
| Maps and places | Mapbox, Google (Places, Maps) | US |
| Wallet passes and sign-in | Apple, Google | US |
| Reviews, listings and social publishing | Synup, Zernio (also your ad measurement and calendar connections) | US (Synup); Spain (Zernio) |
| Support | Google Workspace, Slack | US |
| Printing and fulfillment | Gelato, Cloudprinter | Netherlands (Cloudprinter); the print location's country (Gelato) |
| Email verification | MillionVerifier, Bouncer | As listed in the AI & Vendor Disclosure |
Services you choose to connect, such as your own Google Analytics, Microsoft Clarity or ad accounts, are your vendors, not our Subprocessors.
New Subprocessors. We'll give at least 30 days' notice before a new Subprocessor processes Client Personal Data. We'll update the disclosure page and email your legal-notice address, or notify you in the portal. You may object in writing within that period on reasonable data-protection grounds. We'll then work with you in good faith on an alternative. If we can't resolve your objection, you may end the affected Services on written notice without an Early Termination Fee. That is your sole remedy. In an emergency, for example to replace a failing provider, notice may be shorter, and we'll tell you as soon as we can.
6. Requests, reviews, location and deletion
People's requests. The platform lets guests opt out, get a copy of their information, correct it and delete their account themselves, and it honors Global Privacy Control automatically. If we receive a request about Client Personal Data directly, we'll send it to you or tell the person to contact you. We won't answer it ourselves unless
you ask us to or the law requires it. We'll help with requests the tools don't handle, by appropriate technical and organizational means, within 10 business days of your written request.
Showing compliance. Once a year, or after a Security Incident, or when a regulator asks, we'll answer your reasonable written security and privacy questionnaire and provide our current security summary. If that isn't enough to show compliance with a Privacy Law, you may have an independent auditor, bound by confidentiality, assess our compliance. Assessments are held at most once a year, with 30 days' notice, during business hours, without access to other clients' data or to systems that would compromise their security. You pay for them unless they find we materially broke this DPA. Instead, we may give you a report from a qualified independent assessor using an appropriate framework, at our own cost, and the CTDPA allows this.
Where data is kept. Client Personal Data is stored in the United States (our production database is in Ohio). A few Subprocessors process limited data outside the US, as the table above and our AI & Vendor Disclosure show: Zernio in Spain and Cloudprinter in the Netherlands. They do so under contracts with the safeguards the law requires. We'll list any new location before it's used.
Government requests. If we receive a legal demand for Client Personal Data, we'll send the demand to you where we can. If we must respond, we'll tell you first unless the law forbids it, and disclose only what's required.
Exports and portability. You can export your business data at any time from the portal: customers, consents, orders, rewards, gift cards, menus and content, in common machine-readable formats (CSV or JSON). Exports of guest data are logged with who made them and when. Once exported, the data is your responsibility under Privacy Laws.
Return and deletion when the Agreement ends. You have 60 days to request your export (Platform Services Agreement § 4.7), and exports are never withheld, even in a payment dispute. After that window we delete Client Personal Data from active systems within 30 days, and from backups within 90 days as they rotate out. Until deletion, it stays protected by this DPA. We keep only what the law requires, such as invoices, tax records, consent and opt-out records, and records needed for open disputes or legal claims. We keep those only as long as required, under this DPA's protections. On request, we'll confirm the deletion in writing.
7. Liability, term and general
- Liability. Each party's liability under this DPA is subject to the limits and exclusions in the Agreement, and the Agreement's cap covers this DPA and the Agreement together. Nothing in this DPA limits a party's liability that the law doesn't allow to be limited, or your liability for your own breach of Section 2 or of Privacy Laws.
- Changes in law. If a Privacy Law requires changes to this DPA, we may update it by giving 30 days' notice, and the update will be no less protective of personal data. You may object as Section 5 describes.
- Term. This DPA lasts as long as we process Client Personal Data. Sections 3, 4, 6 and 7 continue to apply after the Agreement ends, for as long as we hold any Client Personal Data.
- Notices. Notices go to the legal-notice contact in your account and to legal@shopandtable.com, with privacy questions to privacy@shopandtable.com.
- Law. The Agreement's governing law and dispute terms apply.
Annex A: Details of processing
| Nature and purpose | Providing the Services the Client chooses: websites and apps; ordering, payments and receipts; pickup, delivery and shipping; loyalty, memberships, gift cards and store credit; events and tickets; bookings and catering; texts, email and push; inbox, AI phone agent and chat; reviews and social publishing; marketing campaigns and advertising measurement the Client turns on; hiring tools; kiosks, counter and kitchen screens; fraud prevention and dispute evidence; support, security and improvement of the Services |
|---|---|
| People | The Client's guests and customers, people who call, text or message the Client, subscribers, ticket holders, job applicants, staff and drivers |
| Types of data | Names and contact details; account sign-in data and passkeys; order, payment-token and delivery details (never full card numbers); addresses and tap-shared location; loyalty, gift card and credit records; messages, call recordings and transcripts; consent and opt-out records; birth month and day, and the 21-or-over result (never the birth year); reviews and photos; device, IP and fraud-check records; cookie choices; job applications and résumés |
| Sensitive data | Diet and allergy preferences, only with the guest's separate consent; per-order allergy notes; drivers' location during deliveries; applicants' data the Client asks for in hiring forms. Never Social Security numbers, health records, biometrics or financial account numbers |
| Duration | The term of the Agreement plus the export and deletion periods in Section 6, and the specific periods in the Privacy Policy. For example: call recordings 90 days, paid-order fraud records 13 months, allergy notes 30 days, consent records as long as the law requires |
| Instructions | The Agreement, this DPA, the platform settings the Client chooses and written instructions consistent with them |
Annex B: Security measures
- Access control. Personal accounts with two-step sign-in; least-privilege roles; access removed when a person leaves; administrative access logged and reviewed.
- Separation between clients. Every query is scoped to the client account, and the database enforces row-level security on every exposed table, with allow and deny tests for each policy.
- Encryption. TLS in transit; encryption at rest; sensitive guest preferences encrypted with a key held in a secrets vault that no client or team role can read.
- Payments. Card numbers are entered only into Square's or Stripe's fields and never touch our servers.
- Secrets and code. Credentials are kept out of code and rotated; code changes are reviewed; dependencies are monitored; webhooks are verified by signature and processed idempotently.
- Monitoring and resilience. Error and uptime monitoring; audit logs for sensitive actions, exports and deletions; backups with tested restores; an incident response plan, tested at least once a year.
- Personnel. Confidentiality agreements; security and privacy training; background checks where lawful.
- Vendors. Security and privacy review before onboarding, written contracts, and periodic re-review.
- Data minimization. Retention limits enforced by scheduled deletion jobs; fraud and dispute records kept for limited periods; no data collected for features a client hasn't turned on.

