How Daap Toi collects, uses, shares, and protects personal data.

1. Who this notice applies to

This notice applies whenever Daap Toi acts as the controller for the personal data processed through our service.

• It covers data collected through the website, mobile app, account support, moderation review, and user safety workflows.
• If you contact us about privacy or data rights, you can reach us at [email protected].
• If we materially change how we process personal data, we will update this notice and publish the revised version date on this page.

2. Personal data we collect

We only collect the categories of data needed to run the service, maintain safety, and improve product operations.

• Account and profile data such as email address, display name, avatar where supported, language choices, account status and coordination settings you choose to provide.
• Private meal plan data such as selected city, optional area, flexible availability window, meal slot, food goals, dish notes, per-person budget, languages, preferred group-size range and optional coordination preferences.
• Matching and participation data such as derived meal opportunity membership, interest decisions, proposed and confirmed table membership, restaurant proposals and acceptances, cancellation and lifecycle history, messages, self-reported attendance and food-value feedback, confidential reports and blocks.
• Technical and usage data such as device information, security logs, approximate network metadata, and app activity needed to secure the service and troubleshoot incidents.
• Place data such as a Google provider place identifier and a limited restaurant name, address or map snapshot selected during event coordination. Matching uses the city and optional area you submit, not continuous precise-location tracking.

A raw meal plan can reveal travel timing and dining preferences. It is used by its owner and the matching system and is not exposed as a public profile or global listing.

3. Why we use personal data

We use different legal bases depending on the feature and the purpose of processing.

• We process data to perform our contract with you, including operating your account, matching compatible meal plans, creating participant-only event spaces, recording explicit restaurant decisions and enabling table chat.
• We process data for legitimate interests such as fraud prevention, service security, product improvement, safety review, dispute handling, block enforcement and measuring service reliability, balanced against user rights and expectations.
• We process some data to comply with legal obligations, including records needed for safety investigations, law-enforcement cooperation, or dispute resolution where required.
• Where consent is the appropriate basis, such as optional marketing or certain optional tracking settings, you may grant or withdraw that consent through the controls we provide.

4. How data is shared

Some data is visible to other users by design, while other sharing only happens with processors or where law requires it.

• Raw meal plans are not public. Eligible users may see a derived meal opportunity without another owner's identity or full schedule; proposed or confirmed table participants may see limited participant and coordination context needed for that event.
• We share data with service providers that help us host and secure the platform, deliver account email, store data, operate messaging, provide restaurant and map search, support safety review and analyze service health under contractual controls.
• We may disclose data to regulators, courts, insurers, or law-enforcement authorities when we are legally required to do so or when necessary to protect rights, safety, or the integrity of the service.
• If data is transferred outside your home jurisdiction, we use appropriate transfer safeguards that are reasonable for the service and the processors involved.

5. Retention and security

We keep data for as long as it is needed for the purposes described above, then delete or de-identify it where practical.

• When an account-deletion request is accepted, account access ends immediately and personal data is erased from active systems within 30 days.
• Limited de-identified shared-meal references may remain for other diners for up to 365 days after account closure or the meal ends, whichever is later. They do not include the deleted profile, email, notes, or messages.
• Restricted backups expire within 90 days after active-system cleanup, and deletion-request records containing only operation identifiers, state, timestamps, and sanitized errors expire 90 days after completion.
• A specific legal or safety record is retained beyond these periods only under a documented, time-limited hold that is reviewed regularly; there is no automatic indefinite safety hold.
• We use technical and organizational safeguards designed to reduce unauthorized access, loss, misuse, or disclosure, but no online service can promise absolute security.

6. Your choices and rights

Depending on your location, you may have legal rights over your personal data and practical controls inside the product.

• You can review and update parts of your profile and settings directly in the service.
• You may ask for access, correction, export, restriction, objection, or erasure by using the request tools we provide or by contacting us. You can permanently close an account in the app or at /delete-account using its verified email. We may ask you to verify your identity before completing a request.
• Some requests may be limited where we need to keep records for safety, fraud prevention, legal compliance, or the rights of other users.
• If a processing activity relies on consent, you may withdraw that consent at any time, but withdrawal does not affect processing that already took place lawfully before withdrawal.
• Where applicable, you may lodge a complaint with the UK Information Commissioner's Office or the data-protection supervisory authority responsible for your location.

7. Service-specific privacy considerations

Shared dining creates privacy considerations specific to profiles, attendance records, and trust systems.

• The service uses submitted constraints to group compatible meal plans and rank personalized meal opportunities. This can affect which opportunities you see, but it does not automatically commit you to a meal or select a restaurant; interest and proposal acceptance require your actions.
• Messages, event decisions, consent records, reports, blocks and participation history may be retained where necessary for safety, service integrity, legal compliance and dispute handling after you leave an event or close an account.
• Confidential reports are used for safety review and are not published as public accusations. Blocks are used to reduce future matching and messaging where applicable without rewriting historical shared-event records.