Trust Center
This page separates product state, technical test evidence, synthetic showcases and open release gates. It is not a certificate or a list of reassuring slogans.
An installer test proves installation. HTTP 200 proves availability. externalWrites 0 proves that a test run changed no external system. None of these findings proves rankings, citations, leads, time saved or revenue.
Built means code exists. Verified means a named test produced a reproducible result. Observed means a measurement exists for a suitable period. Open means the claim is not yet supported. The Proof Ledger follows this distinction.
Velunor Bikes at velunor-bikes.example, Qevora Systems at qevora-systems.example and Studio Talvori at studio-talvori.example are invented companies. Names, domains, goals, KPIs, approvals and outcome values exist only to demonstrate the product. They are not customer references.
Version numbers, check counts, manifests, file hashes, runtime receipts and SiteOne detection can be real test evidence. They are described as technical artifacts and are not assigned to a fictional company as business impact.
Workspace, goals, evidence, actions, approvals, receipts and audit live in the local product database. The public website loads analytics only after consent. Form data is not sent to analytics. Production secrets belong only in the separated Secure Profile.
Installers maintain ownership markers, manifests and file hashes. A release still needs fully signed artifacts, an SBOM, provenance, reproducible packages and documented verification on every target platform. MarketingOS claims no higher maturity until these gates pass.
Responsible disclosure matters more than an invented seal. Reports go to support@scilipoti.de. There is currently no formal bug bounty program, guaranteed response time or external certification.
They include separated operating system identities, enforced capability grants, a secret broker, egress rules, host key verification, signed receipts, signed releases, recovery tests and cross-platform security checks. Release status changes only after supporting evidence passes.
Continue
The security page explains the Direct Profile, Secure Profile and host runtime boundaries without shortcuts.