Skip to main content

Trust Center

Trust is clearer when the limits are explicit.

This page explains what ChefFlow verifies, what it does not verify, how payment records work, and where support escalation starts.

How booking paths workPricing source of truth

What We Verify

  • - Public chef listings are tied to a real ChefFlow account before they appear in the directory.
  • - Directory approval checks profile completeness, service details, and contact-path accuracy.
  • - If a profile shows an insurance or certification badge, ChefFlow has an active uploaded record on file for that chef.
  • - If payment is taken through a ChefFlow checkout flow, the payment record runs through Stripe and can be referenced by support.

What We Do Not Verify

  • - ChefFlow does not run a universal background check on every chef.
  • - ChefFlow does not guarantee that every chef meets every local licensing or permit requirement in every jurisdiction.
  • - ChefFlow does not guarantee event quality, food safety outcomes, or chef-client fit.
  • - ChefFlow does not offer a marketplace-wide replacement guarantee, automatic refund promise, or universal no-show insurance.

What a profile badge actually means

Buyer trust gets weaker when records, marketing copy, and support promises blur together. ChefFlow separates them on purpose.

Current record badge

A public insurance, certification, or business-record badge means ChefFlow has an active uploaded record on file and the visible effective/expiry window has not lapsed.

Self-reported profile detail

Service statements such as travel policies, dietary handling, cleanup, or carrying insurance can come from chef-published settings. Those details help buyers plan, but they are not the same as a current-record badge.

Why a badge may disappear

If a record expires, is removed, or is no longer active, the public badge can disappear even if the chef still mentions that topic elsewhere on the profile.

Payment, cancellation, and support expectations

ChefFlow has different public booking paths, but the trust posture is the same: review the written terms before paying, use the chef contact path first, and use support for escalation when the issue is bigger than routine planning.

Payment protection

If payment is processed through ChefFlow, checkout runs on Stripe. ChefFlow does not store full card numbers, and there is a payment record tied to the booking.

Cancellations and refunds

Deposit, cancellation, and refund terms come from the chef agreement, quote, or booking terms. Review those written terms before paying. ChefFlow does not impose one universal refund policy across all chefs.

Disputes

If a payment was processed through ChefFlow, support can review the payment record and booking timeline. That does not guarantee a refund. Card disputes may still need to follow Stripe or bank processes.

Chef no-show or day-of issue

Contact the chef immediately, then email [email protected] with the event date, chef name, and payment reference if one exists. ChefFlow can review the record and escalate internally, but does not promise emergency replacement coverage today.

Support Escalation

  1. 1. Use the written chef contact path first for timing, menu, and scope questions.
  2. 2. If the issue involves payment, cancellation, or a serious service problem, email [email protected] with the event date and any payment receipt.
  3. 3. For security concerns, email [email protected].

References

How It WorksPricingContact[email protected][email protected]

Support Can Help With

  • - Review ChefFlow payment records, booking timestamps, and account-linked communications that exist inside the product.
  • - Clarify which booking path was used and where the written terms or payment trail should live.
  • - Escalate serious service, payment, or security issues internally for review.

Support Cannot Do

  • - Guarantee refunds, replacement chefs, or a specific dispute outcome.
  • - Override a chef-client written agreement that was made outside ChefFlow.
  • - Certify that a chef is compliant with every local law, permit, or licensing rule everywhere they operate.

Want to test these workflows in your own operation?

Sign up free and validate inquiry, event, and payout workflows end-to-end.

Sign up

Looking to hire a chef instead? Start with how the booking paths work.

Looking to book a private chef?

Book a Chef

Request your private dining experience

Food near you

Restaurants, caterers, food trucks

How it works

The full process explained