Skip to main content

Legal

Acceptable Use Policy

Public legal text sourced from the repository documentation set. These documents remain subject to legal review where marked as draft.

Last updated March 29, 2026

Acceptable Use Policy

APPROVED v1 — Approved by EXEC 2026-03-31.

Effective Date: [TO BE DETERMINED]

Last Updated: March 29, 2026

This Acceptable Use Policy ("AUP") governs your use of the EVC Platform ("Service") operated by Wizdom Networks ("Company", "we", "us", "our"). This AUP is incorporated into and forms part of the Terms of Service.

Violation of this AUP may result in enforcement actions as described in Section 5.


1. Prohibited Content

You must not use the Service to create, store, or distribute:

  • Malware or malicious software. Applications designed to damage, disrupt, or gain unauthorized access to computer systems, networks, or data.
  • Illegal content. Any content that violates applicable laws, including but not limited to content that promotes illegal activity, facilitates fraud, or infringes on the rights of others.
  • Harassment or abuse. Applications designed to harass, bully, threaten, defame, or intimidate individuals or groups.
  • Spam or unsolicited communications. Applications designed to send bulk unsolicited messages, phishing attempts, or deceptive communications.
  • Infringing content. Applications that infringe on copyrights, trademarks, patents, or other intellectual property rights of third parties.
  • Regulated content without compliance. Applications that process health, financial, or other regulated data without appropriate compliance measures.

2. Prohibited Activities

You must not engage in the following activities:

2.1 Platform Integrity

  • Reverse engineering. Decompiling, disassembling, or otherwise attempting to derive the source code of the platform, its pipeline, or governance engine.
  • Circumventing quotas. Attempting to bypass build credit limits, rate limits, or other usage restrictions through technical means.
  • Automated scraping. Using bots, crawlers, or automated tools to extract data from the Service beyond what is available through the provided API.
  • Credential sharing. Sharing account credentials between individuals. Each user must have their own account. Organization features are available for team collaboration.
  • API abuse. Making excessive API calls designed to degrade Service performance or availability.

2.2 Build-Specific Rules

  • Harmful applications. You must not submit prompts intended to generate applications designed to cause physical harm, financial fraud, identity theft, or other damage to individuals or organizations.
  • System prompt extraction. You must not submit prompts designed to extract, reveal, or reverse-engineer the platform's internal system prompts, pipeline instructions, or LLM provider configurations.
  • Illegal output. You must not submit prompts specifically crafted to produce output that would be illegal to create, possess, or distribute under applicable law.
  • Evasion prompts. You must not submit prompts designed to circumvent content safety measures implemented by the platform or its LLM providers.

2.3 Resource Abuse

  • Deliberate quota exhaustion. Intentionally consuming build credits or compute resources with no productive purpose (e.g., submitting empty or nonsensical prompts to consume credits).
  • Denial of service. Attempting to overwhelm Service infrastructure through volume attacks, build flooding, or resource exhaustion techniques.
  • Multi-account abuse. Creating multiple accounts to circumvent trial limits, free credits, or enforcement actions.

3. Your Responsibilities

3.1 Build Output Review

You are responsible for reviewing all build output before deploying it to any environment. The Service generates code using AI systems, and output may contain errors, security vulnerabilities, or unintended behavior. You must not deploy unreviewed build output to production systems.

3.2 Compliance

You are responsible for ensuring that your use of the Service and any applications you build comply with all applicable laws, regulations, and third-party agreements.

3.3 Prompt Content

You are responsible for the content of prompts you submit. Prompts are transmitted to third-party LLM providers for processing. Do not include sensitive personal information, passwords, API keys, or other secrets in your prompts.


4. Reporting

If you become aware of any violation of this AUP, please report it to us at [abuse@wizdom.dev]. Reports should include:

  • Description of the violation
  • Any relevant evidence (URLs, screenshots, build identifiers)
  • Your contact information (optional, but helpful for follow-up)

We will investigate reports promptly and take appropriate action. We will not retaliate against anyone who reports a violation in good faith.


5. Enforcement

We enforce this AUP through a graduated response:

5.1 Warning

For first-time or minor violations, we will issue a written warning via email explaining the violation and required corrective action. You will have a reasonable period to comply.

5.2 Suspension

For repeated violations, serious violations, or failure to comply with a warning, we may suspend your account. During suspension:

  • You cannot create new builds or access the API
  • Existing build artifacts remain accessible for export
  • Billing continues during suspension (cancel your subscription to stop billing)

5.3 Termination

For severe violations, repeated violations after suspension, or violations that pose a risk to other users or the platform, we may terminate your account immediately. Upon termination:

  • All access to the Service ceases immediately
  • You have 30 days to request export of your data
  • After 30 days, your data may be permanently deleted

5.4 Immediate Action

We reserve the right to take immediate action without prior warning for violations that: (a) pose an imminent security threat to the platform or other users; (b) involve illegal activity; (c) could expose us to legal liability; or (d) involve active exploitation of platform vulnerabilities.


6. Changes to This Policy

We may update this AUP from time to time. Material changes will be communicated at least 30 days in advance via email. Your continued use of the Service after changes take effect constitutes acceptance of the updated AUP.


7. Contact

For questions about this AUP or to report a violation: [abuse@wizdom.dev].