Legal

Compliance policy

How Cheffar approaches trust, payments, cook screening, and day-of standards—so hosts, cooks, and our team share the same bar for running private meals at home.

Effective 10 August 2026

Purpose

This policy explains the compliance standards that guide Cheffar operations: bookings, payments held until the meal is done, cook verification, host and kitchen safety, and fair use of the product.

It works with our Terms of service, Privacy policy, Trust & safety pages, and in-product rules. Where they conflict with marketing copy, these documents and the in-product rules control.

Who this applies to

This policy applies to Cheffar staff, contractors acting for Cheffar, hosts, cooks, and third parties who access booking, payment, or support data while providing services to Cheffar.

Independent cooks remain responsible for the food and service they deliver and for their own licenses and legal duties. Cheffar is responsible for running the product, screening standards we publish, and handling funds as described in the booking flow.

Cook screening and tiers

Cooks who list on Cheffar complete the steps we require before serving hosts. Screening may include identity checks, document review, food-safety or professional evidence, profile review, and training modules we assign.

We use public tiers—Executive Chef and Cordon Bleu—to describe listing levels. Tiers reflect the criteria we set in product, not a government license. We may pause, reverse, or close a cook listing when screening fails, documents lapse, or risk warrants action.

Bookings and the home kitchen

Bookings are for private home hospitality: a screened cook preparing in the host’s kitchen for the agreed time and scope. Hosts must provide accurate location, access, guest count, and any critical dietary needs. Cooks must only accept bookings they can complete safely and lawfully.

No party may use Cheffar to launder payments, mis-state a meal, or arrange activity outside what the booking allows. We may cancel bookings that break this standard and report serious issues where law requires.

Payments and held funds

Cheffar labels labor fee (cook work) separately from market budget (ingredients for that meal). A platform fee, when it applies, shows at checkout.

Funds for a booking are collected and held until shopping and service meet the status rules in the product. Release, refund, and dispute paths follow those rules and our payment partners’ requirements. Circumventing holds, fake refunds, or off-platform payment pressure is a breach of this policy and our Terms.

Safety and reporting

Hosts and cooks must treat each other with respect in the home. Harassment, threat, discrimination, theft, or unsafe food practice is grounds for account action and may be reported to authorities.

Report concerns through in-product tools or Contact / support as soon as practical. We review reports with the booking record and applicable screens. Emergency situations: contact local emergency services first, then notify Cheffar when you can.

Data and privacy compliance

Staff and processors only access personal and booking data for legitimate product, support, safety, or legal reasons. Handling rules sit in our Privacy policy. Training and access controls limit misuse. Suspected data incidents must be escalated to Cheffar leadership immediately.

Markets and local law

Cheffar launches and expands by market (city and country). Where local law requires food-hygiene registrations, tax, consumer, or payments rules, we aim to operate within those requirements and may limit features until compliance is in place.

Wallets and local payment methods appear only where live. Using a method outside listed rails for a Cheffar booking does not receive product protection.

Fraud, reviews, and platform integrity

Fake accounts, review fraud, fee evasion, identity concealment, and spam listing are prohibited. We use technical and manual review to protect hosts and cooks. Proving abuse may lead to removal of content, holds on payouts, or permanent ban.

Records and cooperation

We keep booking, payment, and screening records for as long as needed for safety, disputes, finance, and legal duty (see Privacy policy). We cooperate with lawful requests from authorities and with payment partners’ compliance programs.

Updates

We may update this policy as markets, product, or law change. The effective date above will change when we publish a revision. Material changes may also be noted in-product or by email.

Contact

Compliance questions: Contact on Cheffar or support inside your account. Reference the booking ID when the question relates to a specific meal.