A small, conditional technology footprint

The site does not intentionally set a first-party cookie for the contact form. The current frontend uses self-hosted font files and hand-built SVGs; it does not embed video, chat, pixels, payment scripts or reCAPTCHA.

The optional analytics path is disabled when no Google Analytics measurement ID is configured. When it is configured, this implementation waits for an affirmative analytics choice before loading the analytics script.

When optional analytics is configured, the site stores the visitor’s analytics choice in browser storage so the choice can persist across pages. This preference is used only to remember the consent state and can be changed from Cookie settings in the footer.

A browser’s own settings can also clear or block storage. Blocking optional storage should not prevent reading the informational pages or submitting the form, although analytics will remain unavailable.

• Reject optional analytics: no optional analytics script is loaded.
• Accept optional analytics: the configured analytics provider may receive the limited, non-free-text events described in the Privacy notice.
• Manage settings: review the available optional category and save a new choice.

A provider is not treated as active merely because the code supports it. The production technology and subprocessor registers record whether Firebase, an email provider or analytics is actually configured. Provider terms, locations, retention and transfer safeguards must be verified before publication of a final provider-specific table.

This is an implementation baseline. Owner and lawyer review is required if analytics or any other non-essential script is enabled, or if the deployed infrastructure differs from the repository inventory.