Privacy Policy

This Privacy Policy explains the information practices for the PraiseWall static website concept. The company data source intentionally leaves owner, email, phone, and address blank until an operator supplies those details.

Information submitted through a form can include your name, email address, message, or plan interest. Contact form values may be stored in your browser; paid orders are stored in Cloudflare KV. A production implementation should connect forms and billing to appropriately secured services and publish the applicable processor disclosures.

PraiseWall should collect only information needed to operate the requested feature. Payment details should be handled by the selected payment processor rather than stored in the static site's localStorage. Checkout uses the fmzpay hosted payment page.

Testimonial content is supplied by customers and may contain names, locations, dates, ratings, or other information that the submitter chooses to provide. The wall operator should publish only content it has permission to display and should provide a reasonable path for correction or removal requests.

PraiseWall does not use testimonial content for model training. Testimonial content is intended for the testimonial display service and its related administration, not for training an artificial intelligence model.

Cookies and local storage may be used for preferences, cart state, selected plan state, or similar site functions. See the Cookies Policy for more detail. The site does not require advertising cookies for its core static pages.

Data retention should be limited to what is reasonably necessary for the requested service, contractual records, security, dispute handling, or legal obligations. Where a production processor is used, its retention terms should be reviewed separately.

You may request access, correction, deletion, or clarification regarding information held about you, subject to applicable law and legitimate recordkeeping needs. Use the published contact route once the company contact fields have been configured.

This policy may be updated as the production service changes. The effective version should be displayed with an effective date before launch.

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