NEYRO Short answer: without checking the contract, neither “restaurants never see customer data” nor “your own app automatically imports an aggregator’s customer base” is a safe claim. Data needed to prepare or deliver an order, ongoing access to contact records and marketing use are separate questions.
What the platforms’ published policies say
Wolt’s Kazakhstan privacy notice says partners may receive information needed to prepare or deliver an order; where necessary this can include a phone number, for example to clarify a substitution. Glovo’s privacy notice lists the establishment selling a product among recipients while an order is being carried out. This supports operational sharing for a specific order; it does not establish that every merchant always sees a full phone number or purchase history, can export a customer database, or may send marketing messages.
For Wolt partners in Kazakhstan, the Merchant App terms state that the partner’s obligations for processing Wolt customer data are set out separately in its contract with Wolt. Check the exact product, contract and console available to your business.
Four questions to keep separate
- What is visible for an order? Check which fields staff can see for preparation, substitutions, delivery and support.
- Can data be exported? A field in an order card does not prove bulk export or access after fulfilment.
- How long may records be kept? Confirm retention and handling in the contract and applicable privacy rules.
- Can the restaurant market to the customer? Access to contact details is not, by itself, marketing consent. Use clear notice and obtain voluntary consent where required.
What a restaurant’s own app changes
A website or app creates a separate direct-order channel. For orders placed in that channel, the system can support service and analytics within its stated purposes and valid legal basis. It does not automatically transfer order history from Glovo or Wolt, and it does not remove customers’ rights over their personal data.
A practical rollout is to define the direct-order journey, required fields, staff access, retention and consent first; then connect the app to a CRM and test it with a sample order. Do not copy aggregator contacts into a marketing list until the contract and lawful basis have been checked.
Restaurant checklist
- Review a test order in the merchant console and note the exact fields visible to staff.
- Ask the platform in writing about contact details, history, exports and retention.
- Compare the answer with your contract and product (marketplace, own delivery or another service).
- Design contact collection and consent separately for direct orders.
- Measure repeat orders by source without merging platform data unless authorised.
Takeaway: the useful question is which data the restaurant can access for a specific operation and which further uses the contract and customer consent permit. Checked against published policies on 30 September 2026; your merchant console and contract were not reviewed.
Official sources: Wolt Kazakhstan privacy notice; Wolt Merchant App terms (Kazakhstan); Glovo privacy notice.