EXANIA/GOVERNANCE & LEGAL
AI SYSTEMS / OPERATING CONDITIONS

Intelligence
demands accountability.

Clear rules for accessing Exania research, evaluating specialised AI systems and developing secure institutional deployments.

LAST UPDATED / 09 NOV 202627 CLAUSES / INTERNATIONAL SCOPESCROLL TO EXPLORE
01 / GOVERNANCEAN OPERATING FRAMEWORK FOR INTELLIGENCE

Powerful systems.
Defined responsibility.

Research, production infrastructure and institutional decisions require different levels of control. These terms establish the public baseline. Binding commitments are defined in written project agreements.

01

Authorised access

Access is limited to approved users, purposes and environments.

02

Human accountability

Critical outcomes demand evaluation, oversight and lawful decisions.

03

Data governance

Information, intellectual property and infrastructure are controlled by defined roles.

04

Contractual precision

Security commitments, acceptance tests and service levels belong in signed agreements.

02 / ACCESS CONTEXTSELECT A CONTEXT TO EXPLORE

One framework.
Distinct environments.

The applicable rights and obligations depend on what an organisation is actually accessing.

01 / 03● DEFINED SCOPE

Website & research

Public materials are made available for information and legitimate institutional enquiry. Reading them does not grant access to private models or create a procurement agreement.

ACCESSPublic information
PRIMARY TERMSWebsite terms
03 / THE AGREEMENT27 CLAUSES / FIVE CHAPTERS

Terms of Use.

A comprehensive framework covering institutional AI, security, data governance, cloud operations and commercial responsibilities.

EXANIA AIEXOHOOD LABS INC.09 NOVEMBER 2026
CLAUSE 01 / 27FOUNDATION

Agreement and scope

These Terms of Use (the “Terms”) govern access to the public Exania AI website, its research and documentation pages, institutional enquiry interfaces, and any features expressly made available under these Terms. Exania AI is presented as an artificial intelligence initiative of Exohood Labs Inc. (“Exania”, “we”, “us”). Accessing publicly available content is permitted subject to applicable law and these Terms.

A proposal, demonstration, model catalogue or description of an architecture is not a binding offer of production services. A separate signed agreement is required where a party intends to procure, evaluate, deploy or integrate a model, dedicated environment, private infrastructure or professional service.

CLAUSE 02 / 27FOUNDATION

Order of precedence

Where an authorised customer signs a Master Services Agreement, Statement of Work, enterprise licence, evaluation agreement, data processing agreement, service schedule, security addendum or public-sector procurement contract, that document governs its stated subject matter and prevails over conflicting provisions of these general website Terms.

If multiple signed documents apply, their express order-of-precedence provisions control. These Terms do not override mandatory law, an applicable data protection agreement or a government body's lawful procurement conditions. A confidentiality agreement applies to information within its stated scope.

CLAUSE 03 / 27FOUNDATION

Eligible users and authority

Use the website only where you have legal capacity to do so. If acting for a government agency, public body, business, university, research centre or other organisation, you represent that you are authorised to communicate on its behalf. You must not imply that a preliminary conversation is official approval, government endorsement or a binding purchase order.

Certain deployments may require contractual eligibility checks, sanctioned-party screening, security due diligence, export-control analysis or verification of the organisation's authority and permitted use. We may decline an engagement where lawful requirements or unacceptable risks prevent it.

CLAUSE 04 / 27FOUNDATION

Definitions

“Model” means an AI or machine-learning system, including its weights, interfaces, fine-tuning or associated components where applicable. “Input” is material provided to a system; “Output” is material returned by that system. “Customer Data” refers to information supplied or controlled by a customer under an applicable contract.

“Enterprise Services” means privately contracted development, evaluation, hosting, inference, integration, support or research services. “Documentation” means applicable product-specific written descriptions and instructions. “Authorised User” is an individual granted access by a contracting organisation or by us.

CLAUSE 05 / 27FOUNDATION

Research, roadmap and availability

Research notes, diagrams, model profiles, public demonstrations, case-study concepts and future capabilities explain a technical direction. They may change as engineering and regulatory assessments evolve. Unless a written agreement states otherwise, they do not guarantee a release, a security certification, specific performance, continuous availability or commercial suitability.

Access to a publication, concept demonstration or web page does not create a right to inspect model weights, private datasets, infrastructure configurations, internal methods, source code or restricted research materials.

CLAUSE 06 / 27USE & ACCESS

Website access and limited licence

We grant visitors a limited, revocable, non-exclusive and non-transferable permission to access the public website for legitimate informational, research and business-enquiry purposes. This permission does not transfer ownership of trademarks, original content, platform architecture, internal models or confidential information.

Material marked with a separate licence, including third-party and open-source components, remains subject to its relevant terms and mandatory legal exceptions. No broad licence to reproduce, resell, extract or train unrelated models on protected Exania content arises from viewing the site.

CLAUSE 07 / 27USE & ACCESS

Accounts, credentials and access controls

If we provide an invitation, evaluation account, API key, organisational workspace or remote environment, it may only be used by the authorised people and within the authorised scope. Keep secrets, tokens and credentials confidential; use reasonable device safeguards; promptly notify the designated security contact if compromise or inappropriate access is suspected.

Do not share accounts with unauthorised users, defeat identity checks, circumvent rate limits, bypass geographical controls, or connect unapproved automated agents. Administrator privileges, audit retention, logging, network allowlists and access expiry are governed by the applicable deployment specification.

CLAUSE 08 / 27USE & ACCESS

Prohibited conduct

Do not use Exania systems or website features to conduct unlawful activities, deliver malware, cause denial of service, obtain unauthorised access, exfiltrate secrets, impersonate institutions, submit fraudulent or infringing material, defeat safeguards or compromise the rights and safety of others.

Without written permission, you must not scrape protected data, extract or replicate private models, bypass safety policies, automate mass submissions, attempt to steal prompts or weights, reverse engineer protected services contrary to applicable rights, or use a service in violation of sanctions and export controls.

CLAUSE 09 / 27USE & ACCESS

Security research and vulnerability disclosure

No public website access grants permission to run scanning, exploitation, load testing, adversarial evaluation or red-team activities against production infrastructure. Security research requiring access must be authorised in writing and limited to the agreed targets, techniques, dates and reporting procedures.

If you believe you have found a vulnerability, stop before accessing third-party information or disrupting systems and use the institutional contact channel to request a secure reporting route. We do not promise a bounty or safe-harbour arrangement unless a separate published or signed programme expressly provides one.

CLAUSE 10 / 27USE & ACCESS

Institutional enquiries and submissions

When you contact Exania, submit accurate professional information and a relevant description of your organisation's needs. Enquiries are preliminary and may be screened for abuse prevention or operational routing. A submitted form is not a service acceptance, confidentiality agreement, purchase order or procurement award.

Do not put classified data, restricted intelligence, patient records, financial secrets, credentials, trade secrets or third-party personal information into a public contact form. Arrange an appropriate confidential channel and written safeguards before transferring sensitive project materials. How enquiry data is handled is further explained in the Privacy Policy.

CLAUSE 11 / 27INTELLIGENCE & OVERSIGHT

Model development and evaluation

A model's architecture, training process, evaluation dataset, operational setting, permitted uses, performance criteria and acceptance tests must be defined for the relevant project. A demonstration, benchmark, marketing description or research result cannot substitute for project-specific validation in the customer's intended conditions.

Evaluation and production use may be subject to different controls. Customers should verify documentation, limitations, provenance and applicability before promoting a research prototype to a critical workload or treating a limited test as an operational authorisation.

CLAUSE 12 / 27INTELLIGENCE & OVERSIGHT

Outputs, accuracy and model limitations

AI outputs may be probabilistic, incomplete, outdated, inaccurate or biased. Responses, classifications, rankings, translations, generated code and analytical recommendations can fail even when presented confidently. No publicly displayed example constitutes a warranty that a model will perform identically under other data, language, domain or infrastructure conditions.

Users must test and independently verify outputs before relying on them. The applicable contract may define quality thresholds, test procedures, warranties or remediation obligations; these are not established through public website content alone.

CLAUSE 13 / 27INTELLIGENCE & OVERSIGHT

Human oversight and consequential decisions

AI assistance must be subject to oversight proportionate to the intended risk. A customer deploying a system in public administration, healthcare, law enforcement, employment, credit, critical infrastructure, education or another sensitive context is responsible for ensuring appropriate human review, legal authorisation, documentation and impact assessment within its role.

An AI-generated result should not be the sole basis for a decision materially affecting a person's rights, safety, liberty, livelihood or access to essential services unless the relevant legal framework expressly permits the use and all applicable safeguards are implemented. Obligations assigned to providers and deployers by law remain unaffected.

CLAUSE 14 / 27INTELLIGENCE & OVERSIGHT

Restricted uses and high-risk applications

Exania technology must not be deployed for prohibited or otherwise unlawful AI practices, discriminatory profiling, unlawful surveillance, deceptive manipulation, unauthorised biometric use or infringement of fundamental rights. Additional approvals, conformity processes or restrictions may apply where a jurisdiction classifies a proposed system or use as high-risk or otherwise regulated.

The customer and Exania must establish which party is the provider, deployer, importer, distributor or other regulated actor for the specific system, where legally relevant. No page on this website should be understood as stating that any particular model is approved for regulated use.

CLAUSE 15 / 27INTELLIGENCE & OVERSIGHT

Public-sector and critical environments

Government, defence-adjacent and critical-sector projects may involve security clearances, data residency, sovereign controls, records requirements, procurement law, freedom-of-information duties, public accountability or special incident protocols. These requirements are assessed on a project-by-project basis and documented in signed terms and deployment design.

The website itself is not an authorised channel for classified material, protected government systems or operational intelligence. Nothing here constitutes a public-sector framework agreement, accredited hosting offer or blanket security clearance.

CLAUSE 16 / 27DATA & INFRASTRUCTURE

Customer inputs, provenance and lawful rights

An organisation submitting data to an authorised environment must have the rights, approvals and legal bases needed to supply and process it. Customers are responsible for lawful sourcing, applicable notices, data quality and use limitations within their control. Exania's obligations concerning received data depend on its contractual role and the relevant law.

Customer information is not made public by these Terms, and these public Terms alone do not authorise Exania to use confidential Customer Data to train general models. Any permitted training, evaluation reuse or fine-tuning must be addressed in a separate written agreement and, where applicable, lawful data processing instructions.

CLAUSE 17 / 27DATA & INFRASTRUCTURE

Inputs, outputs and intellectual property

Customer ownership of pre-existing Inputs and other protected materials is not transferred merely by providing them under an authorised contract. Rights in a model, its weights, pre-existing tools, proprietary methods, custom developments, fine-tuned components and Outputs must be expressly allocated by the applicable agreement and relevant intellectual property law.

AI-generated materials may not qualify for protection in every jurisdiction and may resemble material produced for others. Customers should review outputs for legality, originality, third-party rights and suitability. Except where a signed contract expressly grants it, these website Terms do not convey a licence to Exania model weights or source code.

CLAUSE 18 / 27DATA & INFRASTRUCTURE

Fine-tuning, training and feedback

Fine-tuning datasets, retrieval corpora, evaluation results, prompts, interaction logs and feedback can have different sensitivity and ownership characteristics. A specific project should identify permitted processing purposes, retention, deletion, segregation and whether any material may contribute to model development.

Feedback volunteered about public website usability may be used to improve the site, subject to privacy law and any confidentiality restriction. It must not be assumed that the submission of feedback grants rights over confidential datasets, protected source material or private customer records.

CLAUSE 19 / 27DATA & INFRASTRUCTURE

Security, confidentiality and controlled access

Restricted designs, security information, confidential documents, non-public models, customer datasets and protected infrastructure details must be exchanged only under agreed safeguards. Where applicable, parties should establish encryption, personnel access, authentication, segregation, monitoring, incident communication and confidentiality commitments in the signed contract.

No website text alone constitutes a promise of a named certification, security clearance, dedicated hardware, recovery time or independent audit. Such commitments require documentary verification and agreed contractual terms.

CLAUSE 20 / 27DATA & INFRASTRUCTURE

Cloud and computing services: EXO POWER

EXO POWER COMPUTING SERVICES LTD may provide cloud, computing or related infrastructure functions for an agreed Exania engagement, depending on the contracting structure and documented technical scope. Its inclusion in this policy does not mean every Exania workload runs on its infrastructure or that it acts as a data controller for all customer information.

The applicable contract and data processing terms must identify the operating entity or entities, controller and processor roles, authorised subcontracting, infrastructure locations, cross-border transfers, access controls, incident duties and deletion or return of data at termination. Company names and operational roles must not be treated as interchangeable.

CLAUSE 21 / 27DATA & INFRASTRUCTURE

Privacy and international transfers

Personal data connected with the public website and enquiries is described in the Exania Privacy Policy. For enterprise deployments, any roles as controller, processor or sub-processor, processing instructions, international transfer mechanisms and data-subject assistance must be addressed through the applicable data protection documentation.

Information may not be transferred or made available across borders simply because the platform supports remote computing. Location, customer authorisation, legal restrictions and technical feasibility are assessed for each deployment. Rights and obligations that cannot lawfully be waived remain in effect.

CLAUSE 22 / 27DATA & INFRASTRUCTURE

Third-party tools and dependencies

External model components, cloud infrastructure, networking, datasets, identity services, communications systems or developer tools may be involved where permitted for a specific engagement. Third-party licences and conditions can apply. The agreed supplier list and subcontracting rules govern contracted customer environments.

Links from the public site are provided for convenience and do not imply ownership, control or endorsement of independently operated resources. No unidentified third party is authorised by these Terms alone to receive confidential customer data.

CLAUSE 23 / 27COMMERCIAL & LEGAL

Commercial engagements and procurement

Quotes, pricing, capacity reservations, statements of work and public-sector procurement responses require written agreement on scope, operator, deliverables, price, currency, taxes, licence metrics, milestones, personnel, support and any acceptance criteria. Public website content is not a binding quotation or obligation to allocate infrastructure.

Any subscription, dedicated-compute fee, model-development fee, renewals, refund rights, payment schedule, purchase-order terms or procurement conditions must be established in the signed commercial documents and remain subject to mandatory law.

CLAUSE 24 / 27COMMERCIAL & LEGAL

Service levels, changes and incidents

Maintenance windows, change management, incident classification, security reporting, disaster recovery, uptime, latency, support hours and escalation rules depend on the ordered service and its written service-level and security schedules. Public availability of the Exania site does not guarantee continuous availability of a private AI environment.

We may modify public informational pages and non-contractual demonstrations for engineering, security or legal reasons. We will follow any notice, approval, continuity or transition obligations expressly agreed for enterprise services or required by law.

CLAUSE 25 / 27COMMERCIAL & LEGAL

Suspension, termination and exit

We may restrict public website functionality where reasonably necessary to prevent abuse, respond to a credible security concern or meet a legal obligation. Enterprise suspension and termination rights, cure periods, continued access, dispute procedures and transition assistance are governed by the written engagement.

Return or deletion of customer materials, preservation obligations, log retention, model artefacts, export formats and decommissioning procedures must be specified in contract and applicable data processing terms. We do not assert a general right to keep customer data indefinitely after termination.

CLAUSE 26 / 27COMMERCIAL & LEGAL

Warranties, allocation of risk and liability

We aim to keep public information accurate and exercise reasonable care, but uncontracted demonstrations and general descriptions may be incomplete or unsuitable for a particular application. Any binding performance assurance, remedial obligation or allocation of financial risk for paid services must be stated in the relevant contract.

Nothing in these Terms excludes liability for fraud, fraudulent misrepresentation, death or personal injury caused by negligence, or any other responsibility that cannot lawfully be excluded. Any agreed exclusions, liability limits or indemnity arrangements must comply with applicable law and the parties' signed commercial terms.

CLAUSE 27 / 27COMMERCIAL & LEGAL

Changes, disputes and contact

We may update these general website Terms prospectively and display the revised date on this page. Material changes to paid services, where they require notice or consent, follow the relevant contract and mandatory law. If a provision is unenforceable, the remainder should continue to the extent legally permissible.

Governing law and dispute forum for an enterprise engagement are stated in its signed documents. For matters relating only to the public site, applicable jurisdiction and non-waivable rights determine the competent forum. For terms or procurement enquiries, use Contact Exania. For personal data questions, email privacy@exania.ai.

04 / OPERATING ENTITIESCLARITY IN ACCOUNTABILITY
EXANIA / ENTERPRISE INFRASTRUCTURE

The right entity.
The right obligation.

Corporate ownership, cloud service delivery and customer data responsibilities are related, but they are not interchangeable.

01 / CORPORATE INITIATIVE

EXOHOOD LABS INC.

Exania is presented as an AI initiative of Exohood Labs Inc. The legal entity responsible for each contracted service is identified in the applicable agreement.

EXANIA / CORPORATE
02 / COMPUTING INFRASTRUCTURE

EXO POWER
COMPUTING SERVICES LTD

EXO POWER may deliver agreed cloud or computing functions. Hosting locations, data roles, service levels and controls must be set out in the relevant contract.

CLOUD / CONTRACT DEFINED
05 / CONTACT & NEXT STEPS

Build with
clear terms.

Every institutional engagement begins with a defined purpose, an accountable operator and the right safeguards for the intended environment.

Discuss an engagement
EXANIAPRIVACY / YOUR CHOICE CONSENT CONTROL

Privacy on your terms.

We use optional analytics to improve this website and optional marketing technology for communications. None of these trackers runs until you consent. Privacy policy.