Privacy notice
Tablescape Studio (“Tablescape”, “we”, “us”) is event planning software for event companies, planners and venues. It is run by The H Group LLC, doing business as Tablescape, in California. This notice explains what personal information we collect, why, who helps us handle it, how long we keep it and what you can ask us to do with it.
The short version
- We collect what event companies and their teams put into Tablescape, what their clients and guests send through the links those companies share, and the technical data needed to run the sites.
- We use it to run Tablescape. We do not sell personal information, we do not share it for advertising, and our sites have no advertising trackers and set no cookies.
- If you are a client, guest, vendor or staff member of an event company, that company decides what is collected about you. We handle it for them, as their service provider.
- You can ask to see, correct or delete your information by emailing hello@tablescape.vip. We answer within 45 days.
Who we are and who this covers
This notice covers our website at tablescape.vip, the Tablescape app at app.tablescape.vip, the pages the app makes for clients, guests, vendors, staff and valet guests, our developer tools (the API, the AI assistant connector and webhooks) and the emails Tablescape sends.
We play two roles:
- For our own customers and website visitors, we decide how personal information is used. This covers the event companies that use Tablescape, the people on their teams, and people who visit tablescape.vip or send us an inquiry.
- For an event company’s own clients, guests, vendors and staff, we act for that company as its service provider. The company decides what it collects and why. We use that information only to run Tablescape for that company, as our agreement with it requires (see For event companies and venues). The company’s own privacy notice explains how it uses your information, and it is the right place to start with a request.
Eventra, our rentals and logistics partner at eventra.vip, has its own privacy notice.
What we collect
These are the kinds of personal information Tablescape collects, with examples. Over the last 12 months we collected each kind for the purposes in How we use it. The California summary puts the same information in one table.
Account and workspace
- What
- The email address and password you sign in with (the password is stored only as a one-way hash by our sign-in provider), or, if you choose Sign in with Apple or Sign in with Google, the name, email address and account ID that Apple or Google shares with us (Apple lets you hide your email behind a private relay address); for Sign in with Apple we also keep a token from Apple, used only to disconnect Tablescape from your Apple ID when you delete your account; your mobile number, and whether you agreed to texts and calls with tips and offers (when, and the wording you saw); your company’s name, web address name, email and phone, the role of each team member, your time zone, your plan and trial dates, which version of our terms and this notice you agreed to, and when, and the IP address and browser of each sign-in, which our sign-in system records. When a workspace’s free trial starts, we also keep a keyed hash of the account’s mobile number (see How long we keep it).
- Kind under California law
- Identifiers; customer records; commercial information; internet or other electronic network activity; account login (sensitive).
Event plans and business records
- What
- Event names, dates and venues, floor plans and designs, menus, budgets, proposals, contracts and signatures, payment schedules and payment records, messages, notes, tasks, vendor and staff lists with names, phone numbers, shifts and pay rates, photos you upload such as dish or inspiration photos, and 3D venue scans. Payment records hold amounts, dates and the method name (for example “Zelle” or “Check”). Tablescape never asks for card or bank account numbers.
- Kind under California law
- Identifiers; customer records; commercial information; professional or employment information; photos and scans (visual information).
Clients
- What
- Names, emails and phone numbers, and what clients do on their private link: approvals, signatures, messages, change orders, changes to the guest list and invitation (including guests’ names, emails and phone numbers), inspiration they pin, a note that they have paid an installment (how they paid, such as “Zelle”, and an optional short note) where the company offers it, and feedback after the event. A client’s review is shown publicly only when the client allows it and the event company does not hide it.
- Kind under California law
- Identifiers; customer records; commercial information.
Guests
- What
- Names, households, emails and phone numbers, RSVP answers, meal and drink choices, dietary needs and allergies, accessibility needs (for example a wheelchair), a guest’s age or whether they are a child, song requests, table and seat, invitation and ticket status, and check-in at the door.
- Kind under California law
- Identifiers; age and disability (characteristics of protected classifications); dietary, allergy and accessibility notes, which can reveal health information (sensitive).
Valet parking
- What
- When an event company runs valet through Tablescape: the claim tag number, the car’s license plate, make, model and color, where it is parked, marks and photos of existing damage, a note, the name each attendant enters, and the times a car was checked in, requested and handed over. A guest who scans their claim tag can ask for their car from their phone; we record that request, not who made it.
- Kind under California law
- Identifiers (license plate); photos (visual information); professional information (attendants).
Inquiries
- What
- What someone types into an event company’s inquiry form, or ours: name, email, phone, type of event, date, guest count, budget, venue, how they heard about the company, and notes.
- Kind under California law
- Identifiers; commercial information.
Integrations
- What
- API keys (we keep only a one-way hash and the first characters, so you can tell which key is which), who made each key and when it was last used, webhook addresses and a log of webhook deliveries, and calendar feed links.
- Kind under California law
- Identifiers; internet or other electronic network activity.
Technical data
- What
- When your browser loads our sites, our hosting and database providers receive your IP address, browser type and the pages and data requested, and keep them in their logs. Cloudflare, our host, may also give us totals of page views, such as counts by page, country and browser; this sets no cookies and does not follow you to other sites. To stop abuse of public pages we keep short-lived counters made from a keyed hash of your IP address (made with a secret key kept in our database, so the address can’t be worked out from the hash without that key): when a guest searches for their name on an event website (with the time and whether a name was found), and when someone sends an inquiry form (with a keyed hash of the email address entered). See How long we keep it.
- Kind under California law
- Identifiers (an IP address, including in hashed form); internet or other electronic network activity.
Cookies and storage in your browser
Tablescape does not set cookies, and neither do our sites. The app keeps working copies of plans, your sign-in session and your preferences in your browser’s local storage, so it opens quickly and keeps working when the connection drops. It also keeps recent weather, map and song search results there for a while, and valet phones keep the night’s cars until 30 days after the event. Our website remembers whether you last looked at monthly or yearly prices. This information stays on your device, and you can clear it in your browser settings at any time.
The install code
If you use our phone app, it keeps a random install code so we can limit new accounts and free trials per device: two new accounts and one free trial on each device. On our website, the app keeps a code like it in your browser’s local storage. We store only a scrambled version of the code (a keyed hash), never the code itself and never your phone’s hardware or advertising ID. Signing in to an account you already have is never limited.
The door scanner
When an event’s staff scan entry tickets or valet tags, the app uses the phone’s camera only while the scanner is open. The camera picture stays on the phone; only the code it reads is used. Tablescape does not ask for your location.
Sensitive personal information
Account logins, and dietary, allergy and accessibility notes about guests, count as sensitive personal information under California law. We use them only to provide Tablescape: to sign you in and to show the event company and its venue and caterers what each guest needs. We do not use them to infer anything about anyone, and we do not sell or share them.
What we do not collect
We do not collect payment card or bank account numbers, government ID numbers, precise location, fingerprints, face scans or other biometric information, and we do not build profiles of people.
Where it comes from
- From you, when you create an account, use the app, fill in a form or reply through a link.
- From an event company and its team, when they enter details about their clients, guests, vendors, staff and valet guests’ cars.
- From a company’s clients, who can add guests and their contact details to the guest list from their private link.
- From your device, automatically, as described under technical data.
How we use it
- To provide Tablescape: save and sync plans, show each person only the pages their link allows, and run the features a company turns on.
- To sign people in and keep accounts secure. When you choose a new password, the app checks it against a list of passwords exposed in data breaches (see Have I Been Pwned).
- To send the emails Tablescape sends: sign-in emails such as password resets, alerts the company’s team turns on (new inquiries, client activity, RSVPs, a morning summary), and, when a company turns them on, payment reminders to its clients, RSVP reminders to its guests and an automatic reply to a new inquiry.
- To answer questions and give support.
- To reach you by phone or text about your account and support, and to allow one free trial per phone number. Only if you tick the separate box when you give us your number do we also text or call you with tips and offers. You can stop them at any time by replying STOP or by emailing hello@tablescape.vip.
- To prevent abuse: rate limits on public forms and links, and spam checks.
- To fix problems, keep records of what you agreed to, and meet our legal obligations.
Apart from the texts and calls you can opt in to above, we do not use personal information for marketing or advertising, we do not build profiles of people, and we do not use your content to train AI models. We do not make decisions about people by automated means that have legal or similarly significant effects.
AI assistants
Tablescape has no built-in AI features, and it does not send your information to an AI provider on its own. Our connector lets an event company link an AI assistant, such as Claude or ChatGPT, to its workspace with an API key the company creates. When it does, the assistant can read, and if the key allows, add to the company’s events, and the assistant’s provider handles that information under its own terms. Each company decides whether to connect one, and can revoke the key in the app at any time.
Who helps us run Tablescape
Our service providers
These companies run parts of Tablescape for us and receive personal information only as needed for their service.
Supabase
- Does
- Our database, sign-in and file storage, the server functions behind emails, calendar feeds and the API, and the sign-in emails such as confirmations and password resets. Our database is in Supabase’s us-west-1 region, in Northern California.
- Receives
- Everything stored in Tablescape, and request data such as IP addresses.
Cloudflare
- Does
- Hosts tablescape.vip and app.tablescape.vip, protects them from attacks, and passes API and AI assistant requests to our database.
- Receives
- Request data such as IP addresses and browser type, and the content of the requests it passes on.
Fastmail
- Does
- Sends Tablescape’s alert, reminder and automatic reply emails, once email alerts are turned on.
- Receives
- Each email’s recipients and content.
Services your browser contacts directly
Our pages load fonts, code libraries and a few lookups straight from these services. When they do, your browser sends them your IP address and browser details, and each service handles that under its own terms and privacy policy, not under an agreement with us. Tablescape does not send them names or contact details.
Google Fonts, jsDelivr and cdnjs
- Does
- Serve the fonts and some of the code libraries the pages use.
- Receives
- Request data such as IP addresses and browser type, when your browser downloads these files.
Open-Meteo, OpenStreetMap and Nager.Date
- Does
- Weather, sunset times and place search (Open-Meteo), street address lookups and the small maps on event websites and vendor sheets (OpenStreetMap), and public holidays (Nager.Date).
- Receives
- The venue’s place name, address or map position, or the country and year, plus request data such as IP addresses.
Apple and Google sign-in
- Does
- Confirm who you are when you choose Sign in with Apple or Sign in with Google. You sign in on Apple’s or Google’s own screen; we never see that password.
- Receives
- That you are signing in to Tablescape, plus request data such as IP addresses. They tell us your name, email address and an account ID, and nothing else from your Apple or Google account.
Apple (iTunes Search)
- Does
- Song suggestions and previews when someone searches for a song.
- Receives
- The search words, plus request data such as IP addresses.
Have I Been Pwned
- Does
- Tells the app whether a new password has appeared in a known data breach.
- Receives
- Only the first 5 characters of a one-way hash of the password, never the password itself, plus request data such as IP addresses.
Paying for a plan. Today we arrange payment for Tablescape plans directly with each company and record the plan by hand. We do not store card numbers. If we add card payments for plans, we will name the payment processor here before it starts.
We may also disclose personal information when the law requires it, to protect the rights, safety or property of people or of Tablescape, or as part of a merger, sale or transfer of our business, in which case this notice keeps applying to the information transferred.
Places you choose to send it
- Links you share. Client, guest, vendor, staff, valet and event website links are private addresses. Anyone who has one can open its page, so share them only with the people they are meant for.
- AI assistants, the API and webhooks. When a company connects an AI assistant, uses the API, or sets up a webhook (for example to Zapier), Tablescape sends the requested event information to that service. Those services handle it under their own terms.
- Calendars. A calendar feed link sends event dates and details to the calendar app that subscribes to it.
- Eventra. When a planner sends a request to Eventra, our rentals and logistics partner at eventra.vip, or a client does so from their link (only if the company turns that on), the event details and contact details in the request go to Eventra. Eventra’s own privacy notice covers what it does with them.
- Payment pages. If an event company adds its own payment links (for example Stripe, Square, PayPal, Venmo or Cash App), its clients see them on their client link. Tapping one opens that company’s page at the payment service, which handles the payment under its own terms. Tablescape does not receive the payment or the card or bank details used for it.
- Maps, calendars and messages. Buttons such as Directions, Add to calendar and WhatsApp open Google Maps, Google Calendar, Outlook or WhatsApp with the details filled in, only when someone taps them.
No selling, no sharing, no ads
We do not sell personal information, and we do not share it for cross-context behavioral advertising, as California law defines those terms. We have not done either in the last 12 months, including for consumers under 16. Our sites have no advertising trackers, and we do not let other companies collect information about your activity on our sites to follow you across other sites. We do not give personal information to other companies for their own direct marketing, and we offer no financial incentive in exchange for personal information.
Because we do not sell or share personal information, there is no “Do Not Sell or Share My Personal Information” switch to offer. If that ever changes, we will update this notice first and give you a way to opt out before it starts.
California summary
The categories California law asks us to list, for the last 12 months. “Service providers” means the companies in Our service providers, each only for its own service. “Services your browser contacts” means those in Services your browser contacts directly, which receive request data only.
| Category | Examples | Disclosed for a business purpose to | Sold or shared |
|---|---|---|---|
| Identifiers | Names, emails, phone numbers, IP addresses (also as keyed hashes), account and API key identifiers, license plates | Service providers; the event company the information belongs to; Eventra, when a planner or client sends it a request; services a company connects; services your browser contacts (IP addresses) | No |
| Customer records | Contact details, signatures, payment records without card or bank numbers | Service providers; the event company | No |
| Characteristics of protected classifications | A guest’s age or child status; accessibility needs | Service providers; the event company | No |
| Commercial information | Plans and trial dates, proposals, budgets, payment schedules, inquiries | Service providers; the event company; Eventra, when a planner or client sends it a request | No |
| Internet or network activity | Request logs, sign-in records, page view totals, API and webhook logs | Service providers; services your browser contacts | No |
| Visual information | Uploaded photos, 3D venue scans, valet damage photos | Service providers; the event company | No |
| Professional or employment information | Team roles, staff shifts and pay rates, attendant names | Service providers; the event company | No |
| Sensitive personal information | Account logins; guests’ dietary, allergy and accessibility notes | Service providers; the event company | No |
Sources are in Where it comes from, purposes in How we use it and periods in How long we keep it. We do not collect biometric information, precise location, education records or inferences about people.
How long we keep it
- Your workspace (your account, events, inquiries, clients and guests) stays while your account is active.
- When a free trial or a paid plan ends, your workspace moves to the Free plan and keeps all its data. Nothing is deleted because a trial or plan ended.
- Closing your account. You can delete your account in the app, under Your account, or by emailing us. Your sign-in is deleted right away, along with any workspace only you belong to; a workspace you share is handed to the teammate you choose, or deleted for everyone if you choose that. Export what you want to keep first.
- Free-trial record: when a workspace’s free trial starts, we keep a keyed hash of the account’s mobile number (made with a secret key kept in our database, so the number can’t be worked out from it without that key). It stays after the account is closed, so each number gets one free trial. The number itself is deleted with your account.
- Device record: the keyed hash of an install code, with the new accounts and the free trial it was used for. It stays after an account is closed, so closing accounts doesn’t reset a device’s limit; which account it was is removed.
- Things you delete, such as an event, leave the live database right away. Queued emails tied to a deleted event, such as its alerts and reminders, are deleted by the next daily cleanup; other copies, such as the event’s name in a morning summary email, leave on the email queue schedule below.
- Links stop working on a schedule: event websites 60 days after the event, staff links and entry tickets 7 days after.
- Valet parking records (plates, cars, damage notes and photos, and the night’s log) are deleted 30 days after the event day. An owner or admin can delete one car’s record sooner.
- The email queue: an email Tablescape has sent is deleted from the queue 30 days after it was sent. An email that could not be sent is deleted 90 days after it was queued.
- Updates waiting for your team: what people send through shared links and the API, such as guest replies, client messages, approvals, signatures and “I’ve paid” notes, website song requests, staff check-ins and new guests, waits in a queue until your team’s app adds it to the event. Once it has, the queued copy is deleted when it is 90 days old, and the event keeps what was added. A queued update your team’s app has not added yet is never deleted automatically.
- Abuse counters: the hashed records of event website name searches and of inquiry form sends are deleted once they are an hour old.
- Team invitations: an invite link, and the email address it was for, is deleted 90 days after it was used or expired.
- Other records: webhook delivery logs are deleted when they are 30 days old, and API usage counts when they are a day old. The record of which reminders went out is kept for 400 days, so nobody gets the same reminder twice.
- Sign-in records: our sign-in system’s log of sign-ins, sign-ups and password resets, with the IP address of each, is deleted when it is 90 days old. The record of a device that is still signed in, with its IP address and browser, stays until that device signs out or the account is closed.
- When these deletions happen: an automatic cleanup runs once a day (the inquiry form counters once an hour), so each item above is deleted within a day after its period ends.
- Logs at our providers, such as request logs at Supabase and Cloudflare, are kept for the period set by our plan with each provider, and then the provider deletes them. We do not copy them into Tablescape.
Your rights and how to ask
If you live in California, you have the right to:
- Know what personal information we collect about you, where it comes from, why we use it and who we disclose it to, and get a copy of it in a portable format.
- Delete personal information we collected from you, with some legal exceptions (for example records we must keep).
- Correct personal information that is wrong.
- Opt out of the sale or sharing of your personal information. We do neither, so there is nothing to opt out of.
- Limit the use of sensitive personal information. We use it only to provide Tablescape, as the law allows.
- Not be treated differently for using any of these rights. We will not deny you service, charge you a different price or give you a lower level of service because you made a request.
We offer the same choices to everyone, wherever they live.
How to ask
Email hello@tablescape.vip or write to The H Group LLC, doing business as Tablescape, PO Box 1177, Yorba Linda, CA 92885. Tell us what you are asking for and the email address or event your request is about. In the app, every team member can see their workspace’s information, and owners, admins and planners can correct most of it. Owners and admins can also delete events and download a backup that saves every event, guest list and company setting to one file. Other team members can ask their owner for a backup, or email us.
We confirm we have your request within 10 business days and answer within 45 calendar days of receiving it. If we need more time, up to another 45 days, we tell you why within the first 45. To protect you, we check that a request really comes from you, usually by writing to the email address we have for you, and we ask only for what we need to do that. You can ask someone to act for you; we will ask for your signed permission and may check your identity with you directly. If we cannot do all of what you ask, we tell you why.
If an event company holds your information
If you are a client, guest, vendor or staff member of an event company, that company controls your information in Tablescape. Please contact the company first. If you write to us, we will pass your request to the company and help it answer.
Global Privacy Control
We honor the Global Privacy Control (GPC) signal. If your browser sends it, we treat it as a valid request to opt out of the sale and sharing of your personal information. Since we do neither, honoring it changes nothing about how our sites work today, and we will keep honoring it if our practices ever change. Some browsers also send a “Do Not Track” signal; we do not track visitors across other sites, so our sites work the same either way.
For event companies and venues
An event company or venue that uses Tablescape decides what it collects about its own clients, guests, vendors, staff and valet guests, and why. For that information the company is the business in charge of it (often called the controller), and Tablescape is its service provider (often called the processor). Our terms of service set out what we promise as a service provider. In short, we:
- use that information only to run Tablescape for the company, keep it secure, fix problems and meet our legal obligations;
- never sell it, never share it for advertising, and never combine it with information from other companies or sources except as the law allows a service provider to;
- pass it only to the companies listed in Our service providers, for their part of the service;
- help the company answer requests to see, correct or delete it, and tell the company if we can no longer meet these promises;
- delete it on the schedule in How long we keep it, or when the company deletes it or closes its account.
The company is responsible for giving its own privacy notice and for any consent the law requires. The inquiry form, RSVP page and client page that Tablescape makes for a company say that the company receives what is sent there and that Tablescape runs the page for it.
Children
You must be 18 or older to create a Tablescape account. Tablescape is a tool for businesses and is not meant for children. We do not knowingly collect personal information directly from children under 13, and we do not sell or share the personal information of anyone, including consumers under 16.
Event companies sometimes enter information about guests who are children, for example the court at a quinceañera or a child who needs a kids’ meal, and a parent or guardian may answer an invitation for the family. We handle that information only for the event company, as described above. The company is responsible for any permission the law requires. If you believe a child under 13 has given us personal information directly, email hello@tablescape.vip and we will delete it.
Where your information is stored
Tablescape is run from California. Our database and file storage are in the United States, in Supabase’s Northern California region. Cloudflare and the services your browser contacts directly answer each visitor from data centers around the world, close to where the visitor is.
If you use Tablescape from outside the United States, your information is transferred to, stored in and processed in the United States, where privacy laws may differ from those where you live. We protect it as this notice describes wherever it is handled.
Security
Tablescape uses encrypted connections (HTTPS) everywhere, keeps each company’s data apart with database access rules, stores passwords and API keys only as one-way hashes, and gives each guest, vendor, staff and valet link its own code. Removing a team member revokes their API keys and webhooks. Uploaded 3D venue scan files work like share links instead: each one is stored at its own hard-to-guess web address, and anyone who has that address can open the file. No system is perfectly secure. If we learn of a breach that affects your personal information, we will tell you, and the event company concerned, as the law requires.
Changes to this notice
When we change this notice, we post the new version here with a new version number and date. If a change is significant, we tell account owners by email or in the app before it takes effect. If we ever want to use personal information in a way this notice does not describe, we will ask first.
- Version 1.4
- No change to this notice. Its version number follows the terms, which changed.
- Version 1.3
- When a trial or paid plan ends, the workspace now moves to the Free plan and keeps its data; the one-year deletion after a trial or plan ends is gone. The inquiry form’s keyed counters are now described.
- Version 1.2
- First published version.
Contact us
The H Group LLC, doing business as TablescapePO Box 1177
Yorba Linda, CA 92885
hello@tablescape.vip
For privacy requests, write “Privacy request” in the subject line so it reaches the right person quickly.