Skull in a chef's hat with crossed chef's knivesSous ChefCHEF’S CREW

Sous Chef privacy policy

Effective October 28, 2026. Sous Chef: Chef’s Crew is operated by John Prodromidis. Contact us through Sous Chef support.

Account and kitchen information

We save account names, email addresses, account identifiers, salted password hashes and hashed session tokens. Saved kitchen records can include recipes, notes, approved supplier invoices and purchase amounts, source filenames, invoice file hashes, prices, stock counts, duties, schedules, team details and timecards. Optional labor models save hourly cost estimates and cook names or references; these are not verified salary or payment records. Payroll tools save employee reference mappings, reviewed time classifications, snapshots, draft exports and matching time-receipt comparisons. No payroll payment or provider submission is performed.

Plans and subscription payments

Free and Pro kitchen tools both require an account. Creating a Free account does not require payment details or start a trial. When a kitchen owner chooses Pro checkout, Stripe receives the owner’s name, email, a kitchen reference and subscription/payment details. When tax-enabled checkout is available, Stripe also collects your billing address and saves it to your Stripe customer record to calculate applicable tax on checkout and renewals. Payment details are entered on Stripe’s hosted pages; Sous Chef does not store full card numbers or card security codes. Our database keeps the kitchen plan, paying account reference, Stripe customer, checkout, subscription and invoice identifiers, trial-use status and access dates. Signed Stripe notifications confirm payments and subscription changes. Billing is restricted to the paying owner; purchasing does not grant ownership or change employee permissions.

The first Pro trial for a kitchen lasts three days, requires a payment method and automatically converts to the displayed monthly price unless canceled before the trial ends. Owners can manage payment details and cancellation through Kitchen plan when billing is connected. Canceling renewal keeps already-paid access through its verified period. Deleting a paying account stops its future app subscription billing before sign-in access is removed; Stripe may retain financial records under its own retention requirements. Free accounts and existing kitchens are not charged automatically.

Location and documents

Foreground location is requested for punches or when a manager chooses the kitchen location. Punch coordinates are sent for immediate geofence verification; application timecards save the result, distance and accuracy, rather than raw punch coordinates. These results are linked to the worker and known kitchen location. Managers can save exact kitchen coordinates. There is no background location monitoring.

Bundled document tools read original photo, PDF, Word, text and CSV bytes on your device. Approved structured information is sent when you save it. Invoice imports can include extracted line text, filename and file hash; recipe imports save approved recipe fields and the filename. A recipe URL you choose is sent to the server for a public-page request; the approved recipe and source URL are saved through the recipe workflow. iOS sharing uses temporary files cleaned up when sharing closes. Copies you save or share remain at your chosen destination.

Product scanning and prices

Barcode camera frames and uploaded barcode photos are decoded on your device; these images are not sent to the server or stored. When you choose a product lookup, the barcode is sent to our server and to Open Food Facts and Open Prices to identify the product and retrieve dated community price observations. These providers receive the barcode and our server request, without your account details, kitchen records or device location. Opening a source link sends your browser request to that provider. Lookup results are not saved as a search history. Product barcodes and reviewed product, supplier, pack, price, date and source details become shared kitchen records when you save a food cost. Price observations are not verified invoices or current stock reports.

Employee contacts and shift texts

Chefs and managers may save employee phone numbers, station preferences and private cook notes. Contact records and notes are restricted to chefs/managers; employees can view and manage their own shift-text number and choices. Directory entries do not create an account or grant kitchen access. Private chef notes are excluded from employee schedules and text messages.

Automatic shift reminders and missing-clock-in checks require a Pro kitchen, a configured sending service, kitchen enablement and the employee’s direct agreement in My shift texts. A chef cannot give this agreement for someone else. We save the employee’s account and kitchen references, email, mobile number, selected message types, agreement time, policy version, a random agreement reference, withdrawal time and enrollment-confirmation status. Changing the number or enrolling again after withdrawal requires fresh agreement. We do not sell mobile numbers or share SMS consent with third parties for their marketing. Read the shift text terms.

When activated, Twilio receives the recipient number and work message, including kitchen/shift details, and returns message identifiers and status. Private chef notes are not sent. Reply STOP or choose Stop texts to withdraw. Signed provider opt-out events disable later texts; a START reply alone does not re-enroll someone. HELP replies direct you to support. The attempt/result ledger keeps kitchen, staff, shift and agreement references, event times, status and provider identifiers, without the phone number or message body. These references remain linked to the account and are not anonymous data. Accepted messages are not proof of delivery, and uncertain send outcomes are not automatically retried.

No SMS sending is activated by default. Account deletion removes the linked staff contact profile, direct agreement and text-result records; nonpersonal shared usage counters survive deletion. Separately identified notes authored by a departing chef are removed from retained employee profiles. Twilio’s provider records and your phone carrier follow their own retention rules.

Staff shift emails

Staff email reminders and arrival checks are a separate Pro channel, off by default and awaiting sender activation. Chefs record the employee’s permission for work emails and choose reminder types. Eligible recipients must have joined this kitchen with an active app account. When enabled, Resend receives the recipient email, kitchen and shift details, a message in the selected style and a stop-email link. Private chef and shift notes are excluded. Opening the stop-email page does not change preferences; confirming it stops future staff emails for that kitchen without requiring sign-in or a paid plan. SMS and password-reset settings are separate.

The delivery ledger stores the recipient email, staff/kitchen/shift references, event time, status, provider identifiers, a random claim reference and a hash of the stop-email token. It does not store the email body or raw token. Provider acceptance does not prove inbox delivery. Unknown send outcomes are retained without automatic retries. Shared daily/monthly staff sending counters have no employee information and are independent of password-recovery limits. Staff email jobs and linked contact details are removed when their account is deleted; provider copies follow Resend’s retention settings.

Password recovery and barcode cache

Password recovery requires a connected email service and is disabled until configured. When enabled, Resend receives the account email and a single-use reset link. The link expires after 30 minutes; the database stores only its token hash. Using it signs out existing sessions. Recovery abuse counters store a keyed hash of the submitted email and network address, a count and expiry; raw addresses are not stored in these counters. Public barcode results may be cached for six hours. The lookup limit stores only a kitchen identifier, its current minute and count, without an employee identifier or barcode search history.

Purpose and access

We use records to authenticate accounts, provide kitchen tools, attribute work, share information with authorized members, answer support requests and protect the service. Action histories retain who completed, verified, corrected or reviewed work. Existing kitchen permissions control access. Cloudflare Workers and D1 host the service and database; Cloudflare processes network and service information to deliver and protect requests. Public recipe sites receive the server request when you import a page. We do not sell information or use advertising tracking. No external OCR, payroll payment, automatic email/SMS invitation or patient/EHR integration is connected. Shift texts and emails use their separately configured, opt-in services described above.

Support, logs and retention

The support form saves reply email, message and optional signed-in account ID. Its abuse counter stores a daily hash derived from the network address supplied by Cloudflare, a count and expiry. Raw addresses are not stored in that counter. Hashing does not establish that network information is anonymous. Counters become eligible for cleanup after their two-day boundary and are removed on subsequent request-service activity. Closed support tickets and resolved legacy account-request records become eligible for cleanup after 90 days, measured from their last update, and are removed on later request-service activity. Open support tickets have no automatic expiry. Do not send passwords, payment details or patient information. No support email is sent automatically.

Cloudflare retains operational request logs for troubleshooting, security and service performance. These logs include request URLs and query parameters, raw network IP addresses, browser and request headers, network-derived location, connection and TLS metadata, response status, request identifiers and execution timing. Network-derived location is separate from foreground device GPS. URLs can contain kitchen or record identifiers, so these logs can be linked to an account or kitchen. Application errors use a generic operational message; that does not remove the provider request metadata.

The current Cloudflare Workers Free plan has a standard Workers Logs retention period of three days. Database Time Travel provides a separate recovery window of up to seven days on this plan. These provider copies are separate from live application records, support counters and deletion receipts. Account deletion does not immediately erase provider logs or recovery history. Other provider security records and any separately configured destinations follow their own settings and retention; the three-day period is not a promise for every provider copy.

Account deletion

Open Management (or More), Delete account. Confirm your current password and type DELETE MY ACCOUNT. Where ownership and associated records are clear, deletion removes the account and every sign-in session in an automatic transaction and displays a completion receipt. The revoked session on your device can recover only that receipt for up to seven days while it remains on the device; it cannot open account or kitchen data. The server retains a hash of that revoked session with the receipt and its expiry. This restricted lookup remains linked to the deletion transaction and is not anonymous data. No new login credential, email service or support conversation is needed.

Account deletion removes your sign-in account and sessions, linked staff profile, contact details, text/email-result records and personal authored notes. Shared kitchen recipes, completed work, stock counts and recorded hours remain with Former team member labels and a non-sign-in history identifier. Other people keep their work and current permissions. Historic payroll drafts containing removed personal identifiers are withdrawn; retained timecards and sanitized snapshot evidence remain work history. Original payroll CSV artifacts cannot be downloaded again through the app after withdrawal. A private kitchen containing only your records is removed. Owners see an impact preview and may choose an existing active chef or manager as successor; no live transfer occurs without that choice. Shared kitchens may also continue with existing manager access and no owner. Older accounts are eligible for the same deletion process. A concurrent change can stop the transaction for a retry, without a completion receipt or partial deletion.

Only a configured record-specific legal retention rule can preserve a restricted copy, with a documented basis and retention date. Expired restricted copies and receipts are removed during subsequent deletion-service activity; this is not a guarantee of deletion at the exact expiry instant. Other kitchen records have no general automatic expiry. Copies independently exported or shared cannot be recalled by account deletion.

Your choices

You can sign out, change your password, export available records and use in-app account deletion. Device settings control camera and foreground location permissions. Specialty-meal tools are planning drafts and should not contain patient records. For access questions or a privacy issue, use Support.