Skip to content

Legal And Safety

Last updated: 2026-06-28

Legal and safety pages explain the rules that govern Cortensor services, data handling, token-related risk, restricted addresses, and user responsibility. They are written for operators, developers, token holders, partners, and users who need to understand the legal posture before using a product surface, node role, API, dashboard, or token-related workflow.

Terms of Use service rules

Access, accounts, professional-use framing, fees, token risk, prohibited use, third-party services, liability, termination, and disputes.

Privacy Policy data handling

Personal data, wallet activity, website analytics, Portal and gateway metadata, router payloads, off-chain storage, retention, cookies, and user rights.

Disclaimer risk posture

Experimental software risk, token risk, user responsibility, restricted-address authority, liability limits, and no-fiduciary-duty language.

Restricted addresses safety controls

Addresses tied to launch sniping, scams, stolen funds, malicious behavior, or other network-integrity risks.

Read First

Start with the Terms of Use if you are using Cortensor services, running infrastructure, building on the API, or interacting with token-related surfaces. Read the Privacy Policy before submitting personal data, account data, API traffic, prompts, outputs, wallet information, or off-chain payloads. Read the safety pages before OTC activity, staking, rewards, or any workflow that depends on wallet eligibility.

Pages

  • Terms Of Use covers service access, eligibility, accounts, fees, token usage, token migration, prohibited use, third-party providers, liability, termination, and disputes.
  • Privacy Policy covers what data may be collected, why it is used, how it may be shared, how blockchain data behaves, and what rights users may have.
  • Disclaimer And Legal Safety summarizes the binding disclaimer, experimental-platform risk, token-risk posture, restricted-address authority, and user responsibility.
  • Safety And Restricted Addresses explains restricted-address categories and lists the published addresses with explorer links.
flowchart LR
  Website["Website<br/>analytics, forms, cookies"]
  Portal["Portal<br/>account, API keys, billing"]
  Gateway["Gateway<br/>auth, quota, usage"]
  Router["Router<br/>payloads, sessions, logs"]
  Chain["Blockchain<br/>wallets, transactions"]
  Legal["Legal pages<br/>terms, privacy, safety"]

  Website --> Legal
  Portal --> Legal
  Gateway --> Legal
  Router --> Legal
  Chain --> Legal

Product Touchpoints

Area Legal and safety concern
Public website Analytics, cookies, contact forms, email capture, and policy updates.
Portal Account profile, organization data, API keys, billing data, usage records, and support requests.
API gateway Key verification, usage metering, rate limits, payment flows, request metadata, and abuse controls.
Router API Prompts, outputs, session IDs, route metadata, encrypted payloads, off-chain URNs, and timeout/error records.
Dashboard Wallets, contract reads/writes, node metadata, staking/admin actions, and public-chain state.
Token and staking Token migration, allocation, staking, rewards, restrictions, no-advice language, and wallet eligibility.
Restricted addresses Network integrity, scams, launch sniping, stolen funds, OTC checks, and enforcement consistency.