Privacy Policy for Tableful

Effective date: September 1, 2026 · Last revised: October 6, 2026

At Tableful (https://tableful.club), one of our main priorities is the privacy of our visitors and users. This Privacy Policy describes what information Tableful collects, how we use it, what we share and with whom, and the choices you have. Questions: support@tableful.club.

1. The identity ladder — what we collect depends on how you use Tableful

Tableful is designed so you can do more with less identity. What we collect scales with what you do:

Browsing (no account) — Browse public events, venues, and hosts. Collects: Standard log/device data (IP, browser type, timestamps, pages visited); analytics identifiers (cookies).

Shadow RSVP (no password) — RSVP to casual events; retrieve tickets by code. Collects: Email (required), phone (only if the host requires it), a device token so your RSVPs persist until you claim the account.

Guest checkout (no password) — Buy a seat or table without creating a login. Collects: Ticket name + email (always); phone and other host-required fields; payment identity via Stripe (we never store full card numbers). We mint a shadow record on that email so tickets and refunds work, and so a later sign-in with the same verified email can claim the orders.

Verified account — Request to join hosted tables; likes, comments, messages; save events. Collects: The above plus name/display handle, profile details you choose to add, optional photo/bio/social handle for vetted offers.

Full account (host / earn / Connect) — Host; earn payouts; link music apps when that feature is on. Collects: The above plus transaction history, and — for hosts/promoters earning payouts — identity verification and tax information collected by Stripe Connect (KYC).

You may claim a shadow account into a full account at any time; claiming merges its history.

2. Information we collect in detail

Account and profile data: name, email, optional phone, birthday/age (legal eligibility and categorization), gender (optional, editable), profile photo and bio (photos are moderated before public display).

Social login data: if you sign in with Google, Apple, or Facebook, we receive the identifiers and profile fields you authorize (for Facebook: ID, name, email, gender, birthday — used to build your profile; editable afterward; not continuously re-synced). To remove Facebook-linked data, email us with subject "Facebook Data Removal Request."

Transaction data: purchases, amounts, offers, seats, refunds, payout and commission records for earners. Optional tips (when tipping is on): amount, destination (servers/venue pool vs Tip Tableful), and payout status. Instant pay memos (when Instant is on) are unique references so ops can match a Zelle / Cash App / Venmo send. Production may keep tips and Instant off; we do not claim they are live on production in this policy.

Event and social activity: RSVPs, table requests and approvals, reviews and ratings, messages you send through the platform, check-ins and redemptions at events.

Communities (hubs): hub membership, join proof (such as a school email domain), maintainer role, and member-board posts. Public directory pages show hub name, kind, city, and tagline, not your private proof.

Connect Music (when you link an app; production still coming): which provider you connected, encrypted tokens, and artist or channel keys we sync for night matching (Spotify top/saved/followed artists if that flag is on; Apple Music library artists; SoundCloud follows/likes; Tidal favorite artists; YouTube subscriptions and liked-video channels). Not every song you play. Not YouTube watch history.

Upload scans: image bytes sent to NSFW vendors at upload time; a small operations record of flagged or blocked scans. Photos you upload are scanned for NSFW content.

Location: approximate location (derived from IP) and, if you grant it, device location — used for city/near-me discovery and map search.

Device and push data: device tokens for web push notifications (only if you opt in).

Usage and diagnostics: cookies, pages, clicks, latency and performance traces, and error reports via Google Analytics (G-669BLH6B84), Amplitude, and Sentry.

Log files: standard hosting logs (IP, ISP, timestamps, referring/exit pages), not linked to personally identifiable information.

3. How we use information

To operate the Services (bookings, thresholds, escrow-style holds, payouts); to coordinate events (including sharing entry information with venues — see §4); to power discovery and search; to prevent fraud and enforce safety (rate limits, repeat-offender detection, moderation); to communicate with you (transactional messages always; marketing only with consent); to analyze and improve performance; and to comply with law.

Payment-rail and invoice records — which rail was chosen, amounts owed, the 14-day grace, the 4% step, and the 50/50 split — are kept so payouts can run. Tableful holds those records as intermediary only.

4. What we share, and with whom

Venues: when you purchase or hold a confirmed seat, the venue receives the names of attending guests for entry (disclosed at payment time), plus check-in/redemption status for included items. Venues are independent controllers of what happens on their premises.

Hosts: hosts see the profile tier appropriate to their offer's commitment preset (open offers: minimal; request-and-approve: basic profile; vetted: photo/bio/social handle you provided). Guest-to-guest ratings are private: never public, visible only to premium hosts for vetting and to Tableful for safety.

Promoters/collaborators: attribution and earnings data needed to pay commissions.

Service providers (processors): Stripe (payments, Connect KYC, Transfers), Clerk (authentication), Neon (database), Vercel (hosting), Sentry (error monitoring), Google Analytics and Amplitude (analytics), Resend/Courier/Twilio (email/SMS/push delivery), OpenRouter (AI concierge processing; prompts are not used to identify you), Sightengine and Amazon Rekognition (image NSFW verdicts).

Music providers you Connect: Spotify, Apple, SoundCloud, Tidal, and/or Google (YouTube), only after you authorize that app. They process the OAuth or MusicKit handshake under their own policies. We do not sell your music graph.

FAST gifts: if a host lists Cash App / Venmo / Zelle handles, you pay that organizer off Tableful. We may store the handles they published and an honor-system “I sent a gift” mark. We do not receive those gift funds.

Legal: where required by law, or to protect rights, safety, and the integrity of the Services. We may provide transaction-related information to law enforcement in connection with investigations.

We do not sell your personal information, and we do not share it for cross-context behavioral advertising.

A note on third-party cookies: if third-party ad servers or networks ever serve content or links on Tableful, their cookies/JavaScript/beacons are governed by their own policies, which Tableful does not access or control; consult those policies for opt-out instructions.

4a. YouTube API Services (Limited Use)

Tableful uses YouTube API Services when you Connect YouTube. Google’s consent screen (and our Connect YouTube start copy) describe the access we request. We request only the read-only scope youtube.readonly: subscriptions and the channels of videos you have liked, so we can suggest nights for you. We store encrypted access and refresh tokens plus those channel keys. We do not collect YouTube passwords, watch history, comments, or upload rights, and we do not request write scopes.

How we use, process, and share that API Data: internally, to suggest nights to you. Processors that host our app (currently Neon and Vercel) store the encrypted tokens and keys. We do not sell YouTube data. We do not use it for advertising or for purposes unrelated to those night suggestions. We do not allow third parties to serve advertisements from this YouTube data. Hosts do not receive a listening diary. They see music taste only if you send a Request and you have chosen to make that taste visible. Guests control public versus private, including music taste. Tableful matching of other people to your graph is later.

Tableful's use of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Cookies we set are described in this Privacy Policy. Google may set its own cookies on Google’s pages during sign-in. Tableful does not place advertising pixels from YouTube API Data.

In addition to disconnecting on Account preferences (which drops stored YouTube tokens and stops refresh, and keeps channel keys until you remove them), you can revoke Tableful’s access at Google’s security settings page: https://security.google.com/settings/security/permissions. Questions or complaints about these privacy practices: support@tableful.club. Google’s Privacy Policy: http://www.google.com/policies/privacy. YouTube’s Terms of Service: https://www.youtube.com/t/terms.

4b. Connect Music (production still off)

Connect Music on production stays off until we enable it. Staging may already let you link apps when secrets are present. Spotify guest Connect stays behind its own flag even after that. Disconnect clears stored tokens and keeps synced artist or channel keys until you remove them on Account preferences. YouTube Authorized Data is also revocable at Google’s security settings page. Guests control public versus private, including music taste. Hosts do not get a music-taste filter. They see that taste only through a Request you send, and only if you chose to share it. Tableful matching of other guests to your music graph is later. This is not a host-facing listening diary.

4c. Other music apps you may Connect

When you Connect a music app, we access only the surfaces listed here, after you authorize that app, and only to suggest nights to you. We do not sell the graph. Contact: support@tableful.club.

Spotify (when that flag is on): top, saved, and followed artists via the scopes named on Spotify’s consent screen. Not every play. Collection and use follow this Privacy Policy, including cookies (§2 usage/diagnostics and the cookie note in §4). Disconnect on Account preferences keeps keys until you remove them.

Apple Music: library artists via MusicKit (Music User Token). Apple’s authorization sheet states the purpose. Favorites for matching, not a listening diary.

SoundCloud: follows and likes needed to operate Connect. We do not harvest emails or credentials. SoundCloud Personal Data is processed under this Privacy Policy; we request only what Connect needs.

Tidal: favorite / collection artists and the user-read scopes named on Tidal’s consent screen. This Privacy Policy is the notice shown before we request that access.

5. Your choices and rights

Access, correction, deletion: edit profile fields in the app; request export or deletion at support@tableful.club. Deletion removes your profile and personal data except records we must retain (transaction/tax records, safety and fraud-prevention logs, legal holds). Disconnect Music on Account preferences stops refresh and drops tokens; you can also remove previously set artist or channel keys there.

Connect / Stripe: hosts manage Stripe Connect from Getting paid / payouts. Guests manage music links on Account preferences when that feature is offered.

Marketing opt-out: every marketing message includes unsubscribe; event-related transactional messages continue while you hold active bookings.

Push and location: controlled in your device/browser settings.

Cookies: manageable through your browser; disabling some cookies may limit features.

California residents (CCPA/CPRA): you have the right to know, access, correct, delete, and to non-discrimination. We do not sell or share personal information as those terms are defined by the CPRA. Submit requests to support@tableful.club; we verify using your account email.

Other regions: where local law grants additional rights (e.g., EEA/UK GDPR), we honor them; contact us to exercise them.

6. Retention and security

We retain account and transaction data while your account is active and as required for tax, accounting, dispute, and safety purposes (payment and payout records are retained per financial regulations). We use encryption in transit, access controls, and least-privilege secrets management. No system is perfectly secure; we will notify affected users and regulators of breaches as required by law.

7. Children's privacy

The Services are not directed at children. We do not knowingly collect personal information from anyone under 13. Accounts, self-RSVPs, and purchases require the actor to be 18+ (we may collect birthday and/or an age attestation to enforce this). An adult may purchase and assign or send a seat to a younger attendee where the event allows; that attendee is not the account buyer. Alcohol-inclusive offerings and venue door rules may require 21+ in the U.S. — those remain host/Venue Spec Sheet rules, not a second account age. Users under 18 are never shown adult-tagged content. If you believe a child provided us information, contact us and we will promptly remove it.

8. Scope; third parties; changes

This policy covers our online Services only — not information collected offline or by venues, hosts, advertisers, or linked third parties under their own policies (review e.g. Google's policy at https://policies.google.com/privacy). We may update this policy; material changes will be posted here with a new revision date, and continued use constitutes acceptance.

Contact: support@tableful.club · Tableful · Hollywood, CA 90028