!Technical audit required: The final policy must list every cookie or similar technology actually deployed, its provider, purpose, category, and duration. Scan the production site after all Joomla extensions, analytics, embeds, forms, videos, chat, and scheduling tools are configured.
01What cookies and similar technologies are
Cookies are small data files stored or read on a browser or device. Similar technologies include local storage, pixels, tags, scripts, software-development kits, and identifiers that recognize a browser or measure interactions.
They may support security and core operation, remember choices, measure use, or support embedded third-party features. Some information associated with these technologies may be personal information. See the Privacy Policy.
02Categories
1Strictly necessary
Required for security, session management, load balancing, consent choices, form integrity, or another service explicitly requested by the visitor. Disabling these in the browser may prevent the site from working.
Always active where permitted2Preferences
Remember optional choices such as language, display settings, or other personalization.
Consent where required3Analytics
Help understand visits, page use, errors, and performance so the website can be improved.
Consent where required4Marketing
Measure campaigns or support advertising and cross-site tracking. Chapter Partner should not enable these without an identified need, an appropriate legal basis, and required controls.
Consent where required
03Current cookie inventory
The table below is a deployment framework and must be replaced with the results of the production cookie audit.
| Name or technology | Provider | Purpose | Category | Duration |
|---|
| Joomla session cookie | ChapterPartner.com | Maintain a session and support website operation | Strictly necessary | Confirm from production configuration |
| Cookie-consent record | Consent tool to be confirmed | Remember consent and preference choices | Strictly necessary | Confirm from selected tool |
| Analytics cookies, if enabled | Analytics provider to be confirmed | Measure visits and website interactions | Analytics | Confirm from selected provider |
| Scheduling or embedded-media storage, if enabled | Third-party provider to be confirmed | Provide requested embedded functionality | Necessary, preference, analytics, or marketing depending on operation | Confirm from selected provider |
Do not present this framework as a verified inventory until it has been tested against production behavior.
04Consent
Where law requires consent, non-essential technologies should remain disabled until you make a freely given, specific, informed, and unambiguous choice. Rejecting non-essential technologies should be as straightforward as accepting them, and core website access should not be conditioned on optional consent unless law permits it.
The consent interface should identify purposes, allow category-level choice, record the selection, and make withdrawal available at any time. Withdrawing consent does not affect processing that occurred lawfully before withdrawal.
05How to manage choices
Use the website’s “Cookie settings” control to revisit optional choices after the consent platform is installed. You may also delete or block cookies through browser settings. Browser controls may not manage every similar technology, and blocking strictly necessary storage can impair functionality.
⚙Cookie settings control requiredAdd the consent manager’s reopen-settings button or link here when implemented.
06Third-party content
Scheduling calendars, videos, maps, social feeds, payment services, chat tools, and other embeds may set or read their own technologies. Where required, those resources should be blocked until the relevant consent is given or loaded only after a visitor requests the feature.
Third parties act under their own terms and privacy notices unless a written agreement states otherwise.
07Do Not Track and preference signals
Browser “Do Not Track” signals are not interpreted consistently. Where applicable law requires recognition of a legally valid opt-out preference signal, the production consent and analytics configuration should be tested and configured to honor it.
08Changes to this policy
This policy may change when technologies, vendors, purposes, or law change. Update the inventory and “Last updated” date whenever a production change affects cookies or similar technologies.