Trust / Privacy

TRUST & LEGAL

Privacy, stated plainly.

Overview

This notice describes the informational website and pre-launch waitlist available today. It does not describe a live dating service, because HLALY accounts, matching and messaging are not yet open.

Website copy V1.1prelaunch website notice
ON THIS PAGEInformation handled by the pre-launch website
HLALY CONTEXT

CURRENT SCOPE

This notice is about the informational website and launch enquiries available today. It is not the final privacy notice for a live matchmaking service.

DATA LIFECYCLEThe privacy story should remain clear from collection to use, permitted sharing, retention, and deletion or correction requests.

BEFORE MEMBER ACCESSA fuller member-service privacy notice, vendor detail, international-transfer explanation, and production retention rules must be published before account access opens.

Information handled by the pre-launch website

The official /register route can collect your email address, optional first name, confirmation that you are 18 or over, country, and UK city/region where applicable. It also records whether you separately chose optional marketing emails, the version and time of that consent choice, and limited campaign/referral attribution needed to understand how the waitlist grows. The canonical HLALY backend is intended to be the source of truth for verification status and these audit records.

A raw form submission does not count as a verified waitlist member. HLALY sends or requests an email-ownership verification step through the connected waitlist backend. Verification tokens are treated as credentials and are not intentionally sent to Google Analytics or PostHog.

The website does not include advertising pixels in this pre-launch setup. Optional Google Analytics and PostHog measurement can run only after analytics consent is granted through the website consent mechanism. The analytics layer is designed not to send waitlist email addresses or names. Campaign/referral context may also be included with the explicit waitlist request so the backend can preserve acquisition attribution without putting the email address into analytics tools.

Normal hosting and security infrastructure may receive technical request information such as an IP address, browser type, requested page and request time. The website gateway may use short-lived rate limits and, when configured, a privacy-conscious anti-abuse challenge. A keyed one-way request fingerprint may be sent to the canonical HLALY backend for abuse prevention without placing the raw IP address in website analytics.

The Stay in touch form remains a separate updates request. Submitting it asks HLALY to send editorial and product updates and can send the email address you enter, page/source context, limited acquisition attribution, a consent copy version and consent timestamp to the configured server-side endpoint. It does not change your verified-waitlist marketing choice.

The public website now has two distinct data paths: ordinary technical delivery data needed to serve the site, and a voluntary Stay in touch submission that sends an email address plus minimal page/source context to the server-side subscription endpoint. Neither path creates a dating profile or matching account.

When you choose to email

Links to hello@hlaly.app open your own mail application. The website does not intercept or save the message. Your email provider and the recipient mailbox process the address, message, attachments and delivery metadata you choose to send.

Do not include identity documents, health information, payment information or intimate profile details in the waitlist, Stay in touch form or ordinary email unless HLALY provides a secure process specifically for that purpose.

A direct email enquiry and a Stay in touch submission serve different purposes. The newsletter route should remain minimal and should not be used to collect profile answers, identity documents, payment information, health information, or intimate relationship details.

Sale and sharing

HLALY does not sell information submitted through this pre-launch website. Waitlist, verification, email and technical delivery data may be handled by approved infrastructure and communications providers only for the relevant service, security and communication purposes.

A final production vendor list, retention schedule, international-transfer explanation and applicable contractual safeguards should be maintained as the production providers are finalised.

The subscription endpoint is designed so the deployment can forward data server-side to an approved provider—such as an AWS-hosted API, CRM, or mailing platform—without exposing provider credentials in browser code. The production privacy notice should identify the processor actually used and the purpose for which it receives the data.

Retention and requests

Waitlist information should be retained only as long as required for the pre-launch/access purpose, security, consent evidence and applicable legal obligations. Technical logs and provider-level retention remain controlled by the active production configuration.

You can ask about access, correction or deletion of information associated with the pre-launch website by writing to hello@hlaly.app. Applicable privacy rights vary by location, and identity may need to be confirmed before a request is completed.

The production team should define how long public-update subscriptions, delivery logs, suppression records, and direct correspondence are kept. Unsubscribing from updates and requesting deletion of other correspondence are related but not necessarily identical processes.

Age and changes

The HLALY waitlist is intended for adults aged 18 or older and requires an 18+ confirmation. The pre-launch waitlist does not ask for a full date of birth.

This notice will continue to evolve before live member accounts begin processing full profile information. Material changes should be dated and explained rather than silently replacing the current description.

The public update form is not a substitute for age verification or member onboarding. It should remain a lightweight communications request until HLALY opens a separate, properly governed account process.

How this privacy notice connects to the rest of HLALY

Data & Privacy Choices describes the controls intended for a future member account. Website Technologies explains browser-side storage. Account Deletion explains the difference between current correspondence and a future member profile. Community Guidelines and Safety explain how information misuse, blocking, reporting, and serious harm are handled from the behaviour side.

OFFICIAL DOCUMENT

Privacy — authoritative document

Formal access point for the HLALY Privacy Notice or Privacy Policy PDF and its authoritative metadata.

Website explanation

The information above explains this subject in plain language and helps people understand how it connects to the rest of HLALY.

Website copy: V1.1 · Prelaunch Website Notice
Authoritative document

Use the document controls to open or download the formal file published for this subject.

Privacy notice / policy
Document type
Privacy notice / policy