AXNS logo AXNS
Legal Framework

AXNS Legal Policies

These policies describe the rules for using AXNS websites and interfaces, how personal information is handled, the role and limitations of advisory DAO governance, and the responsibilities of users interacting with blockchain-based systems.

Community-led AXNS uses advisory DAO governance for community proposals and directional voting.
Non-custodial approach Users remain responsible for wallets, private keys, transaction approvals and device security.
Contact Policy and support enquiries: [email protected]

Terms of Use

Effective: 29 July 2026

1. Acceptance and scope

By accessing or using the AXNS website, documentation, community pages, dashboards, decentralised application interfaces, software components, developer resources or related online services (collectively, the “Services”), you acknowledge that you have read and agree to these Terms of Use. If you do not agree, you must not access or use the Services.

These Terms apply to public-facing AXNS interfaces and informational resources. Separate products, smart-contract deployments, token distributions, staking arrangements, governance modules, bridges, wallets, exchanges or third-party integrations may require additional product-specific terms. Where product-specific terms conflict with these general Terms, the product-specific terms will govern for that product.

2. Nature of AXNS and the Services

AXNS is presented as a community-led decentralised technology initiative. It may rely on public blockchain networks, distributed software, smart contracts, independent infrastructure providers, community contributors, multisignature signers, timelock mechanisms and third-party interfaces.

No statement on the website should be interpreted as a representation that a single incorporated company owns or controls every part of the protocol. Public blockchain components may continue operating independently of the website, particular contributors or interface maintainers. Availability of an interface does not mean that every underlying network, contract or third-party service is controlled, endorsed or guaranteed by AXNS contributors.

3. AXNS token and protocol utility

The AXNS token is intended to support protocol-related utility, participation and governance functions that may be introduced or modified over time. Unless expressly stated in separate legally reviewed documentation, possession of AXNS does not by itself provide equity, shares, debt rights, ownership of an incorporated entity, voting rights in a company, a bank deposit, a claim against a treasury, a right to dividends, a guaranteed yield, a guaranteed redemption price or a promise of future appreciation.

Utility features may be unavailable, delayed, changed, restricted or discontinued because of technical, legal, security, governance, liquidity or market conditions. References to planned features, roadmaps or future integrations are statements of present intention and are not binding commitments.

4. Eligibility

  • You must be at least 18 years old and legally capable of entering into these Terms.
  • You must not be located in, ordinarily resident in, or accessing the Services from a jurisdiction where such access is prohibited.
  • You are responsible for determining whether your use of the Services is lawful in your jurisdiction.
  • You must not use the Services on behalf of a sanctioned person, prohibited organisation or unlawful enterprise.
  • Additional eligibility, verification or geographic restrictions may apply to particular products or interfaces.

5. Non-custodial wallets and account responsibility

Unless expressly stated otherwise, AXNS interfaces are intended to operate on a non-custodial basis. You retain control of your wallet and remain solely responsible for private keys, seed phrases, passwords, authentication methods, devices and transaction approvals.

  • Never disclose a seed phrase or private key to any person claiming to represent AXNS.
  • Verify website domains, smart-contract addresses, token addresses and transaction details before signing.
  • Use secure devices, updated software and appropriate wallet-security practices.
  • Understand that public blockchain transactions are generally irreversible.
  • Incorrect addresses, unsupported networks, malicious approvals or compromised devices may cause permanent loss.

6. Transaction execution

Blockchain transactions are submitted to independent networks. AXNS contributors do not guarantee that a transaction will be accepted, confirmed, completed within any period, executed at a displayed price or reversed after submission. Network congestion, validator behaviour, gas fees, slippage, miner or validator extractable value, front-running, reorganisation, chain interruption or third-party failures may affect execution.

7. Fees

You may incur blockchain gas fees, protocol fees, liquidity-provider fees, bridge fees, exchange fees, wallet fees, taxes or third-party charges. Displayed estimates may differ from final amounts. You are responsible for reviewing and accepting all applicable fees before approving a transaction.

8. No professional advice

Website content is provided for general informational and educational purposes. It is not personalised financial, investment, legal, accounting, regulatory, cybersecurity or tax advice. You should obtain advice from qualified professionals and independently assess technical documentation, smart contracts, applicable law and your ability to bear loss.

9. No warranties

To the maximum extent permitted by applicable law, the Services are provided “as is” and “as available”, without warranties of any kind. No warranty is made regarding availability, accuracy, completeness, reliability, security, merchantability, fitness for purpose, non-infringement, compatibility, future development, token value, liquidity, governance results, rewards, transaction execution or uninterrupted operation.

10. Limitation of liability

To the maximum extent permitted by law, AXNS contributors, community participants, developers, maintainers, delegates, multisignature signers, service providers and governance participants will not be liable for indirect, incidental, special, consequential, exemplary or punitive loss, loss of profits, loss of opportunity, loss of data, loss of digital assets, loss arising from wallet compromise, or loss caused by reliance on website content.

Nothing in these Terms excludes liability that cannot lawfully be excluded. Different jurisdictions may provide mandatory consumer rights that remain unaffected.

11. Indemnity

To the extent permitted by law, you agree to indemnify and hold harmless AXNS contributors and maintainers from claims, losses and reasonable costs arising from your unlawful use of the Services, infringement of third-party rights, breach of these Terms or misuse of smart contracts and interfaces.

12. Suspension and restriction

Access to centralised website features, hosted interfaces or community resources may be restricted, suspended or discontinued for security, maintenance, legal, regulatory, sanctions, abuse-prevention or technical reasons. Restriction of a hosted interface may not stop independent public blockchain contracts from operating.

13. Taxes

You are solely responsible for identifying, reporting and paying taxes, duties or assessments arising from your transactions, rewards, transfers, disposals, governance activity or use of digital assets.

Privacy Policy

Effective: 29 July 2026

1. Who this policy applies to

This Privacy Policy applies to people who visit AXNS websites, submit enquiries, join mailing or community forms operated through the website, interact with hosted interfaces, report security issues, or otherwise provide personal information through AXNS-managed channels.

2. Responsible contact

AXNS is presently described as a community-led decentralised initiative rather than a separately incorporated operating company. For privacy and website-support enquiries, the designated contact is [email protected]. Where a separate service provider acts as an independent controller or processor, its own privacy notice may also apply.

3. Information we may collect

Information you provide

  • Name, display name, email address and contact details.
  • Support enquiries, feedback, proposal submissions and correspondence.
  • Information submitted through forms, community applications or security reports.
  • Wallet address or transaction hash when you voluntarily provide it for support.

Technical and usage information

  • IP address, browser type, device type, operating system and approximate region.
  • Pages requested, timestamps, referring page, error logs and security events.
  • Cookie preferences and other essential website state.
  • Public wallet addresses, transaction hashes and on-chain events when an interface reads public blockchain data.

Public blockchain information

Public blockchain data is generally visible to anyone and may be permanently recorded. A wallet address may become personal data when linked to an identifiable person. AXNS cannot delete or alter information already written to an independent public blockchain.

4. How information may be used

  • Provide, secure, maintain and improve the website and hosted interfaces.
  • Respond to enquiries, support requests and security reports.
  • Detect fraud, phishing, abuse, attacks and unauthorised activity.
  • Maintain service logs, troubleshoot errors and preserve website integrity.
  • Communicate service updates, governance information or policy changes.
  • Comply with legal obligations, court orders and lawful regulatory requests.
  • Establish, exercise or defend legal claims.
  • Administer community proposals, consultations and advisory governance processes.

5. Lawful bases

Depending on the jurisdiction and context, processing may rely on consent, performance of a requested service, legitimate interests in operating and securing the website, compliance with legal obligations, or protection of legal rights. Where consent is relied upon, you may withdraw consent for future processing, subject to legal and technical limitations.

6. Sharing of information

Personal information may be shared only where reasonably necessary with:

  • Hosting, infrastructure, security, communications and technical-service providers.
  • Professional advisers, auditors or incident-response specialists.
  • Authorities where disclosure is legally required or reasonably necessary to protect rights and safety.
  • Successor maintainers or governance-approved service providers following a documented transition.

AXNS does not state that personal information is sold to advertisers. If advertising or behavioural analytics are introduced later, this policy and the cookie controls should be updated before implementation.

7. International transfers

Internet infrastructure and service providers may process information in multiple countries. Where required, reasonable contractual, organisational or legal safeguards should be used for restricted international transfers.

8. Data retention

Information is retained only for as long as reasonably required for the purpose collected, security, dispute resolution, legal compliance and recordkeeping. Support correspondence may be retained for a reasonable support-history period. Security logs may be retained long enough to investigate incidents and protect systems. Public blockchain data is not controlled by AXNS and may remain permanently available.

9. Data security

Reasonable administrative and technical safeguards may be used, but no internet transmission, hosting provider, wallet connection or storage system can be guaranteed completely secure. You should avoid sending seed phrases, private keys, passwords or unnecessary identity documents by email or support forms.

10. Your rights

Depending on applicable law, you may have rights to request access, correction, deletion, restriction, objection, portability, withdrawal of consent or information about processing. These rights may be limited by legal obligations, security requirements, the rights of others and the immutable nature of public blockchains.

To submit a request, contact [email protected]. Reasonable identity verification may be requested before acting on a request.

11. Children

The Services are not directed to children. AXNS does not knowingly seek personal information from people below the minimum legal age applicable in their jurisdiction. If you believe a child has provided personal information, contact support.

12. External platforms

Social networks, wallet providers, block explorers, GitBook, exchanges, bridges and other external services process information under their own terms and privacy notices. AXNS does not control their independent processing.

Cookie Policy

Effective: 29 July 2026

1. What cookies and similar technologies are

Cookies are small text files stored on a device. Similar technologies may include local storage, software development kits, pixels, tags, device identifiers and browser-storage mechanisms.

2. Essential technologies

The website may use technologies that are reasonably necessary for security, network routing, load balancing, fraud prevention, preference storage, accessibility, session continuity and remembering privacy choices. Blocking essential technologies may prevent parts of the website from functioning.

3. Analytics and optional technologies

If optional analytics, advertising, behavioural tracking or social-media pixels are introduced, the cookie notice and consent mechanism should be updated. Where applicable law requires consent, optional technologies should not be activated until valid consent is obtained.

4. Current cookie position

This policy is drafted for a primarily informational website. It does not represent that every hosting or content-delivery provider sets no technical cookies or logs. Infrastructure providers may process connection data and apply security technologies under their own documentation.

5. Managing preferences

You can control cookies using browser settings and any consent controls displayed on the website. Deleting cookies may remove saved preferences. Browser-level blocking may affect functionality.

6. Future changes

The cookie list should be reviewed whenever analytics, embedded media, support chat, advertising technology, wallet analytics or new third-party integrations are introduced.

Digital Asset and Protocol Risk Disclosure

Effective: 29 July 2026

This section forms part of the legal policies. It is not a prediction of every possible risk. Before interacting with digital assets or smart contracts, users should independently evaluate their knowledge, financial circumstances, technical security and applicable law.

1. Market and price risk

Digital-asset prices may be highly volatile and may decline rapidly. Historical performance, community growth, token supply mechanics, burns, staking features or roadmap statements do not guarantee future value, liquidity or demand.

2. Liquidity risk

Markets may have insufficient buyers, sellers or liquidity. Slippage may be substantial, and a user may be unable to enter or exit a position at an expected price.

3. Smart-contract risk

Smart contracts may contain coding errors, design weaknesses, economic exploits, permission issues, integration failures or unexpected behaviour. Audits and testing reduce some risks but do not eliminate them.

4. Blockchain and network risk

Networks may experience congestion, outages, forks, reorganisations, validator failures, governance disputes, fee spikes or changes to protocol rules. Third-party bridges and cross-chain systems create additional technical and security risks.

5. Wallet and cybersecurity risk

Phishing, malware, malicious approvals, fake applications, compromised devices, SIM swapping and loss of private keys may cause irreversible loss. Users are responsible for verifying domains and transaction details.

6. Governance risk

Advisory votes may be influenced by low participation, concentrated holdings, delegate conflicts, inaccurate information, voter apathy, coordination failures or manipulation. A proposal may be delayed, rejected, modified or not implemented after a vote.

7. Regulatory and legal risk

Laws and regulatory interpretations concerning tokens, decentralised protocols, financial promotions, staking, rewards, privacy, taxation and virtual-asset services vary by jurisdiction and may change. Features may be restricted, modified or discontinued in response.

8. Third-party dependency risk

Hosting providers, wallets, exchanges, liquidity venues, oracles, analytics tools, block explorers, bridges and communication platforms may fail, change terms, block access or suffer security incidents.

9. Tax risk

Token transfers, rewards, disposals and governance benefits may create tax obligations. Treatment differs by jurisdiction and may change.

10. Experimental technology

AXNS components may be experimental, under development or subject to change. Roadmap dates and planned features are not guarantees.

DAO Governance Notice

Effective: 29 July 2026

1. Governance model

AXNS is intended to use a community-led advisory governance model. Community proposals, discussions, polls, delegate feedback and token-based signals may guide protocol direction. Unless a proposal is executed through an approved technical or operational mechanism, an advisory vote is not automatically binding.

2. Purpose of advisory governance

  • Identify community priorities and ecosystem needs.
  • Provide transparent signals regarding proposed upgrades and initiatives.
  • Review treasury priorities, integrations, grants and community programmes.
  • Support progressive decentralisation while maintaining security safeguards.
  • Create public records of proposals, discussion and voting outcomes.

3. Proposal lifecycle

  1. Discussion: a concept may be presented to the community for feedback.
  2. Drafting: the proposal should describe objectives, implementation, costs, permissions, risks and measurable outcomes.
  3. Review: technical, security, treasury and legal implications may be evaluated.
  4. Advisory vote: eligible participants may provide a governance signal under published voting rules.
  5. Implementation decision: authorised mechanisms, multisignature signers, timelocks, developers or other approved executors may assess whether and how the proposal can safely be implemented.
  6. Execution and reporting: implemented actions should be recorded transparently where reasonably possible.

4. Non-automatic execution

A successful advisory vote does not require implementation where the proposal is unlawful, technically unsafe, materially incomplete, impossible to execute, inconsistent with security controls, outside available resources, dependent on unavailable third parties or likely to expose users to unacceptable harm.

5. Multisignature and timelock safeguards

Governance execution may use multisignature approvals, role-based permissions, timelocks, audits and public notice periods. These controls are intended to reduce unilateral action and permit review before sensitive changes. They do not guarantee that every decision or transaction will be free from error or compromise.

6. Treasury governance

Treasury proposals should identify the requested amount, recipient, purpose, milestones, reporting obligations, conflicts and cancellation conditions. Advisory approval does not create a legally enforceable entitlement until the transfer or agreement is formally authorised and executed.

7. Conflicts of interest

Proposal authors, delegates, reviewers, signers and contributors should disclose material financial or personal interests where reasonably possible. Governance participants should evaluate proposals independently and avoid misleading the community.

8. Delegation

Delegation may allow participants to assign voting power to another address or representative. Delegators remain responsible for choosing delegates. Delegates should communicate their positions and disclose material conflicts.

9. No fiduciary relationship

Participation in advisory governance does not automatically create a partnership, agency, employment, fiduciary duty or corporate office between participants, contributors, token holders, signers or maintainers.

10. Emergency actions

Where a credible exploit, security incident, legal prohibition or infrastructure failure creates an urgent threat, authorised security participants may take proportionate temporary action before a full governance process. Emergency actions should be documented and reviewed when disclosure is safe and legally permitted.

11. Evolution of governance

Governance rules may evolve through testing, community feedback and published proposals. Eligibility, quorum, voting periods, proposal thresholds and execution mechanisms should be documented before they are relied upon.

Acceptable Use, Sanctions and Compliance Policy

Effective: 29 July 2026

1. Prohibited use

You must not use AXNS-hosted Services to:

  • Commit fraud, theft, deception, market manipulation or unlawful financial activity.
  • Launder proceeds of crime, finance terrorism or evade sanctions.
  • Distribute malware, phishing links, credential-stealing tools or malicious code.
  • Attempt unauthorised access, denial-of-service attacks or exploitation of hosted infrastructure.
  • Impersonate contributors, moderators, support personnel or governance delegates.
  • Misrepresent token features, guaranteed returns, partnerships, approvals or regulatory status.
  • Infringe intellectual-property, privacy or other legal rights.
  • Use the Services in breach of applicable law or court orders.

2. Sanctions

You must not use hosted AXNS Services if you are subject to applicable sanctions or acting for a sanctioned person or prohibited jurisdiction. Hosted access may be restricted where reasonably necessary for sanctions or legal compliance.

3. AML and identity verification

Public non-custodial software does not necessarily perform customer onboarding. However, product-specific services involving custody, fiat conversion, exchange, token sale, regulated financial activity or third-party providers may require identity verification, source-of-funds checks, transaction monitoring, geographic restrictions or other controls.

4. Cooperation with lawful requests

Relevant hosted-service records may be preserved or disclosed where required by valid legal process. AXNS cannot alter independent public blockchain records.

5. Community conduct

Community channels should not be used for harassment, threats, spam, doxxing, discriminatory abuse, impersonation or deliberate misinformation. Third-party platforms may apply additional rules.

Security and Responsible Disclosure Policy

Effective: 29 July 2026

1. Reporting vulnerabilities

Good-faith security reports may be submitted to [email protected]. Include a clear description, affected component, reproducible steps, potential impact and non-destructive evidence.

2. Safe research expectations

  • Do not access personal information that is not necessary to demonstrate the issue.
  • Do not disrupt services, drain funds, alter records or exploit users.
  • Do not publicly disclose an unremediated vulnerability without allowing a reasonable response period.
  • Do not use social engineering, physical attacks or denial-of-service testing.

3. No automatic bounty promise

Submission of a report does not create a right to payment. Any bounty or recognition must be expressly approved in writing or through a published programme.

4. Security communications

Legitimate AXNS support will not request seed phrases, private keys or remote wallet access. Users should verify announcements through official channels.

Intellectual Property and Brand Policy

Effective: 29 July 2026

1. Website materials

Unless a separate open-source licence states otherwise, website design, original text, graphics, logos, branding and media are protected by applicable intellectual-property laws. No transfer of ownership occurs through website access.

2. Open-source software

Code published under an open-source licence may be used only under that licence. Third-party components remain subject to their own licences and notices.

3. AXNS marks

AXNS names, logos and visual identifiers must not be used to falsely imply endorsement, official status, partnership, exchange listing, audit approval or guaranteed association.

4. Community references

Accurate, non-misleading editorial references may be made to AXNS. Commercial use, token promotion, merchandise or confusingly similar branding may require prior permission.

Third-Party Services and Links Policy

Effective: 29 July 2026

AXNS websites may link to wallets, exchanges, decentralised exchanges, block explorers, bridges, social networks, documentation hosts, analytics services and other third parties. Links are provided for convenience and do not guarantee availability, legality, accuracy, security, solvency or endorsement.

You are responsible for reviewing third-party terms, privacy notices, fees, permissions and security practices. AXNS contributors are not responsible for losses caused by third-party services, fake websites, compromised integrations or changes made by independent providers.

Community and Marketing Communications Policy

Effective: 29 July 2026

1. Official channels

Users should verify announcements using official AXNS website links. Community members, influencers and unofficial groups are not automatically authorised representatives.

2. No guaranteed-return claims

No person should represent that AXNS provides guaranteed profit, guaranteed appreciation, risk-free returns or assured liquidity. Statements about token mechanics, rewards or roadmap plans must not be presented as certainty where outcomes depend on market, technical, governance or legal conditions.

3. Email preferences

Where optional email updates are offered, users may unsubscribe using the available mechanism or by contacting support. Service and security notices may still be sent where reasonably necessary.

4. User-generated content

Community opinions belong to their authors. AXNS does not necessarily endorse user-generated content, price predictions or third-party analyses.

Complaints and Dispute Notice

Effective: 29 July 2026

1. Contact first

Questions or complaints concerning the website, policies or hosted interfaces should first be sent to [email protected] with sufficient information to understand the issue.

2. Decentralised limitations

AXNS contributors may be unable to reverse blockchain transactions, retrieve private keys, recover funds sent to an incorrect address, compel validators, alter independent smart contracts or control third-party services.

3. Applicable law

Because AXNS is presently described as a community-led decentralised initiative and no separate operating legal entity has been identified in these policies, applicable law and forum may depend on the user’s location, the relevant service, the responsible service provider and mandatory conflict-of-law rules. Separate product terms should identify a governing entity and jurisdiction before regulated or contractual products are offered.

4. Informal resolution

Where appropriate, parties should attempt good-faith informal resolution before starting formal proceedings. This does not remove rights that cannot legally be waived.

Changes to These Policies

Effective: 29 July 2026

These policies may be updated to reflect protocol development, new features, governance decisions, security practices, service providers or legal requirements. The effective date should be updated when material changes are published.

Material changes may also be announced through official AXNS channels. Continued use after an updated policy becomes effective may constitute acceptance where permitted by applicable law.

Contact

AXNS Protocol Support

For website support, privacy requests, policy questions, security reports or legal correspondence:

Email: [email protected]
Website: AXNS Protocol
Governance model: Community-led advisory DAO governance

Do not send seed phrases, private keys, wallet passwords or unnecessary sensitive identity documents by email.