Privacy at Hello

Privacy &
cookie settings.

Last updated 14 August 2026

What this website measures

With your permission, this site uses Google Analytics through Google Tag Manager when a container is configured, or through a direct GA4 fallback. It measures page visits, article-reading milestones, booking-button clicks and useful interactions such as opening a FAQ or using the treatment assistant.

Free text typed into the treatment assistant stays in your browser and is not included in Analytics events. Only the result category, match status and number of characters may be measured. These fields are not direct identifiers, but Google Analytics can still process pseudonymous identifiers and technical data such as device, browser, approximate location, page, time and referring site.

When you separately accept Advertising, Google Ads conversion measurement records that a booking click or a WhatsApp contact followed an advertisement, so the studio can tell which campaigns lead to appointments. If a Meta Pixel is configured, the same choice lets it measure page views, clicks toward Fresha and WhatsApp contacts to evaluate campaigns on Meta services. Neither is loaded when Advertising is declined, and Google advertising identifiers are redacted from any request made before that choice.

Purpose and legal basis

Analytics is used to understand site performance and improve the path to a booking. Advertising measurement is used to attribute bookings and contacts to the campaigns that produced them, on Google Ads and, where configured, on Meta services. It may also support advertising personalisation on those services. Both purposes are optional, based on consent, and can be accepted or declined independently.

Your choice and storage

On a first visit, optional Google and Meta tags are blocked. The site stores your separate Analytics and Advertising choices in local storage for 180 days. Changing the purposes offered resets that record, so the choice is asked again. If you withdraw a choice, the site stops the corresponding events, updates the available consent controls and attempts to remove accessible first-party measurement cookies. A script already loaded in the current page cannot be unloaded; reloading applies the declined choice before any optional tag loads.

After consent, GA4 can set the first-party cookies _ga (pseudonymous browser distinction) and _ga_<measurement-id> (session state). This implementation limits their configured lifetime to 180 days; Google may refresh that expiry while Analytics remains active. Accessible Analytics cookies are removed when the saved choice expires or consent is withdrawn.

Campaign parameters present in the address you arrive with — utm_*, and the Google advertising identifiers gclid, gbraid and wbraid — are kept in the page address reported to Analytics; every other query parameter is removed before any measurement call. If a visit includes a valid utm_source, the site keeps that source in session storage only after Analytics consent. It can be included in an Analytics contact event and as a short source label in a WhatsApp message. It is removed when Analytics is declined or withdrawn and expires when the browser session ends.

After Advertising consent, Google can set _gcl_aw and related _gcl_* cookies to keep the advertising click identifier that brought you here and attribute a later booking to it, and Meta can set _fbp and, when relevant, _fbc for the same purpose on its own services. Accessible advertising cookies are removed when Advertising is withdrawn; Google's and Meta's own retention rules may still apply to data already received.

Recipients and retention

When Analytics is accepted, measurement data is sent to Google as a service provider for the studio and may be processed internationally under Google's contractual safeguards. Event-level GA4 data is intended to be retained for 14 months; the studio must keep the Analytics property setting aligned with this published period. Aggregated reports may remain after event-level data is deleted. Read the Google Privacy Policy.

When Advertising is accepted, conversion data is sent to Google Ads and may be processed internationally under Google's contractual safeguards, and — where a Meta Pixel is configured — campaign measurement data is sent to Meta under Meta's terms and safeguards. Read the Google Privacy Policy and the Meta Privacy Policy.

The site's DM Sans and Playfair Display font files are self-hosted on this domain and do not create a separate connection to Google.

Bookings on Fresha

Booking links open Fresha, a separate service with its own privacy and cookie choices. If the studio's GA4 Measurement ID is enabled in Fresha, Fresha may send booking-funnel page views and completed-booking events to the same Analytics property after consent on its website.

Fresha does not support cross-domain tracking, so a click on this site and a completed Fresha booking are reported as separate parts of the journey and cannot always be attributed to the same visitor or marketing source.

Fresha processes booking data under its own privacy notice, and the studio receives the information needed to provide your appointment. Read the Fresha Privacy Policy before booking.

Search visibility

Google Search Console is used to monitor how public pages appear in Google Search. It provides aggregated search-performance information and does not add a visitor-tracking tag to this website.

Who is responsible and your rights

The data controller for this website is Hello Lash Lifting Bali, Jalan Pantai Seseh, Cemagi, Mengwi, Bali 80351, Indonesia. Subject to applicable law, you may ask to access, correct or delete personal data, restrict or object to processing, withdraw consent, or raise a concern with the competent privacy authority. Withdrawing consent does not affect processing already performed while it was valid.

For a privacy question or request, email hello.lashlifting.bali@gmail.com.