Cookie Policy

1. Current status

The website code currently sets no analytics, advertising, profiling, or preference cookies and uses no equivalent non-essential tracking technologies. The optional consent interface is therefore disabled by default. A consent banner should not be shown merely to announce that no consent is required.

The site infrastructure may still process request and security logs without writing information to your device. Complete and verify the hosting details in the Privacy Policy before launch.

2. Technologies covered

“Cookies” in this policy includes cookies and comparable technologies that store or access information on a device, such as local storage, pixels, tags, SDKs, and fingerprinting techniques. Technologies strictly necessary to provide a service requested by the user may be used without consent; optional analytics, marketing, or profiling technologies require prior consent where applicable.

3. Current technology register

• Website: no cookies or local-storage entries are set by the current production configuration.
• Consent record: sks-cookie-consent; first-party local storage; stores necessary/analytics/marketing choices, policy version, and timestamp; used only if the consent interface is enabled; retained until cleared or superseded by a new consent version. [TO COMPLETE before enabling: set and document a maximum retention period.]
• External Airtable form: no Airtable content is embedded and no Airtable request is made until you activate the external link. Once opened, Airtable’s own technologies and notices apply. [TO COMPLETE: audit the published form, list its cookies/trackers and durations, and link the applicable Airtable notice.]

Infrastructure or security settings can change independently of this source code. A live-site scan must be performed before launch and after material vendor or configuration changes.

4. Consent controls for future use

The repository includes an optional, accessible consent interface for future non-essential tools. If enabled, optional scripts must be blocked before consent, “reject optional” must be as easy as “accept all,” categories must be specific, consent must be recorded, and the footer must allow choices to be changed or withdrawn at any time.

To keep optional scripts blocked, add them as type="text/plain" with data-consent-category="analytics" or data-consent-category="marketing". Do not enable the interface or any tool until this register names the provider, purpose, category, first/third party, data collected, duration, recipients, and any international transfer.

5. Browser controls and changes

You can remove stored information through browser settings. Blocking strictly necessary technologies may affect a requested feature. We will update this policy and the consent version when technologies or purposes change materially.

Questions may be sent through the contact page.