Privacy Policy

Last updated: November 1, 2026

Welcome to TableMesh. This Privacy Policy explains how Sheep Labs LLC (“we,” “us,” or “our”) collects, uses, and shares information when you use the TableMesh website, the TableMesh mobile app, and related services.

By using TableMesh, you agree to this policy. If you do not agree, please do not use the service.

1. Information we collect

We collect information you give us, information collected automatically, and information from sign-in providers.

A. Information you provide

  • Account. Name, email address, and a password if you create one. Phone number is optional. Sign-in with Google or Apple gives us the name and email (and profile photo, if that provider shares it). We do not receive your Google or Apple password.
  • Profile. What you choose to add, such as a photo, bio, birthday, gender, city, job, company, education, dietary preferences, and hobbies. You can limit what other people see.
  • How you heard about us. An optional answer at the end of signup, and any short note you type if you pick Other.
  • Content. Tables you host or join, messages, photos, and comments.
  • Payments. If you buy a ticket or TableMesh Plus, our payment providers collect the card details. We store the subscription status, not your full card number.
  • Support. Whatever you send us when you write in.

B. Information collected automatically

  • Usage. Screens you open, tables you view or join, and features you use. We use this to run and improve TableMesh.
  • Device. Device type, operating system, app version, and similar technical details.
  • Location. With your permission, precise location so we can show nearby tables and set a place when you host. You can turn this off in your device settings.
  • Contacts, if you ask us to look. Finding friends from your address book is optional. The app hashes phone numbers on your device and sends us only those hashes, to see which ones match a member. We do not receive your contacts' names. The raw numbers stay on your phone (including if you send someone an invite by text).

C. Marketing and referral visits

When you open TableMesh from an ad, a shared link, or another site, we record that visit so we can see which marketing works. We record each visit, not only the first one.

A visit can include:

  • UTM tags (source, medium, campaign, content, and term).
  • Ad click IDs when the link has them: Meta (fbclid), Google (gclid, gbraid, wbraid), TikTok (ttclid), and Microsoft (msclkid).
  • The page that referred you, without the query string.
  • The landing page, whether you were on the website or the iOS or Android app, and the time.

Before you have an account, the visit is stored against an anonymous id on that browser or install. When you sign up or log in, we attach those visits to your account. We do not put your name or email on the visit itself. To connect a website click with a later app install, we may store a salted hash of the IP address. We do not store the raw IP address on that click record.

The same session and the same link details are not stored again and again. Visits linked to your account are deleted when you delete the account. A visit we have not linked to an account stays without your name or email.

2. How we use information

  • Run the product: accounts, tables, chat, tickets, and subscriptions.
  • Show you people and tables that fit, and let other members see the profile fields you leave visible.
  • Send service messages, such as a sign-in code, a ticket, or a change to an event you joined.
  • Send product and marketing email as described below.
  • Measure which ads and pages lead to signups and later use of TableMesh.
  • Keep the service safe: fraud, abuse, and verification you opt into.
  • Understand how the product is used, so we can fix and improve it.

3. Advertising measurement, including Meta

We advertise TableMesh, mostly on Meta (Facebook and Instagram). To see which ads lead to real use, we share some events with Meta.

  • Website. The site loads the Meta pixel. It records page views and, when they happen, signup and registration events.
  • Server. Our server also sends Meta conversion events: signup and completed registration, and, for people who arrived from an ad, StartTrial, Subscribe, and a custom event when you first join a table (FirstTableJoined). Those calls can include a hashed email or phone number and the Meta click id (fbc / fbclid). Hashing means Meta receives a one-way code, not the plain address or number. We do not send your password, your messages, or your precise location for advertising.
  • The app. The iOS and Android apps include the Meta SDK (Facebook App Events). It can log app events such as a first open, completed registration, the start of a trial, and a subscription. On iPhone and iPad we ask for Apple's App Tracking Transparency permission after you sign in, not on the first launch screen. Until you allow tracking, the SDK does not turn on collection of the iOS advertising identifier. You can change that later in Settings, Privacy & Security, Tracking. Declining does not block the app. On Android there is no Apple-style prompt, and the SDK may use the Android advertising identifier for those app events.

We do not currently send conversion events to Google or TikTok. If we advertise there, we may send them similar events, using the same kinds of identifiers, so we can measure those ads. We already store their click ids when a link contains them, as described above. We do not send events to Microsoft.

4. Email

We send email through Resend.

Transactional email is part of using a feature: a sign-in or confirmation code, a ticket you bought, or a notice that an event you joined changed or was cancelled. You cannot turn those off while you use the feature. Ticket emails include an unsubscribe link for later updates about that event.

Marketing and lifecycle email is separate. We send, or are preparing to send, product updates and notes such as a welcome, a digest of nearby tables, or a reminder if you have been away. Those messages can record opens and link clicks, and the links can include UTM tags so we know which email helped. Every marketing email has a one-click unsubscribe link, and you can change email preferences. People in Canada, the European Union, and the United Kingdom receive marketing email only after they opt in. Transactional email does not depend on that opt-in.

5. Face verification (biometric information)

A verified badge is optional. You can use TableMesh without it.

If you choose to verify, the app takes a short video selfie. Amazon Rekognition checks that the video is of a live person, then compares a still image from that check with photos already on your profile. The point is to show other members that the profile photos match a real person. We do not use this for advertising, and we do not sell biometric information.

We configure the Rekognition session not to store audit images. We do not save the video or the reference still in our database. The still is used in memory for the comparison and then dropped. What we keep is the outcome (pass or fail), the liveness and similarity scores, the time, whether it was iOS, Android, or web, and how many profile photos were compared. Those records stay with your account and are deleted when you delete your account.

6. Who we share information with

  • Other members. Profile fields you leave visible, and the tables you host.
  • Service providers, only as needed to run TableMesh:
    • Supabase — accounts, database, and file storage.
    • Vercel — the website. If the in-app assistant is on, messages you send it may go through the Vercel AI Gateway or Anthropic so it can reply. When an OpenAI safety check is enabled, the text of those messages may also be sent to OpenAI for moderation.
    • Stripe — card payments on the web (tickets, TableMesh Plus, and restaurant billing).
    • RevenueCat — App Store and Google Play subscriptions.
    • Apple — Sign in with Apple.
    • Google — Sign in with Google, Maps, and Places (searching for a restaurant or city).
    • Firebase Cloud Messaging — push notifications. The app uses this with Notifee to display them. The website can also use Firebase for web push.
    • PostHog — product analytics (what features get used, not the text of your private messages for ads).
    • Resend — email, as described above.
    • Twilio — text messages, such as a sign-in or host code.
    • Amazon Web Services (Rekognition) — optional face verification.
    • Meta — advertising measurement, as described above.
    • Cloudflare — Turnstile, a bot check on some public forms.
  • Legal and safety. We may disclose information if the law requires it, or to protect TableMesh, our members, or the public.

We do not sell personal information for money. Sharing hashed identifiers with Meta for ad measurement can count as a “sale” or “share” under some U.S. state laws, including California's. See Your choices.

7. Your choices

  • Profile. Update your account in settings, and choose which fields other people can see.
  • Location, contacts, camera, and notifications. Turn these off in your device settings. Some features will not work without them.
  • iOS tracking. Settings, Privacy & Security, Tracking.
  • Marketing email. Use the unsubscribe link in a marketing email, or your email preferences. Service emails tied to an action you took are separate.
  • Ads opt-out. Email contact@tablemesh.com with the subject “Do Not Sell or Share” and we will take you out of audiences we build for ads. Where the law requires it, we honor a Global Privacy Control signal. You can also limit ad personalization in your Meta settings.
  • Delete your account. You can delete it from settings in the app. That removes your profile and the records tied to it, including marketing visits we have linked to you and face-verification scores.

8. Children

TableMesh is for people 18 and older. We do not knowingly collect information from anyone under 18. If you believe a child has given us information, email us and we will delete it.

9. Contact

Questions about this policy: contact@tablemesh.com. Sheep Labs LLC.