Last updated: May 1, 2025
FormGrid may use cookies or local storage to remember visitor choices and support basic site behavior. The main purpose of the static site storage is functional, including keeping cookie-consent preferences and maintaining the demo cart while a visitor compares plans.
The cookie banner explains that cookies may be used to improve the experience and analyze traffic. Accept and Decline choices are stored locally so the notice does not repeatedly interrupt the same browser.
The static demonstration stores cart items, the GRID10 promotion code, subscriber-demo state, and cookie consent. These values represent front-end state and do not constitute a live billing ledger or a payment-provider record.
If analytics are enabled in a production deployment, the site owner should configure the chosen analytics provider according to applicable law and update disclosures where necessary. Sample form and response content should not be presented as live analytics.
Current browsers provide controls for removing cookies and local storage. Clearing those values can reset the cookie banner, the demo cart, and other saved browser preferences used by the static site.
Third-party destinations linked from FormGrid can have separate cookie and privacy practices. Review the destination’s terms before entering personal or payment information on another service.
Before launch, the owner should review analytics tags, authentication providers, payment integrations, and embedded services. The production policy should describe any additional providers or technologies actually enabled.
Cookie behavior can change when site analytics, authentication, or account functions are added or removed. The publication date at the top of this page identifies the current policy version.
Before production launch, the site owner should review browser privacy settings, consent requirements, analytics providers, authentication services, and any embedded tools that can access local storage. This page describes the static demonstration and should be updated whenever the live implementation adds a technology that changes cookie or storage behavior.