Acceptable Use Policy
Effective date: 17 April 2026
1. Purpose
This Acceptable Use Policy defines prohibited use of DGS. It applies to websites, authenticated workspaces, mission briefs, uploads, prompts, generated outputs, billing flows, APIs, and any Standard, Synthetic, Deep, or restricted engine access.
2. Illegal, harmful, or deceptive use
You may not use DGS to plan, enable, automate, conceal, or materially assist:
- illegal activity, fraud, scams, deception, impersonation, or evasion;
- harassment, threats, exploitation, abuse, defamation, or targeted intimidation;
- privacy invasion, doxxing, unauthorized surveillance, or unlawful data collection;
- creation or distribution of misleading, manipulated, or falsely attributed materials;
- activity that violates intellectual property, confidentiality, contractual, or data rights.
3. Security abuse
You may not use DGS to develop malware, steal credentials, bypass access controls, exploit systems, evade detection, automate unauthorized vulnerability exploitation, exfiltrate data, or interfere with the Service or third-party systems.
4. Physical, critical, or regulated harm
You may not use DGS to cause physical harm, construct weapons, bypass safety systems, misuse critical infrastructure, or provide operational instructions that create unacceptable safety, nuclear, chemical, biological, energy, transportation, medical, financial, legal, or regulatory risk.
5. High-impact decisions
DGS outputs may support professional work, but you may not use DGS as the sole basis for decisions that determine legal rights, medical treatment, employment, credit, housing, insurance, safety approvals, nuclear operations, engineering sign-off, investment decisions, or other high-impact outcomes. Qualified human review is required.
6. Data and upload responsibility
You may not upload or submit data unless you have the right to do so. You are responsible for removing secrets, payment card numbers, regulated personal data, confidential third-party data, or sensitive materials that should not be processed through the Service.
7. Platform integrity
You may not bypass quotas, payment flows, access controls, workspace boundaries, engine restrictions, rate limits, security checks, or billing reconciliation. You may not attempt to extract hidden prompts, internal topology, model credentials, private artifacts, or restricted Synthetic/Deep systems.
8. Enforcement
DGS may remove content, block missions, pause runs, suspend users, revoke workspace access, restrict engines, report unlawful activity, or terminate accounts when we reasonably believe this policy has been violated or risk is unacceptable.
