Current cookie status
The Higgfield cookies notice records that the current public website does not set application cookies. There are no login cookies, preference cookies, analytics cookies, advertising identifiers, conversion pixels, or consent-manager cookies in the site code. The tools also avoid persistent browser storage.
This statement applies to the static Higgfield application as built for production on 2026-08-28. It should be checked against the actual deployed network behavior before release and reviewed whenever hosting, embedded content, measurement, authentication, or preferences change.
What cookies normally do
A cookie is a small value a website or related service asks a browser to store and return with later requests. Cookies can support sign-in sessions, security, language choices, shopping carts, analytics, advertising, or remembering consent. Similar technologies include localStorage, IndexedDB, pixels, and device identifiers.
Not every technical request creates a cookie. A browser can request HTML, styles, fonts, images, or scripts without the application setting persistent state. The present site uses that simpler model: pages and approved brand assets load, while tool choices remain in memory only for the current page.
Browser-only tool state
When you type a source description or select a motion control, JavaScript reads those values to update the visible result. The site does not place the description or result in a cookie, localStorage, IndexedDB, or a remote project store. Reloading the page clears the current interaction.
This temporary state is sufficient for a deterministic planning prototype. It is not a security boundary for secrets, so users should still avoid entering private or sensitive information. A neutral description of the source image is the intended input.
No analytics or advertising cookies
Higgfield does not currently connect Google Analytics, advertising networks, marketing automation, heat maps, session replay, attribution services, or social pixels. Local observable events are dispatched inside the browser for development testing and are not sent to an analytics endpoint.
Because no remote measurement vendor is enabled, the site does not claim to measure visitor activation, retention, conversion, or advertising audiences. A future measurement plan would require data minimization, provider review, event testing, policy updates, and a jurisdiction-appropriate consent decision.
No account or preference cookies
There is no registration, authentication, saved project library, billing profile, or personalized dashboard. Consequently, the application has no session identifier, refresh token, remembered account, or cross-device preference cookie. Tool routes are public static pages.
The site also does not remember effect filters, theme choices, dismissed notices, recent tools, or planning results between visits. A future preference feature should use the least persistent mechanism that meets the need and disclose its purpose and lifetime.
Hosting and external services
The configured deployment platform is Vercel, although deployment was not performed by the local generation task. Hosting infrastructure may process ordinary request and security information. Before public release, the deployed site should be inspected with browser developer tools to confirm whether platform configuration introduces any storage or headers not represented here.
A mailto link can open your email application, which is outside the website. Your email service may use its own cookies when you visit its web interface. Those cookies are controlled by that service and are not set by Higgfield merely because the site provides an email address.
Browser controls
Most browsers let users view, block, or delete cookies and site storage. Since the current application does not rely on such storage, blocking application cookies should not prevent the public pages or local planning controls from working. Browser extensions may alter behavior independently of this site.
Clearing site data will not delete an Higgfield account or project because neither exists. Support email is handled by email providers and is not browser storage controlled through this domain’s cookie settings.
Changes that require a new review
Authentication, analytics, embedded media, chat, payments, personalization, fraud tools, A/B testing, saved projects, or preference storage would materially change this notice. Those features should not be enabled silently. Their cookies or similar technologies need a purpose, provider, lifetime, security review, and appropriate user controls.
The privacy notice and terms may also require updates when technology changes. A consent banner should not be added as decoration; its design must reflect actual storage behavior and applicable requirements. Conversely, the absence of a banner is not a substitute for verifying the deployed site.
Questions and verification
Questions about this notice may be sent to support@higgfield.cc. Include the route, browser, and observed cookie or storage key without sending unrelated private information. A reproducible report can help distinguish application behavior from a browser extension or unrelated service.
Production verification should inspect response headers, document cookies, localStorage, IndexedDB, network requests, embedded resources, and the rendered policies. The notice is complete only while those observations continue to match the no-cookie, no-storage behavior described above.
Repeat this inspection after every hosting or dependency change, not only when the interface visibly changes.