Last updated: May 24, 2026
NEUGI is designed for local-first operation. By default, runtime state, memory, and configuration are stored in your local NEUGI directory and infrastructure under your control.
When you configure third-party providers, prompts and related content are sent directly to those providers according to your configuration and their policies. NEUGI maintainers do not proxy that traffic as a hosted relay service.
You are responsible for securing API keys, tokens, and environment variables in your deployment. Use least-privilege credentials and rotate secrets regularly.
NEUGI does not require centralized telemetry to operate. If you enable external monitoring integrations in your own environment, data handling follows the tools and services you choose.
No system can guarantee perfect security. You remain responsible for host hardening, network controls, access management, backup strategy, and incident response.
You control retention, cleanup, and deletion in your own runtime. Review configured memory lifecycles, logs, and backup policies to align with your compliance needs.
If your deployment processes personal or regulated data, you are responsible for compliance with applicable frameworks (for example GDPR, PDPA, HIPAA, or industry-specific controls).
This policy may be updated as NEUGI evolves. Continued use after updates indicates acceptance of the revised policy.
Privacy questions: atharia.agi@gmail.com