Privacy
This page describes what UzMaps receives, what it keeps and for how long. It covers the map platform itself and the integrations built on it, including the UzMaps app in the laCafe marketplace.
It is written to be read, not to be agreed to. Where something is not collected, it says so, because "we may collect" is how a privacy page avoids answering the question.
The map platform#
A map is a series of requests for tiles, styles, fonts and search results. Each one carries what any HTTP request carries: an IP address, a user agent, a referring origin and, when the caller has one, an API key.
What is kept. Request counts per API key, per day, so a key's owner can see their own usage and so capacity can be planned. Standard web server logs, which contain IP addresses, for the short period needed to investigate abuse and faults.
What is not kept. No cookies are set by the map API. No identifier is assigned to a visitor and no profile is built. Search queries are answered and not stored against anybody. Locations are not tracked: when a map shows someone their own position, that position is computed in their browser or on their phone by the device, and is never sent to UzMaps.
Who else sees it. Nobody. Map data is served from our own servers in Uzbekistan; there is no third-party analytics, advertising or tag on the API.
The laCafe integration#
The UzMaps app in the laCafe marketplace is installed by a restaurant and runs on our servers. It asks laCafe for exactly two permissions, and cannot use any other.
| Permission | What it reads |
|---|---|
org:read | the restaurant's name, and its branches — name, address, opening hours as free text, and the map pin where one exists |
maps:geocode | nothing; it lets the app register itself as the restaurant's address-lookup provider |
What the app never sees. Orders, customers, the menu, sales reports, payments, staff and phone call records. Those need permissions the app does not request, so laCafe refuses them to it.
Address lookups. When a guest types an address on a restaurant's site, laCafe sends the app the text or the coordinate, and nothing else about the guest. No name, no phone number, no order. The lookup is answered from the map and is not stored.
What is kept. One record per install: the laCafe install and organisation ids, the restaurant's name, the permissions granted, whether registration succeeded, and when the branches were last checked. Support messages sent from the app's own page, with the text written and the address given for a reply. Nothing else.
Branches on the map. A restaurant is a public business and its branches are places on a public map. When an install's branches are checked against the map data, any branch that is missing becomes a candidate to be added, carrying the branch name, its address and its map pin. Two things are deliberately excluded: the branch phone number, which the restaurant gave laCafe for a different purpose, and any branch with no map pin, since adding one would mean guessing where it is. Candidates are reviewed by a person before anything is published, and a restaurant that would rather not appear can say so — see below.
Uninstalling. Removing the app in the laCafe panel stops it immediately: laCafe stops issuing tokens, the next call fails, and the app stops acting for that restaurant. The install record is kept so a reinstall is recognised and so support can answer questions about what happened.
Retention#
| What | Kept for |
|---|---|
| Web server logs | 30 days |
| Per-key request counts | 13 months |
| laCafe install records | while installed, and 12 months after removal |
| Support messages | 24 months |
Children#
UzMaps is a mapping service for businesses and their customers. It is not directed at children and does not knowingly collect anything from them.
Asking about your data#
Write to support@uzmaps.uz. Restaurants using the laCafe app can also write from the app's own page in the laCafe panel, which identifies the install automatically.
We answer requests to see what is held about an organisation, to correct it, to have it deleted, and to have a branch taken off the public map. There is no charge and no form to fill in.
Changes#
Material changes are noted here with the date they take effect. The current version of this page is the one in force.