Privacy Policy

TasteDesk builds ordering apps for restaurants. Each restaurant gets its own app on the App Store and Google Play — its own name, icon and branding — running on shared TasteDesk infrastructure. We are based in Yerevan, Armenia, and you can reach us at sales@tastedesk.am.

Two roles, and the difference matters. When you order from a restaurant through its TasteDesk app, the restaurant decides what it does with your order and your contact details — it is the controller of that data, and TasteDesk processes it on the restaurant's behalf. For the restaurant's own account with us — the owner and staff logins, the subscription, the billing — TasteDesk is the controller.

If you want a copy of your data or want it deleted, you can write to either us or the restaurant you ordered from; see your rights.

The app does not ask you to sign up. On first launch it creates a guest session for that one restaurant, and that session is what your saved addresses and order history hang off. There is no password, no email address and no social login involved.

The session token is stored in your device's keychain (iOS Keychain / Android Keystore), not in plain storage. Your name and your preferred order type stay on the device and are sent to the restaurant only when you actually place an order; Settings clears both.

Uninstalling is not deletion. It removes the app's own storage, but on iOS a keychain entry can outlive the app and be picked up again by a reinstall, and nothing about uninstalling reaches the server: the guest session, the addresses saved against it and your past orders stay where they are. To have them deleted, ask us at sales@tastedesk.am — see your rights.

We collect what an order needs to reach you, and not more.

• Contact details. The name and phone number you give at checkout, so the kitchen and the courier can reach you about your order.
• Delivery address. Street and number, entrance, floor, apartment, plus the map coordinates of the pin — what a courier needs to find the door. Saved addresses are kept against your guest session so you do not retype them.
• Your order. Dishes, quantities, options, any note you add for the kitchen, the total, the payment method you chose, and the order's status over time.
• Payment record. Which method you used and whether the payment succeeded. Card details are entered with the payment provider, not with us — see payments below.
• Location, only on request. Only when you tap the locate button on the address screen, and only while the app is open. There is no background location permission in the app, and nothing about it tracks you between orders.
• Technical session data. The IP address and device/browser identifier attached to a login session, kept so a session can be recognised and revoked. Plus ordinary server logs and crash diagnostics.

We do not collect advertising identifiers, we do not build advertising profiles, and there are no third-party analytics or ad SDKs in the app.

Staff who run the restaurant side sign in with a real account rather than a guest session. For those accounts we hold a name, an email address, a phone number, a hashed password or PIN, the role the account has, and the tokens behind email verification and password resets.

We also record active sessions and the devices authorised for a restaurant — the tablets on the counter and the kitchen printers — so an owner can see what is signed in and revoke anything that should not be. Subscription and invoice records are kept for the restaurant's account with us.

Depending on what the restaurant has enabled, you can pay in cash on delivery, by card, or through Idram or Telcell. Card payments are handled by the restaurant's bank gateway — ArCa or Ameriabank. Your full card number and CVV are entered on the provider's page and never reach TasteDesk's servers.

If you choose to save a card for next time, what comes back to us from the provider is a reference to it: the cardholder name, a masked number (for example 421744**5423), the expiry month and year, the issuing bank and country. That is enough to show you which card you are picking, and not enough to charge it anywhere else.

We do not sell personal data. It is shared only with:

• The restaurant you ordered from. Your order, your name, your phone number and your delivery address go to the restaurant's board and print in its kitchen. That is the point of the order.
• Payment providers. ArCa, Ameriabank, Idram or Telcell, when you pay by a method they handle. They act as controllers of what you give them, under their own terms.
• Google Maps Platform. Address autocomplete and geocoding run through our server against Google Maps so the address you type becomes coordinates a courier can follow. The text you search and the coordinates of your pin are sent; your identity is not.
• Our infrastructure and error-monitoring providers. Hosting, database and (where enabled) Sentry for crash and error diagnostics, all bound to process data only for us.
• Authorities. Where the law actually requires it.

Contact details, the delivery address and the order itself are processed to perform the order you asked for. Payment and invoice records are kept because tax and accounting law requires it. Session records, rate limiting and error diagnostics rest on our legitimate interest in keeping the service secure and working. Location is used only with the permission you grant on your device, and you can withdraw it at any time in your phone's settings without losing the ability to order — you can always type the address or move the pin by hand.

Orders and their delivery details stay for as long as the restaurant needs them for its records and for the retention period tax law imposes on it. Saved addresses live as long as your guest session does. Login sessions expire on their own and are deleted after expiry. Server logs and crash diagnostics are kept for a short operational window and then rotated out.

Traffic runs over HTTPS. Session tokens sit in the device keychain rather than plain storage, refresh tokens are stored hashed and rotate on use, and passwords and PINs are hashed. Each restaurant's data is scoped to that restaurant, so one restaurant's app cannot read another's orders or customers. No system is perfect; if something goes wrong that affects you, we will say so.

You can ask for a copy of the data held about you, ask for it to be corrected, ask for it to be deleted, object to processing, or ask us to stop while a complaint is resolved. You can delete a saved address yourself in the app at any time.

For anything wider, write to sales@tastedesk.am and tell us which restaurant's app you used, so we can find the right records. Because the restaurant is the controller of your order data, we may need to pass the request to it, and we will tell you when we do. We answer within 30 days.

The apps are meant for adults ordering food. They are not directed at children, and we do not knowingly collect data from anyone under 16. If you believe a child's data has reached us, write to us and we will remove it.

If this policy changes, the date at the top of the page changes with it. Where a change materially affects how your data is handled, we will make it visible in the app rather than relying on you to re-read this page.