What data leaves the endpoint?
Only AI-related records. Filtering happens on the endpoint, and the server validates every incoming record again: anything unrelated to AI is discarded before it is stored. API key values, MCP arguments and environment variables are not collected.
Does Aletheon Guard send prompt content anywhere?
No. Detection runs locally in the browser, and prompt content is not sent to Aletheon’s servers. Guard is currently in development; we can discuss rollout timing for your organisation during the demo.
How is it deployed?
A one-line command (macOS, Linux) or an installer package (Windows MSI, macOS pkg, deb, rpm). Packages can be distributed through MDM, and the Chrome extension can be force-installed by policy. First results typically appear within 15–30 minutes.
Is an on-premises deployment available?
Yes. Aletheon is available as an EU-hosted cloud service and on-premises. We discuss on-premises terms and timelines during the demo.
Does Aletheon certify compliance?
No. It provides the inventory, risk classification, decision records and audit log that support your obligations under NIS2, DORA, GDPR and the EU AI Act. Whether your organisation is compliant remains for you and your legal advisers to determine.
Where is the data stored?
Aletheon Cloud is hosted in the EU. Each customer’s data is kept in a separate tenant, isolated at the database level, and no other customer can access it.