Skip to content

Privacy

Privacy by deployment architecture, not by slogan.

This notice explains the public website boundary and the data paths a LowToHi operator may configure.

01

Public website

The hosting provider may process standard request metadata required to deliver and secure the site. Any analytics or additional tracking must be disclosed by the deployed service owner.

02

Language and interface preferences

The site may store a local preference so navigation remains in the selected language. Product sessions may use security cookies defined by the deployed authentication configuration.

03

User-controlled deployments

Local data remains inside infrastructure controlled by the operator unless that operator enables remote models, external tools or connected services.

04

Remote providers

When a remote provider is enabled, the admitted request fragment is processed under that provider’s contract, retention policy and regional configuration.

05

Contact and deletion

The public deployment must configure a verified privacy contact before collecting contact-form or customer data.