Privacy Policy

1. Scope of this policy

This Privacy Policy explains the information handling associated with the Aqvarin Ledger website and project communications. It describes the custom website components provided here and distinguishes those components from hosting services, theme features and any third-party applications that may be enabled separately.

A paid engagement may require additional confidentiality, security or data-processing terms for client systems and records. Those arrangements should be agreed before project access is granted. This website policy does not authorize unrestricted access to client information or replace an engagement-specific agreement.

2. Information entered into the website form

The project form includes fields for name, company, email, phone, service interest, current tools, preferred timing and project details. In its current implementation, the form operates locally in the browser. It checks the required fields and displays a confirmation without submitting their contents to Aqvarin Ledger or creating a server-side record.

The custom form does not email the contents, collect payment or save an inquiry to a database. Its confirmation does not mean that Aqvarin Ledger has received the details. The browser may retain previously typed values through its own autofill or session behavior; those browser functions are controlled by the browser and its settings. If a submission service is connected, this policy and the form operation should be updated to describe the actual handling before that service is used.

3. The visual AI demonstration

The interactive LLM visual accepts a short task description solely to trigger an animation and a predefined status message. It does not send the text to an AI provider, generate an analysis or retain it in custom browser storage.

Do not include personal records, confidential business data or credentials in demonstration fields. Their purpose is to illustrate the conceptual movement of a request through a workflow rather than provide a live AI service.

4. Direct communications and engagement information

If you contact Aqvarin Ledger through an active email or other agreed communication channel, the business may receive your contact information, the message contents and any files you choose to provide. Communications may also include information about the service requested, project requirements, scheduling and contractual arrangements.

During an engagement, further information may be needed to scope, configure, test or support a workflow. The client and Aqvarin Ledger should establish permitted information sources, authorized access and any special handling requirements before supplying those materials. Share only information relevant to the agreed purpose.

5. Technical information from hosting

The website is intended to be hosted on Shopify. Hosting and delivery systems may process technical information such as IP addresses, browser and device characteristics, request times and pages requested to deliver content, maintain security and operate the service. The exact collection depends on the hosting configuration and enabled features.

The supplied custom sections do not install a custom analytics service, advertising pixel, session recorder or marketing tracker. Shopify, the theme or additional applications may have their own behavior. Enabled features should be reviewed before publication, particularly where they collect information beyond what is needed to deliver the site.

6. Fonts, images and external content delivery

The selected fonts are loaded from Fontshare, with system fonts used as a fallback. A request to an external font service may expose technical request information, including an IP address and browser information, to that service. Images uploaded to Shopify Files are delivered through the platform’s content delivery infrastructure.

These requests deliver site assets and do not transmit the contents of the local project form through the supplied code. If external asset loading is changed or additional services are installed, the resulting information flows should be evaluated and reflected in the applicable disclosures.

7. Purposes of information use

Information actually received through a connected communication channel may be used to respond to a request, discuss requirements, prepare a proposal, arrange services, administer an engagement, provide support and maintain relevant business records. Technical information may be used by hosting services to operate, troubleshoot and protect the website.

Information should be used only for a stated and appropriate purpose. Providing project details should not be treated as permission for unrelated marketing or disclosure. Any optional marketing activity should use a separate, suitable permission process where required.

8. Legal grounds and regional requirements

Where an applicable privacy law requires a legal basis, the relevant basis depends on the activity. It may include steps requested before an agreement, performance of an agreement, compliance with a legal obligation, a properly assessed legitimate interest or consent where consent is required.

Where consent is used, it should be specific to the processing and capable of being withdrawn as required by law. A checkbox in a local demonstration form does not authorize collection that the form does not perform. The obligations and rights applying to a particular activity depend on the relevant jurisdiction, the business’s operations and the information involved.

9. Service providers and disclosures

Information received during actual communications or engagements may need to be handled by providers supporting email, hosting, business administration, payment processing or the agreed technical implementation. Access should be limited to the purposes and arrangements applicable to the engagement.

If a project uses a third-party model or integration service, the parties should agree which information may be sent to that provider and review its relevant terms, retention options and processing settings. This website’s visual demonstration does not send task text to a model provider.

Disclosure may also be required to comply with a legal obligation or address a legitimate security or legal matter, subject to applicable law. This policy does not claim that all third-party providers use identical safeguards or data settings.

10. Advertising, sale and targeted processing

The custom sections supplied for this site do not include advertising technologies or functions for selling inquiry information. This description is limited to those sections; it is not an assertion about every separately enabled Shopify feature or application.

Before enabling targeted advertising, marketing pixels or another use that may fall within a jurisdiction’s definitions of sale, sharing or targeted advertising, the business should assess the required notice, consent and opt-out mechanisms and update this policy. A provider’s terminology alone does not determine how a privacy law treats the processing.

11. Cookies and preferences

Hosting, themes and enabled applications may use cookies or comparable technologies to support the site. The supplied custom code does not create cookies or store project details in localStorage or sessionStorage. The Cookie Policy describes these distinctions and the available controls.

Optional analytics or advertising should be managed through the relevant consent settings where required. Browser settings can also restrict or remove cookies, although doing so may affect site functionality. A cookie preference should correspond to the technologies actually configured on the site.

12. Retention

The local form and demonstration do not create a custom server record to retain. Communications and engagement records actually received may be kept for the time reasonably needed to address the request, provide services, maintain required business records or resolve a relevant legal matter.

Retention should take account of the type of information, the purpose, contractual requirements and legal obligations. Client project data may have a separate return or deletion arrangement. This policy does not invent a single retention period for every provider or record type.

13. Security and sensitive information

Information handling should use safeguards appropriate to the engagement, including suitable access boundaries and an agreed method for exchanging credentials or confidential materials. No website, transmission method or storage system can be represented as completely free of risk.

Do not enter payment card details, bank credentials, access tokens, government identification numbers, health records or sensitive customer information into public inquiry or demonstration fields. If a project needs protected information, agree on an appropriate access and transfer process first.

14. International access and transfers

Hosting, communication or technical providers may operate infrastructure in more than one country. Applicable rules may require additional measures when personal information is transferred across borders. The requirements depend on the information, locations and provider arrangements involved.

For an engagement that involves such transfers, the parties should assess the necessary contractual and organizational measures before connecting information sources. This policy does not claim that every potential provider or project is hosted solely in the United States.

15. Privacy requests and choices

Depending on applicable law, individuals may have rights to access, correct, delete or obtain a copy of personal information, restrict or object to certain uses, withdraw consent, opt out of qualifying processing or appeal a decision about a request. These rights may be subject to lawful exceptions and verification requirements.

Send a request using the contact details below and identify the communication or engagement involved. Provide enough context to locate relevant information without sending unnecessary sensitive records. Aqvarin Ledger should respond within the period required by applicable law and explain any applicable limitation. Where local law allows, you may also contact the appropriate privacy authority.

16. Children and other people’s information

The site describes services for business operations and is not designed to collect information from children. Do not submit a child’s personal information through public inquiry channels.

If you provide information about a colleague, customer or another individual during a project, you must have the appropriate authority and provide any notice required for that disclosure. Permission to discuss a workflow does not automatically permit unrestricted use of the records within it.

17. Policy updates

This version is dated September 27, 2026. Changes to hosting, forms, connected services or information handling may require revisions. Material changes should be communicated in a manner appropriate to the activity and applicable law.

Questions about this policy, or about information supplied through an actual communication channel, can be directed to the contact details below.