Security
Last updated: 19 July 2026
Security is one of our four core services — and the standard we hold our own work to. This page outlines the practices behind AIBOX deployments and this website.
1. On-premises by design
The strongest security control in AIBOX is architectural: models and data run inside your perimeter. There is no third-party AI cloud receiving your documents, no per-request data sharing, and no training on your content.
2. Deployment practices
Encryption in transit for all service interfaces; access to administrative functions restricted to named, authenticated users on the principle of least privilege.
Segmented network placement agreed with your IT team, so AIBOX reaches only the systems it integrates with.
Update and patching plans defined per deployment, including model and component updates.
3. Operational security
Monitoring and logging appropriate to the deployment, with alerts routed to your operators. Backup and recovery procedures are agreed as part of every implementation.
4. This website
aibox.bg is served exclusively over HTTPS and collects only the data described in our Privacy Policy.
5. Responsible disclosure
If you believe you have found a security issue in this website or an AIBOX product, please write to hello@teamlandi.com. We appreciate coordinated disclosure and will respond promptly.
Questions? Write to us at hello@teamlandi.com