Privacy policy
Updated 28 October 2026. Version 4.0.
Meeting people starts with sharing a little about yourself. This policy explains what Meetable collects, how we use it to bring people together, and the choices you have along the way.
Who we are and what this covers
This policy covers Meetable’s websites, web onboarding and booking, iOS and Android apps, waitlists, newsletters, support channels and the dinners and social experiences we organise. Some features are available only in certain cities, app versions or limited releases; the relevant description applies when you use that feature.
Meetable Labs, Inc., a Delaware C corporation, is the data controller (the responsible party under South Africa’s POPIA). Our business address is 1111B S Governors Ave, #88059, Dover, DE 19904, United States of America. South African operations are carried out by MTBL Africa (Pty) Ltd, registration 2026/424249/07, and UK operations by Meetable UK Ltd.
For privacy questions or requests, email hello@meetable.social. This policy replaces earlier website and app privacy notices. It does not change the separate privacy notices of a payment provider, app store or other service you choose to use.
The information we collect
Account and contact details
Your name and preferred name, email, phone number, sign-in identifiers, authentication and verification status, and account settings. When you choose Apple or Google sign-in, we receive the account identifier and the profile details that provider shares, which may include your name, email and avatar. We do not receive your Apple or Google password.
Your profile and onboarding answers
Photos, bio and profile prompts; date of birth and age; gender; city, general neighbourhood and city requests; languages, home countries and travel interests; occupation, career and life stage; interests, social and conversation preferences; availability, preferred age mix, budget, food and drink preferences, dietary restrictions and accessibility needs. We also retain progress and completion state so you can resume onboarding and use your profile across the web and app.
Dinners, connections and messages
Bookings and waitlists, table assignments, restaurant and event details, attendance and no-shows, cancellations, dinner history or passport stamps, feedback and post-dinner connection choices. Messaging data includes message text, voice notes where available, participants, timestamps, delivery and read state. Reports, blocks and support conversations are described below.
Purchases, Credit and gifts
Tickets and seat packs, entitlements and any subscription state, Credit balances and ledger entries, redemption and expiry, gift sender and recipient details and a gift message if provided, orders, receipts, payment provider references, amounts, currencies, payment status, refunds, disputes and fraud checks. We receive transaction information from payment providers and app stores; payment credentials are handled by those providers. Do not send full card details to support.
Identity, device and service data
Identity inquiry references, outcomes and associated verification metadata; device and operating-system information, app version, IP address, time zone, notification tokens, security logs, error and crash reports, and service interactions. Browser storage can hold consent choices, authentication, onboarding drafts and checkout state. Optional analytics and connected services are explained in their own sections.
Information from other people
We may receive your details from someone sending you a gift, a member who reports an incident, a venue confirming attendance, or a payment, identity or sign-in provider. We also receive whatever you choose to send through email, WhatsApp, feedback or enquiry forms. For restaurant, business or employment enquiries, this may include your role, organisation, contact details and application material.
Sensitive information and permissions
Dietary and accessibility answers can reveal health or religious information. Other profile answers, reports or messages can also reveal sensitive personal information. We use relevant details for dinner planning, accommodation, matching and safety, and rely on explicit consent where required for special-category information, or another specific exception permitted by law. You can ask us to remove optional answers or withdraw consent; that may limit the accommodation or personalisation we can offer.
Some details are needed to provide the service, such as contact and sign-in details, eligibility information and a booking’s city. Optional profile details can be left out. If required information is missing, we may be unable to create the account, verify eligibility or arrange the booking.
Camera and photo-library access support profile photos and verification; microphone access supports voice notes; notifications support reminders and updates. Where app lock uses Face ID or a fingerprint, your device performs the check: Meetable does not receive your device’s biometric template. Optional location access can suggest a nearby dinner city and support verification checks. Where you add a dinner to your calendar, the app shares the event details with your chosen calendar service. Device permissions can be changed in your system settings. They are separate from any consent needed to process personal information.
How we use information and make matches
We use information to create and secure your account, build your profile, save your progress, check eligibility, arrange dinners, process purchases and Credit, deliver gifts, handle refunds, enable messaging and connections, respond to support requests and investigate safety issues. We send service messages such as sign-in codes, booking confirmations, restaurant details, reminders, receipts and account notices.
Matching uses your city, availability, preferences and profile answers alongside practical constraints such as table capacity, age mix and previous attendance. Software helps assess compatibility and compose tables; staff can review and adjust arrangements. This processing can influence who you meet and which dinner you are offered. We also generate profile presentation and dinner content as described below. Contact us if information is wrong or you want a matching or account decision reviewed by a person.
We use diagnostics, feedback, service activity and, where enabled, analytics to improve reliability and understand what works. Tests may compare different booking or onboarding experiences and record which version you saw and its outcome. We use waitlist and city-request data to plan launches. Marketing messages and advertising choices are separate from messages needed to deliver your booking.
Identity and age checks
Where verification is required, Persona runs the check on our behalf. The current member flow uses a selfie and liveness check, with verification metadata and device or location signals for fraud prevention and age assurance. Meetable does not ask for a government identity document in this flow.
Persona processes the verification source material. Meetable retains inquiry references, status and relevant outcomes to manage eligibility and safety; we do not show verification source material to other members. A failed or incomplete check may prevent access to features. Contact support if you believe the outcome is wrong. Account deletion includes a request to delete or redact the associated Persona inquiry, subject to any lawful retention requirements.
What members and restaurants can see
Members may see the profile details shown in the relevant feature: your first or preferred name, photos or avatar, age or age band, general city or neighbourhood, bio, languages, interests, prompts and other profile details you choose to share. Tablemates see their shared dinner and relevant table content. Connections and chat participants can see the messages you send, membership of the conversation and its delivery or read state. Where music sharing is available, only the selection you publish is shown.
Some dinner content has separate choices for using a detail in matching, displaying it to tablemates or attributing it to you. Those choices apply to that content; they do not make information you otherwise publish on your profile private. Do not put information in a public profile or message that you do not want its recipients to see. Recipients can keep copies or screenshots.
We do not display your email, phone number, payment credentials or identity-check source material as member profile fields. Private questionnaire answers and safety reports are not published to other members. A mutual connection may be shown to the people involved; feedback and internal matching information are used to operate the service.
Restaurants and hosts receive the reservation and operational information needed to host the group, including headcount, timing and relevant dietary or accessibility arrangements. We aim to share the minimum needed, using group-level requirements where practical. A requirement can still identify you in a small group. A venue separately controls information you give it directly, including payment for your meal.
Optional connected services
Spotify: if this feature is available and you connect it, you authorise read access to your top artists and tracks (user-top-read). We process authorisation tokens and connection state to retrieve that music, and store the items you choose to publish, including their names, artwork and Spotify links. Your full listening history and Spotify password are not displayed to members. Disconnect in the music section of your profile to remove the Meetable connection and published selection; you can also revoke Meetable’s access in your Spotify account. Spotify’s own processing is covered by its privacy policy.
For special events booked through Luma, we may receive attendee, ticket, payment and booking-status information to reconcile access and cancellations. Any external checkout or communication service you choose also applies its own privacy notice.
AI-assisted content and support
Where dinner-content features are enabled, we use Anthropic’s Claude to help create table introductions, conversation suggestions and icebreakers. The input is limited to selected profile facts and sharing permissions, which can include first names, internal member and table references, interests, food interests, languages, occupation, home countries, travel, conversation style and profile prompts. Generated content may be shown to the relevant table. It can be inaccurate; you can contact us about inappropriate content or your sharing choices.
Our support team can also use Claude to draft replies for a person to review. A limited recent conversation and relevant context, such as your first name, city, account or verification status, dinner history, bookings and Credit balance, may be sent to Anthropic. The draft tool removes common contact details, links, identifiers and secrets from message text, but this does not make the remaining conversation anonymous or guarantee that every sensitive detail is removed. Staff may use AI tools for related operational assistance using information needed for the task.
These tools assist content creation and staff work. A support draft does not itself issue a refund, change your booking or decide a safety case. We do not send identity-verification source material or full payment credentials to these tools for these purposes. We do not use your Spotify data as input to these AI features. For privacy concerns or a request for human review, email us.
Support, feedback and safety
When you contact support through the app, email or WhatsApp, we process the conversation, attachments you send, contact details, read state and relevant account, booking and payment history. Email conversations can be brought into our support workspace so staff can respond with the context of previous contact. Please avoid sending unnecessary sensitive information.
Reports and blocks can include the people involved, allegations, messages or evidence, incident details and follow-up actions. Authorised staff use these to investigate, protect members, moderate accounts and prevent repeated abuse. We may retain limited evidence or a restriction record when needed for safety or legal claims, including after account deletion. We handle reports carefully, but cannot promise absolute confidentiality where investigation or the law requires disclosure.
Post-dinner feedback, attendance, no-show and connection records help us improve tables and handle concerns. They may affect future arrangements or eligibility. You can contact support to challenge inaccurate records or ask for a person to review an account restriction.
Marketing and advertising
Waitlist, newsletter and promotional communications use your contact details, city, interests in Meetable and communication preferences. Marketing emails include an unsubscribe link. You can also email us to stop marketing. Opting out does not stop service messages about an existing account, payment or booking.
We advertise Meetable on Facebook and Instagram. With advertising consent, the Meta Pixel and server-side Conversions API can send events such as sign-up and purchase, value and currency, browser and ad-click identifiers (_fbp, _fbc), IP address and browser type, and hashed contact or matching details such as email, phone, first name, city and country. Hashing allows Meta to match its records; it does not make the information anonymous. We do not include private questionnaire answers, dietary or accessibility details, messages or verification source material in these advertising payloads.
We use advertising measurement to understand campaign results and, where enabled, to build member or similar audiences and show relevant Meetable advertising. Meta’s role depends on the activity: its own processing is governed by Meta’s privacy policy, and collection or transmission can involve joint-controller responsibilities. You can withdraw advertising consent in Cookie settings on the relevant site and contact us about removal from audience lists. Withdrawing stops future consent-based processing; it does not undo data already lawfully processed.
Our reasons for processing information
For UK and EEA data protection purposes, we rely on contract for accounts, bookings, matching, messaging and purchases; legal obligation for required financial and regulatory records; and legitimate interests for proportionate security, fraud prevention, support, safety, service improvement and operational assistance. We balance these interests against your rights. We rely on consent for advertising, optional marketing where required, and analytics storage or recording where consent is required. Special-category information also requires an applicable additional condition, such as explicit consent.
A device permission, acceptance of this policy or a booking does not by itself give consent for unrelated advertising or sensitive-data uses. You can withdraw consent or object to legitimate-interest processing by contacting us. Withdrawal does not affect the lawfulness of earlier processing.
Under POPIA, relevant grounds include consent, contract, legal obligation and legitimate interests under section 11, with additional protections for special personal information. We apply the requirements of other local laws where they govern our processing.
Where information is processed
Meetable is a US company with operations and providers in several countries. Information may be accessed or processed outside your country, including in the US, UK, EU and South Africa. A provider’s regional hosting option does not mean all support access and subprocessors remain in that region.
International transfers must have the safeguards required by applicable law, such as an adequacy decision, approved contractual clauses and the UK addendum, or another valid mechanism. POPIA section 72 governs relevant transfers from South Africa. Contact us for information about destinations and safeguards applicable to your data.
How long we keep it and account deletion
We keep information for as long as needed for the purpose described here: account and profile data while providing the service; booking and transaction records for delivery, reconciliation, refunds and applicable financial-record duties; support and safety records to resolve issues and protect members; and diagnostics and analytics for service improvement. Retention depends on the record, legal requirements, unresolved disputes and safety needs. Ask us for the period or criteria applying to a particular record.
You can request deletion in the app’s account settings, through our account-deletion page, or by emailing hello@meetable.social. We may verify that the request is yours. Deletion is a process across our systems and providers, rather than an instant removal from every system.
The deletion workflow removes or redacts account and profile details, questionnaire answers, uploaded media, notification tokens and associated records, and requests deletion or redaction from relevant providers, including Persona. It also addresses connected Spotify data and generated dinner content associated with your account. Message content can be replaced with a deleted-account marker and voice-note files removed. This cannot erase copies or screenshots already kept by recipients.
We may keep limited transaction, refund, dispute, consent, deletion-audit and safety records when needed for legal obligations, claims, fraud prevention or an unresolved issue. Backup copies may remain until replaced or expired. A provider may retain information it independently needs under the law. Deleting Meetable does not delete your Apple, Google, Spotify or payment-provider account, or automatically cancel an app-store subscription: manage that separately with the store.
Keeping information secure
We use technical and organisational measures such as access controls, secure transport, restricted operational access and monitoring. Access is intended to be limited to the people and systems that need it. No service can guarantee absolute security. We investigate suspected breaches and notify affected people and regulators when required by applicable law.
Protect sign-in codes and account-bound links. A personalised booking, ticket or refund link may contain an access token; avoid forwarding it or posting it publicly. Contact support promptly if you believe someone else has accessed your account.
Your choices and privacy rights
Depending on applicable law, you can ask to access or correct information, receive a portable copy, delete it, restrict processing, object to legitimate-interest processing or profiling, withdraw consent, and request human review of a decision where the law provides that right. You can object to direct marketing at any time. You do not need to delete your account to unsubscribe or raise a privacy concern.
Edit available profile details in your account, manage permissions in device settings, disconnect optional services through the relevant feature, and use Cookie settings for website choices. For other requests, email hello@meetable.social. We may ask for proportionate identity checks. We respond within the applicable legal period, normally one month for UK/EEA requests, and explain any lawful extension or refusal.
You can complain to the UK Information Commissioner’s Office, South Africa’s Information Regulator, or the data protection authority where you live or work in the EEA. Other local rights, including US state rights where applicable, may include access, correction, deletion and opting out of targeted advertising or legally defined sale or sharing. Use advertising settings and contact us to exercise those rights, including through an authorised agent where permitted. We will not unlawfully discriminate against you for exercising privacy rights.
Age requirements
Meetable membership and dinners are for people aged 21 and over. We use date of birth and, where required, verification to check eligibility. We do not knowingly offer membership to people under 21. If you believe an underage person has provided information, contact us so we can investigate and remove it where appropriate.
Changes and contact
This version was updated on 28 October 2026. We will publish changes here and provide additional notice for material changes where required. If a new use requires consent, updating this page alone does not provide it. Earlier versions are available on request.
For privacy questions, access or deletion requests, objections, or a complaint, email hello@meetable.social or write to Meetable Labs, Inc., 1111B S Governors Ave, #88059, Dover, DE 19904, United States of America.