Cookie Policy

This Cookie Policy describes cookies and similar technologies in connection with the Elmhurst Codecraft website. It should be read together with the Privacy Policy. The website uses Shopify as its publishing platform, so it is important to distinguish the custom page features from technologies that the platform or separately installed applications may use.

A cookie list cannot be inferred from the visible design alone. The categories below explain the relevant purposes and controls. Actual names, lifetimes and providers depend on the live storefront settings and should be kept consistent with the technologies that are active.

A cookie is a small piece of information that a website or service asks a browser to retain. The browser may return that information on a later request to the relevant service. Cookies can support a session, remember a choice, help deliver a secure page or contribute to measurements of website activity.

Session cookies generally expire when the relevant browser session ends. Persistent cookies may remain until their expiry or until you remove them. First-party cookies are associated with the website you are visiting; third-party cookies are associated with another service involved in the page. These categories describe how a technology works, rather than whether every use is automatically necessary or lawful.

Local storage and session storage can keep information in a browser without using the cookie mechanism. A tracking pixel is a small network request that can report an event to a provider. Scripts, tags and software development tools can also process information about a page visit.

Browser caching is different: it may temporarily retain ordinary assets such as images and fonts to load a page efficiently. Downloading an image or font still involves a request to the server supplying the asset. A statement that custom code does not set cookies should not be interpreted to mean that the hosting platform receives no technical requests.

The custom Elmhurst Codecraft sections use JavaScript for the section index, scroll reveals, button movement, expandable content and the local project brief. These custom features do not intentionally set cookies, create local-storage records or introduce an advertising or session-recording script.

The project brief retains entries only within the active form while you complete it. Validation and the completion message run in the current page. Its button does not send form values to a server, and the form is cleared after a valid confirmation. Its temporary reference is not saved as a tracking identifier by the custom tool.

Shopify and the supporting infrastructure may use technologies needed to deliver, secure or administer a storefront. Depending on enabled features, these purposes can include security checks, session management, storefront access and localization. A platform may process technical request information even where a visitor does not use a project form.

Features such as shopping carts, customer accounts or checkout are not part of the custom web-development page described here. If those platform features are enabled elsewhere, their technology use must also be reflected in the store’s live privacy configuration. Essential technology is limited to what is necessary for the relevant requested function.

Preference technologies may remember a selected language, region or privacy choice. They can make a website easier to use on a later visit. Whether a particular preference requires consent depends on its purpose and applicable law.

The custom section index, FAQ and modal do not remember their open or closed state after the page is reloaded. A visitor can use them without a custom profile being created. Any additional preference feature installed outside these sections should be identified in the live consent controls.

Analytics technologies can measure visits, page use, device characteristics or traffic sources. Their data may help identify errors or understand how a website is used. The custom sections do not add their own analytics provider, but Shopify features or independently installed tools may operate according to the storefront configuration.

Optional analytics should be enabled only under the applicable legal requirements, including consent where required. Analytics should not be described as essential solely because a business would find the measurements useful. The purpose, provider and relevant retention period should be disclosed when such a tool is enabled.

The custom page does not embed a social-media feed, an external video player, an interactive map or an advertising pixel. Email addresses, the business address and the phone number are shown as plain text, so they do not launch a third-party messaging or mapping service from the page.

If advertising tags, behavioral measurement or external embeds are later added, they may process information under their providers’ terms. Such additions require a review of this policy, the Privacy Policy and the relevant consent setup before they are used. A redesign does not make optional tracking necessary.

Where an on-site privacy banner or preference center is provided, use its controls to make or change the available choices. Non-essential technologies that require consent should remain disabled until valid consent is given. Rejecting an optional category should not disable the basic custom navigation or the local project brief.

The custom sections do not provide a separate consent banner and do not manage independently installed applications. Platform consent settings must be configured through the applicable storefront controls. A preference recorded in one browser may not automatically apply to another browser or device.

Most browsers allow you to inspect stored site data, remove cookies and restrict some third-party storage. The location and wording of those controls vary by browser and version. Removing data can reset preferences or end an active session for a feature that relies on it.

Blocking all cookies may affect platform functions even though the custom section interactions do not need them. Browser blocking does not automatically remove historical records already held by a provider. For questions about a specific provider’s records, use the applicable privacy request process.

Some browsers or extensions can send privacy signals such as Global Privacy Control. Where applicable law requires an opt-out signal to be honored for an activity performed by this website, the live platform and tracking configuration should process that signal as required.

A legacy Do Not Track setting is not universally implemented in the same way. This policy does not promise that every third-party system responds to every signal. A visitor can contact us about the privacy choices relevant to a specific live feature.

A technology’s retention period depends on its function, provider and configuration. The custom sections do not create a persistent form record or a custom tracking cookie. Platform cookies may have their own session or fixed expiry periods, and independently added tools may use different periods.

We may update this policy when the actual website configuration changes. The posted update date identifies the current version. Questions about a particular cookie should include its name, the domain shown in the browser and the approximate time it was observed; please do not send the cookie’s full value if it contains a token or personal information.