EONVANT

Trust

Privacy and security principles

These statements describe how EONVANT is built today. They are limited to what the architecture actually supports; we do not claim protections or certifications we have not earned.

  • Private to your account

    Decision records, evidence and outcomes are owner-scoped. Access is enforced at the database level by row-level security rules tied to your authenticated account.

  • You control the data

    You can export your records as readable JSON and permanently delete them from Settings. Deletion removes the data we store.

  • AI and research only run when you trigger them

    Research and analysis are user-initiated. Nothing runs in the background to generate answers you did not ask for.

  • No autonomous execution

    EONVANT is decision support. It does not place orders, send emails, execute transactions, or act on your behalf.

  • Honest scope

    We do not display certifications, audit reports, residency guarantees or retention commitments we have not earned or contracted.

Current architecture

  • Authenticated accounts. You sign in before any decision record can be created or read.
  • Owner-scoped persistence. Records, evidence, challenges, decisions, actions and outcomes are stored per account and enforced at the database level by row-level access rules.
  • Server-side research and analysis capabilities run only when you explicitly trigger them, never in the background.
  • You can export your records as readable JSON and permanently delete them from Settings.
  • EONVANT remains decision support. It does not autonomously execute external actions on your behalf.
  • Model independence is a design constraint: the decision record format is ours, so providers can be replaced without changing your records.
  • We do not display certifications, audit reports, residency guarantees or retention commitments, because none have been earned or contracted yet. Billing is not enabled.