Company and business details
Agency name, contact person, business communication details, and other business identifiers shared voluntarily.
Yono DMC uses this website as a trade-facing company and inquiry platform. The information submitted here is meant to support communication, quotation, and destination operations for travel agents, not to create a consumer retail data funnel.
Trade Only
Primary audience
Quote + Portal
Main channels
Service Use
Data purpose
Account Flow
Support path
Scope of this policy
Business inquiry data
Used to review agency, partnership, or company-level requests routed through the site.
Quote request data
Used to prepare quotations and route a live travel brief into the right destination workflow.
Business follow-up
Used to maintain continuity when the desk needs to clarify, amend, or support an active request.
Helpful B2B privacy pages explain the why behind data collection, not just the mechanics.
The public forms and communication channels are intentionally commercial and trade-focused, so the data categories reflect that purpose.
Agency name, contact person, business communication details, and other business identifiers shared voluntarily.
Destination, dates, pax mix, rooming pattern, service scope, budget cues, and other trip-planning details shared through site forms and operational follow-up.
Messages exchanged through quote forms, operational follow-up, and business-support channels when the desk reviews a trade request.
If portal access or trade onboarding is provided, operational and account-support details may also be maintained for continuity.
Useful privacy pages explain the operational purpose behind data collection in plain language.
To respond to destination inquiries and trade requests from travel agents
To prepare quotations and support operational coordination when a booking moves forward
To manage business communication, account verification, and follow-up on active requests
To maintain internal records needed for service continuity, support, and commercial review
The emphasis stays on operational necessity rather than broad or undefined business use.
Information is shared only with internal teams or relevant suppliers when needed to price or operate the requested service.
Data is not positioned for consumer retail fulfillment because the website is designed for trade-only business use.
Information may be disclosed if required for legal, regulatory, or financial compliance connected to a booking or account relationship.
Business data is not intended to be sold as a public marketing list or redistributed outside the operating context of the request.
The strongest privacy pages explain not only what is collected, but how long it is likely to remain relevant and who should be able to access it.
Business information should be accessible only to the teams and workflows that need it for support or operations.
Information is generally kept only as long as it remains commercially or operationally useful for the business relationship.
The site is not intended to function as a public consumer booking funnel or a retail traveler database.
Privacy-related review should flow through the official account or quotation record when a business relationship is active.
Privacy sits best inside a connected cluster with terms, policy, and inquiry pages.
Terms and conditions
Read the broader site-use and inquiry-channel conditions that sit alongside this privacy policy.
Payment terms
See the related commercial page that explains how invoice and account records fit into the trade process.
Request a quote
See the main trade form where destination and commercial data is actively collected.
Next Step
Good privacy pages should make the policy path obvious so agencies know how information is handled inside the trade workflow.