私隱政策

FoodFoot (飯腳, foodfoot.app) is a Hong Kong restaurant-matching web app: open a table, share the LINK with your dining partners, everyone swipes on their own phone, then reveal which restaurants you all liked. This policy explains what we collect, how we use it, where it is stored and what rights you have. Privacy enquiries: aidonkey.work@gmail.com.

No sign-up or login is needed and we never ask for your name, phone number or email. Opening a table and swiping generates: table data (a random 5-character table code, the restaurants dealt, the filters you chose — area, cuisine, price level, party size, solo or not — creation time, and which players have finished); swipe records (like or pass for each card, with the table code and your player code); a player code generated randomly in your browser on first visit (for example p3k9x2a7; the person who opens the table is always a), used only to tell players at the same table apart and not linked to your identity; usage events (share, download, invite LINK opened, nudge sent) with the table code, animal persona key, collection count and event type — no personal data; and your animal collection, kept only in your browser.

Note: anyone with a table’s LINK can view that table’s reveal (which restaurants matched and how many liked each). Share it only with your dining partners.

When an owner registers we collect: restaurant name, area, cuisine category, price level, signature dish, one-line intro, food photos (1 to 4), restaurant IG (optional), contact name, WhatsApp number, email (optional), what you want to do (optional), and two consent choices (consent to data collection; opt-in to marketing). Public: restaurant name, area, cuisine, price level, dish, intro, IG and photos appear in the deck immediately. Not public: contact name, WhatsApp, email, goal and marketing consent are used only to contact you about listing and partnerships; database access rules prevent anonymous visitors from reading these fields. When you press “Next” on step one, the restaurant name, contact name and WhatsApp are recorded once (even if you do not finish step two) so we can follow up. Photos are uploaded to our cloud storage and shown on the card via a public URL.

The feedback form collects: subject (optional), message, any contact you choose to leave (IG / WhatsApp / email, optional), and the page path you were on when you submitted. Please do not include sensitive data such as ID or bank details.

Threads search is an internal operator tool; players and owners never connect Threads. If you have authorised us via “Log in with Threads”, section 8 explains how your data is handled.

Player data runs the matching flow (waiting for everyone, reveal), builds each restaurant’s real cumulative like count shown on cards, and gives us operating metrics (tables opened, completion rate, shares). Owner data lists your restaurant and lets us contact you about listing and FOODIE tasting campaigns; marketing messages are sent only if you ticked the marketing opt-in, and you can withdraw at any time. Feedback is used to follow up on your issue and reply if you left a contact. We do not sell your data or use it for personalised advertising.

External links: cards and area pages link to restaurants’ official Instagram accounts and to press coverage. Once you leave foodfoot.app, that site’s own privacy policy applies.

We use no advertising cookies and no third-party tracking cookies.

Tables, swipes, events, owner registrations and feedback: there is currently no automatic deletion; data is kept until you ask us to delete it (section 7). Browser storage stays on your device until you clear site data (Safari may clear it after 7 days without a visit). Threads cookies expire after about 60 days or when you log out on /threads; see section 8.

Under the Hong Kong Personal Data (Privacy) Ordinance you may access, correct and request deletion of your personal data. Email aidonkey.work@gmail.com and we will reply within 40 days. Owners: state the restaurant name and the WhatsApp number used to register. Players: we cannot tell which player code is yours, so include the table code (the 5 characters at the end of the LINK). Feedback: give the approximate time and content. To withdraw marketing consent, email us or tell us when we WhatsApp you. See Data deletion for steps.

FoodFoot uses Meta’s Threads API to search public Threads posts as an internal signal of restaurant buzz. This is an operator tool (the /threads page), not a player or owner feature — using FoodFoot or listing a restaurant never involves Threads. If you have authorised us via “Log in with Threads” (for example the operator or a Meta reviewer), the following applies. What we receive: your Threads access token (threads_basic, threads_keyword_search), your Threads user ID and username, and the public posts returned when you search (post ID, text, timestamp, username, permalink, media type, whether it is a reply). Storage: the access token lives only in an httpOnly cookie in your own browser (about 60 days); our server does not store it, log it or return it to browser scripts. Your username is kept in a second cookie so the page can show who is logged in. Search results are used within the request and your browser’s memory only and are never written to our database. If a buzz ranking is launched later, we will store only aggregate mention counts per restaurant (restaurant, count, window, fetched time), never data about individual Threads users or posts. Revoke: Threads app → Settings → Account → Website permissions → remove FoodFoot; the token becomes invalid and Meta notifies us. You can also press log out on /threads to clear these cookies immediately. Deauthorise / deletion notifications: Meta sends us your Threads user ID when you revoke access or request deletion; we record only that ID (with the deletion confirmation code) in our server logs for reconciliation, and there is nothing else to delete. Deletion requests: see the Data deletion page for steps and status lookup.

Changes are published on this page and reflected in the date at the top.