A consultation website
Public explanatory pages and proposed legal texts can be read without an account. The consultation is not the future central fire-safety registry. No advertising tracker is added.
Accounts and contributions
The database stores your email, public display name, password hash, sponsorship history, comments, voting identifiers, moderation decisions and security audit events. Your email is not displayed publicly. The president and authorized administrators have role-limited access.
Public comments and archives
Published contributions, their public display names and their approved revisions may be consulted and used in an OPSI consultation brief. A comment refers to a precise version of a proposed section. Non-public drafts and sponsorship email addresses are not part of public archives. The participation FAQ explains moderation, retention and requests for correction or withdrawal.
Aggregate audience counts without consent
The public consultation server counts requests by public page, UTC day and hour, successful OPSI document downloads, and selected feature activations, even if you decline optional cookies. The MySQL counters contain no IP address, browser identifier, fingerprint, browsing history, full URL or personally identifiable event record. Counts are requests or actions, not unique visitors or completed reading. Aggregate counts are kept for trend analysis without a defined automatic expiry.
Optional audience statistics
Only if you actively agree, OPSI also uses a signed pseudonymous browser cookie for session and page history, estimated active time, coarse browser/device/OS information, campaign source, referral domain, time-zone offset, approximate viewport dimensions, scrolling and game/feature-use events (never answers or typed text). No IP address or complete user-agent string is kept in these optional statistical records. The data are accessible only to the president and kept for 395 days by default (the hosting retention value may differ). Withdrawal stops tracking immediately and requests deletion of the associated browser history. A browser does not prove a unique person.
Technical and security logs
The host, web server and security services may separately process IP addresses to protect the infrastructure, prevent abuse and investigate incidents when demonstrably necessary. Such technical records are not joined to audience statistics or used to reconstruct the journeys of people who refuse tracking. Their actual fields, authorized access, retention and deletion schedule, as well as Apache/proxy logs and backups, must be verified and documented with the hosting provider before launch; PHP cannot control their expiry.
Cookies and local progress
Sign-in uses a secure session cookie. A signed browser identifier limits repeated votes, without proving a unique person. With your separate optional agreement, the site can save learning progress and the history of questions you submit on your device (up to one year). Without agreement, learning and question history remain only in the current page memory; the games still work. Theme changes and game scores use local preferences. Technical rate-limit records are periodically purged. You can change or withdraw optional choices from the footer.
Email
Verification, sponsorship and account-recovery messages use the server-configured transport. When Microsoft Graph is enabled, necessary delivery information is sent to that service. Delivery is not guaranteed merely because the service accepted a message.
Retention and your requests
Legislative archives and contribution history are retained for consultation traceability; withdrawal normally hides a comment without erasing its history. Exceptional redaction is separately controlled and logged. Contact info@opsi.info (privacy officer contact for this project, subject to confirmation of the designated person) for access, correction, withdrawal or retention questions. Pseudonymized records remain personal information; counters created without identifiers must not be misrepresented as anonymization of existing personal data. The operator must validate the legal grounds and retention schedules. This implementation is not a legal compliance certificate.
FAQ — Participation and privacy