Security and responsible use

• The public trust surface is for FEN protocol facts, N521 research evidence, FENiOS context, planning, and structured draft generation.
• Public planning tools should not receive credentials, private keys, confidential records, regulated data, or other sensitive material.
• Protected workflows should use account checks, access review, operator gates, monitoring, and rate limits.

• Access tracks reduce ambiguity without granting automatic protocol execution.
• Treasury, validator, relay, and manager operations should stay out of public browser code.
• Privileged protocol actions should use least-privilege operational access and explicit human review.

• Privileged decisions are not made in browser code, and public pages do not expose private operator account details.
• Access review, privileged action approval, relay operation, and abuse-review outcomes stay in protected operational systems.
• The public account page can show readiness metadata when available; it does not reveal private credentials, privileged internals, private keys, or relayer secrets.
• Manual support review may delay or decline access when security, abuse-prevention, or account-integrity checks require it.

• Do not use the site to create harmful, deceptive, infringing, or unlawful material.
• Do not attempt to bypass, disrupt, overload, or interfere with the public site.
• Do not misrepresent public planning outputs as final professional advice.
• Do not submit third-party confidential information without permission.

If you notice a public-site security issue, privacy concern, broken link, or confusing legal notice, contact partnerships@fenrua.ai with a concise description. A machine-readable security contact is also available at /.well-known/security.txt.

Public planning outputs are designed to be useful drafts. Review them before using them for planning, partner conversations, product decisions, or public materials.