Privacy Policy

yhangry is an online marketplace connecting customers (“Clients“) with independent chefs and culinary professionals (“Chefs“) through the yhangry website at https://yhangry.com/ and related features (the “Platform“).

This Privacy Policy explains what personal information we collect, how we use and share it, how long we keep it, and the rights you have. It applies to Clients, Chefs, visitors to the Platform, and people whose details a Client gives us: guests at booked events, gift card recipients and referred contacts.

1. Who is responsible for your information

The yhangry company responsible for your personal information (the “controller”) depends on your country of residence:

Your country of residence	Controller
United States	Yhangry, Inc., a Delaware corporation, principal place of business 251 Little Falls Drive, Wilmington, Delaware 19808, United States (“Yhangry Inc“)
Everywhere else (including the United Kingdom and the European Union / EEA)	Yhangry Ltd, a private limited company registered in England and Wales with company number 11874670 and VAT number 348811579, registered office at International House, 64 Nile Street, London, N1 7SR (“Yhangry Ltd“)

References to “yhangry“, “we“, “us” and “our” mean the entity responsible for you under this table.

Chefs are separate, independent controllers of the personal information they receive to perform a booking (for example, your name, event address and dietary information). The Chef Agreement requires them to use that information only for your booking, any related complaint, dispute or legal claim, and their own legal obligations, and to comply with data protection law.

2. The information we collect

From everyone:

Identity and contact data: name, email address, phone number, account details, login credentials, and (optionally) date of birth if you choose to provide it, for example to receive birthday offers.

Technical data: IP address, browser type and version, operating system, device identifiers, and other technical information about how you access the Platform.

Usage data: how you use the Platform, such as pages visited, booking patterns, interaction times and features used.

Cookies and similar technologies: see Section 12.

Communications data: messages and calls made through the Platform, and records of your communications with our support team. See Section 4 (Communications monitoring and recording) for messages and calls between Chefs and Clients made through the Platform; support records are kept under Section 9.

Feedback and survey data: your responses to satisfaction surveys we send after events (including scores and free-text feedback), and whether you respond to invitations to review us on independent review platforms.

Fraud prevention data: identity, payment and transaction information used for fraud prevention checks, carried out through our payment provider (see Sections 3 and 6). Failing a check can lead to a booking being cancelled or Platform access being withdrawn, as described in Section 5 of the Booking Terms.

From Clients:

Booking data: event details, dates, menu selections, guest counts, pricing and transaction history.

Location data: the event address and general city information.

Dietary and allergy information: allergies, intolerances and dietary requirements you tell us or your Chef about, for you or your guests. This can include information about health. We use it to deliver the booking safely and, where relevant, to resolve complaints and defend payment disputes and chargebacks (Sections 3 and 6). We share it with your Chef so the booking can be performed safely.

Payment data: billing address and payment method information, processed securely by our payment providers (such as Stripe). We do not store full card numbers.

Reviews and ratings: the reviews and star ratings you leave for Chefs, with the display name you use. Reviews are published on the Platform (see Section 6).

Guest data: if you use our split bill feature or provide guest details, we process your guests’ names, contact details and payments, and any dietary information you provide for them. Only share a guest’s details where they agree (or, for a child guest, where you are their parent or guardian or have the parent’s or guardian’s agreement), and tell them about this Privacy Policy. When we first contact a guest directly, for example with a split bill payment request, we include a link to this Privacy Policy.

Gift card and referral data: the recipient name and contact details you give us to deliver a gift card, and referral code usage linking the referrer and the referred person, so we can apply rewards and prevent abuse.

From Chefs:

Profile data: photos, biography, menus, prices, availability, travel radius and other information you choose to share to promote your services, together with the ratings and reviews Clients leave for you.

Verification and compliance data: the information you provide during onboarding, your insurance self-certification and, on request, your certificate of insurance or other evidence of cover.

Payout data: bank details, held and processed by Stripe for payouts.

Event check-in data: when you check in at an event, the time and GPS location of your check-in are recorded. See Section 5.

Event evidence: the photos and notes you upload for each booking (including no-show and venue reports). See Section 5.

Tax reporting data: identity, address, tax identification and earnings information we may be required to collect, verify and report to tax authorities: Yhangry Ltd under platform reporting rules, and Yhangry Inc for required US tax forms. See Section 6.

Performance data: your response times, booking and completion history, review scores, reliability record (including cancellations) and any Cancellation Charges on your account (charges under Section 10.2 of the Chef Agreement when you cancel a confirmed booking). The Chef Agreement (Section 6.2) explains how matching and ranking use this data.

From guests at events: a guest may appear incidentally in a Chef’s event evidence photos (Section 5), and a Client may give us a guest’s contact, payment or dietary details as described above.

3. How we use your information and our legal grounds

Where UK or EU data protection law applies, we must have a legal ground for each use. Our uses and grounds are:

What we do	Legal ground (UK/EU)
Provide and operate the Platform, create and manage your account	Performance of a contract
Process bookings, payments, payouts, refunds and Cancellation Charges	Performance of a contract
Share booking details between the Client and the Chef so the booking can be performed	Performance of a contract
Match Clients with Chefs and rank or order Chefs (see Chef Agreement Section 6.2)	Legitimate interests (running an effective marketplace)
Publish Client reviews and ratings of Chefs, and use review scores in ranking	Legitimate interests (helping Clients choose Chefs and keeping the marketplace trustworthy)
Deliver gift cards and run the referral programme (contact the recipient, link the referrer and the referred person, apply rewards)	Performance of a contract with the purchaser or referrer; legitimate interests as regards recipients and referred contacts (delivering the gift and operating the programme)
Use Chef profile content (photos, menus) to promote the Platform (Section 7)	Legitimate interests (promoting the marketplace), under the licence in Section 18.3 of the Chef Agreement
Send transactional and operational messages by email, SMS or WhatsApp (booking confirmations, reminders, arrival updates, support)	Performance of a contract
Send marketing communications and personalised offers	Consent where required by law; otherwise legitimate interests. You can opt out at any time (Section 7)
Ask for and act on feedback, including satisfaction surveys and invitations to review us on independent review platforms	Legitimate interests (understanding and improving the service). You can opt out (Section 7)
Monitor and record communications made through the Platform	Legitimate interests (keeping bookings and payments on the Platform, and evidence for complaints, disputes and chargebacks). See Section 4
Record event check-in time and location, and collect event evidence	Performance of a contract with the Chef (check-in is a payout condition of the Chef Agreement); legitimate interests as regards Clients and guests (evidencing attendance and service delivery). See Section 5
Defend payment disputes and chargebacks, and resolve complaints	Legitimate interests (defending legal claims and keeping the marketplace fair)
Run fraud prevention checks through our payment provider, and detect, prevent and address fraud, misuse or illegal activity	Legitimate interests, and legal obligation where applicable. Failing a check can lead to a booking being cancelled or Platform access withdrawn (Section 5 of the Booking Terms)
Use AI tools, under human oversight, to help draft support responses and assemble complaint, dispute and chargeback evidence	Legitimate interests (efficient support and dispute handling).
Handle incidents and insurance claims involving a Chef’s insurance	Legitimate interests (managing incidents and claims)
Use your name, image or likeness in our marketing materials	Consent (Section 7)
Report Chef identity and earnings information to tax authorities	Legal obligation. See Section 6
Comply with other legal and regulatory obligations	Legal obligation
Set non-essential cookies (analytics, personalisation, marketing)	Consent (Section 12)
Improve and develop the Platform, including analytics	Legitimate interests

Aggregated or statistical data that does not identify you (for example, booking volumes or traffic trends) is not personal information, and we may use it for analytics and service improvement.

Information you are required to provide. Some information is required by law or is needed to perform our contract with you. If a Chef does not provide the tax information yhangry must collect and verify, payouts may have to be paused or the account closed. Without booking, payment and dietary information we cannot deliver a booking.

Automated decision-making. Chef matching and ranking use the performance data in Section 2, with the main parameters described in Section 6.2 of the Chef Agreement. Decisions with significant effects for a Chef (payout holds, no-show findings, account suspension) involve human review before a final outcome; they are not taken solely by automated means.

4. Communications monitoring and recording

We monitor and record communications between Chefs and Clients made through the Platform: the Platform messaging portal and the Platform calling facility. Using the messaging portal or the calling facility means the communications you send and receive there are monitored and recorded.

We do this for two purposes:

to enforce the rules that keep bookings and payments on the Platform (see Section 15 of the Booking Terms and Section 16 of the Chef Agreement); and

for reference in complaints, disputes and chargebacks, where these records form part of the evidence.

We do not monitor channels we do not operate, such as your own phone, email or WhatsApp conversations held outside the Platform.

We keep monitoring and recording records for two years, or longer where they are evidence in a live complaint, dispute, chargeback or legal claim.

5. Event check-in and event evidence

Check-in. On the day of an event, the Client is shown a check-in code and the Chef enters it on the booking. We record the time and GPS location of the Chef’s check-in. GPS location is captured once, at the moment of check-in; we do not otherwise collect a Chef’s location. If check-in is impossible for a reason outside the Chef’s control, attendance can be verified from other evidence instead (Section 11.1 of the Chef Agreement). The check-in record is the delivery record for the booking: it evidences the Chef’s attendance and is used to release payouts, resolve complaints and defend payment disputes and chargebacks.

Event evidence. Chefs upload photos of each event (and notes and photos for no-show and venue reports). These are collected as the delivery record and used only to evidence the service, resolve complaints and defend disputes and chargebacks. We never use event evidence for marketing. Chefs are instructed to photograph the food, preparation and venue setup and to avoid capturing guests; if you appear incidentally in an event photo, it is used only as described in this Section.

Between Clients and Chefs: each sees the information necessary to perform the booking (for example, names, event details, event address and dietary information). Chefs act as independent controllers of this information (Section 1).

Publicly on the Platform: Chef profiles (photos, menus, prices) and the reviews and ratings Clients leave, displayed with the reviewer’s display name. We may moderate or remove reviews that break our rules (see the User Content section of our Website Terms & Conditions; Section 18.1 of the Chef Agreement sets the review rules Chefs must follow).

Service providers: companies that process data for us, such as Stripe for payments and payouts, cloud hosting, email, SMS and WhatsApp messaging providers, customer support tools, survey and review-platform tools, AI and automation providers (Section 3), and analytics providers.

Fraud screening: fraud and payment screening is carried out by our payment provider (Stripe) as part of processing payments. We do not use external credit reference agencies.

Payment disputes and chargebacks: where a payment is disputed, we share relevant records (booking details, communications records, check-in records and event evidence) with our payment providers, the card networks and the cardholder’s bank to defend the dispute.

Marketing partners: to deliver offers and advertising, subject to your choices in Section 7.

Tax authorities: Yhangry Ltd is a UK platform operator. It may be required to collect, verify and report Chef identity and earnings information to HMRC under the UK’s platform reporting rules (implementing the OECD Model Reporting Rules for Digital Platforms). Equivalent information may be reported or exchanged under Council Directive (EU) 2021/514 (“DAC7”) and its national implementations, including with the tax authority of a Chef’s country of residence. For US Chefs, Yhangry Inc may report identity and earnings information to the IRS and state tax authorities on required tax forms (Section 30.3.2 of the Chef Agreement).

Authorities: where required by law, court order, or to protect rights and safety.

Insurers: where an incident or claim involves a Chef’s insurance, we may share relevant booking and incident information with the Chef and the relevant insurer.

Business transfers: in connection with a merger, sale or corporate reorganisation. We will notify you if this happens.

We do not sell personal information. In the preceding 12 months we have collected the categories of personal information listed in Section 2 and, where applicable, disclosed them for the purposes in Section 3 to the categories of recipients listed in this Section; tax authorities receive only Chef tax reporting data, and credit reference and fraud prevention agencies receive only fraud prevention data.

7. Marketing and your choices

You can opt out of marketing emails at any time using the unsubscribe link or your account settings.

Where required by law, we obtain your consent before sending marketing SMS messages. You can opt out of SMS at any time by replying STOP, and of WhatsApp messages by following the instructions in the message.

You can opt out of satisfaction surveys and review invitations using the unsubscribe link in those emails or by contacting [email protected].

No mobile phone numbers are shared with third parties or affiliates for their marketing or promotional purposes, and text messaging originator opt-in data and consent are not shared with any third parties.

Your name and likeness: we only use a Chef’s or Client’s name, image or likeness in marketing materials with their consent, which can be withdrawn at any time with effect for future use. A Chef’s profile content (photos, menus) is displayed on the Platform to promote their services and may also be used to promote the Platform, as licensed in Section 18.3 of the Chef Agreement; the reviews Clients leave are displayed under the licence Clients grant in the User Content section of the Website Terms & Conditions. Where marketing material features a Chef personally (their name, image or likeness, including a profile photo showing them), we first obtain the consent described above.

8. International transfers

The Platform is operated from the United Kingdom, and personal data is stored securely on cloud-based systems hosted in the United Kingdom and the European Economic Area (EEA). If you are outside the UK and EEA, your information is transferred to and stored there. Some of our service providers (Section 6), such as payment, messaging, survey and analytics providers, may process your information in other countries, including the United States.

Where information protected by UK or EU data protection law is transferred to a country without an adequacy decision, we use appropriate safeguards, such as the EU Standard Contractual Clauses and the UK Addendum or International Data Transfer Agreement. You can request a copy of the relevant safeguards by contacting [email protected].

9. How long we keep your information

Account data (including profile data and marketing preferences): for as long as your account is active and for up to 6 years after it closes, unless you ask us to erase your data sooner (Section 10). We keep consent and opt-out records for as long as needed to honour them.

Booking and transaction records (including dietary and allergy information and guest data): while the booking and any complaint, dispute or chargeback window remains open, then as required by legal, tax and regulatory obligations.

Reviews and ratings: published reviews remain on the Platform after the reviewer’s account closes, unless you ask us to erase your data (Section 10).

Communications monitoring and recording records: see Section 4.

Check-in records and event evidence: kept as the delivery record for the booking for up to 6 years after the event, or erased sooner on request (Section 10); we may keep what we need to defend legal claims.

Chef performance data: cancellations count towards the suspension limit over a rolling 12-month period (Section 10.3 of the Chef Agreement). Cancellation Charges are retained until cleared, then for the applicable limitation period (Sections 26.2 and 26.4 of the Chef Agreement). Response times, review scores and completion history are kept while your account is active and for up to 6 years after it closes, unless you ask us to erase your data sooner (Section 10).

Verification, insurance and tax reporting data: as required by the platform reporting rules and other legal obligations.

Everything else (including technical, usage and feedback data): for as long as needed for the purpose it was collected for (Section 3), and afterwards only where we need it to comply with law, resolve disputes or enforce agreements.

The 6-year periods above reflect the time limits for legal claims, and the tax and regulatory record-keeping rules that apply to us.

If you make a rights request (Section 10), we will respond within one month of receipt. Where a request is complex, we may extend by up to two further months; if so, we will tell you within one month of your request and explain why. Full erasure from backup systems can take up to 90 days after we action an erasure request.

10. Your rights

United Kingdom and EU/EEA. You have the right to: access your data; request correction or erasure; restrict or object to processing (including processing based on legitimate interests, and direct marketing at any time); request portability; and withdraw consent at any time where processing is based on consent. You may lodge a complaint with your supervisory authority: in the UK, the Information Commissioner’s Office (https://ico.org.uk/); in the EU/EEA, the authority in your country (https://www.edpb.europa.eu/about-edpb/our-members_en). We would appreciate the chance to address your concern first: contact [email protected].

United States (including California CCPA/CPRA). You have the right to: know what personal data we collect and how we use it; request access to, correction of, and deletion of your personal data; request portability; opt out of targeted advertising and of any “sale” or “sharing” of personal data (see Section 6); limit use of sensitive personal information where the law provides that right; and not be discriminated against for exercising your rights. Residents of other US states may have similar rights under their state’s law. If we decline your request, you may appeal by replying to our decision or emailing [email protected] with “Appeal” in the subject line; we will respond within the period your state’s law requires and tell you how to contact your state Attorney General if you are unhappy with the outcome.

Sensitive personal information (California). Some information we collect is “sensitive personal information” under California law: login credentials, dietary and allergy information (which can concern health), and the precise geolocation recorded at Chef check-in. We use sensitive personal information only to provide the services described in this policy, to verify service delivery, and to resolve complaints, disputes and chargebacks. We do not use or disclose it for purposes California law gives you the right to limit, so we do not offer a “Limit the Use of My Sensitive Personal Information” mechanism.

Everywhere else. Where the data protection law of your country of residence gives you rights over your information and that law applies to us, we will honour them. Contact [email protected] and we will respond in line with the law that applies.

We may need to verify your identity before acting on a request. An authorised agent may make a request on your behalf where the law allows. The response times in Section 9 apply to all rights requests.

11. Children

The Platform is not intended for anyone under 18, and no one under 18 may create an account or use the Platform. We do not knowingly collect personal information directly from children under 13 (US COPPA compliance). If we learn that someone under 18 has created an account, or that a child under 13 has given us personal information directly, we will delete that information promptly unless we are legally required to retain it.

A Client may give us limited information about a child guest, such as dietary or allergy requirements, so a booking can be delivered safely. We use it only for that purpose and as part of the delivery record, and we keep it in line with Section 9. We do not sell or share the personal information of anyone we know to be under 16. Event evidence photos are handled as described in Section 5, and Chefs are instructed to take particular care not to photograph children.

12. Cookies

We use cookies and similar technologies to enable Platform functionality, analyse traffic and usage, and provide personalised recommendations and marketing. We set non-essential cookies (analytics, personalisation and marketing) only with your consent, which we collect through our cookie banner when you first visit. There is currently no way to reopen the cookie banner afterwards, so to change your choice, block or clear cookies in your browser settings. See also the California “sale or sharing” point in Section 6.

13. Security

We implement technical and organisational measures to protect your data, including encryption in transit, access controls and payment processing through PCI-compliant providers. No system is 100% secure, and we cannot guarantee absolute security.

14. Changes to this Privacy Policy

We may change this Privacy Policy from time to time. If a revision is material, we will notify you before it takes effect, through the Platform or by sending you a notification. The revised policy applies from its effective date to the personal information we hold.

15. Contact us

Questions or concerns about this Privacy Policy, or requests to exercise your rights: [email protected].

Last Updated: 18 August 2026