Privacy Policy
Who processes data
KyrgyzGo is the service operator. The owner must publish the legal name, address and required registration details after qualified legal review. Contact channels are available on the support page.
Data we process
For a request we process your name, phone number, optional email, selected service, dates, guest or passenger count, place or route and optional comment. Request chat messages are stored with the request.
Technical analytics contain only the event type, time, internal listing or request identifiers and a pseudonymous session hash. Phone numbers, email addresses, message text, private links and secrets are not written to analytics.
Why data is used
Data is used to send a request to the selected provider, check availability, communicate about the request, operate chat, protect the service and improve usability. Sending a form does not itself confirm a booking.
Who can access data
Contact details and request information are available to the selected provider and KyrgyzGo administrators. Infrastructure providers may process only the data needed to operate the service. The processor list and any cross-border processing require legal review.
AI assistant
AI is optional. KyrgyzGo currently uses DeepSeek as an external provider. Only the travel context needed for an answer, bounded recent conversation history and current catalog search results are sent. Profile contact details and server-side booking drafts are not sent to DeepSeek.
KyrgyzGo stores AI conversation history on its own server for up to 30 days. A request is created only after the customer presses the explicit submit action.
Do not send passwords, access keys, session data, passport, payment, medical or other sensitive information to the AI assistant. The catalog and request flow work without AI.
Retention and deletion
AI conversations are deleted according to the configured retention period. Exact retention and deletion procedures for accounts, requests, chats and backups require owner action and legal review. Access, correction or deletion requests can be sent through support.
Security and cookies
The service uses a protected session, CSRF protection and private request-link tokens. Do not publish or forward a private request link. Cookies support the session, security and pseudonymous product analytics; they are not used for advertising profiles.
Synthetic test data
Synthetic catalog listings remain marked internally and create test requests only. A clear warning is shown before submission; no real service, payment or real-provider notification is triggered.