Trust
We would rather tell you exactly what is true today than describe the company we hope to become.
What Heisterlux is built around
For each principle we separate what we aim for, what exists today, and what must be true before launch. "Today" only describes internal foundations in development environments. None of it is available to customers, and none of it is a security or recovery guarantee.
Explainability
- Principle
- A recommendation should come with its reasons: which recorded facts it rests on, which rule was applied and what is not known.
- Evidenced today
- In an internal development environment, recommendations are derived by fixed rules from recorded facts and declarations, without a language model. No customer-facing explanation exists yet.
- Before launch
- A customer-facing explanation showing facts, rule and gaps, independently tested for completeness.
Evidence and provenance
- Principle
- Records should show where information came from, who recorded it and when, and keep observed use apart from formally documented use.
- Evidenced today
- In an internal development environment, records carry their basis and recording history and are append-only.
- Before launch
- Define which evidence is accepted and how provenance is shown to customers; close open findings from internal testing of the audit trail.
Historical justification
- Principle
- The reason a reliance was accepted at the time should be kept as it was, not rewritten when circumstances change.
- Evidenced today
- The internal foundation seals justifications so earlier versions stay intact; later changes are added alongside them.
- Before launch
- Customer-facing history views and retention terms.
Uncertainty
- Principle
- Missing, conflicting or incomplete evidence should be shown as such, not smoothed into a confident answer.
- Evidenced today
- In the internal foundation, missing input produces "insufficient basis" instead of an invented conclusion, and conflicting or incomplete support is kept as its own state.
- Before launch
- Customer-facing display of uncertainty, tested with real users.
Human authority
- Principle
- Heisterlux recommends; people and organizations decide. A recommendation is not a decision, and a decision is not enforcement.
- Evidenced today
- The internal foundation has no mechanism that makes or enforces a decision. It does not yet verify a person’s authority to make a declaration; that is a known open design point.
- Before launch
- Decide and build how authority is verified and how decisions are recorded, before customers rely on declarations.
Customer data ownership
- Principle
- Customer data belongs to the customer. They should be able to take it out and have it deleted.
- Evidenced today
- Nothing is claimed as proven yet.
- Before launch
- Export and deletion functionality, defined terms, data location and a subprocessor list, published before the first customer.
Recoverability
- Principle
- Customers should be able to rely on their data surviving failures. Tested recovery before the first paying customer is a hard product gate.
- Evidenced today
- Nothing is claimed as proven yet.
- Before launch
- Tested restore, stated recovery point and recovery time objectives, export and deletion, and security measures — each with evidence. None of these is claimed today.
This website
- No analytics, advertising, session recording or chat widgets.
- No third-party scripts. Fonts and images are served from this site.
- In our pre-launch checks this site did not set cookies or use browser storage. Behaviour of the hosting infrastructure is reviewed as part of the launch.
- Forms do not accept submissions yet. When they do, the privacy notice will say exactly what is collected, why, by whom and for how long.
How we label product claims
Every capability carries one of four statuses: Available, In development, Up next or Exploring. Available requires a production release to customers, defined scope and audience, a support route and approval to publish. Code, test environments and architecture decisions do not count.
Before the product becomes available
Before the product becomes available we intend to publish, on this page:
- where customer data is stored and processed, and by which subprocessors;
- how access to customer data is controlled and logged;
- how to report a security issue, and how we respond;
- the terms and data processing agreement that apply.
Heisterlux does not currently hold security or AI management certifications, and does not claim to.
Reporting a security issue
[To be confirmed before launch: Heisterlux security contact]
