Cookie Policy

1. What this Policy covers

This Cookie Policy explains how Woodlentra Studio may use cookies and similar technologies when a visitor accesses this website. It should be read with the Privacy Policy. A cookie is a small text record stored by a browser. Similar technologies include local storage, session storage, pixels, tags and device identifiers that recognize a browser, retain a preference, protect a session or measure an interaction.

The live website may be operated through Shopify and may use theme features, security controls and installed applications. The exact technologies present can change when hosting, analytics, consent, anti-abuse or embedded-content settings change. Woodlentra Studio will configure optional technologies in accordance with applicable consent requirements and will update this Policy when a material change is made.

2. Categories of technology

Strictly necessary technologies support page delivery, load balancing, security, fraud prevention, consent recording, accessibility preferences and other functionality required for the website to operate. These technologies generally cannot be disabled through a website preference tool because the requested service would not function reliably without them.

Preference technologies remember choices such as language, interface state, region or consent preference. They are used only when the relevant feature is enabled and may be treated as optional in some jurisdictions.

Analytics technologies help understand aggregate page usage, navigation, device categories, errors and performance. They should not be activated before required consent is obtained. Analytics information is used to improve content structure and technical operation, not to make decisions about an individual.

Marketing technologies can recognize a browser across services or support campaign measurement. Woodlentra Studio does not require marketing cookies for a visitor to submit a project inquiry. If marketing technology is introduced, it will be identified in the preference interface and used only when a valid basis exists.

3. First-party and third-party cookies

A first-party cookie is set for the domain being visited. A third-party cookie is set through another provider whose technology appears on the page. Hosting, analytics, media, scheduling, security or form services may set or access their own technologies. Third-party providers determine part of the processing and may maintain their own retention schedules and privacy terms.

The presence of a third-party name in a technical tool does not mean that Woodlentra Studio endorses all of that provider’s activities. Providers should be limited to those reasonably required for site operation or an enabled feature.

4. Typical purposes and duration

Session technologies expire when the browser session ends or shortly afterward. Persistent technologies remain until their stated expiration, manual deletion or replacement. Necessary records may persist long enough to maintain security, record a consent choice, prevent repeated abuse or preserve an essential preference. Optional analytics and marketing retention should be limited to the period reasonably necessary for the configured purpose.

Cookie duration is not the same as business-record retention. Information derived from a cookie may be aggregated, anonymized, deleted or retained under the Privacy Policy after the cookie itself expires.

5. Current functional inventory

The following functional inventory describes the types of records that may be present. The browser’s storage inspector and the active consent interface provide the most current technical names because names can be assigned or changed by Shopify, hosting infrastructure and installed applications.

• Security and anti-abuse records used to distinguish legitimate traffic and maintain availability.
• Session and routing records used to deliver pages consistently through hosting infrastructure.
• Consent records used to remember whether optional categories were accepted or rejected.
• Interface preference records used to preserve a user-selected experience where enabled.
• Analytics identifiers or event records used only when analytics is enabled and legally permitted.
• Embedded-service records used only when a visitor activates a feature delivered by another provider.

6. Consent and preference control

Where required, optional technologies are blocked until a visitor makes a choice. Consent must be freely given, specific, informed and capable of withdrawal. Rejecting optional categories should not prevent access to ordinary informational content or the core inquiry function.

A visitor may reopen the website’s privacy or cookie preference control, when present, to change a decision. A change applies prospectively and may not remove records already created; browser controls can be used to delete existing storage. If the website does not display a preference control, optional nonessential technologies should not be active unless another lawful configuration applies.

7. Browser controls

Most browsers permit a user to view, block, limit and delete cookies or clear site data. Controls differ by browser and device. Blocking all storage can affect security checks, consent memory, form state and other functionality. A visitor who clears consent records may be asked to make a choice again.

Private browsing and device-level privacy settings can reduce persistence but do not necessarily prevent all server-side logs or security records. “Do Not Track” signals are not interpreted consistently across the industry. Where a legally recognized opt-out preference signal applies to a relevant activity, it will be evaluated in accordance with applicable law.

8. Embedded content and external services

An embedded video, map, scheduling interface, font, chat tool or other external feature can permit the provider to receive technical information when the feature loads or is activated. Woodlentra Studio seeks to avoid unnecessary external loading and does not use clickable map, telephone or email actions in the legal pages. A visitor should review the privacy choices applicable to any external service independently selected.

9. Analytics safeguards

If analytics is enabled, configuration may include data minimization, shortened retention, regional processing options, restricted advertising features and consent-dependent loading. Aggregated reporting is preferred where it can meet the operational purpose. Analytics is not used to request passwords, confidential project data or private repository information.

10. Changes to this Policy

This Policy may be updated when technologies, vendors, features or legal requirements change. The effective date identifies the current version. A material change to optional tracking practices will be reflected in the consent experience where required.