This policy is a comprehensive working draft for ITMATIX LexSystems. It must be reviewed against the final contracting entity, operating practices, jurisdictions and applicable law before public launch. Effective date: 22 October 2026, subject to approval.
For “purpose of this policy”, the website owner should inventory the actual technologies used, explain their purpose and duration, and obtain consent where required before non-essential technologies activate. Configuration must be tested on the live website and updated when vendors, scripts or functions change.
For “what cookies are”, the website owner should inventory the actual technologies used, explain their purpose and duration, and obtain consent where required before non-essential technologies activate. Configuration must be tested on the live website and updated when vendors, scripts or functions change.
For “session cookies”, the website owner should inventory the actual technologies used, explain their purpose and duration, and obtain consent where required before non-essential technologies activate. Configuration must be tested on the live website and updated when vendors, scripts or functions change.
For “persistent cookies”, the website owner should inventory the actual technologies used, explain their purpose and duration, and obtain consent where required before non-essential technologies activate. Configuration must be tested on the live website and updated when vendors, scripts or functions change.
For “first-party cookies”, the website owner should inventory the actual technologies used, explain their purpose and duration, and obtain consent where required before non-essential technologies activate. Configuration must be tested on the live website and updated when vendors, scripts or functions change.
For “third-party cookies”, the website owner should inventory the actual technologies used, explain their purpose and duration, and obtain consent where required before non-essential technologies activate. Configuration must be tested on the live website and updated when vendors, scripts or functions change.
For “strictly necessary cookies”, the website owner should inventory the actual technologies used, explain their purpose and duration, and obtain consent where required before non-essential technologies activate. Configuration must be tested on the live website and updated when vendors, scripts or functions change.
For “preference cookies”, the website owner should inventory the actual technologies used, explain their purpose and duration, and obtain consent where required before non-essential technologies activate. Configuration must be tested on the live website and updated when vendors, scripts or functions change.
For “analytics cookies”, the website owner should inventory the actual technologies used, explain their purpose and duration, and obtain consent where required before non-essential technologies activate. Configuration must be tested on the live website and updated when vendors, scripts or functions change.
For “advertising cookies”, the website owner should inventory the actual technologies used, explain their purpose and duration, and obtain consent where required before non-essential technologies activate. Configuration must be tested on the live website and updated when vendors, scripts or functions change.
For “embedded content cookies”, the website owner should inventory the actual technologies used, explain their purpose and duration, and obtain consent where required before non-essential technologies activate. Configuration must be tested on the live website and updated when vendors, scripts or functions change.
For “cookie categories explained”, the website owner should inventory the actual technologies used, explain their purpose and duration, and obtain consent where required before non-essential technologies activate. Configuration must be tested on the live website and updated when vendors, scripts or functions change.
For “why we use cookies”, the website owner should inventory the actual technologies used, explain their purpose and duration, and obtain consent where required before non-essential technologies activate. Configuration must be tested on the live website and updated when vendors, scripts or functions change.
For “consent where required”, the website owner should inventory the actual technologies used, explain their purpose and duration, and obtain consent where required before non-essential technologies activate. Configuration must be tested on the live website and updated when vendors, scripts or functions change.
For “cookie banner preferences”, the website owner should inventory the actual technologies used, explain their purpose and duration, and obtain consent where required before non-essential technologies activate. Configuration must be tested on the live website and updated when vendors, scripts or functions change.
For “withdrawing consent”, the website owner should inventory the actual technologies used, explain their purpose and duration, and obtain consent where required before non-essential technologies activate. Configuration must be tested on the live website and updated when vendors, scripts or functions change.
For “browser-level controls”, the website owner should inventory the actual technologies used, explain their purpose and duration, and obtain consent where required before non-essential technologies activate. Configuration must be tested on the live website and updated when vendors, scripts or functions change.
For “blocking all cookies”, the website owner should inventory the actual technologies used, explain their purpose and duration, and obtain consent where required before non-essential technologies activate. Configuration must be tested on the live website and updated when vendors, scripts or functions change.
For “effect of disabling cookies”, the website owner should inventory the actual technologies used, explain their purpose and duration, and obtain consent where required before non-essential technologies activate. Configuration must be tested on the live website and updated when vendors, scripts or functions change.
For “cookie inventory”, the website owner should inventory the actual technologies used, explain their purpose and duration, and obtain consent where required before non-essential technologies activate. Configuration must be tested on the live website and updated when vendors, scripts or functions change.
For “cookie duration”, the website owner should inventory the actual technologies used, explain their purpose and duration, and obtain consent where required before non-essential technologies activate. Configuration must be tested on the live website and updated when vendors, scripts or functions change.
For “analytics configuration”, the website owner should inventory the actual technologies used, explain their purpose and duration, and obtain consent where required before non-essential technologies activate. Configuration must be tested on the live website and updated when vendors, scripts or functions change.
For “ip and device identifiers”, the website owner should inventory the actual technologies used, explain their purpose and duration, and obtain consent where required before non-essential technologies activate. Configuration must be tested on the live website and updated when vendors, scripts or functions change.
For “cross-device limitations”, the website owner should inventory the actual technologies used, explain their purpose and duration, and obtain consent where required before non-essential technologies activate. Configuration must be tested on the live website and updated when vendors, scripts or functions change.
For “third-party privacy practices”, the website owner should inventory the actual technologies used, explain their purpose and duration, and obtain consent where required before non-essential technologies activate. Configuration must be tested on the live website and updated when vendors, scripts or functions change.
For “social media integrations”, the website owner should inventory the actual technologies used, explain their purpose and duration, and obtain consent where required before non-essential technologies activate. Configuration must be tested on the live website and updated when vendors, scripts or functions change.
For “embedded video and maps”, the website owner should inventory the actual technologies used, explain their purpose and duration, and obtain consent where required before non-essential technologies activate. Configuration must be tested on the live website and updated when vendors, scripts or functions change.
For “security-related cookies”, the website owner should inventory the actual technologies used, explain their purpose and duration, and obtain consent where required before non-essential technologies activate. Configuration must be tested on the live website and updated when vendors, scripts or functions change.
For “load balancing and sessions”, the website owner should inventory the actual technologies used, explain their purpose and duration, and obtain consent where required before non-essential technologies activate. Configuration must be tested on the live website and updated when vendors, scripts or functions change.
For “fraud prevention”, the website owner should inventory the actual technologies used, explain their purpose and duration, and obtain consent where required before non-essential technologies activate. Configuration must be tested on the live website and updated when vendors, scripts or functions change.
For “local storage technologies”, the website owner should inventory the actual technologies used, explain their purpose and duration, and obtain consent where required before non-essential technologies activate. Configuration must be tested on the live website and updated when vendors, scripts or functions change.
For “pixels and tags”, the website owner should inventory the actual technologies used, explain their purpose and duration, and obtain consent where required before non-essential technologies activate. Configuration must be tested on the live website and updated when vendors, scripts or functions change.
For “do-not-track signals”, the website owner should inventory the actual technologies used, explain their purpose and duration, and obtain consent where required before non-essential technologies activate. Configuration must be tested on the live website and updated when vendors, scripts or functions change.
For “global privacy signals”, the website owner should inventory the actual technologies used, explain their purpose and duration, and obtain consent where required before non-essential technologies activate. Configuration must be tested on the live website and updated when vendors, scripts or functions change.
For “international requirements”, the website owner should inventory the actual technologies used, explain their purpose and duration, and obtain consent where required before non-essential technologies activate. Configuration must be tested on the live website and updated when vendors, scripts or functions change.
For “children and cookies”, the website owner should inventory the actual technologies used, explain their purpose and duration, and obtain consent where required before non-essential technologies activate. Configuration must be tested on the live website and updated when vendors, scripts or functions change.
For “changes to cookie use”, the website owner should inventory the actual technologies used, explain their purpose and duration, and obtain consent where required before non-essential technologies activate. Configuration must be tested on the live website and updated when vendors, scripts or functions change.
For “testing before launch”, the website owner should inventory the actual technologies used, explain their purpose and duration, and obtain consent where required before non-essential technologies activate. Configuration must be tested on the live website and updated when vendors, scripts or functions change.
For “consent records”, the website owner should inventory the actual technologies used, explain their purpose and duration, and obtain consent where required before non-essential technologies activate. Configuration must be tested on the live website and updated when vendors, scripts or functions change.
For “vendor changes”, the website owner should inventory the actual technologies used, explain their purpose and duration, and obtain consent where required before non-essential technologies activate. Configuration must be tested on the live website and updated when vendors, scripts or functions change.
For “cookie audits”, the website owner should inventory the actual technologies used, explain their purpose and duration, and obtain consent where required before non-essential technologies activate. Configuration must be tested on the live website and updated when vendors, scripts or functions change.
For “retention and logs”, the website owner should inventory the actual technologies used, explain their purpose and duration, and obtain consent where required before non-essential technologies activate. Configuration must be tested on the live website and updated when vendors, scripts or functions change.
For “third-party links”, the website owner should inventory the actual technologies used, explain their purpose and duration, and obtain consent where required before non-essential technologies activate. Configuration must be tested on the live website and updated when vendors, scripts or functions change.
For “how to contact us”, the website owner should inventory the actual technologies used, explain their purpose and duration, and obtain consent where required before non-essential technologies activate. Configuration must be tested on the live website and updated when vendors, scripts or functions change.
For “how to report a concern”, the website owner should inventory the actual technologies used, explain their purpose and duration, and obtain consent where required before non-essential technologies activate. Configuration must be tested on the live website and updated when vendors, scripts or functions change.
For “policy updates”, the website owner should inventory the actual technologies used, explain their purpose and duration, and obtain consent where required before non-essential technologies activate. Configuration must be tested on the live website and updated when vendors, scripts or functions change.
For “effective date”, the website owner should inventory the actual technologies used, explain their purpose and duration, and obtain consent where required before non-essential technologies activate. Configuration must be tested on the live website and updated when vendors, scripts or functions change.
For “relationship to privacy policy”, the website owner should inventory the actual technologies used, explain their purpose and duration, and obtain consent where required before non-essential technologies activate. Configuration must be tested on the live website and updated when vendors, scripts or functions change.
For “technical limitations”, the website owner should inventory the actual technologies used, explain their purpose and duration, and obtain consent where required before non-essential technologies activate. Configuration must be tested on the live website and updated when vendors, scripts or functions change.
For “no unnecessary cookies commitment”, the website owner should inventory the actual technologies used, explain their purpose and duration, and obtain consent where required before non-essential technologies activate. Configuration must be tested on the live website and updated when vendors, scripts or functions change.
For “jurisdiction and interpretation”, the website owner should inventory the actual technologies used, explain their purpose and duration, and obtain consent where required before non-essential technologies activate. Configuration must be tested on the live website and updated when vendors, scripts or functions change.