Privacy Policy

The public inquiry form is designed to collect less. Do not submit passport scans, payment-card details or medical records through it.

Information collected

The form may collect name, email, nationality or country, approximate dates, group size, comfort level, interests, message, consent time and technical anti-abuse signals. WordPress stores the inquiry privately and sends a notification to the configured site email.

Purpose

We use the information to answer the inquiry, assess service fit, prepare a proposal, protect the form from abuse and maintain a basic communication record. We do not sell inquiry information.

Sensitive booking information

If a verified provider later needs passport or other identity data for a booking, it must explain the purpose, responsible entity, secure channel and retention. Do not send it merely because an unverified contact asks.

Retention and deletion

Inquiry records should be kept only as long as reasonably needed for response, follow-up, legal obligations and dispute prevention, then deleted or anonymised. You may request access, correction or deletion through the site contact, subject to legal retention duties.

Hosting and service providers

The site uses WordPress and SiteGround hosting. Email delivery, security, caching and analytics tools may process technical data according to their configurations and terms. Any future advertising or behavioural analytics must be added to this notice before deployment where required.

Security

No internet system is risk-free. We limit public-form content, use anti-spam controls and restrict inquiry visibility. Travellers should also avoid reusing passwords or sending identity documents over public chat.

Data minimisation by design

The first-contact form asks for information needed to understand and respond to a trip request. It is intentionally not a booking form. Nationality or country can help identify questions that need official checking, but the public form does not require a passport number, scan, card detail or medical file. Free-text information should remain proportionate.

Technical anti-abuse data may include submission time, network or browser signals and challenge results. The purpose is protecting the form, not building a hidden traveller profile. If analytics or advertising tools are introduced, this notice and consent controls must be updated before relevant processing begins.

Who may receive inquiry information

Authorised Kakagogo personnel and service providers supporting WordPress hosting, security or email may process the inquiry to operate the website and respond. A licensed travel partner receives details only when needed to prepare or perform a clearly identified service. We do not publish an inquiry or sell it as a lead list.

Medical details belong with the treating institution, and passport data needed for real-name booking belongs in the verified provider process. Where translation or coordination requires limited sharing, the purpose and recipient should be explained. Access is limited to what the role needs.

Retention, deletion and legal records

Unqualified or abandoned inquiries should not be kept indefinitely. Active proposal and contract records may require longer retention for service, accounting, legal or dispute purposes. Deletion or anonymisation follows the record type and applicable obligations rather than one arbitrary period for everything.

A request for access, correction or deletion should identify the email used and relevant inquiry without sending additional sensitive documents unless identity verification becomes necessary. Some records may be retained where law or a legitimate dispute requires it; the reason should be explained.

Security and traveller responsibility

Hosting, updates, access control, anti-spam and backups reduce risk but no internet transmission is perfectly secure. Travellers should use a unique email password, verify the sender before opening a link and never provide a one-time payment or login code to someone claiming to be a guide.

If Kakagogo later requests sensitive booking data, verify the legal entity, contract and channel first. Report suspicious messages through a known site contact rather than replying to the same sender. A security incident affecting personal information is assessed and handled according to applicable duties.

International visitors and cross-border communication

A traveller may access the website or communicate from outside China while hosting and service providers operate in other locations. Internet routing, email and supplier involvement can create cross-border processing. Before a sensitive booking transfer, the responsible entity and purpose should be identified. The public inquiry form remains intentionally limited so initial international contact does not require high-risk data.

Applicable privacy rights depend on the traveller, entity, processing and law. This notice describes Kakagogo’s operating approach but does not reduce mandatory rights. A final contracting entity may provide an additional notice for booking data, payment, hotel or licensed travel fulfilment. Read that notice before supplying identity documents.

Cookies and future changes

WordPress, security and session functions may use technically necessary storage. Optional analytics, advertising or personalisation should not be introduced silently; their purpose, provider and consent treatment must be documented where required. Material policy changes update the page date. Continued browsing is not used as a substitute for consent where law requires a clearer choice.

Children and group inquiries

A parent or authorised adult should make inquiries involving children and should minimise information about them. Age range can affect pacing and ticketing, but a public message does not need a child’s full birth date, school, passport or photograph. Group organisers must have an appropriate basis before sharing another traveller’s information and should not upload a roster merely to request a sample route.

If exact identity details later become necessary for a booking, the responsible licensed provider explains the fields and secure channel. Kakagogo does not use children’s information for behavioural advertising or publish a family’s trip story without an appropriate permission process.

Privacy choices should remain understandable at each stage. An initial inquiry needs only planning facts; a proposal may need contact and group details; a confirmed real-name booking may require passport information through the responsible provider; a medical institution controls its own clinical record. Kakagogo does not collapse those stages into one permanent traveller profile. When information is no longer needed for the stated purpose or an applicable record duty, it should be deleted or anonymised rather than retained because storage is inexpensive.

Questions about data should identify the relevant inquiry or booking and the action requested. We will not ask a person to publish additional private information to prove a concern. Where identity verification is necessary, the method should be proportionate to the risk and use a verified channel. Complaints about another hotel, insurer, medical institution or licensed travel seller may need to be directed to that entity because it controls the relevant record.