AI disclosure
Some jurisdictions and internal policies require that a user be told when they are interacting with an AI system rather than a person. DioscHub does not inject an automatic disclosure banner, and it does not decide the wording for you — because what a disclosure must say, and whether one is required at all, depends on your jurisdiction and your use case. Disclosure is a control DioscHub puts in your hands rather than a fixed string it imposes.
Put the disclosure in the greeting
Section titled “Put the disclosure in the greeting”The assistant’s greeting — the opening message shown at the start of a conversation — is operator-configured free text, and it is the natural place for an AI-interaction notice. Set it on the Assistant to state, in your own words and to the standard your context requires, that the user is chatting with an AI assistant. Because you author it, you control the exact wording and can match it to the regulation you are meeting.
The “Powered by DioscHub” mark is not a disclosure
Section titled “The “Powered by DioscHub” mark is not a disclosure”Do not mistake the Free-tier “Powered by DioscHub” attribution for an AI disclosure. It identifies the platform vendor, not the nature of the assistant, and it says nothing about the user interacting with AI. If your obligation is to disclose AI interaction, meet it in the greeting — the attribution does not satisfy it, and replacing the attribution with your own branding on a paid tier does not remove any disclosure you placed in the greeting.
Next: Audit trail.