Legal and Company Centre

Fenrua Labs Pty Ltd may enter into service subscriptions and client-specific business agreements, issue invoices, receive payment, and carry out the research, development, software, infrastructure, hosting, integration, support, and related technology activities covered by those arrangements.

Browsing this public website does not itself form a paid service agreement. The service description, price, scope, and terms presented or agreed for a particular service govern that service.

Current website state: public company information, technical documentation, evidence records, service discovery, and bounded read-only observation functions. Fenrua Labs may separately contract, invoice, receive payment, and deliver services through ordinary business arrangements.

Fenrua Labs Pty Ltd may receive payment for its lawful business activities through the commercial method agreed for the relevant service. The current public website is an information, evidence, and service-discovery surface and does not presently provide self-service account creation or checkout.

A payment settles the price of the relevant service. It does not by itself give a customer equity, ownership, profit-sharing, investment returns, token allocation, or rights outside the applicable service terms or client agreement.

Fenrua BlackBox Protocol is Fenrua's privacy-preserving protocol-infrastructure direction for verifiable AI automation. Its bounded business and technical scope includes research, development, software, infrastructure access, hosting, integration, technical support, evidence-aware workflows, and related technology services. Fenrua AI is a public development direction for controlled model systems; it does not make a model, API, application, encrypted vault, or compute-unit programme publicly available.

Identity, authority, integrity, policy, verification, containment, recovery, secret handling, and vulnerability reporting remain important technical functions where relevant. They are not the complete definition of Fenrua Labs' business or future direction.

Each public evidence record is limited to its named artifacts, revisions, timestamps, hashes, validation steps, maturity, and stated limitations.

Periodic synchronization validates published records and internal bindings; it does not rerun the underlying research and validation work or attest live services, protected systems, private client environments, signing keys, private gateways, validators, private meshes, or operational controls beyond the record's stated scope.

Public records are for technical review, verification, evidence inspection, and professional due diligence. They do not expose private infrastructure, protected operational wiring, credentials, provider routes, or confidential execution context.

Any private-chain observation is bounded infrastructure evidence. It is not a public-mainnet deployment claim or proof of protected runtime safety.

The public observation endpoints derive a short-lived, per-instance salted abuse-control identifier from request network metadata. The application code does not retain or log the raw network address for that purpose.

Business email, private vulnerability reporting, and external provider logs are separate operational channels. Their public descriptions must reflect verified current handling rather than hypothetical future systems.

Business and collaboration enquiries: partnerships@fenrua.ai.

Do not send private keys, credentials, witness material, client-confidential data, or unredacted vulnerability details through public channels.

This centre records company identity and the current public operating scope. It does not amend any service terms, privacy notice, or client-specific agreement that applies in its own context.