Rules for using this site

Terms of Use (this site)

These terms govern use of the C0/C1/C2 site that delivers computation evidence as Evidence Packs. Transaction terms are finalized by individual contract, which prevails over these terms.

Version: TOS-v1.2 / Effective: 2026-04-23

This page

This page summarizes the rules and prohibited acts for using this site. It tells you the baseline conditions for using the site, demos, and forms.

How this differs

Transaction information covers what can be disclosed before contract, and Privacy covers personal-data handling. This page covers the rules for using the site itself.

What to see next

Go to Transaction information for pre-contract conditions, Privacy for data handling, or Paths if you are deciding how to proceed.

1. Definitions

"We" / "us" means the business entity that operates this site and service, and that appears as the contracting party in individual contract documents, invoices, purchase orders, or equivalent instruments. Business name, address, billing entity, and other required disclosures are provided in writing after eligibility review or at the time of contract draft presentation, as set out in the Transaction Information page.

"C0" means a framework that accepts existing data and calculation conditions, fixes a single-point computation result as an Evidence Pack, and returns it without disclosing internal methods (formulas/implementation).

"C1" means a framework that fixes continuous data, observation logs, time series, or other inputs into an event sequence or threshold events usable for evaluation, explanation, and audit, and returns them as an Evidence Pack.

"C2" means a framework that verifies results across multiple conditions, systems, candidates, or data sources using a consistent judgment protocol, and returns consistency/inconsistency or comparison results fixed as an Evidence Pack.

"Evidence Pack" means a verification JSON containing integrity-checking information (digests/hashes, etc.) required for acceptance. It does not constitute an electronic signature, legal notarization, or guarantee of truth.

"Central ledger verification operations" means operations in which we use verification records or ledger information we maintain to check consistency of Evidence Pack references, verification hashes, integrity values, and similar items. It does not automatically include an external ledger, third-party anchor, or public blockchain.

"Confidential Information" means technical, operational, or business information, designs, actual data, credentials, restricted URLs, deliverables, or other information that either party discloses in connection with consultation, eligibility review, demos, transaction negotiation, individual contracts, delivery, or other service-related activities, and that should reasonably be treated as confidential. Excluded are: information that is publicly known; information lawfully held by the recipient at the time of disclosure; information that becomes publicly known after disclosure through no fault of the recipient; and information required to be disclosed by law or regulation.

"Individual Contract" means any SOW, purchase order, invoice, accepted quotation, NDA, individual terms sheet, or other written or electronic agreement between us and the user that sets out the conditions of the service.

2. Scope

This site provides C0 / C1 / C2 descriptions, fixed demos, eligibility review, and intake (Plan 1 / Plan 2 / Plan 3 / inquiries), and related documents. Actual delivery content, return scope, retention policy, use restrictions, acceptance criteria, acceptance procedures, pricing, delivery timing, and other conditions are finalized by individual contract.

Descriptions, demos, public examples, or published pricing on this site do not guarantee that we will accept, execute, or deliver for all themes, jurisdictions, use cases, or inputs.

3. No warranties

Deliverables are intended as verifiable records of computation results (Evidence Pack) and do not guarantee business adoption or specific outcomes.

Design measures such as reducing reverse-engineering/estimation risk, digest-only output, quantization, and relativization are design goals for defense, load control, and exposure suppression, and do not guarantee impossibility of reverse-engineering or inference.

The value of this service lies not in formula secrecy or technical irreproducibility per se, but in the Evidence Pack issued by us and the verification procedures and central ledger verification operations we maintain.

4. Prohibited acts

  • Inference of internal methods via reverse computation using outputs/APIs/demos, or extraction via repeated queries / systematic exploration (parameter sweeps, etc.) (model extraction)
  • Scraping/automated collection, bypassing technical limitations, or unauthorized access
  • Spamming forms/APIs, vulnerability probing, or service disruption
  • Use for illegal or public‑policy‑violating purposes
  • Sending designs, actual data, credentials, restricted URLs, sensitive specifications, or other confidential information before NDA or equivalent agreement is in place
  • Redistributing confidential information or deliverables to third parties without permission (unless allowed by individual contract)

5. Transactions (acceptance)

Transactions are primarily B2B; acceptance criteria, return scope, retention policy, use restrictions, acceptance procedures, liability limits, etc. are fixed by individual contract.

For the public scope of transaction terms (pricing guides, delivery timing, etc.), see Transaction information (public scope).

Deliverables are an Evidence Pack set; definitions such as delivery upon presentation (access‑controlled/expiring URL, etc.) are fixed by individual contract.

Unless otherwise specified in an individual contract, the currently operational standard acceptance procedure is to verify opaque_ref (public reference) + evidenceHash (acceptance digest) as the primary verification pair via the audit API (/api/scu/audit), confirm pack integrity with pack_sha256 (Evidence Pack integrity value) as needed, and confirm status=MATCH (verification match). MISMATCH (needs review, including not-yet-anchored or inconsistent results) in public or simplified verification does not immediately confirm tampering; it may include not-yet-anchored, reference mismatch, input differences, environment differences, or other circumstances. Final acceptance judgment follows the acceptance procedure set out in the individual contract.

6. IP / confidentiality

Copyright, know-how, trade secrets, and other rights related to this site and service belong to us or legitimate rights holders. Rights do not transfer unless explicitly transferred by individual contract.

Indemnification for third-party claims alleging that a deliverable infringes third-party intellectual property rights is limited to the scope expressly set out in an individual contract. Unless otherwise agreed, our indemnification obligation is limited to third-party claims arising from the deliverable we created itself, and excludes claims arising from user-provided data, user instructions, user modifications, combinations/distribution not approved by us, or use outside the agreed purpose. Any indemnification cap follows the liability limits in these terms.

Prior to NDA or equivalent agreement, users shall send only public-information-level summaries and shall not send confidential information. We will use information received at the pre-NDA stage only for eligibility review, safeguard assessment, initial communication, and determining whether an individual contract is required.

Unless otherwise agreed by individual contract or NDA, neither party shall use or disclose the other party's confidential information beyond what is necessary for considering, negotiating, executing, delivering, accepting, complying with law, or obtaining professional advice in connection with this service.

We may withhold disclosure of detailed information before an NDA or individual contract is executed, as necessary.

7. Personal data

Personal data handling follows Privacy Policy .

For matters involving personal data subject to the EU GDPR or UK data protection laws, we and the user will set out a Data Processing Agreement (DPA) or other data-processing terms in the individual contract where required. Where a DPA or equivalent terms are required, the relevant personal data must not be sent until those terms are fixed.

8. Disclaimers / liability limits

We take reasonable security measures but do not guarantee perfect confidentiality, perfect security, perfect availability, or acceptance by any third party.

Unless otherwise agreed by individual contract, liability is capped at the consideration actually received by us for the relevant transaction. 'Relevant transaction' means, in principle, one transaction unit identified as a whole by a single individual contract, purchase order, invoice, or equivalent instrument. Where multiple individual contracts, purchase orders, or invoice units exist, each is treated independently.

However, unless otherwise specified by individual contract or mandatory law, the above cap does not automatically apply to the following liabilities to the extent permitted by applicable law.

  • Damage caused by our intentional misconduct or gross negligence
  • Death or bodily injury to a third party
  • Compensation to affected individuals for personal-data leakage where required by applicable law
  • Third-party intellectual-property claims to the extent expressly covered by these terms or an individual contract

9. Changes to terms

We may update these terms as needed. Material changes will be notified via announcement on this site, notice to registered contacts, or other reasonable equivalent means. Where a separate effective date is specified for a change, the change takes effect from that date.

Registered contacts are contact points specified by the user in an individual contract, purchase order, inquiry form, or equivalent record. For material changes, we will endeavor to give 30 days' prior notice where operationally practicable.

Existing individual contracts follow the version in effect when that contract was executed. Revisions to these terms generally apply to new or renewed transactions on or after the effective date. If a user does not agree to a material change, the user may stop new use or renewed transactions after the effective date. Ongoing individual contracts remain governed by their own terms.

10. Governing law & jurisdiction

For domestic B2B transactions, the default governing law for these terms is Japanese law, and the Tokyo District Court has exclusive jurisdiction as the court of first instance for disputes.

For cross-border B2B transactions, depending on the user's location, jurisdiction, contract language, regulatory requirements, or nature of the case, the governing law, jurisdiction, place of arbitration, contract language, and other dispute-resolution conditions may be separately specified in an individual contract, in which case the individual contract prevails. JCAA, SIAC, HKIAC, ICC, or another neutral arbitral institution/place of arbitration may be selected by individual contract where needed.

11. Language priority

Non-Japanese pages on this site are reference translations. If there is a conflict or interpretation gap between language versions, the Japanese version prevails. If an individual contract separately specifies the contract language, that individual contract controls.

12. Force majeure

We are not liable to the extent delay or non-performance is caused by events beyond our reasonable control, including natural disasters, war, terrorism, labor disputes, cyberattacks, cloud/communications/power or other external infrastructure failures, laws or governmental measures, epidemics, transportation disruption, or similar events. In such cases, we will provide reasonable notice and endeavor to mitigate the impact. Payment obligations for completed work or incurred costs are not automatically waived unless otherwise agreed by individual contract.

13. Severability / survival

If any part of these terms is found invalid, unlawful, or unenforceable, the remaining provisions remain effective. The affected part will be interpreted or replaced, to the extent possible, by a valid provision closest to the original purpose.

Provisions that by their nature should survive termination, including confidentiality, intellectual property, payment, liability limits, governing law/dispute resolution, language priority, and provisions on acceptance records and retention, survive to the extent necessary.

14. Sanctions / export control

The user must comply with Japan's Foreign Exchange and Foreign Trade Act, U.S. OFAC sanctions, EU/UK financial sanctions, the EU Dual-Use Regulation, the U.S. EAR, and other applicable sanctions and export-control laws. We do not accept applications, contracts, billing, delivery, or acceptance for transactions involving sanctioned countries/regions, sanctioned persons, or transactions that may conflict with applicable sanctions or export-control laws.

15. Assignment

In connection with a business transfer, company split, merger, or other reorganization, we may assign our position, rights and obligations, contract records, acceptance-response duties, and retention operations under these terms or an individual contract to a successor. Such assignment means succession of retention, acceptance-response, and contract operations for already issued Evidence Packs, and does not automatically change whether or how new Evidence Packs may be issued.

The user may not assign, transfer, pledge, or sublicense its position, rights, or obligations under these terms or an individual contract to a third party without our prior written consent.

16. SLA

Unless expressly stated in an individual contract, no Service Level Agreement (SLA), including availability, response time, support hours, recovery time, or service credits, is provided for this site or service. If required, SLA terms are set out per matter in an individual contract.

These terms describe public information scope; individual conditions (scope, deliverables, acceptance, consideration, etc.) are finalized in contract documents.