1. Who This Policy Applies To

This AUP applies to:

Every Operator that installs, activates, or operates a Dioschub instance, regardless of tier (Free, Pro, or Enterprise); and
Every User who accesses or uses Dioschub through an Operator’s deployment.

Operators are responsible for ensuring that all Users within their deployment comply with this AUP. An Operator’s failure to enforce this AUP against its Users is itself a violation of this AUP.

This AUP is incorporated into the Dioschub EULA and Terms of Service. By installing or using Dioschub, all Operators accept this AUP. For Enterprise customers, this AUP forms part of the Enterprise Agreement.

2. Permitted Use

Dioschub is licensed exclusively for internal business use by the Operator’s own employees, contractors, and agents. Permitted uses include:

Internal productivity and knowledge management — AI-assisted drafting, research, summarisation, and analysis for internal business purposes;
Business process automation — connecting internal tools and workflows via MCP-compatible integrations for the Operator’s own operations;
Knowledge base management — building and maintaining internal knowledge bases accessible to Permitted Users;
Sector-specific internal assistants — configuring assistants for internal use in domains such as healthcare, finance, legal, and customer operations, subject to all applicable regulations; and
Development and testing — evaluating Dioschub capabilities within a controlled internal environment.

Internal use only

Dioschub may not be used to provide AI services to external customers, end-users, or any party outside the Operator's organisation without a separate commercial agreement with Intrigsoft. This applies to all tiers.

3. Operator Responsibilities

As the operator of a self-hosted Dioschub deployment, you are solely responsible for:

3.1 Configuration and Oversight

Configuring Dioschub appropriately for your use case, including system prompts, role-based access controls, tool permissions, and compliance settings;
Ensuring that AI-generated outputs are subject to appropriate human review before being used for any consequential decision, including decisions affecting individuals’ employment, health, financial standing, or legal rights;
Disclosing to Users that they are interacting with an AI system where required by applicable law or where such disclosure is necessary to avoid misleading Users; and
Maintaining audit logs and oversight mechanisms sufficient to detect and respond to misuse within your deployment.

3.2 Regulatory Compliance

Complying with all applicable laws and regulations in connection with your use of Dioschub, including data protection law (GDPR, HIPAA, PDPA, and equivalents), sector-specific AI regulations, financial services regulations, and healthcare regulations as applicable to your industry and jurisdiction;
Obtaining all necessary regulatory approvals, certifications, or consents before deploying Dioschub in regulated contexts; and
Implementing any domain-specific controls required by applicable regulation, including PHI redaction for healthcare deployments, PCI-DSS controls for payment-related deployments, and AI risk classification procedures under the EU AI Act for high-risk use cases.

3.3 Third-Party Services

Ensuring that your use of third-party services connected to Dioschub (including LLM providers, identity providers, and MCP tool servers) complies with those providers’ own terms of service and acceptable use policies; and
Accepting sole responsibility for API costs, data handling, and compliance obligations arising from third-party integrations.

3.4 User Management

Restricting access to Dioschub to authorised Permitted Users only;
Revoking access promptly when a User’s authorisation ends (e.g. upon termination of employment or contract); and
Educating Users on the appropriate and lawful use of AI tools within your organisation.

4. Absolute Prohibitions

Zero tolerance — no warnings issued

The uses listed in this Section are prohibited absolutely. Discovery of any such use will result in immediate termination of the Licence Key (where technically possible) and all legal remedies available to Intrigsoft. No warning period applies.

4.1 Weapons and Physical Harm

Dioschub must not be used in connection with:

The design, development, production, testing, or deployment of weapons systems, including conventional weapons, chemical weapons, biological weapons, radiological or nuclear weapons, or autonomous weapons;
Planning, facilitating, or supporting acts of terrorism, political violence, or mass harm; or
Any activity intended to cause physical harm to individuals or groups.

4.2 Mass Surveillance and Privacy Violations

Operating mass surveillance systems that monitor individuals without their knowledge or lawful authority;
Building systems to track, profile, or score individuals based on protected characteristics (race, religion, gender, sexual orientation, political opinion, or similar) in ways that are discriminatory or unlawful;
Aggregating personal data to build individual profiles for purposes the individuals have not consented to and that are not otherwise lawfully justified; or
Circumventing privacy protections, anonymisation measures, or consent mechanisms.

4.3 Child Safety

Generating, processing, distributing, or facilitating access to child sexual abuse material (CSAM) or any content that sexualises, exploits, or endangers minors; or
Using Dioschub in any way that facilitates grooming, trafficking, or harm to children.

4.4 Disinformation and Manipulation

Generating disinformation, propaganda, or deliberately false content intended to deceive the public or manipulate political processes at scale;
Creating synthetic media (deepfakes, voice clones, or fabricated documents) that falsely represent real individuals without their consent and with intent to deceive or harm; or
Operating coordinated inauthentic behaviour campaigns or influence operations.

4.5 Safety System Circumvention

Deliberately engineering system prompts, tool configurations, or inputs designed to bypass, override, or neutralise the safety guardrails of underlying LLM providers (including Anthropic, OpenAI, and Google);
Using Dioschub to probe, attack, or extract information from LLM safety systems for the purpose of circumventing them; or
Configuring Dioschub in a way that is designed to generate outputs that violate the LLM provider’s own usage policies.

4.6 Illegal Activity

Using Dioschub to facilitate, plan, or execute any activity that is illegal under applicable law, including fraud, money laundering, tax evasion, sanctions violations, or intellectual property theft; or
Using Dioschub in jurisdictions where its use would violate local law or regulatory requirements.

4.7 Unauthorised External Deployment

Providing access to Dioschub to external customers, third parties, or the general public as a product or service without a separate commercial agreement with Intrigsoft; or
Reselling, sublicensing, or otherwise commercialising Dioschub without authorisation.

5. Restricted Uses Requiring Additional Controls

The following uses are not prohibited outright but require Operators to implement additional controls before deployment. Proceeding without adequate controls is a violation of this AUP:

5.1 High-Stakes Decision Making

Using Dioschub to assist in decisions that materially affect individuals’ lives — including employment decisions, credit or insurance assessments, medical diagnoses or treatment recommendations, or legal determinations — requires:

A qualified human to review and take responsibility for every AI-assisted decision before it is acted upon;
Clear disclosure to affected individuals that AI has been used in the process where required by law; and
Documented procedures for challenging or appealing AI-assisted decisions.

5.2 Regulated Industries

Deploying Dioschub in healthcare, financial services, insurance, legal services, or other regulated industries requires Operators to:

Obtain all applicable regulatory approvals or certifications before deployment;
Implement all sector-specific technical controls required by applicable regulation; and
Maintain documentation sufficient to satisfy regulatory audit requirements.

5.3 Processing Sensitive Personal Data

Configuring Dioschub to process special category personal data (health data, financial data, biometric data, or data revealing racial or ethnic origin, political opinions, religious beliefs, sexual orientation, or criminal history) requires:

A lawful basis under applicable data protection law for each category of sensitive data processed;
Appropriate technical controls to minimise exposure of sensitive data within the system prompt, tool calls, and conversation logs; and
A completed Data Protection Impact Assessment (DPIA) where required by applicable law.

6. AI Output Responsibility and Disclaimer

Intrigsoft is not responsible for AI-generated outputs.

Dioschub is a self-hosted platform that routes requests to third-party LLM providers chosen and configured by the Operator. Intrigsoft does not control, monitor, or review the outputs generated within any Operator's deployment.

The Operator is solely responsible for all outputs generated through their Dioschub deployment, including outputs that are inaccurate, inappropriate, harmful, or in violation of applicable law. This responsibility cannot be transferred to Intrigsoft by virtue of the platform having been used to generate the output.

Operators must not represent to Users, regulators, or third parties that responsibility for AI-generated outputs lies with Intrigsoft. Any such misrepresentation is itself a violation of this AUP.

Intrigsoft additionally disclaims responsibility for:

Outputs generated by LLM providers that violate those providers’ own usage policies — such violations are between the Operator and the LLM provider;
Outputs resulting from misconfiguration of the Dioschub deployment by the Operator or its Users; and
Outputs generated during any period in which the Operator was operating in violation of this AUP.

7. Technical Enforcement Limitations

Intrigsoft acknowledges the following constraints on its ability to enforce this AUP technically:

Free Tier — Dioschub's Free Tier currently operates without a Licence Key. Intrigsoft has no technical mechanism to suspend a Free Tier installation. Enforcement against Free Tier violations is by legal remedy only, including injunctive relief and claims for damages under the EULA.
Enterprise Tier — Enterprise licences are validated with extended offline grace periods. Revoking an Enterprise Licence Key does not immediately disable the installation. Enforcement is through contractual termination under the Enterprise Agreement, with legal remedies where the Operator continues to operate in breach.
Pro Tier — Pro licences are enforced via the Intrigsoft licence server. Revocation of a Pro Licence Key disables the installation upon the next licence validation cycle.

The absence of a technical enforcement mechanism for Free and Enterprise tiers does not limit Intrigsoft’s legal rights. Operators who continue to use Dioschub after termination of their licence or after being notified of a violation do so in breach of the EULA and this AUP, and Intrigsoft reserves all legal remedies.

8. Enforcement and Consequences

8.1 How Violations Come to Light

Because Dioschub is self-hosted, Intrigsoft does not proactively monitor deployments. Violations typically come to light through:

Reports from the Operator’s own users or administrators;
Reports from third parties affected by the Operator’s use of Dioschub;
Regulatory investigations or legal proceedings; or
Intrigsoft’s own investigation following a credible complaint.

8.2 Enforcement Tiers

Intrigsoft applies the following enforcement approach based on the nature and severity of the violation:

Violation Type

Tier

Response

Section 4 absolute prohibition (weapons, CSAM, surveillance, etc.)

All tiers

Immediate termination — no warning

Deliberate safety bypass or guardrail circumvention

All tiers

Immediate termination — no warning

Illegal activity or regulatory violation

All tiers

Immediate termination — no warning

External deployment without commercial agreement

Pro / Enterprise

Immediate termination — no warning

Misconfiguration or accidental policy breach

Pro / Enterprise

Written warning — 14 days to remedy

Exceeding plan limits in good faith

Pro

Notice to upgrade — 14 days

Failure to remedy after written warning

Pro / Enterprise

Termination

8.3 Reporting a Violation

If you become aware of a Dioschub deployment that appears to violate this AUP — whether your own or another Operator’s — please report it to legal@intrigsoft.com. Include as much detail as possible. All reports are treated confidentially.

8.4 Self-Reporting

Operators who discover an accidental or unintentional violation within their deployment are encouraged to self-report promptly. Self-reporting before Intrigsoft becomes aware of a violation is treated as a mitigating factor and may result in a warning and cure period rather than immediate termination, provided the violation is not an absolute prohibition under Section 4.

9. Relationship to LLM Provider Policies

Dioschub connects to third-party LLM providers including Anthropic, OpenAI, Google, and others. Each of these providers has its own usage policies that govern what their models may be used for.

This AUP operates alongside, and does not replace, those provider policies. Operators are bound by both this AUP and the usage policies of any LLM provider they connect to Dioschub. A use that is permitted under this AUP may still be prohibited by the LLM provider’s policies, and vice versa. The more restrictive rule applies.

Violations of an LLM provider’s usage policy by an Operator using Dioschub are between that Operator and the provider. However, if such a violation also constitutes a violation of this AUP, Intrigsoft may take enforcement action under Section 8.

10. Changes to This Policy

Intrigsoft may update this AUP from time to time to reflect changes in law, technology, or the capabilities of Dioschub. Changes will be published on our website with an updated effective date.

For Pro subscribers, material changes will be notified by email at least thirty (30) days before they take effect. For Enterprise customers, material changes are subject to the notice provisions in the Enterprise Agreement. For Free Tier users, the current version of the AUP published on the Intrigsoft website governs use at the time of installation and operation.

Continued use of Dioschub after the effective date of a revised AUP constitutes acceptance of the changes.

11. Contact

For questions about this AUP, to report a violation, or to discuss whether a specific use case is permitted:

Intrigsoft Pvt Ltd

Sri Lanka

Email: legal@intrigsoft.com