PRIVATE BY DEFAULT.

Concierge requests

When you send a private request, we keep the contact detail and preferred reply channel you provide, city or destination, dates, group size, request type, brief, source surface and received time. We use them to answer, route and manage that request. The rate limiter uses a network address briefly in memory, but the enquiry record does not store it.

Service measurement

We count anonymous homepage, Features and Access events using fixed page and action labels: views, CTA clicks, form starts, submissions, outcomes and confirmed emails. The event log contains no email, city, referral code, URL, query string, referrer, free text or persistent visitor or device identifier. A network address may be held briefly in memory for rate limiting, but it is never written to the event log. Event rows older than 180 days are removed as new measurement events are processed.

Who sees a request

Public and browser roles cannot read the concierge desk. Authorized TIL6 desk operators can see requests to reply, price and support them. The form does not book, hold or charge anything.

Waitlist details

For early access we keep your email, optional city, confirmation time, referral relationship, queue/admission state and an operator audit. Tokens are stored as one-way hashes. We do not upload address books, create a public member directory or store a permanent IP address or persistent device fingerprint.

Retention and control

Unconfirmed waitlist entries are eligible for expiry and referral credits are reversible. Concierge requests do not currently have an automatic expiry. Email concierge@til6.com to request access, correction, export or deletion.