Cookie Policy

What this site stores in the browser

Pages are ordinary HTML. The stylesheet, script, fonts, and images load from this same site. The inquiry form keeps its security token in hidden fields inside the page, not in a cookie. Submitting the form does not create a login session.

The script does not write to local storage or session storage. It does not set a cookie from JavaScript. PHP session cookies are not started.

What is not on the site

There is no Google Analytics tag, no Google Tag Manager container, no Google Ads tag, no advertising pixel, no social plugin, no embedded map, and no chat widget. Those tools often set cookies. They are absent, so this policy does not describe them as if they were installed. The contact script can report a stored inquiry to a tag only after the server has saved the inquiry, and only if an operator later adds real measurement IDs, turns tracking on, updates this policy, and adds a consent choice before the tag runs. No measurement ID is configured, so the page does not load those services. If an operator later adds a tool that sets a nonessential cookie, this page has to be rewritten and a real consent choice has to be added before that tool runs. A banner with buttons that do nothing would be worse than silence, so none is shown today.

Hosting and proxies

The application itself is cookie-free. A host, a security proxy, or a service such as Cloudflare can still set cookies if the operator turns that service on. This build does not enable Cloudflare. Server logs at the host may record IP addresses and request paths. Those logs are not cookies, but they are a reason to read the privacy policy alongside this page. If the live host introduces a cookie, the operator should name it here: the cookie name, who sets it, and how long it lasts.

How browser controls work

You can block or delete cookies in the browser you use. The control is usually under privacy or site settings, and the vendor of the browser documents the current clicks. Blocking cookies should not stop this site from being read or from accepting the inquiry form, because the form does not depend on a cookie. Blocking JavaScript will hide the mobile menu's collapse behavior and the larger photo view. The pages, including the form, still work with a normal submit. The terms explain what that submit does and does not do.

If you want a training question handled under the privacy policy, use the contact form. Cookie questions can go there as well. There is no separate cookie-preferences account.