YOUR DETAILS. YOUR CHOICE.

Your enquiry

We use the contact and destination details you submit to answer your request. You can add an email address or a note if you want to. A wholesale enquiry also includes the business and quantity details you provide.

Requests are saved in our private enquiry database. Depending on the deployment, this is a database on our application server or a connected Supabase database. A confirmation and reference are shown only after a request has been saved. The website does not collect payment details.

Enquiry records are scheduled for deletion after 90 days. If an operational forwarding service or Google Sheet is connected, a copy may be shared with our team for fulfilment. Copies in connected services are managed separately from the enquiry database. WhatsApp and Telegram conversations are handled by those services under their own privacy terms.

Notifications and team access

When connected, our Telegram bot sends our authorised administrators a new-request alert with the reference, tea selection and total. Administrators can retrieve the contact details they need to answer your request through the private bot. Access is limited to two administrator accounts.

You can choose to connect Telegram notifications using the private link shown after your request. This associates your Telegram chat with the request so the bot can send status updates. Sending /stop to the bot removes that subscription. The link expires after seven days; the chat association is also removed when the enquiry is deleted. Queued notification records are retained for no more than 30 days. Administrator account records remain until revoked.

Your exploration notes

If you submit an exploration note, we store your chosen display name, experience and any practice fields you fill in. The note stays private until an administrator approves it; approved notes appear on the tea page. We retain submissions and their moderation status until removal is requested or we remove them. A keyed hash of the connecting address limits repeated submissions; we do not store the raw address with your note. Contact us to request removal, identifying the tea, display name and date of your note.

When our moderation bot is connected, your display name, note and practice fields are sent to authorised administrators through Telegram. Telegram handles these messages under its own privacy terms.

Necessary browser storage

Your cart is stored on your device. A recent request confirmation is kept in this browser tab for up to 24 hours so you can reopen it after refreshing. The confirmation contains the selected teas and reference, rather than your contact details. While a request is awaiting confirmation, this tab also keeps a random retry key and a one-way fingerprint of the request for up to 24 hours, so reopening the form can safely retry the same submission. The fingerprint does not contain readable contact fields.

Optional analytics

With your explicit choice, our own analytics measures page views, visible tea cards, product selections, cart actions, checkout progress, accepted enquiries and contact-link clicks. We also measure scroll depth, brief periods of active reading and website performance to improve the shop. Declining analytics does not affect your cart or request.

Analytics does not receive your name, phone number, email, street address, notes, form values or raw browser user agent. Catalogue items, quantities, prices and currency describe product interest. An accepted request reference lets us count the same lead once; it is excluded from analytics reports and journey exports. We do not record your screen or fingerprint devices.

After you allow analytics, a random browser identifier connects page visits and selected actions, including return visits in the same browser. It expires 90 days after creation and is not renewed by activity. A separate visit identifier expires after 30 minutes without activity. Clearing cookies or changing browsers creates a different identity; we do not match devices or identify people. Short-lived cookies also keep the first recognised campaign, public landing path and referring service consistent across tabs, and remember whether you dismissed the optional questions. Page addresses exclude query strings and fragments. Activity before this consent is not reconstructed, and earlier visits are not linked to the browser identifier.

We collect broad device, browser and operating-system families and your browser language. If a local country database is configured, the server may use the connecting IP address momentarily to estimate a country. No raw IP address is saved in analytics or sent to a geolocation service. We do not collect precise location, city or browser geolocation; an estimated country can be wrong.

Optional audience questions

After a request, visitors who allowed analytics can choose to share an age band, country or region, tea experience and reason for visiting. Every question can be skipped. The answers are linked to the analytics visit, with no contact details added, and used in grouped audience reports. Groups with fewer than five responses are hidden. We do not infer age, gender, income or other personal traits from browsing.

Analytics events, browser and visit identifiers are scheduled for deletion after 90 days. Authorised administrators can view grouped journey reports and download pseudonymous event sequences containing a random browser ID, visit ID, event label and timestamp for private analysis. These exports contain no contact details, request references, demographics or form answers. Operational enquiry counts are part of running the service and do not depend on optional tracking.

We remember your analytics choice for six months. Choosing decline stops future collection and clears the browser identifier, visit, campaign and optional-question cookies plus saved tab attribution. Previously recorded events follow the 90-day retention period above; downloaded reports must be deleted by the operator on the same schedule. Browser Do Not Track and Global Privacy Control preferences override analytics consent. A previous consent to visit-only analytics does not enable this browser-level measurement; we ask again.

Questions about your details

To ask about access, correction or deletion of your enquiry, include your request reference when replying through the contact channel used for your request.