Website privacy and analytics

The public website and documentation have Necessary, Preferences and Analytics choices. This feature does not add analytics to the customer panel, authentication service or any SDK. Reading public pages does not require accepting optional storage.

Visitor controls

Use Accept all, Reject optional or Manage preferences in the notice. Both optional categories start off. Cookie settings in either footer reopens the controls. Closing the window does not accept anything. The shared choice lasts 180 days without being extended by visits. See Cookie policy and Website privacy.

Preferences remembers theme selection and documentation menu state. Without it, controls still work on the current page. Analytics permits public page views and selected panel, documentation and SDK link clicks. Search terms and copied code are never measurement inputs. Navigation and appearance remain usable if Google or browser storage is blocked.

Build configuration

Only the operator preparing a public-site build needs these settings. They are public configuration, not credentials. They apply independently of the landing’s indexing mode.

Build argument / environment variable	Default	Purpose
SITE_ANALYTICS_ENABLED	false	Explicit opt-in for the deployment.
SITE_ANALYTICS_MEASUREMENT_ID	G-8PQMHR5409	Public GA4 web-stream identifier.
SITE_ANALYTICS_SETTINGS_REVIEWED	false	Operator acknowledgement that the provider settings below were reviewed.

The landing and docs Dockerfiles accept these build arguments. The pilot reads its public settings from the versioned infra/pilot/site-settings.json; the Jenkins Secret file is not a source of analytics build settings. Run build-sites, then deploy-sites on the same Git revision to update only these static sites. The deployment checks pinned image IDs and HTTP output, preserves the running application and retains the previous site images for rollback. A later full application deployment supersedes that partial site override. Do not place Google credentials in an image or bundle.

Enablement is accepted only with https://localisync.com for LANDING_SITE_URL and https://docs.localisync.com for DOCS_SITE_URL. Runtime origin must match too. Local and test builds default off. Missing review acknowledgement or an invalid public origin fails the build rather than silently enabling collection elsewhere.

Before enabling a public build

1. Open the intended GA4 web data stream as an authorized account administrator. Confirm its measurement ID and that it is dedicated to the intended public-site measurements.
2. Disable enhanced automatic measurements such as site search, form interaction, outbound clicks, downloads, video and history-based page views. Page views and approved CTA codes come from the integration; automatic collection must not broaden this list.
3. Keep Google Signals, advertising personalization, user-provided data and additional advertising destinations off. Check any connected tag destinations and cross-domain linker settings; no account ID or URL decoration is used by this integration.
4. Inspect account retention settings separately from browser cookie expiry. Update the website notice with verified account facts if making a more specific retention claim.
5. Set both enablement and review acknowledgement to true, build both sites, and use the normal authorized deployment process. This does not enable search indexing.
6. With a clean browser, confirm no Google connection before choice or after rejection. Accept Analytics, confirm one page view and an approved click, then withdraw permission from each site and verify that collection stops. Record actual live results separately.

The review variable is an operator assertion, not an API verification of your Google account. Google settings can change independently; review them when upgrading or changing the stream.

Failure recovery and maintenance

• Choice cannot be saved: inspect browser cookie restrictions; optional analytics stays off when permission cannot be validated. If a previous grant cannot be replaced, the current page stops analytics without reloading that old grant. Other pages may retain the old choice: allow site cookies and save again. No customer login is required to change settings.
• No measurements: check explicit build settings, exact origin, browser permission and content blockers. Do not remove the consent gate to diagnose this.
• Permission withdrawn: loaded tag code requires a page reload. A suspended page reacts when it resumes; the other site’s optional records are cleared when it processes the change.
• Starlight upgrade: verify that theme and sidebar reads/writes remain consent-gated. The narrow sidebar module replacement must still match; global storage APIs are never patched.
• Disable analytics: rebuild with SITE_ANALYTICS_ENABLED=false. The policy and preference controls remain available. This does not delete previously collected Google data.

Run pnpm test:privacy, documentation/landing checks and relevant browser tests. Automated tests intercept production and Google traffic; they do not demonstrate live GA ingestion. The policies describe actual site behavior and are not a legal compliance certification.