Discretion is the product.

Who we are

Jetblanc is a private aviation partner desk based in Bangkok, Thailand. Travel, yacht, golf, hotel, event and concierge businesses can embed, share or refer our flight-request service to their clients. We coordinate private charter through established aviation partners; flights themselves are performed by licensed third-party operators.

What we collect

When you send a trip request we collect the route, dates, passenger count, aircraft preferences, baggage, pets, special requirements and budget, together with your name and chosen reply channel (email or WhatsApp).

We also record how you found us, including referral or campaign references attached to the page you visited, and any correspondence that follows. When you allow optional analytics, advertising platforms may also measure page and request interactions using cookies or similar identifiers.

For partner enquiries, including LinkedIn forms, we collect the details you submit, such as your name, email, company, whether you arrange client travel and the timing of any Asia trip. We keep the form and campaign reference, submission time and contact-permission record. Please do not include passenger names or private client details in a partner enquiry.

How we use it

For flight requests, we use your information to arrange your trip: preparing options with our sourcing partners, replying on your chosen channel and keeping an accurate record of what was requested and offered.

For partner enquiries, we use your information to respond about private-flight support and referral terms, check your business and role, and avoid duplicate contact. An enquiry does not automatically create a partnership or authorize us to contact your clients. We ask for permission before sharing a client trip brief for sourcing.

Campaign and interaction information is used to understand which outreach produces genuine requests and to prevent Jetblanc from optimizing advertising toward irrelevant enquiries. Optional advertising measurement is not required to use the flight desk.

We do not sell your information, and we will not add you to marketing lists without asking you first.

Who we share it with

To source and perform a flight, relevant trip details are shared with the disclosed fulfillment partner and aircraft operator, limited to what they need to quote and operate the trip. Identifying personal details are shared only when operationally required, and the contracting party is always named to you before you commit.

We use trusted service providers to run the site and request workflow, including Vercel for hosting, Supabase for secure request records, and Resend and FormSubmit for operational email delivery. If you contact us through WhatsApp, its own terms also apply. Optional advertising measurement may be provided through Google Tag Manager and the advertising services configured through it after you allow analytics.

If you submit a LinkedIn form, LinkedIn processes the submission under its own privacy terms and makes it available to Jetblanc. We use Google Workspace for business email and maintain internal enquiry records with access limited to those handling the enquiry. Consent to analytics on our website is separate from your LinkedIn form submission.

Jetblanc Partners and price estimates

If you request a flight through a Jetblanc partner's page, website button, WhatsApp link or partner hub, we record which partner introduced you and, with your consent, share the status of your request with that partner. Partners see your first name and last initial, route, dates, passenger count and request stage. They do not see your contact details unless they submitted them, and they never see supplier identities or costs.

To apply attribution and client-protection rules fairly, we keep salted one-way digests of your email and WhatsApp number linked to the introducing partner. Raw contact details are not stored in those records. A partner link you open is remembered in your own browser for 30 days so a later request can be credited correctly.

When you use the instant estimator, we store the route, dates, passenger count, the estimate shown and a keyed digest of your network address for abuse prevention and accuracy measurement. Estimates are linked to a request only if you go on to submit one.

Partner applicants and partner team members provide business and contact details, sign-in email, accepted terms version and, for payouts, the payment details they enter. We use these to run the program, send sign-in codes and partner updates, and pay earned fees.

Requests through AI assistants

An assistant may submit your itinerary and reply contact only with your explicit approval. These requests enter the same Jetblanc desk and operational email workflow as website requests. We record the submitting integration's random identifier and consent attestation, not a verified identity or authority to buy a flight. Your assistant provider handles its own conversation and credentials under its own privacy terms.

Self-service API access does not require personal details. We store a one-way key hash, random identifier, creation and expiry times, test status and policy version. Keys expire after 30 days and can be revoked. A credential can access only its own request receipts, client-visible updates, explicitly linked and published proposals, and staff-recorded confirmation evidence. It cannot access other customers' records or internal supplier notes. Use a separate key for each customer or private workspace.

For delegated OAuth access, we verify your email through Supabase and send a sign-in code through Resend. We record your user and approved application identifiers, read or approved-action permissions, consent time, expiry and revocation. A necessary, HTTP-only sign-in cookie lasts up to 30 minutes. Agent grants last up to 30 days and can be revoked at jetblanc.com/oauth/consent. Revocation is checked on each private request; it does not delete the operational history. Consent and sign-in pages do not load our optional advertising measurement.

Approved clarification answers, amendments and reconfirmation requests are retained with the trip record and notified to the desk. Staff-recorded booking outcomes include the contracting party, reference, final terms fingerprint and private supporting evidence. Private evidence references are not exposed through the agent API. These records document human-reviewed external actions, not authority for an assistant to spend money.

The isolated sandbox accepts only fictional scenarios and fixed actions, not traveller names, contact details or arbitrary notes. Saved workspaces use a one-way credential hash, fixture state, retry records and expiry time. They become inaccessible after 24 hours and are physically removed during subsequent workspace creation. They do not create operational requests, emails or supplier contacts. Hosting security logs may still record access metadata.

To limit abuse, the agent interface maintains counters using a keyed, daily-changing digest of the connecting network address; our application does not store the raw address in those counters. Hosting providers may retain network and security logs under their own policies. Operational counters and expired access records are reviewed during maintenance. We retain authorised trip records under the retention terms below.

Do not send passport numbers, payment credentials, medical records or unnecessary passenger identities through this interface. Revoking a key does not cancel a sourcing request or erase business records. Contact sun@jetblanc.com for correction, cancellation, access or deletion; we may need to verify your authority before acting.

Analytics choices

Advertising measurement does not load until you choose Allow analytics. You can decline without affecting the request form or WhatsApp service. Campaign references submitted as part of a flight request remain attached to that business record so we can identify how the request reached Jetblanc.

Advertising click identifiers are retained only after you allow analytics. If you decline, a request may still include non-identifying campaign labels such as its source or campaign name, but not the advertising platform's click identifier.

You can change a stored analytics choice at any time through Analytics choices in the site footer. Jetblanc sends the updated choice to its measurement tags before any later measured interaction.

How long we keep it

We keep trip records for as long as needed to arrange and support your travel and to maintain accurate business records. If you ask us to delete your information, we will do so unless a legal or safety obligation requires otherwise.

Partner enquiry records are kept while needed to handle the enquiry or an agreed business relationship. We review inactive enquiries and remove information we no longer need, while retaining limited records necessary to respect opt-outs and maintain accurate business records.

Your choices

You can ask at any time what we hold about you, ask us to correct or delete it, or withdraw consent. One message to flights@jetblanc.com or a reply in an existing thread is enough.

International handling

Because we arrange travel across Asia through partners in several countries, trip details may be handled outside the country you are in. We share only what the trip requires.

Changes to this policy

This policy is written deliberately in plain language. As Jetblanc formalizes its corporate structure, a counsel-reviewed version will replace it; the promises above will not weaken.