Policy protocol / 01
This page describes the limited information used by the public static demonstration, the choices stored in your browser and what would require a separate agreement.
The system-map controls, incident drill, module roster, sliders, assessment console, FAQ search and form validation run locally. Their selected values are used to update the visible page and are not sent to Tubareqoli by this static demonstration.
The application form demonstrates required fields and validation states. Pressing its button prepares a local confirmation only. Do not enter confidential production details, credentials, customer records or sensitive incident information into a public demonstration.
Choosing a cookie option stores a small preference in local browser storage so the panel can remain dismissed. It does not create a cross-site advertising profile. You can remove the preference at any time through browser storage controls.
A hosting provider may process basic request information such as an IP address, time, requested path, browser information and response status for security and reliability. Retention and location depend on the hosting arrangement used for a deployed copy.
The pages request fonts, Bootstrap, Bootstrap Icons and jQuery from public content delivery networks. Those providers may receive standard request metadata. A deployer that requires tighter control can replace those references with locally hosted library files.
For questions about a deployed Tubareqoli site, contact the address shown in the header or footer and identify the page and information involved. We will clarify what is controlled by the site operator and what belongs to an independent hosting provider.
Operational rule: never paste passwords, keys, production logs containing personal data or live customer identifiers into a public training form.
