Data & privacy
regional-privacy-2026-11-19-v4 · 19 November 2026
The operational marketplace stores authenticated account records on its server. It does not import the fictional records or local accounts from the separate review website. Guest and Host account access uses contact verification where enabled. Payments are not active.
Information used
When account access is enabled, contact verification, names, addresses, cooking preferences and consent records support account and order functions. Kitchen applications include contact details, a location pin and privately uploaded eligibility evidence. Do not include medical histories, card numbers, CVV, UPI PINs, bank passwords or unnecessary identity information in free-text fields or uploads.
Access and storage
Hostinger hosts the operational service and its dedicated database. Your authenticated session uses an HttpOnly cookie lasting up to 14 days; signing out removes that session. Profile data is scoped to the signed-in account and selected country. Kitchen eligibility documents are accessible only to that kitchen's account and the platform owner. The database records changes and operational events. Expired sign-in challenges, sessions and rate-limit records are eligible for bounded deletion 24 hours after expiry; the cleanup runs hourly and does not delete account or financial history. Operator identity, financial retention schedules and country-specific privacy disclosures are still being finalised by the owner.
Contact verification and payments
Email verification uses the configured mailbox provider. If mobile verification is enabled, Twilio Verify receives the mobile number and code verification request. Availability depends on the configured provider for the selected country. Payment-provider connections are not active; this portal cannot collect money, register a reusable payment mandate or make host payouts.
Saved baskets and combined payments
A signed-in guest may save dated meal selections and cooking instructions in a country-specific basket. Each checkout reserves individual meals under one provider payment. Each host receives only the fulfilment information for their own meals. Per-meal refunds and payout allocations remain separate, while the owner can reconcile the shared payment. Basket estimates do not reserve stock or take payment.
Updates and support
Order and support events create a private in-app inbox. When enabled, email updates are sent through the configured mailbox provider. Delivery attempts and limited error codes are retained for operational follow-up; an email failure does not change payment status. Support requests, replies, favourites and submitted meal requests are stored in the selected country account. Nearby eligible hosts see opted-in meal descriptions and cooking preferences, without guest identity, contact details or precise coordinates. A host receives fulfilment information only through an authorised paid order.
Maps and location
Map tiles are supplied by OpenStreetMap infrastructure. Tile requests disclose the map area being viewed and ordinary connection information. A kitchen or recipient pin is selected by a deliberate map click or the optional location button. Device location requires browser permission. If you use address suggestions, the typed query and selected country are sent by our server to Photon, operated by komoot. An optional address lookup using device location sends those coordinates to Photon to identify the area. The suggestion request is not saved as a location history by this application; ordinary service connection records may exist at those providers. You can use manual address and map controls instead. Precise kitchen details are not included in the public discovery response; authorised collection and fulfilment workflows use the necessary location/address details. Location is not used to send unsolicited invitations or marketing. If you enable nearby guest discovery, eligible nearby hosts may also see your revealed aggregate guest rating alongside your first name and approximate area. Review scores are linked to completed orders and stay blind until both parties submit or the review window ends.
Guest maps use approximate kitchen pins supplied by the public catalogue. Host delivery maps show recipient pins only for that host’s active delivery orders. Nearby discovery is optional and off by default. If you enable it, your first name and selected area become visible to approved kitchens within their service radius. Discovery pins are rounded to two decimal places before storage, roughly a kilometre of precision. Precise guest coordinates and billing addresses are excluded from nearby discovery. You can turn discovery off on the Guest map, which removes its stored coordinates. The setting is separate for India and Singapore. The optional location button displays your device position in the current map. When nearby discovery is enabled, pressing Save visibility stores and shares only your selected approximate area. Opening Directions sends the selected delivery destination to Google Maps. Test map locations are fictional.
Optional test workspace
The separate /try workspace uses fictional records stored under its own browser-local key for each market. It does not create operational accounts, orders or financial transactions. The owner can reset or export synthetic records for the selected market in the same browser through the Owner Portal. Avoid entering real personal or payment information into the test workspace.
Controlled account access
For a restricted country pilot, the owner may allow a particular email address or mobile number for up to 30 days. The service stores a matching hash, a masked contact hint, an owner-supplied label and an expiry, and records access changes. A hash is a matching safeguard, not anonymisation. Creating an invitation does not send messages, verify a contact, approve a kitchen or activate payments. Verification is still required. Expired or revoked access stops new activity; existing members can still sign in to see their own orders, correct existing account details and reach support. New orders, kitchen listings and offers require current recorded agreements.
Neighbourhood invitations
Invitation links contain only the selected role, country and optional city or area. They do not contain a member identifier, a precise location or contact list. Sharing is initiated by you through your selected app; we do not automatically send invitations or upload contacts. After verification, you may register joining interest for a city and role. The owner sees area-level interest summaries for launch planning.
Choices and contact
You can browse without signing in and decline device-location permission. Authenticated users can correct their account details and sign out on a shared device. Changing a profile does not rewrite historical order snapshots. Contact info@bay-leaf.eu about access, correction, deletion or privacy questions. Server records cannot be deleted by clearing browser storage. Public launch requires the responsible legal entities, lawful processing arrangements, retention periods and applicable rights procedures to be identified and reviewed.