Account and profile data
TableMatch can use Supabase Auth for account sign-in and profile records such as email, display name, player preferences, GM profile details, listing information, and marketplace role.
Lisbon, Portugal
App Privacy
Effective date
This page is app-specific. It is separate from the website, store, analytics, and commission inquiry policy so App Store privacy answers can stay accurate for each app.
TableMatch can use Supabase Auth for account sign-in and profile records such as email, display name, player preferences, GM profile details, listing information, and marketplace role.
The marketplace can store booking intent, scheduled session details, seat counts, listing selections, session-rule snapshots, refund or protection claims, reviews, and moderation notes so players and Game Masters can coordinate a session. New exact-session Table Guide work is source-validated but is not yet live on the public pilot.
If a controlled payment flow is enabled, card details are handled by Stripe Checkout or Stripe Connect and are not stored directly by TableMatch. The public pilot does not accept live real-money bookings. TableMatch can store bounded payment-attempt status, transaction references, refund state, and reconciliation metadata needed to recover a booking safely.
When a player books a campaign, TableMatch may share the player's profile name, contact email, seat count, and session coordination details with the selected Game Master so the game can be prepared and hosted.
Support and trust workflows can use logs, error reports, dispute context, listing IDs, booking IDs, and visible account metadata. Do not send passwords, payment card numbers, private game content, or API keys in support requests.
If you have privacy questions about TableMatch, contact Luna Peregrino using the support email below.
Contact about TableMatch privacy