Cookie Policy

01. Cookies and similar storage

Cookies are small values a website or its host can store in a browser and receive with later requests. Local storage is a related browser feature that keeps values for use by page code; those values are not automatically sent with every network request. Both can support useful functions, such as remembering a privacy choice, but they should be explained according to their actual purpose.

This policy distinguishes storage used by the DNEWIQ pages from storage used by the hosting platform or a separately configured integration. Not every host cookie is set by the pages themselves. The Privacy Policy explains how technical information and direct correspondence are handled more broadly.

02. Storage added by this design

The design adds a local-storage record named dnewiq-consent-v1 to remember privacy choices. It contains a version number, whether analytics and optional preference categories were allowed, the time the choice was recorded, an expiry time and an advertising value set to false. Its lifetime is up to 180 days from the recorded selection. It is replaced when you save a new choice.

This record is used to avoid asking you the same question on every page and to restore your category settings. It is treated as necessary to manage consent, even if optional preferences are rejected. It does not contain your name, email address, project message, payment details or a unique advertising identifier. The design does not store the project-brief fields in this record or elsewhere in local storage.

03. Essential platform functions

The website is intended to run on Shopify. The host may use essential cookies or similar technologies for security, session operation, consent records, delivery of website resources and other functions needed to operate the platform. Their exact names and retention can depend on the host's current implementation and the features that the store actually enables.

Rejecting optional categories through the DNEWIQ panel does not remove storage that the platform needs for essential operation. This website does not include a shopping cart, customer-account form or payment checkout in its own sections, so this policy does not describe a purchase flow that these pages do not provide. If additional platform features are enabled later, their storage must be assessed and described as part of the actual site configuration.

04. Optional analytics

No independent analytics script, heatmap, session recorder or measurement pixel is included in these pages. The analytics choice exists so consent-aware features configured at platform level can receive your selection. Analytics is off by default in this design and remains off when you choose Reject optional. Choosing Accept optional or enabling the analytics category permits that category; it does not install an analytics service by itself.

If optional analytics is added later, the operator should identify the provider, purposes, information collected and relevant storage before using it. The integration must honor the applicable consent settings, including the initial state before a visitor makes a choice. A provider should not be described as present simply because a generic category control is available.

05. Preferences and advertising

The optional-preferences category is reserved for consent-aware features that remember an optional display or experience setting. No such additional preference tool is installed by these pages. Necessary storage for the privacy selection itself is separate from this optional category. Rejecting optional preferences does not prevent the privacy choice from being remembered.

Advertising consent is set to false by the design. The pages do not install advertising pixels, retargeting scripts or cross-site advertising identifiers. DNEWIQ does not use the local project-brief feature to build an advertising audience. If a future site configuration introduces advertising-related processing, the actual tools and choices must be reflected in the policies and platform settings before the changed feature is used.

06. Making and changing a choice

On a browser without a valid saved selection, a banner offers Accept optional, Reject optional and Manage preferences. Accept optional enables the analytics and optional-preferences categories. Reject optional keeps both categories off. Manage preferences opens individual controls so you can choose one category without enabling the other. Essential storage remains active.

You can reopen the same controls with Privacy choices in the footer of the home page or a legal page. Saving a new selection replaces the stored category values and shares them with the available platform privacy controls. A new selection governs future optional processing; it cannot undo an earlier event that a separately configured tool has already processed. These pages do not carry out such optional measurement themselves.

07. Shopify privacy integration

Where the host exposes Shopify's Customer Privacy API, the design passes the analytics and preference selections to that API and keeps marketing consent false. The host's customer-privacy configuration and consent-aware integrations determine how platform-level features use those signals. The banner alone cannot control a third-party script that has been placed outside the consent system and ignores its settings.

The operator must therefore configure the host's consent regions and review any installed apps or theme scripts. If a separate platform banner is present, the site should use one coherent set of controls rather than show contradictory choices. A platform-level change that introduces new storage or changes the treatment of optional features requires a corresponding policy review.

08. Browser controls and privacy signals

You may also use browser settings to block cookies, clear site data or restrict local storage. Clearing the DNEWIQ preference record causes the banner to appear again. Private browsing or a storage restriction may prevent the choice from being saved between visits. The page attempts to continue functioning when local storage is unavailable, but the browser may then ask for a selection again on a later page.

Privacy signals such as Global Privacy Control are handled by the host's relevant settings where supported and applicable. These pages do not implement targeted advertising or a sale of personal information, and their marketing consent remains off. A browser signal should not be assumed to manage every category in every third-party tool; the platform configuration and the actual integration still matter.

09. Project information and external services

Completing the project-brief form validates the fields locally and displays a confirmation. It does not submit the fields to a server or store them as cookies. No form data is added to the privacy-choice record. These sections do not embed a map or social-media feed. Publication images load from website files, and typefaces load through Google Fonts. The external font requests provide the font host with technical request information, such as an IP address and browser headers. These resource requests are separate from the optional analytics and preference categories. The code does not add form field values to font requests.

Direct email, a call or an agreed file-delivery method operates separately from the local form. The service you use to send a message or a file may apply its own cookies or browser storage on its own website. That activity is not a cookie created by the DNEWIQ brief feature. The Privacy Policy addresses the company information received when you communicate directly.

10. Policy updates and questions

The last-updated date identifies the published version of this policy. The policy must remain aligned with the host, apps and scripts actually used on the live website. A future analytics, advertising or embedded-content addition should not be covered by a vague claim that such a tool was always present. Material changes should be explained and appropriate choices provided before optional processing begins.

For a question about storage, describe the page, browser and observed behavior where possible. Do not include passwords, complete cookie values or other information that could expose an active account session. Send the inquiry to editorial@dnewiq.com using the company information below. You may manage the site's own categories directly through Privacy choices in the footer.

Cookie Policy

Contact DNEWIQ CORP

Make it your choice.

Essential storage

Analytics

Optional preferences

Advertising

Your cart is empty

Your cart is empty