Cookie Policy
A code-informed draft explaining the current absence of website tracking and the decisions needed if cookies or analytics are added.
Last reviewed: [OWNER INPUT REQUIRED]
Current website implementation
The current repository does not set application-managed cookies and does not include analytics scripts, marketing pixels, local storage, or session storage. The production hosting provider, CDN, security layer, and any future embedded services may still use technical cookies or similar technologies. Confirm the live deployment before publishing. [OWNER INPUT REQUIRED]
Necessary or technical technologies
Necessary technologies may support page delivery, security, load balancing, preferences needed for a requested feature, or other functions without which a service cannot operate. The exact names, providers, purposes, duration, and classification must be recorded from the production environment. [OWNER INPUT REQUIRED]
Analytics cookies
No analytics provider was found in this repository. If Wirtu later adds analytics, it should identify the provider, data collected, purposes, retention, international processing, and the consent or opt-out method that applies before activating it. [OWNER INPUT REQUIRED]
Preference cookies
No preference-cookie feature was found in the current codebase. If a consent choice, language setting, or display preference is added, document its purpose and duration here. [OWNER INPUT REQUIRED]
Marketing cookies and pixels
No marketing cookie, advertising pixel, or retargeting tag was found in this repository. Do not add these tools without updating this policy and deciding how visitor choices will be collected. [OWNER INPUT REQUIRED]
How visitors can control cookies
Visitors can generally use browser settings to block or delete cookies. Blocking necessary technologies may affect site operation. If Wirtu adds non-essential cookies, it should provide a clear consent or preference mechanism and honor the choices required for the applicable audience. The specific mechanism is [OWNER INPUT REQUIRED].
Updates and contact
Wirtu may update this policy when technologies or providers change. Confirm the last-updated date and change process before publication. Questions can be sent to firomsa@wirtu.tech.
Items to confirm before publishing
- Capture a production cookie scan, including hosting/CDN/security cookies.
- Decide whether analytics, preferences, marketing tools, or embedded content will be added.
- Name each provider, cookie, purpose, duration, data recipient, and control method.
- Choose and implement any consent or preference mechanism required for the target audience.