What we know about you,
and what we don't.
TablePort recognises returning guests across the restaurants that use it. Here is exactly how, written plainly, with no asterisks.
What we collect when you pay
When you pay at a TablePort restaurant we keep three small things: a cryptographic fingerprint of the card you used (a one-way hash, so we never see the card number itself), your billing postal code and country, and which wallet you reached for (Apple Pay, Google Pay, or a plain card).
These three signals let a restaurant you've never visited recognise that you're not a stranger, if you've opted in.
What we share with restaurants
When a restaurant in our network recognises you, the host sees a short brief on their screen. It contains:
- Your first name
- A banded frequency tier: new, regular, top 25%, or top 10%
- Your visit count across the network
- Whether this is your first time at this restaurant, or a return
That is the whole brief. The restaurant never sees which other restaurants you've been to. Never your full name. Never your address. Never anything to do with the card you paid on.
Your control
Three actions, always one tap away:
Architecture, for the curious
Each restaurant holds its own member row for you: what you ordered there, what you liked there, what they noted about your visit. Cross-restaurant recognition is a separate, explicit consent that you grant once and can revoke at any time. Card fingerprints are hashed with pgcrypto before they ever touch a database row. A deletion request cascades across every restaurant in the network as a GDPR-grade DSAR within the statutory window.
Contact
For data requests, complaints, or anything that smells off, write to privacy@tableport.io. A human reads every message.