Acceptable Use Policy

Rules for lawful, secure, and sovereign use of our services, products, and infrastructure. This policy is part of the Terms & Conditions of Service toward how account data, semantic occupancy, retrieval traces, and governance records are handled.

Version 2026-07-21-tac-v5-priv-v4-aigov-v3-aup-v3

This Acceptable Use Policy applies effectively immediately and shall be revised as the service matures. See Terms & Conditions Section 1.1.


1. Scope

 This Acceptable Use Policy (“AUP”) supplements and forms part of the Terms of Service governing use of the AI / LLM and associated governed retrieval infrastructure.  Violation of this Acceptance of Use constitutes a material breach of the Terms and Conditions which may result in governance action, refusal of service, losing privileged seat for our services, including use of tenants and tiers for LLM service, or a suspension/termination may be warranted.

2. What You Do Not Upload
  • malware, ransomware, exploits, Trojans, weaponized payloads, remote-access tools, or other malicious executable content.
  • content that is unlawful under applicable law, including the laws of your jurisdiction and the jurisdiction in which the platform operates.
  • child sexual abuse material (CSAM) or exploitative material involving minors. The platform maintains a zero-tolerance policy for such content.
  • content that infringes copyrights, trademarks, patents, trade secrets, confidentiality obligations, or other intellectual-property rights that you do not lawfully control or have authority to process.
  • credentials, authentication secrets, private cryptographic keys, tokens, or personal data relating to third parties where you lack lawful authority or consent to upload such material.
  • files intentionally designed to evade admission controls, including malformed archives, polyglot payloads, deceptive MIME structures, embedded executable chains, or admission-evasion artifacts.

3. What You Should Not:
  • attempt to retrieve, infer, reconstruct, enumerate, or otherwise gain access to another tenant’s occupancy, retrieval context, governance metadata, or operational state.
  • circumvent, probe, bypass, or manipulate tenant, tier, or governance sovereignty boundaries.
  • brute-force, scrape, crawl, enumerate, fingerprint, or map platform users, tenants, tiers, APIs, retrieval scopes, or infrastructure behavior.
  • launch prompt-injection, retrieval-poisoning, adversarial reasoning, jailbreak, or governance-manipulation attacks against the platform or other tenants.
  • generate output intended to harass, defame, impersonate, fraudulently misrepresent identity, facilitate unlawful conduct, or intentionally deceive.
  • train external systems or models using platform outputs in a manner intended to reverse-engineer platform governance, retrieval architecture, sovereignty boundaries, or operational internals.
  • overload, destabilize, stress-test, or impair the platform through abusive automation, denial-of-service activity, runaway upload loops, excessive retrieval generation, or intentionally wasteful resource consumption.

4. Sovereignty Abuse Will Not Be Tolerated

 Tier requests, tenant structures, and governance-elevation requests must reflect legitimate operational or organizational purposes.
Users may not:
  • manufacture artificial tenants or tiers to circumvent governance restrictions.
  • attempt to fragment occupancy for evasion purposes.
  • misrepresent ownership, authorship, or governance authority over shared or common content.
  • use governance workflows to interfere with another tenant’s sovereignty or retrieval integrity.
The platform reserves the right to deny, revoke, merge, archive, or terminate governance structures determined to be abusive, deceptive, duplication, or operationally harmful.

5. Reporting and Enforcement

 Suspected violations of this AUP needs be reported to  security@signavision.ca .
Reports should include sufficient information to support an investigation,including relevant tenant identifiers, timestamps, retrieval traces, or uploaded artifacts where available. The platform may investigate suspected violations using governance logs,admission provenance records, retrieval traces, and operational observability data.

5.1 Possible enforcement actions may include:

  • warnings.
  • content rejection or removal.
  • occupancy quarantine.
  • tier restriction or revocation.
  • rate limiting or throttling.
  • temporary suspension.
  • permanent account or tenant termination.
  • referral to law-enforcement or regulatory authorities where required by law.
We reserve the right to act immediately where necessary to protect platform integrity, tenant sovereignty, operational stability, or legal compliance.

6. What We Might Scan Nor Reject

 All uploads will be going pass through a quarantine and admission pipeline, which may include file-type detection, malware scanning, MIME validation, and structural sanity checks. Files that fail admission are destroyed, and metadata relating to the rejection is logged for security and audit purposes. Repeated rejections may result in restriction or suspension.

7. Audit and Observability

 The platform maintains governance, admission, retrieval, and operational observability records for security, audibility, sovereignty enforcement,abuse prevention, platform integrity, and lawful-compliance purposes.

These records may include:
  • admission outcomes.
  • scanner verdicts.
  • retrieval traces.
  • governance actions.
  • tier and tenant life cycle events.
  • rate-limiting and abuse-detection events.
  • operational-stability telemetry.
Observability records are not used for advertising or cross-tenant profiling. Retention periods and deletion-life cycle rules are described in the Privacy Policy.

8. Security Research

 Authorized good-faith security research intended to responsibly is close vulnerabilities may be permitted only with prior written approval from the Company. Unauthorized probing, fuzzing, extraction attempts, retrieval-boundary testing, prompt-injection campaigns, or sovereignty-enumeration activities are prohibited unless explicitly authorized in writing Coordinated-disclosure enquirers may be sent to  security@signavision.ca .

9. Changes

 This AUP is versioned. Updates are reflected in the policy version as record entered in your account.

Privacy Policy   ⚙️   Terms & Conditions   ⚙️   Acceptance of Use   ⚙️   Governance