Only what running Drops actually requires.

This Privacy Policy describes how Servd LLC (“we,” “us,” or “our”) collects, uses, shares, and protects personal information through Drops (drops.servdchefs.com and the ordering widget embedded on a chef’s own site — together, the “Platform”).

Drops has two kinds of people on it, and this policy covers both: Chefs, who sign up for an account to list items and run drops, and Diners, who place an order from a chef’s drop without ever creating an account of their own.

We collect only what running the Platform actually requires — taking orders, processing payments, sending order confirmations, preventing fraud, and improving the product. We don’t sell personal information to advertisers.

Drops is one of two products Servd LLC operates. The other, SERVD, is a marketplace for booking private chefs for in-home dinners, and keeps its own separate Privacy Policy. For a chef who uses both, we mirror your basic chef-profile information — display name, bio, cover photo, and account status — from SERVD into Drops each night, so you don’t have to maintain two separate profiles. Nothing else crosses between the two: a diner’s contact and order information stays in Drops and is never shared with SERVD, and Drops never writes back into SERVD’s own systems.

From Chefs, when you create an account:

• Account information — name, email, and phone number, authenticated and stored by Clerk (we never see or store your password).
• Business information — your display name, bio, avatar, catalog items and photos, and pickup or delivery details for each drop.
• Payout information — collected directly by Stripe when you connect a payout account through Stripe Connect. We store only the resulting Stripe account reference — never your bank details, government ID, or anything else Stripe collects during that onboarding.

From Diners, when you place an order:

• Contact information — the name, email, and (optionally) phone number you enter at checkout, so the chef can identify your order and we can send your confirmation. No account or password is created.
• Order information — what you ordered, any note to the chef, and a delivery address if you chose delivery instead of pickup.
• Payment information — your card details, collected and processed directly by Stripe. Drops does not see or store your full card number. If a chef takes your order in person instead (cash or a card reader at pickup), payment happens entirely outside the Platform.

From anyone browsing the Platform:

• Device and usage data — IP address, browser type, the pages you visit, and timestamps, collected to operate the Platform, keep it secure, and understand which pages are actually useful (see Google Analytics below).
• Cookies — a session cookie from Clerk (Chefs only, to keep you signed in) and, where enabled, Google Analytics cookies. Diners placing an order never receive a login cookie of any kind.

We use the information above to:

• Create and operate a chef’s account and catalog.
• Take an order, calculate what’s owed (including any sales tax, calculated through Stripe Tax), and process payment.
• Send transactional email — order confirmations, receipts, and account notices. We don’t send marketing email unless you’ve separately asked to hear from us.
• Pay chefs for the orders they’ve fulfilled, through Stripe Connect.
• Detect and prevent fraud, abuse, and payment disputes.
• Understand aggregate usage (page views, drop-off points) so we can improve the Platform. We don’t build advertising profiles from this data.
• Comply with tax, accounting, and other legal obligations.

We use a small number of vendors to actually run the Platform. Each processes only the data we send them, and only for the purpose below.

• Stripe — payment processing, sales-tax calculation, and Stripe Connect payouts to chefs.
• Clerk — chef account authentication and session management. Diners never have a Clerk account.
• Supabase — our primary database (accounts, catalog, drops, orders). Encrypted at rest.
• Vercel — application hosting and content delivery.
• Resend — transactional email delivery (order confirmations, receipts).
• Google Analytics — aggregate site-usage analytics, where enabled.

We publish updates to this list within 30 days of adding or changing a service provider.

We share information only in the limited circumstances below. We do not sell personal information to advertisers and we do not share it with data brokers.

• Between a Diner and the Chef they ordered from. A chef sees the name, contact details, order contents, and delivery address (if applicable) for orders placed with them — never orders placed with a different chef.
• With our service providers, as described in Section 04.
• For legal reasons — when required by a subpoena, court order, or applicable law, or when we believe it’s necessary to protect the rights, safety, or property of anyone using the Platform.
• In a business transfer — if Servd LLC is acquired or merges with another company, information may transfer as part of that transaction.
• With your consent for anything else.

Depending on where you live, you may have the right to request access to, correction of, or deletion of your personal information, or to object to certain uses of it. To exercise any of these rights, write to legal@servdchefs.com — we’ll respond within the time your local law requires (30 days, absent a specific law that says otherwise).

A Diner can also ask the chef they ordered from to delete their contact information from that chef’s own records, in addition to asking us directly.

A Chef can delete their account at any time from Settings. Doing so removes your catalog and profile from public view; completed-order records are retained as described in Section 07 for tax and accounting reasons.

We keep order records (what was ordered, contact details used for that order, and payment metadata) for as long as needed for tax, accounting, and dispute-resolution purposes — generally seven years, matching standard record-keeping practice for payment transactions. Chef account information is kept for as long as the account is active, plus a reasonable period after deletion to prevent fraud and resolve any outstanding disputes.

Data is encrypted in transit (TLS) and at rest. Payment card data never touches our own servers — Stripe handles that directly, and Drops only ever receives a token referencing the transaction. Access to the underlying database is limited to the small team operating the Platform. No system is perfectly secure, and we can’t guarantee absolute security, but we treat this seriously and will notify affected users if we ever learn of a breach involving personal information.

The Platform isn’t directed at children, and we don’t knowingly collect personal information from anyone under 13. If you believe a child has provided us information, write to legal@servdchefs.com and we’ll remove it.

We’ll update the date at the top of this page whenever we make a change, and post a notice on the Platform for any change we consider material.

Questions about this policy or your data — write legal@servdchefs.com. For anything else, see our Contact page.