This policy applies to the full Türkmen TagamGo application and its six user roles: Customer, Restaurant, Shop, Courier, Taxi Driver (shown as Driver in the app), and Sober Driver. The operator and data controller is Ýalkap Kerimov. Contact: emir.haky@gmail.com.

Data we process

• Account, authentication, and consent: telephone number, one-time-code request and verification records, name, city, role, account status, authentication sessions, internal user ID, and the accepted Terms/Community Rules version and server timestamp.
• Profiles and partner content: business name and address, working hours, vehicle information, profile photo, categories, menu or product names, descriptions, prices, and photos.
• Location: precise location selected or supplied while using map, address, delivery, taxi, sober-driver, or availability features; saved addresses; pickup, destination and route points; and recent executor location while an executor explicitly marks themselves available.
• Orders, purchases, and payment choice: selected items or service, quantity, server-calculated price, the cash form of payment, delivery or trip details, notes, participants, status, cancellation reason, and order history. The app does not collect bank-card information.
• User content and support: temporary active-order participant-chat messages, reviews and comments, complaints, reports, complaint attachments, and communications with support.
• Device and security: app/device installation ID, push token, platform and language, IP address, user agent, timestamps, session and security logs, and records used to prevent spam, abuse, and unauthorized access.

Why we use the data

We use this data to create and authenticate accounts; review partner applications; operate each role; publish partner catalogs and technically validate uploaded photos; calculate and fulfill cash orders, deliveries, taxi trips, and sober-driver requests; match available executors; provide maps and notifications; keep order history; handle complaints and support; review reported content; prevent fraud and abuse; secure the service; and comply with legal obligations.

Who receives data

• Visitors and signed-in customers. Before an order, an approved and published restaurant or shop business profile shows its business name, full business contact telephone number, full business address, map point, working hours, profile/catalog content, prices, and aggregate ratings. This public phone-and-address disclosure applies only to approved public restaurant and shop profiles; customer, courier, taxi-driver, and sober-driver profile telephone numbers and addresses are not exposed through the public partner catalog.
• Participants in a transaction. The customer, selected restaurant or shop, and assigned courier, taxi driver, or sober driver receive only the order, contact, address, route, status, and temporary order-chat information needed to perform that order or trip. The chat is not public or general direct messaging. Sending closes when the order is completed, delivered, or cancelled; existing messages follow the retention rules below rather than being published or automatically erased at that moment.
• Google LLC — Firebase Cloud Messaging and Firebase Installations. Google processes an installation identifier, push token, app identifiers, technical service data, and the notification payload so we can route optional push notifications. The embedded Firebase Messaging privacy manifest also declares limited unlinked “Other Data Types” for an Analytics purpose; this technical SDK processing is not used by us for advertising or cross-app tracking. See Firebase privacy and security.
• Apple Inc. — Apple Push Notification service and iOS reverse geocoding. Notification routing uses an APNs token and notification payload. When the user explicitly asks the app to turn a selected/current coordinate into a readable address, iOS may send that coordinate to Apple's network-based geocoding service. See Apple Privacy.
• Operating-system geocoding provider (iOS and Android). An explicit readable-address lookup may pass the selected/current coordinate to the geocoding provider configured by the device operating system: Apple on iOS, and the Android geocoding provider selected by the device vendor or system configuration (which may be Google or another provider). Availability and the exact Android provider depend on the device. Location access can be controlled in device settings.
• State Company of Electro Communications “Turkmentelecom”. The service is hosted on network infrastructure allocated to Turkmentelecom, which carries server traffic. Internet and mobile network operators also necessarily transmit communications.
• Our controlled SMS gateway and the subscriber's mobile operator. They process the telephone number and verification-message content to deliver a one-time code.
• Operator, support and moderation personnel. They access data only as needed to resolve support requests, review reports and uploaded content, protect users, and operate the service.

We may disclose information when required by law or to protect users and the service. We do not sell personal data and do not use it for third-party personalized advertising.

Maps

The app uses MapLibre to display locally bundled or first-party-hosted map data derived from OpenStreetMap and CARTO sources. Normal map rendering does not send your precise location directly to OpenStreetMap or CARTO. On iOS or Android, an explicit request for a readable address can use the operating-system geocoding provider disclosed above. Map data attribution: © OpenStreetMap contributors and © CARTO.

Photos and public content

A normal partner application remains in review and the partner workspace stays unavailable until an administrator approves it. All partner accounts follow the same approval rules. A profile, menu, or product photo is decoded, resized, re-encoded, size/type checked, and stored on our server, then published immediately without pre-publication moderator approval. It may be reported and an administrator may remove it after publication. Text is checked automatically and may also be reviewed after a report. Public content can be rejected, hidden, or removed under the Terms and Community Rules.

Retention and deletion

A one-time code is valid for five minutes. Authentication sessions expire after no more than 30 days unless revoked sooner. Other data, including existing order-chat messages, is kept while the account and relevant transaction are active and afterward only as reasonably needed for operations, accounting, safety, dispute resolution, enforcement, or legal duties. Closing chat sending at a terminal order state does not itself delete its history. Reports and moderation history may be retained while a safety or legal issue remains open.

You can initiate permanent account deletion in the app through Profile → Delete Account. Confirmation atomically cancels every non-terminal order in which the account is a participant. The server deletes the user record, sessions, push tokens, verification/SMS records, private profile and catalog records, content authored only by that account where retention is unnecessary, and uploaded files not referenced by another lawful record. Necessary completed or cancelled orders and shared structured identifiers are de-identified where reasonably possible. To protect other participants, access-restricted reports, moderation history, attachments, and relevant transaction or chat evidence may remain while reasonably needed for safety, disputes, enforcement, accounting, or law. We remove direct account identifiers and detected occurrences of the registered phone number from retained text, but free-form text or media supplied by participants may contain other personal information that must remain with necessary evidence. If a blocked participant deletes their account, we retain only the private pseudonymous message-author link and block edge needed to keep their retained chat messages hidden from the blocker; it is not displayed publicly or used to restore the account. Restricted backups may retain a protected copy temporarily until their normal overwrite cycle completes.

A blocked user may verify the same telephone number to enter a restricted screen that permits viewing block information and deleting the account; the restricted session cannot use business features.

Your choices and security

You can correct profile data in the app, choose whether to grant location and notification permissions, report content, block a chat participant, and request access or correction by email. Location permission is requested only while using the app; executors share recent location with the service only after explicitly enabling availability. We use HTTPS, access controls, hashed session and OTP credentials, restricted administrative access, moderation, and backups, but no system can guarantee absolute security.

Children and changes

The service is not directed to children acting without a parent or legal guardian where consent is required. Material changes to this policy will be posted at this URL with a new effective date.