Cookies Policy

PraiseWall uses a small set of browser-side mechanisms to make the static site function. The demonstration primarily uses localStorage rather than server-side cookies. Examples include remembering a cookie preference, keeping a cart, remembering a selected plan, recording a local subscription email, and demonstrating a local checkout result.

A local preference does not mean the production service is free of all cookies. If analytics, authentication, payment, embedded media, or other third-party services are added later, those providers may set their own cookies or similar technologies. The production privacy and cookie notices should then identify the relevant categories and purposes.

Essential local storage is used to preserve actions that would otherwise disappear during navigation. Cart state is not a payment record. Selected plan state is not a billing authorization. The static checkout demonstration does not collect card details and does not process a payment.

The site may also use standard browser functionality for accessibility, responsive presentation, and navigation. A browser may retain cached assets independently of the site's local preference controls.

The cookie banner provides Accept and Decline controls for the demonstration preference. The preference is stored locally under the PraiseWall namespace. Clearing site data in the browser can remove that preference and other local demonstration state.

If a production deployment adds non-essential analytics or marketing technologies, those should be introduced only with the notices and consent mechanisms required by the applicable jurisdiction. Third-party processors should be documented in the privacy policy.

Users can usually control cookies and local storage through browser settings. Blocking all storage may affect cart or preference behavior on the static demonstration.

This policy explains the current static architecture and should be revised when integrations are added. The production version should include an effective date and a contact route configured in company.js.

Nothing in this policy is intended to override mandatory privacy rights or statutory requirements. Where local law requires a different consent, disclosure, or retention approach, the production service should follow that requirement.

Contact fields are intentionally blank until configured in company.js.