Help & frequently asked questions

Daap Toi helps adults travelling or eating solo find tablemates who want to try similar dishes. Share portions and costs, try more local food, and make each meal on your trip count.

You must be at least 18 years old, legally able to accept the Terms, and provide truthful account information. Daap Toi is designed primarily for solo travelers and other solo diners whose main goal is a practical shared meal.

No. Daap Toi is for coordinating shared meals around compatible food goals, timing, budget, language, and table size. It is not a dating service, friendship service, profile-browsing network, or general direct-messaging app.

Create a private meal plan with your city, available times, dishes you want to try, budget, languages, and preferred group size. We look for compatible plans and suggest meal opportunities. You decide whether to express interest, then arrange a restaurant and exact time with your tablemates. You cannot create/resume plans or accept another table that overlaps a meal you have already accepted, including across cities. Adjacent meals with no time overlap are allowed; leave the earlier commitment first if your plans change.

No. Your meal plan is private. Potential matches see shared preferences and group counts, without your identity or full schedule. Once a group forms, diners can see limited profile details to help arrange the meal.

No. A meal plan tells us what you are looking for; it is not a reservation or a guaranteed match. We look for compatible cities, times, dishes, languages, budgets, and group sizes, subject to account and safety rules.

A meal opportunity suggests diners whose meal plans fit yours, without showing their names or full schedules. You can express interest in sharing a meal. The table, restaurant, and time are not confirmed at this stage.

An interested group first becomes a proposed table, where diners suggest and choose a restaurant and exact time. When the minimum number accept the same proposal, that restaurant and time are locked for final replies. The table confirms when everyone has replied or the reply deadline arrives, provided the minimum accepted count is still met. Only diners who explicitly accepted are included. Confirmation does not book a restaurant; arrange any booking yourselves.

Expressing interest in an unlocked opportunity does not commit you to a restaurant. Accepting a restaurant and time is an attendance commitment. Suggesting a restaurant automatically selects that suggestion for you. Joining a table already in final replies requires accepting its locked restaurant and time immediately, with the existing deadline unchanged. Review these details before joining.

1. Create a private meal plan with your city, availability, dishes, budget, languages and group size. 2. Review compatible meal opportunities and express interest. 3. When enough diners are interested, a proposed table opens with shared chat. 4. Suggest up to two restaurant/time options each, or accept one suggestion. 5. Once the minimum accept the same option, final replies begin. 6. We confirm when everyone replies or the deadline arrives if enough accepted diners remain. 7. Check the final restaurant, time and diner list, arrange any booking, and meet. After the meal ends, eligible diners can submit feedback about their own attendance and experience. Creating a plan or expressing interest alone is not a reservation.

The choice countdown is the remaining negotiation time, not a promise that the table will form. Individual restaurant suggestions may have an earlier acceptance deadline so there is time for replies and travel. Once a proposal locks, a separate final-reply countdown appears; reply before that deadline if you want to attend. Accepted diners also see an earlier withdrawal deadline, normally five minutes before final replies close. Times use the table city's timezone. The screen refreshes while open, when reopened, and at expiry; the server decides the final result. If it still shows that the deadline passed, refresh to check the latest result.

When the minimum has accepted a locked proposal and everyone has explicitly accepted or declined, the table can confirm early. Otherwise it waits for the final-reply deadline. Merely choosing another suggestion does not count as a final decline. Pending diners may accept or explicitly decline the locked proposal; a diner who already accepted must use withdrawal or exit to cancel that commitment. Only accepted diners attend. If too few accept, choices may reopen while time and a round remain; otherwise the table closes. There are at most two final-reply rounds. Withdrawal in the last round does not immediately close the table or restart its deadline. A smaller confirmed group continues if it meets the minimum.

Matching starts with your dishes, availability, budget and group size. At a proposed table, each diner may keep up to two open restaurant/time suggestions and replace their own open suggestions. Suggesting automatically accepts the new suggestion for you, replacing your previous choice. Only one choice can be accepted at a time. Other suggestions become Not selected, without deleting them or changing anyone else's choice. Not selected is not a final refusal: if that proposal locks, you can still explicitly accept or decline before its reply deadline. A previous explicit decline stays a decline until you change it. Arrange restaurant availability and bookings yourselves.

No. Daap Toi does not currently book restaurants or handle bills, deposits, refunds, or payments. Check availability with the restaurant and agree on the budget and how to split the bill before you meet.

Use your meal plan, restaurant coordination, and table chat to share relevant dietary needs before anyone commits. Confirm ingredients and cross-contamination risks directly with the restaurant. Daap Toi and other diners cannot guarantee that a restaurant can safely meet an allergy or dietary requirement.

Chat is available only to current, authorised participants at a proposed or confirmed table. It is for arranging that meal. Daap Toi does not offer unrestricted one-to-one messaging or a general social inbox.

Use table chat to coordinate the restaurant, exact time, budget, dietary needs, attendance, and practical arrangements. Harassment, dating pressure, fraud, spam, and other off-topic or unsafe conduct can be reported.

Before a table is confirmed, Daap Toi shows limited context that helps diners coordinate, such as display name, languages, table preferences, and shared event context. Email verification is not identity verification, and these signals do not guarantee anyone's conduct. Account restrictions and moderation decisions are handled under platform rules.

Review the available participant, restaurant, and time details before accepting. Meet in a public place, share personal information gradually, tell someone you trust where you are going, arrange your own safe transport, and leave if the situation feels wrong.

Contact local emergency services first if there is immediate danger or a medical emergency. Daap Toi reporting can support later moderation and record review, but it is not emergency monitoring and cannot provide an immediate emergency response.

Report safety issues, spam, harassment, fraud, dating pressure, unsafe requests, or other bad-faith conduct from profile, event, or chat context. You can block at the same time or separately. Blocking prevents the two accounts from being matched into future meal opportunities.

No. Reports are confidential records used for safety and moderation review; they are not published as public accusations. Daap Toi may retain relevant report, message, event, and block records when needed for safety, disputes, fraud prevention, or legal compliance.

current feedback records only your own attendance after a completed meal. Reporting another diner as a no-show and disputing a no-show are not available yet. Use a safety report for conduct concerns.

After an eligible completed meal, current feedback lets you report your own attendance, whether sharing helped you try more dishes, and an optional short note. It is not a public restaurant or peer review and does not verify another participant's attendance.

Use the action for the current stage: cancel an open/paused meal plan, leave a proposed/final-reply table, or cancel a confirmed place before the meal starts. If a table confirms while your leave request is in flight, that request cancels your confirmed place instead; the app reports success only after your place is removed. Once the meal starts, an exit request is rejected with a clear status message. Other diners keep their places if the minimum remains. Exiting never depends on spare matching quota: if your original plan cannot reopen because quota is full or its time conflicts with another commitment, it ends instead. You can create another plan once eligible and capacity is available. A cooldown can pause an otherwise eligible plan. Read the late-cancellation and cooldown FAQs before cancelling.

No. Use the cancellation or leave action shown by the app and provide a reason when requested. A chat message or non-attendance does not cancel a meal plan, proposed table participation, or confirmed table commitment.

Before a proposal locks, you may withdraw and accept one of your own or another diner's open suggestions before its acceptance deadline. During final replies, withdrawal is allowed only before the withdrawal deadline, and only once per diner for that table. If enough accepts remain, the restaurant, other accepts and reply deadline stay locked. If support falls below the minimum and another round is available, choices reopen while everyone else's accepts are preserved. In the last round, the current proposal and deadline remain in place for other diners to reply. You can still leave if you cannot attend, but a late committed departure may count toward the cooldown. A failed or rejected withdrawal does not consume the one allowed withdrawal.

Leaving an accepted final-reply table at or after its withdrawal deadline counts as late. Once that responsibility begins, confirmation cannot make it less strict. For a confirmed place, the late deadline is the earlier of that withdrawal deadline and two hours before the meal starts. The table shows the applicable deadline in its city timezone; the exact boundary counts as late. An ordinary pre-freeze withdrawal, leaving without accepting the locked proposal, or a cancellation caused by the system or another diner does not add a late record for you. If a round reopens, the old round's freeze is cleared and a newly accepted locked round gets its own deadline. Giving a reason or choosing Keep looking does not waive a late record. Use the exit action; a chat message does not cancel your place.

Three late cancellations within a rolling 30-day window trigger a full 24-hour pause, measured from the most recent late cancellation. Once triggered, an older record aging out of the 30-day window does not shorten that pause. Further late cancellations can extend it. During cooldown you cannot create/resume plans, express new interest, join another table, suggest a restaurant, or newly accept a proposal. The table shows the end time before you act and disables new accepts and suggestions. Existing accepted commitments remain valid: you may view tables, chat, attend, decline a pending proposal, and use available withdrawal/exit actions. An otherwise eligible departing plan pauses if Keep looking would bypass the restriction. The restriction expires automatically. Retried requests count once. It is not a fee or public rating; contact support if a record seems wrong.

No. Leaving or cancelling removes that diner's acceptance. Other diners' choices and confirmed places stay intact while the table remains viable. If enough accepted diners remain, the arrangement continues; an ordinary departure does not reset its deadline. If the table must reopen after an unsuccessful timed-out round, fresh agreement is needed. If it closes because time, rounds or participant numbers run out, affected plans may return to matching or pause under the applicable rules. You are not given a late-cancellation record for another person's exit.

Restaurant search and place details use Google Places data when available. Place information can be unavailable, incomplete, or inaccurate, and showing a place does not mean Daap Toi endorses it or has made a reservation.

No. Matching uses the city and optional area you submit with a meal plan, not continuous precise-location tracking. Event coordination may store limited selected place data, such as a Google place identifier, restaurant name, address, or map snapshot.

No. Daap Toi does not sell personal data. It processes and shares limited data as needed to operate accounts, matching, events, messaging, restaurant search, safety, support, security, and legal obligations as described in the Privacy Notice.

You can permanently close your account in the app under Settings → Data Rights, or use /delete-account with your verified account email if you cannot sign in. Access ends as soon as the request is accepted. Personal data is erased from active systems within 30 days. Limited de-identified shared-meal references can remain for up to 365 days after account closure or the meal ends, whichever is later; restricted backups expire within 90 days after active cleanup, and deletion-request records remain for 90 days after completion. A documented legal or safety hold may apply to specific records. Contact [email protected] if you cannot access your account email or need another data right.