From the website to a human reply
The route finder may keep the four route answers in this browser’s session storage so progress can be restored. It does not store the traveller’s email address or optional note there.
When a traveller submits the email form, Supabase validates and saves the route context, email address and optional trip note. The page shows a saved state only after that save succeeds.
If the landing URL contains utm_source, utm_medium or utm_campaign labels, they are stored with the submitted email enquiry to show how that request reached Homeground. They are not added to the WhatsApp message and are not used for cross-site tracking.
Resend then sends a notification to Homeground’s monitored Gmail inbox. For email enquiries, Reply-To is the traveller’s address, so a person can answer directly from the Gmail thread.
If a traveller chooses WhatsApp, clicking the direct link passes the structured route summary and page language to WhatsApp to prepare a message. The link does not contain the traveller’s email, name, phone number or optional note, and it does not create a website enquiry.
Homeground receives the WhatsApp message and the traveller’s WhatsApp number only after the traveller taps Send in WhatsApp. The website cannot confirm whether WhatsApp opened or whether the message was sent.
A prepared email link is only an emergency fallback after the service confirms that an enquiry was not saved. It is not the normal contact path and opening it is never described as a successful submission.
Purpose and fields
Only what is needed for the active request
A traveller can use the route finder without contacting Homeground. These are the information groups used if they later send an email enquiry or open the direct WhatsApp handoff.
Browser session, submitted email enquiry or WhatsApp prefill
Route context
Party, travel style, total nights, pace, proposed cities and page language describe the starting route. An email enquiry also keeps the internal route version; the WhatsApp prefill does not.
Submitted enquiry and Gmail notification
Traveller email
The address entered by the traveller is used to reply to this enquiry. It is not consent for unrelated marketing.
Submitted with an email enquiry only when entered
Optional trip note
Fixed dates, flights, cities, walking needs and other priorities help a person review the route. Medical records should not be entered.
Outbound link after the traveller chooses WhatsApp
Direct WhatsApp handoff
The structured route summary and page language are passed to WhatsApp to prepare a message. The website does not ask for a WhatsApp number; Homeground receives the message and number only after the traveller taps Send.
Email enquiry service
Technical request record
A public reference, time, form version, route revision, landing path, optional URL campaign labels and limited anti-abuse data support reliable submission, source understanding and duplicate prevention.
Service providers
The services in this enquiry path
The locations below identify the configured primary service regions. These providers may also use global infrastructure for delivery, security, support and legal compliance, so processing may occur outside the traveller’s country.
- Website hosting
GitHub Pages · static public siteServes the website and may process ordinary web-request metadata under GitHub’s terms.
- Studio inbox
Google Gmail · monitored Homeground inboxReceives the notification and holds the later email conversation. Google may process data through its global infrastructure; Homeground does not claim a precise physical Gmail location. The website never uses the Gmail password.
- Enquiry storage
Supabase · Seoul (ap-northeast-2)Validates and stores the enquiry before the page can show a received state.
- Email notification
Resend · Tokyo (ap-northeast-1)Sends the saved enquiry to Gmail with the traveller address in Reply-To.
Direct handoff · no website number fieldReceives the structured route summary when the traveller opens the direct link. The studio receives the message and traveller number only after the traveller taps Send. WhatsApp and Meta may process the handoff and later conversation under their own terms and infrastructure.
- Analytics and AI chat
DisabledThe current site does not use non-essential analytics, third-party marketing tracking or an AI chat widget. Simple campaign labels already present in the landing URL may be attached to a submitted email enquiry.
Retention and control
How long information is kept
Homeground applies the following rules to the enquiry records and service copies it controls. Providers may retain limited security, billing or legal records under their own obligations.
- Data controller
Homeground China studioThe studio decides how enquiry information is used to answer and plan the traveller’s request.
- Processing and storage region
Supabase Seoul · Resend Tokyo · Gmail and WhatsApp global infrastructureThese are the configured primary regions; email delivery, WhatsApp conversations, security and support may involve provider infrastructure in other countries.
- Inquiry retention
Up to 12 months after the last substantive contactIf the enquiry becomes a client or contractual relationship, relevant records may be kept longer to provide the service, maintain business records and meet legal obligations.
- Rate-limit retention
24-hour window · scheduled deletion after expiryThe service stores a secret-keyed hash rather than a raw IP address. A one-minute recurring task removes buckets after they pass 24 hours, so deletion normally occurs on the next cleanup run.
- Access, correction and deletion
Verified requests are normally handled within 30 daysHomeground may ask for reasonable identity verification. Deletion does not apply where records must be kept for a contract, legal obligation, dispute or security purpose.
Traveller choices
Contact remains optional
The route finder can be used without giving Homeground an email address or opening WhatsApp. Sending the email form and opening WhatsApp are separate, deliberate actions.
Enquiry processing is separate from marketing consent. Homeground will not use an enquiry address for unrelated marketing without separate permission.
- Do not submit the email form or open the WhatsApp handoff.
- Ask what personal information is held and request access, correction or deletion after reasonable identity verification.
- Continue using the route finder without contacting Homeground.
- Receive a human reply by email, or choose to leave the site and start a WhatsApp conversation.
Privacy contact
Contact Homeground about your information
Use the monitored email below for an access, correction or deletion request. Send it from the same address used for the enquiry when possible. After reasonable identity verification, Homeground normally responds within 30 days.
- Privacy email
yangchunxuan1@gmail.com- Postal contact
Available when legally required