Security

Security and boundary clarity are part of the product trust model

The website is intentionally constrained: explain the product, convert buyers, distribute apps and route users safely. Operational POS work never happens here.

Principles

Security starts with strict surface separation

Visitors, customers and resellers should always know whether they are on the public website, a portal or an operational app.

The website never executes live cashier, stock or branch operations.
Customer and reseller portals are separated from the public marketing site.
License access, downloads and billing visibility stay in the portal layer.
Operational execution remains inside Desktop and Mobile runtimes.

Trust

Trust signals used across the growth website

These trust signals support conversion while reinforcing the product rule that the website is not the POS runtime.

Desktop and Mobile operational workflows remain outside the browser.
Licenses, downloads and onboarding are clearly separated from store operations.
Portal, reseller and public website journeys each use their own route family.
Structured content and canonical routes prepare the site for long-term SEO growth.