Say what is true now.
We describe current website behavior and avoid representing future intentions as completed controls.
Trust center
Clear practices. Careful commitments.
A plain-language overview of how this public website works and how Lemeia approaches project-specific trust questions without making claims broader than the facts support.
Scope commitments in writing.
Client data, vendors, access, retention, security measures, and support obligations depend on the actual project and written agreement.
Avoid absolute promises.
No website, software product, or security process can be described honestly as risk-free, failure-proof, or universally compliant.
This public website today
What we can state specifically.
This summary is intentionally narrow. Product deployments and client systems may use different technology and are addressed separately.
The public website is delivered over HTTPS. That protects information in transit between a compatible browser and the website, but it is not a guarantee against every security risk.
This website does not currently offer visitor accounts, accept payments, or ask visitors to create or submit passwords.
The public contact experience prepares an email in the visitor’s email application. Visitors should not include passwords, payment-card data, health information, or other highly sensitive material.
The calculator, product samples, and system builder run in the browser. If a visitor chooses to email a result, that information becomes part of the email they decide to send.
Trust topics
Read the details without the fine-print theater.
Each page states its scope, current limitations, and the appropriate contact path.
Privacy
What this public website currently handles.
Website requests, local browser storage, email inquiries, external resources, and practical boundaries.
→AccessibilityOur current approach and known status.
Features we have implemented, limitations, feedback, and why we do not make a conformance claim.
→Responsible AIHow AI may support the work.
Human direction, review, project-specific decisions, and the limits of automated output.
→Client engagementsHow project commitments are established.
Discovery, scope, change control, approvals, launch, and support defined around the engagement.
→Last reviewedAugust 21, 2026
These pages describe the public website and Lemeia’s general approach. They are not certifications, security guarantees, legal advice, or substitutes for a signed client agreement.