Privacy Policy
Cook At Mine™ is an online marketplace that helps Hosts find, talk to and book independent local Cooks for personalised meal prep in the Host's own kitchen. This policy explains what personal information we handle, why, who else processes it, how long we keep it and your rights.
Last updated: 2 October 2026
1. Who we are
Cook At Mine™ is a trading name of Lioness Kingdom Ltd, the data controller for the information described in this policy. Lioness Kingdom Ltd is registered in England and Wales (company number 16650834), registered office 3rd Floor, 86–90 Paul Street, London EC2A 4NE, United Kingdom, and is registered with the Information Commissioner's Office (reference ZC234268). Contact: hello@cookatmine.com or our contact page.
2. Information we collect
Account information — first and last name, email address, password (handled by our authentication provider; we cannot see it), or your Google account name and email if you choose to sign in with Google; postcode; account type (Host and/or Cook); the date you accepted our policies and confirmed you are 18 or over.
Profile information — display name, profile photo, bio, travel radius, rate, availability, cuisines, specialities, dietary specialities, languages, experience and services offered (Cooks). Hosts may add household details, typical requirements, dietary preferences, allergies and intolerances, and preferred dates/times.
Allergy and dietary information — you choose whether to provide this to help a Cook prepare suitable meals. It may reveal information about your health. It is shared with Cooks you connect or book with; please only provide information you want to share for this purpose.
Food photographs — portfolio photos you upload.
Verification information — identity documents (Cooks), proof-of-address documents, the name and address shown for the check, optional Level 2 Food Hygiene and Public Liability Insurance evidence, expiry dates, verification status and the reviewer's decision.
Connections, messages and requests — cooking requests, their status, messages sent through the platform, decisions to proceed, safety acknowledgements, blocks and reports.
Video introductions (Meet Your Cook) — who requested and accepted an introduction, the agreed date and time, and limited attendance information from our video provider (when each person joined and left the room). Calls are not recorded under the current implementation and we cannot view or listen to calls.
Bookings — booking date, start time, duration, agreed price, fees, status history, completion confirmations, problem reports, cancellations and their outcome.
Service address — the address where meal prep takes place (address lines, city, postcode and any access notes), entered by the Host for a booking.
Payment and payout information — see section 5. We never receive full card details or Cook bank details.
Notification information — your email communication preferences, and records of which notification emails were queued and sent to you.
Technical information — IP address, device and browser information, timestamps and error logs processed by our hosting and security providers.
3. What other users can see
- Public (anyone): display name, profile photo, broad location shown only as a postcode district such as W3, and for Cooks: rate, cuisines, specialities, availability, travel radius, portfolio photos, verification/credential badges and reviews.
- Never public: surname, email address, password, full postcode, service address, verification documents, payment or payout information, reports and admin notes.
- Shared with a specific user: what you send them in requests and chat; Host dietary/allergy details with Cooks they connect or book with.
- Service address: disclosed privately only to the Cook on that booking, and only once the booking has been paid and confirmed.
4. Why we use your information
- To create and run your account, profiles, discovery, messaging, requests and bookings — to provide the service you request under our agreement with you.
- To take payments, issue refunds and arrange Cook transfers — to carry out bookings; to keep financial records required by tax and accounting law.
- To arrange video introductions and check whether both people attended together — to provide the introduction and support fair, reliable decisions about its completion.
- To send account, booking, request, message and meeting emails — to keep you informed about the service. You can turn off optional email types in your notification settings.
- To review verification, reports, blocks and moderation matters, and to help prevent contact-detail sharing — for the legitimate interest of protecting people using a service in private homes, and to meet legal duties where applicable.
- To display reviews and ratings — for the legitimate interest of a trustworthy marketplace.
- To protect the service, diagnose faults and prevent abuse — for our legitimate interests in security and reliability.
- To answer support requests — to provide the service and respond to you.
- To handle lawful requests, disputes and claims — where required by law or necessary to protect legal rights.
Identity and address documents are reviewed to support safety and verification. Dietary and allergy information is used to help arrange suitable meals and may include health information. Because different information can require different protections under data protection law, we do not treat simply providing it as agreement to every possible use. Contact us before submitting sensitive information if you would like to discuss how it will be handled, or to request its removal, subject to applicable obligations.
We do not sell personal information and do not carry out advertising profiling.
5. Payments, Stripe and payouts
- Booking payments are processed by Stripe. Cook At Mine uses Stripe Connect: Host payments are processed into Cook At Mine's Stripe platform account, and Cooks receive applicable earnings through their own Stripe connected accounts.
- When a booking reaches the payment/confirmation stage, the Host pays the agreed service price plus a £2.99 Host platform fee. Stripe processes the payment. Cook At Mine does not receive or store full card details; we receive limited payment information from Stripe, such as payment and refund references, amounts, currency and status.
- After the booking reaches the applicable completion/release state, the Cook's earnings — the agreed service price less the £2.99 Cook platform fee — are transferred to the Cook's Stripe connected account.
- Cooks provide their identity and bank/payout details directly to Stripe during Stripe Connect onboarding. Cook At Mine does not receive, store or have access to Cook bank account details. We receive only the Stripe connected-account reference, onboarding/setup status, whether charges and payouts are enabled, whether details have been submitted, any reason Stripe has restricted the account, and the list of outstanding requirements Stripe returns.
Stripe handles payment and payout information under its own privacy information. You can review Stripe's privacy information for details of how Stripe processes information you provide directly to it.
6. Video introductions
Meet Your Cook video introductions are optional and run on Daily (Daily.co). Each introduction uses a private, invite-only room that only the two participants can enter and that expires after a limited time. No personal contact details or links need to be exchanged. Calls are not recorded under the current implementation by Cook At Mine, and Cook At Mine cannot view or listen to calls. Daily provides us with limited attendance information (join and leave times), which we use to decide whether both people were in the room together long enough for the introduction to count as completed.
7. Who we share information with
- Other users, as described in section 3.
- Stripe — payments, refunds, transfers and Cook payout onboarding.
- Daily — video introductions.
- Lovable — application hosting, database, file storage, authentication and email sending (Lovable Emails); notification email is delivered through Mailgun in the EU region. The infrastructure supporting these services may involve additional providers.
- Google — only if you choose to sign in with Google.
- Authorities where legally required, or where there is a serious risk to someone's safety.
- Professional advisers, or a buyer if the business is reorganised or sold.
8. International transfers
Some providers, including Stripe, Daily, Lovable and Google, may process data outside the UK, including in the United States. The legal protections applicable to a particular transfer depend on the provider and the destination. Please contact us if you would like information about the safeguards relevant to a particular provider.
9. How long we keep information
- Account and profile information: kept while your account is open. You can delete your account from your account area. When you do, your public profile disappears straight away and your profile, photos, preferences, saved payout link and other personal information we no longer need are deleted. Deletion may be delayed while a paid booking, payout, refund, open problem or retention hold is still outstanding.
- Records kept after account deletion: where money has moved on a booking, we keep the booking and payment record (amounts, dates, status and payment references) for accounting, tax, payment, fraud-prevention, dispute and legal purposes. These records are minimised: your name is replaced with “Deleted user”, and the service address and booking notes are removed. Messages in the conversation linked to such a booking, and reviews from it, may be kept in anonymised form where genuinely needed for disputes, chargebacks, complaints, safeguarding or legal obligations. Other conversations are deleted. Safety reports, administrator notes and verification decision history (not the documents themselves) may be kept where there is a legitimate or legal reason. We do not keep information indefinitely merely because an account once had a booking, and we do not currently apply a single fixed retention period to these records; they are reviewed and deleted when no longer needed.
- Verification documents: the uploaded file is securely deleted 90 days after a decision (approved or rejected), and no later than 180 days after a submission that is never completed. We keep a minimal audit record (user, status, date, document type and reviewer decision). Documents under an active safety investigation, complaint, fraud concern, law-enforcement request or legal claim are placed on a retention hold while that matter requires it. If you delete your account, your verification documents are deleted at the same time unless a retention hold applies.
- Financial and accounting records (amounts, fees, refunds, transfers, payment references and the minimum booking details needed to support them): kept as long as necessary to meet applicable legal, tax and accounting obligations. We do not apply a single period to all booking-related personal information.
- Service addresses: currently remain with the booking record; there is no separate automatic deletion schedule for them. Contact us to request removal when no longer needed, subject to any applicable legal or dispute-related need to keep the record. They are removed from booking records when you delete your account.
- Messages, requests and reviews: kept as part of the account and conversation record; there is currently no automatic deletion schedule for these records.
- Video-introduction attendance information: kept as part of the introduction record; there is currently no automatic deletion schedule for it.
- Notification and email records: kept as part of notification history; there is currently no automatic deletion schedule for them.
- Reports and safety records: may be kept where needed to protect users or deal with a legal claim.
- Technical logs: kept by our providers for security and troubleshooting; their retention periods may differ.
10. Security
We use access controls to limit who can read records, and verification documents are kept in private storage. Passwords are handled by our authentication provider. An administrator reviewing a verification request can open a document via a short-lived private link. Chat filtering helps prevent sharing of phone numbers and email addresses. No system is completely secure — please protect your own password.
11. Your rights
Under UK data protection law you can ask for a copy of your information, ask us to correct or delete it, restrict or object to its use, or receive it in a portable format. Where we rely on consent, you can withdraw it at any time. Many details can be changed in your account area. Contact us via the contact page or hello@cookatmine.com; we aim to respond within one month. You can complain to the Information Commissioner's Office at ico.org.uk or 0303 123 1113.
13. Age
Cook At Mine is for people aged 18 or over. We do not knowingly collect information from children.
14. Changes
We will update this page if our processing changes, with a new date and, for significant changes, a notice in the app or by email.
