Security and approval model
Control first. Autonomy only where it is earned.
Managed AI assistant pilots should be useful without creating hidden risk. Ethonex starts with scoped workflows, approved access, and human review for sensitive actions.
Approved access only
No account connections, files, or private datasets are requested through the public form. Access is reviewed separately after fit is confirmed.
Draft-first external communication
Messages and sensitive outbound actions start as drafts for review. The v0 operating model does not assume unattended external sending.
Least practical privilege
The assistant workflow is scoped around the minimum applications, folders, and permissions needed for the pilot.
Visible operating boundaries
Before setup, Ethonex documents what the assistant can prepare, what requires review, and what remains out of scope.
Human escalation
Unclear, risky, legal, financial, compliance-sensitive, or destructive actions escalate instead of being automated silently.
Offboarding path
Pilot setup should include clear revocation and teardown steps so access can be removed cleanly if the workflow ends.
What not to submit
The request form is not a place for secrets.
Use the public request form to describe work, applications, constraints, urgency, and desired outcomes.
Do not submit passwords, API keys, OAuth tokens, private files, regulated data, mailbox exports, customer lists, or confidential datasets.
If a pilot is approved, Ethonex will handle access review and setup through a separate operator-approved process.
Ready to scope a controlled pilot?
Tell Ethonex what work you want help with. Keep the request high-level and safe; detailed access decisions happen after fit is reviewed.
Request access