FBI-Training
Cookies & tracking
FBI-Training currently uses first-party storage needed for the service, interface preferences and privacy-minimised first-party usage statistics. It contains no advertising tracker and no third-party analytics SDK.
Technical storage
Django may use a session cookie for authenticated or stateful features and a CSRF cookie to protect form submissions. Browser local storage may remember interface preferences such as panel widths. These mechanisms are used to operate the requested service rather than for advertising profiling.
Audience measurement
Server-side sheet and public-course view statistics do not store IP addresses or user-agent strings in the application model and are not linked to the logged-in account. Existing Django sessions are reduced to a one-way hash for duplicate suppression. When no session exists, the record-view endpoint uses a short-lived first-party fbi_view_dedupe cookie containing a random token; only its one-way hash is stored with the view event, and the cookie expires after 30 minutes. View events are retained for at most 760 days by default.
Third-party network requests
The current portal loads the G6 library from jsDelivr and Tiptap modules from esm.sh. These CDN requests are not used by FBI-Training as advertising or audience-measurement trackers, but the CDN operators receive ordinary network request information. External video/media providers may also receive a request when their content is loaded.
Consent and production validation
The current code uses only first-party technical storage plus the short-lived view-deduplication cookie described above; it contains no advertising tracker, cross-site tracker or third-party analytics tag. Before public deployment, the controller must validate every cookie, browser-storage use and audience-measurement mechanism against the applicable deployment policy and legal requirements. Any future tracker that requires consent must remain disabled until valid consent has been obtained.