Privacy policy
What the Plusmark account, cart and order prototype collects, and the production privacy decisions still required before real customer data is collected.
Status of this document
Draft policy — pending business sign-off
Privacy policy is written for this prototype from the information Plusmark publishes today (catalogue, FAQ and contact details). Freight rules, delivery estimates, return windows and refund timelines have not been signed off by the business, so they are marked to be confirmed rather than guessed. Nothing on this page is a Plusmark commitment, and no certification or warranty period is asserted here.
Confirm the terms that apply to your order with the Plusmark desk before placing it — see contact & support.
Stated from published information
- Account profiles, saved addresses and saved boards are stored in the configured Supabase project and protected by row-level security.
- Guest cart and prototype order records stay in browser local storage.
- The custom frontend does not request raw card details.
- External channels such as WhatsApp and email have their own providers and privacy terms.
Awaiting business sign-off
- Production data controller and contact for privacy requests
- Supabase hosting region and retention schedule
- Order, invoice and enquiry retention obligations
- Production analytics, cookie and consent choices
Information in this prototype
Creating an account asks for a name, email address, mobile number and password. The profile row, delivery addresses and saved boards live in the Supabase project configured for this site, and row-level security limits them to the signed-in account holder. Cart contents, prototype orders and enquiries remain in your browser using local storage.
Clearing site data removes the local records. Account data can be changed from the account screens; do not enter sensitive financial credentials.
Payments and external services
The custom frontend does not ask for or store raw card numbers, CVV values or internet-banking passwords. A production Razorpay integration must use the provider checkout and server-side verification; this prototype does not process a real payment.
Product media is delivered through Cloudinary. Telephone, email and WhatsApp links hand you to those respective services when you choose them. Their handling of information is governed by their own terms.
Before production launch
A production privacy notice must identify the responsible business, the data collected and why, service providers, retention periods, security practices and the route for access, correction or deletion requests. Those operational details have not been supplied and are therefore left open rather than invented.
To be confirmed · Approved production privacy noticeTo be confirmed · Privacy request contact and response process