MrPeelz
Privacy

Privacy

Short, because this demo genuinely does very little.

Demonstration copy. This page describes what the demo does. A live MrPeelz site needs a real privacy policy reviewed by a lawyer before launch.

What this demo stores

Two things, both in your own browser and neither sent anywhere:

  • A splash flag in sessionStorage, so the banana only peels once per visit.
  • A demo session in localStorage when you sign in with one of the printed demo accounts. It holds a name, an email and a role. Signing out deletes it.

What this demo does not do

No analytics, no advertising pixels, no third-party trackers, no cookies. The forms do not submit — they show a notice saying so rather than pretending to succeed.

Fonts

Typefaces load from Google Fonts, which means Google receives the request. A production build would self-host them to avoid that.

What a live site would need

Once real orders and accounts exist: what is collected and why, how long it is kept, who it is shared with (payment processor, delivery), the legal basis, and how to request deletion. Under the CCPA a California business of sufficient size also needs a "Do Not Sell or Share" path and a response process for access requests.