Cookie Policy
Last updated: September 27, 2026
This policy separates the local interactions supplied for the site from the cookies and other technologies that hosting services, themes or enabled applications may use.
1. What cookies and similar technologies do
Cookies are small pieces of information stored by a browser and returned with relevant requests. They can support website operation, remember preferences or help a service understand use of its pages. Comparable technologies may include browser storage, scripts and pixels, although they do not all operate in the same way.
This Cookie Policy describes the custom components supplied for Aqvarin Ledger and explains how the hosting platform, theme and optional applications may affect the site. The applicable technologies depend on the published configuration rather than the visual appearance of the page.
2. The custom website sections
The provided custom sections do not create cookies, write to localStorage or sessionStorage, install an advertising pixel or use a custom analytics tracker. Animations, menu behavior, service selection and modal validation run in the browser without requiring a tracking cookie.
The project form does not submit its values to a server or save them through custom browser storage. The LLM demonstration does not send its task text to a model. These descriptions apply to the supplied custom code and do not override functions installed separately through Shopify, the theme or other applications.
3. Hosting and essential operation
Shopify and its delivery infrastructure may use cookies or other technical mechanisms to maintain website functionality, security, access settings or related platform services. Which mechanisms are present depends on the store settings and the features in use.
Cookies that are genuinely necessary for a requested service may be handled differently from optional tracking under applicable rules. A cookie is not automatically essential merely because a provider sets it. The published site configuration should be reviewed to identify its actual purpose.
4. Preferences and functional features
A theme or application may use a cookie or browser storage to remember a user preference, such as a selected region or a consent choice. The supplied Aqvarin Ledger components do not set their own persistent preference record.
If an additional feature is enabled, its storage purpose, provider and duration should be identified as appropriate. A browser may also retain form information through its own autofill features; that behavior is separate from the custom website code and is controlled through browser settings.
5. Analytics technologies
Analytics features may collect information about page visits, device characteristics or interaction events. No optional custom analytics service is installed by the supplied sections.
If analytics are enabled through Shopify or another application, assess the information collected and any required consent or other legal basis. Optional analytics should respect the consent and privacy controls applicable to the visitor. Consent settings should govern the actual tags rather than display a preference that the tags ignore.
6. Advertising and marketing technologies
Advertising pixels and comparable tools may support campaign measurement, audience creation or targeted marketing. The supplied sections do not include these technologies or create advertising audiences.
Before adding them, review their operation, update the relevant disclosures and configure the consent or opt-out controls required in the applicable regions. Advertising, sale, sharing and targeted-advertising definitions vary across jurisdictions; provider labels alone do not establish the legal treatment.
7. External fonts and content delivery
The site requests the chosen fonts from Fontshare and serves uploaded imagery through Shopify’s content delivery infrastructure. Asset requests can disclose technical information to the service receiving the request, such as the request time, IP address and browser information.
An external asset request is not necessarily a cookie, but it is still an information flow relevant to privacy. The supplied code does not append form entries or demonstration text to these requests. Changes to asset providers should be assessed if they materially change information handling.
8. Consent controls
Where optional technologies require consent, they should remain inactive until the appropriate consent is recorded. A consent interface should offer meaningful choices, accurately describe the configured purposes and allow changes as required by applicable law.
Shopify provides customer privacy and cookie-banner settings that can be configured for the applicable site regions. When enabling optional pixels or applications, verify that they respond to the relevant consent signals. The supplied custom sections do not create a separate consent banner because they do not install optional tracking themselves.
9. Managing preferences
If a cookie preference control is provided on the published site, use it to review or change the configured choices. You can also use browser settings to block cookies, remove existing cookies or restrict certain site storage.
Removing or blocking information may affect functions that depend on it. Browser controls vary, and deleting a cookie does not necessarily remove records already held by a service provider. For information actually received through communications or engagements, use the privacy-request process described in the Privacy Policy.
10. Duration and provider details
A session cookie normally expires when its relevant session ends, while a persistent cookie can remain until its stated expiry or until it is removed. The precise duration depends on the cookie and provider configuration.
No fixed inventory of cookie names or durations is claimed here because the live Shopify configuration has not been supplied for verification. Before adopting an inventory, review the published site and enabled applications. Any listed provider, purpose or duration should reflect observed configuration rather than an assumed standard list.
11. Browser signals and opt-out rights
Some browsers can send privacy or opt-out preference signals. Where applicable law requires a business or provider to recognize a qualifying signal, the published configuration should handle it accordingly.
A general browser “Do Not Track” preference does not necessarily have the same effect as a legally recognized opt-out signal. This policy does not promise that every separately enabled provider interprets every browser signal in the same way. Review platform settings and installed tags where qualifying opt-out rights apply.
12. Changes to this policy
This version is dated September 27, 2026. Adding analytics, advertising, embedded media or other applications may change the technologies used and require an updated policy or preference interface.
Questions about cookies, optional technologies or the custom site components can be directed to the contact details below. For broader information handling, refer to the Privacy Policy available through the website footer.
Contact Aqvarin Ledger
Email: projects@aqvarinledger.com
Address: 725 N Montana Ave, Helena, MT 59601, USA
Phone: +1 417 879 1565