Skip to content

Privacy Policy

How MiyoTrip handles travel enquiries, information you provide, and your privacy choices.

Local review draft, prepared on 4 October 2026. This is not an approved or effective privacy policy. The operating legal entity, registered address, applicable jurisdiction and effective date remain to be confirmed. Items awaiting confirmation are identified below.

On this page

1. Who this notice covers

This draft concerns the MiyoTrip website, travel-planning and contact forms, and communications about those enquiries. It distinguishes features checked in the current local preview from arrangements still required for launch. The organisation responsible for your information is [legal entity to be confirmed], with registered address [to be confirmed] and registration country or region [to be confirmed]. MiyoTrip is the brand name, not a confirmed legal entity.

Questions can be sent to [email protected], WhatsApp +8613861800000, or Contact us. Booking information is available in Booking Guide, with website and booking boundaries in Terms & Conditions.

2. Information you choose to provide

You can browse without creating a traveller account. When sending an enquiry, the form identifies required and optional fields. Omitting necessary contact details may prevent a reply; optional information helps explain your preferences. Please keep free-text messages relevant to the trip.

  • Contact information: name, email, country or region, preferred contact method, and optional phone or WhatsApp number.
  • Trip planning: interested route, approximate dates, duration, adult and child numbers, interests and your message.
  • General enquiries: selected topic and message, together with contact information.
  • Submission records: related route, originating page, processing status, and privacy acknowledgement time and version.

3. Website requests and security records

Serving a page or receiving a form involves connection information such as an IP address and browser request details. The checked local web server writes access logs. Form protection also derives a keyed request identifier from an IP address for a 60-second rate-limiting window. The enquiry record itself does not store raw IP or browser user-agent fields.

Production hosting, delivery and security providers, their log contents, access and retention periods remain to be confirmed. This distinction does not mean that visiting the site leaves no technical records.

4. Why information is used

Enquiry information supports understanding your trip, answering questions, discussing a proposed itinerary and recording the conversation. Submission records support follow-up and handling enquiries. Connection information supports delivering pages and protecting forms from abuse. The checked local preview stores enquiries locally; an operational CRM or email dispatch service has not been confirmed.

The final notice must identify the applicable basis for each purpose after the entity and relevant laws are settled, including any applicable pre-contractual, contractual, legal-duty or consent basis. A required privacy acknowledgement is not newsletter permission or blanket consent to every use. Simply browsing is not agreement to all processing.

5. Travelling companions and children

At the planning stage, the form asks for adult and child numbers rather than the identities of every traveller. Please tell companions before providing their information and only do so with appropriate authority. A parent or guardian should handle an enquiry for a child.

Any later need for passenger names, ages or identity documents must be explained separately, with the relevant safeguards and any required guardian permission. The operational procedure and applicable age thresholds are awaiting confirmation.

6. Sensitive information and traveller media

Do not place passport copies, payment-card details or medical records in an initial enquiry. If an accessibility or dietary need is relevant, start with a short practical description. Any necessary sensitive information will require a defined purpose, suitable collection method and applicable permission before collection; those arrangements remain to be confirmed.

A private enquiry is not permission to publish your name, review, photograph or video. Public traveller material requires separate checks of permission and permitted use; local sample content is not proof of verified publication consent.

7. Who may receive information

Enquiry records in the local preview are available through authorised administration. No functioning CRM dispatch or confirmed production email delivery is being represented by this draft.

Before launch, the final notice must identify the roles of hosting, email, customer-management and support providers, and the information each needs. If a trip later requires information for accommodation, transport or a local travel partner, the relevant recipients, purpose and necessary details must be specified. These are proposed service categories, not a statement that enquiries are already shared with them. Any lawful disclosure to public authorities must follow the applicable requirements.

8. Where information is handled

The production storage locations, supplier locations and international data routes have not been confirmed. The final policy must explain relevant destinations, recipients and transfer arrangements, including any required safeguards or separate permissions. It must also explain how you can obtain relevant information about those safeguards.

We do not claim that all information stays in a particular country. Using an external communication or video platform may involve its own international processing.

9. How long records are kept

A final retention schedule is awaiting confirmation. It must distinguish unanswered or completed enquiries, booking-related records, acknowledgement records, security logs and backups, using the purpose and any applicable record-keeping duties to set each period or criterion.

The current system does not provide confirmed automatic deletion of every record. Removing or anonymising enquiry contact fields does not by itself erase all metadata, logs or backups. The disposal process, backup expiry and treatment of lawful retention exceptions must be settled before a deletion promise is published.

10. Storage and security

The checked application encrypts enquiry contact information and detailed messages at the application layer. Other fields, including the originating page, traveller numbers, related route, status and privacy acknowledgement record, are not all encrypted in the same way. Administrative permissions restrict access to enquiry records.

This is not a claim of end-to-end encryption or guaranteed security. Production transport protection, key management, access reviews, backups and incident response require operational confirmation. Please use the contact details above to report a suspected privacy issue.

11. Cookies and external services

The current site uses language-related storage and saves guide-checklist progress in your browser. The cookie notice records acknowledgement; it is not a category-by-category preference manager. See Cookie Policy for the checked storage and browser controls.

A YouTube privacy-enhanced player loads when you choose to play a film, which can still send information to the provider. Choosing WhatsApp, email or a social link opens the relevant external service, whose own notice also applies. The current preview has no installed advertising or analytics tags; future additions require renewed assessment and disclosure.

If your browser needs fallback emoji images, WordPress may request those images from s.w.org. That request can disclose your IP address and technical request information to the remote resource service. This is conditional display support, not an image request made on every page; the resource operator and processing locations still require deployment review.

12. Your requests and choices

Depending on applicable law and the processing basis, you may request access or a copy, correction, deletion, restriction, an objection or transfer of information, and withdraw consent where processing relies on it. Withdrawal does not automatically undo earlier lawful processing. You may also have a right to complain to the relevant regulator.

Contact [email protected] or Contact us, describe your request and identify the enquiry if possible. Identity checks should be proportionate; please do not send an identity document without instructions. The responsible team, response process and deadlines remain subject to confirmation under the applicable law.

13. Marketing and route suggestions

The current site has no newsletter subscription feature. Sending an enquiry or selecting the privacy acknowledgement does not subscribe you to promotional messages. Any future marketing programme needs its own stated purpose, appropriate permission or other applicable basis, and a practical way to stop messages.

Route suggestions match travel preferences with available itinerary content. They do not make booking decisions or decisions with legal or similarly significant effects. You can ask a person about a suggestion or discuss different preferences.

14. Updates and details awaiting confirmation

Changes to actual services or data use should be reflected in a dated notice, with any additional notice or permission required for a new purpose. The draft preparation date is not an effective date. Before publication, the following must be resolved:

  • Legal entity, registered address, registration region, applicable laws and effective date.
  • Purpose-by-purpose processing bases, companion and child procedures, and sensitive-information safeguards.
  • Production suppliers, recipients, locations and international transfer mechanisms.
  • Retention periods or criteria, log configuration, disposal and backup handling.
  • Privacy contact responsibilities, request deadlines, complaint route, incident procedures and any representative required by applicable law.

[email protected]