Cookie Policy

Effective date: September 19, 2026 · Last updated: September 19, 2026

This page documents what was confirmed during the local audit. A cookie or similar technology may be used only for a stated purpose and should be added to this page when it is introduced.

1. What cookies are

Cookies and similar technologies are small pieces of information stored or read by a browser or device. They can support technical operation, remember a choice, or measure activity. A cookie may be first-party, set by KTVendu, or third-party, set by a provider whose content or service appears on a page.

2. Categories used by the consent interface

The local site loads the Cookie Law Info consent interface. It presents these categories:

• Necessary: technical operation, language handling, security, and the consent interface itself.
• Functional: optional features or preferences, only when they are actually enabled.
• Analytics: measurement tools, only when a real analytics provider is enabled.
• Performance: performance or diagnostic tools, only when a real provider is enabled.
• Advertisement: advertising, retargeting, or profiling tools, only when a real provider is enabled.

At the time of the audit, the configuration declared no cookie entries for the categories and no provider-blocking list. The categories therefore describe the available framework, not proof that each category is active.

3. Technology confirmed or configured

• WPML — wp-wpml_current_language: the language script declares a first-party cookie containing the current language, such as en or fr, with path / and a one-day expiry in the current configuration. It supports language routing or preference and is treated as necessary for the bilingual experience.
• Cookie Law Info: the consent banner and preference centre are loaded. The exact preference-cookie name and duration were not independently confirmed from the rendered local page, so none is invented here.
• WordPress and theme libraries: JavaScript libraries such as jQuery and the theme’s cookie helper are loaded, but a library is not itself proof that a particular cookie is created.

4. Technologies not confirmed

No Google Analytics, Google Tag Manager, Meta Pixel, Google Ads tag, reCAPTCHA, Google Maps, Vimeo, or live third-party iframe was confirmed on the audited home page. The audited seller-marketing page refers to YouTube as a possible distribution channel, but no live YouTube embed was loaded there.

Because the production environment, future page variants, and consent history may differ from this local session, these technologies must be rechecked before production and whenever a plugin, embed, advertising campaign, or analytics tool is added.

5. Consent and controls

The current banner exposes Customise, Reject All, and Accept All controls, plus a floating Consent Preferences control that can reopen the interface. The configuration sets optional categories to be off by default and indicates that analytics should not load by default.

Use the floating Consent Preferences control on the site to review or change choices. You can also manage cookies through your browser. Blocking necessary technologies may affect language handling, the consent interface, or other site functions. A future non-essential provider must not be described as controllable until the blocking and withdrawal behaviour is tested.

6. Third-party content and links

When an external embed, map, video, social widget, advertising tag, or similar content is introduced, it may set or read third-party cookies and may transmit technical information to its provider. That content should remain blocked until the required choice is made, where the law requires it. External sites also have their own policies after you leave KTVendu.

7. Updates

This policy must be updated when the site begins using a new cookie, provider, embed, advertising or analytics technology, or a new consent configuration. The last-updated date will be revised at the same time.