Delish logo

Privacy Policy

This page explains the information that may be processed when using Delish-Dilkash web and mobile services, why it is used, and the controls currently available.

  1. About this policy

    This policy applies to the website, mobile application, and their related profile, ordering, delivery, and QR services.

    The information processed depends on the selected feature, sign-in state, and permissions the user grants on the device.

  2. Information processed

    Depending on how the service is used, the following information may be processed:

    • Phone number, information used during SMS-OTP verification, and tokens used to manage the sign-in session.
    • When provided by the user: first and last name, date of birth or age, gender, and profile image.
    • Saved address name and type, written address, coordinates, building, entrance, floor, apartment, intercom, courier instructions, and delivery contact number.
    • Selected branch, delivery or pickup type, cart contents, quantities, favorite products, language, and other preferences.
    • Order items, quantities, prices and totals, delivery fee, order type, status, and history.
    • Selection of CASH, CLICK, or PAYME, payment status, and the returned link or technical information used to proceed to payment.
    • Promo code, bonus, cashback, loyalty tier, and information related to participation in a referral feature.
    • Device identifier, browser user agent, platform or operating system, language, app version, last activity, and, where supported, push token or notification status.
    • The content of a general support request, order comment, rating, or feedback when submitted.
  3. How information is obtained

    Information is obtained from user actions, device capabilities, and the status of service features.

    • When the user enters information in phone, profile, address, checkout, or other forms, or makes a selection.
    • When the user browses the catalog, changes the cart or favorites, uses a QR flow, or creates or tracks an order.
    • When the device or browser sends technical information; geolocation, camera, and notifications are used when the relevant permission and support are available.
    • When a required service status is returned from SMS verification, payment, delivery, or order flows.
  4. Why information is used

    Information may be used to provide the following product functions:

    • Verify a phone number, sign the user in, and maintain the session.
    • Display or save the profile, language, branch, favorites, and other preferences.
    • Maintain the cart, recommend products, and place an order.
    • Select an address, calculate delivery availability and price, and provide details needed by the courier.
    • Create the order, send it to the selected branch, update its status, and display its history.
    • Start the selected payment method, reflect the returned payment status in the order, and open the payment link.
    • Operate promo code, bonus, cashback, loyalty, and referral features.
    • Respond to support requests, identify service errors, and support session and service security.
    • Send order status, news, or promotion notifications according to the user's choice and device capabilities.
  5. Payment-related information

    The current web checkout allows the user to choose cash payment or online payment through CLICK or PAYME.

    When an online method is selected, a payment link returned by the service may be opened, and the result needed to show payment status in the order may be received.

    The current web checkout form does not display fields for a card number, card expiry date, or security code. Processing by the selected payment service on its own page is outside this technical description.

  6. Cookies and browser storage

    The web service uses cookies and browser storage to operate the session and user preferences.

    • Sign-in session tokens and the selected language may be stored in cookies.
    • A device identifier, selected branch, delivery type, guest cart, and favorites may be stored in localStorage.
    • A QR cart and a flag indicating that a QR code was scanned may be stored in sessionStorage for the current browser session.
    • Geolocation, camera, and notification permissions are controlled through browser or device settings.
  7. Sharing with service categories

    To perform a selected feature, information may be exchanged with the relevant service categories within the required technical flow.

    • An SMS delivery service to verify the phone number.
    • The selected payment service to start an online payment and receive its status.
    • Push delivery infrastructure when notifications are enabled and supported.
    • A mapping or geocoding service to search for an address, select a map point, and determine coordinates.
    • Hosting and technical infrastructure that operate the website, API, data, and real-time statuses.
    • The selected restaurant branch, order operator, or delivery flow used to prepare and deliver an order.
  8. Information retention

    Account and service data is kept for as long as needed to provide the service, maintain security, resolve disputes, and meet legal duties; some session and preference information may be stored in cookies, localStorage, or sessionStorage.

    When an account is deleted, the profile and associated personal data are removed. Order and financial records that must be retained for lawful accounting and audit may be kept separately from the account after contact and address details are removed.

  9. Security

    The current interfaces use phone-number verification by SMS-OTP, authentication, and session management for relevant profile, address, and ordering functions.

    • Session information is used to keep the user signed in, and a sign-out control is available.
    • Use of geolocation, camera, and notification features depends on the relevant browser or device permissions.
  10. Available information controls

    The current interface allows users to manage the following information and settings:

    • View or update first and last name, date of birth, gender, and profile image in the profile.
    • Add, edit, or delete saved addresses and select a default address.
    • Sign out, or permanently delete the account and associated personal data.
    • Change geolocation, camera, and notification permissions and clear cookies, localStorage, or sessionStorage through browser or device settings.
  11. Account or information deletion requests

    A signed-in user can permanently delete the account through Profile → Delete account or at https://delish-dilkash.uz/delete-account after verifying the account phone number.

    Deletion revokes active sessions and the account cannot be restored. Order and financial records that must be retained by law may be kept separately from the user in anonymised form. Use the Help center for other data requests.

  12. Children's privacy

    A date of birth or age may be processed when the user provides it in the profile.

    Approved project documentation does not define a minimum age for using the service or a parental-consent rule, so this policy does not state such a requirement.

  13. Policy updates

    This policy may be updated when service features or information-use practices change.

    The current text is published on this page. Significant changes may also be communicated through available website or application notification channels.

  14. Contact

    Use https://delish-dilkash.uz/delete-account to delete an account.

    For other privacy or service requests, use Profile → Help center in the app or the current service contact channels published in the website footer.

Back to top