KOLIANCE
DATA PRIVACY & CRYPTOGRAPHIC BOUNDARY SPECIFICATION

Privacy Policy

Last Updated: October 2026 · Effective Date: October 24, 2026

1. Privacy Principles & Zero Plaintext Credential Rule

At Koliance, privacy and self-sovereignty are built directly into our cryptographic architecture. We believe that user data should belong exclusively to the user. We adhere strictly to the following foundational rules:

Zero Private Keys

We never solicit, store, or transmit your private keys, seed phrases, or master wallet secrets.

Zero Data Reselling

We do not sell, rent, monetize, or broker personal identity information to advertising networks or third parties.

2. Information We Collect & Process

Depending on how you interact with the Koliance Protocol, we may process the following categories of data:

  • Public Blockchain Data: Your public Ethereum / Monad wallet address, on-chain transaction hashes, block receipts, token balances, and smart contract event logs. This information is public by nature of decentralized ledgers.
  • Third-Party Social Attestations: If you connect GitHub, Steam, or Google OAuth via Privy, we only store cryptographic identifiers (e.g. GitHub handle, commit hash proofs, Steam ID) required to mint and verify your on-chain Agent Card trust score.
  • API Usage & Telemetry: Anonymized request counts, rate-limit indicators, and response status codes to maintain gateway availability and enforce quota limits.

3. Local Storage & Cookie Usage

Koliance uses minimal client-side localStorage exclusively for operational and user experience preferences:

  • Active language preference (en / zh).
  • Recently viewed trading pairs and cached market quotes.
  • Session state persistence via secure web3 providers (Privy / Wagmi).

We do not deploy third-party behavioral tracking cookies or invasive cross-site marketing pixels.

4. Cryptographic Boundary & EIP-712 Session Keys

When delegating session keys to autonomous AI agents:

  • Session key authorizations are cryptographically signed using EIP-712 structured data and stored in the on-chain smart contract SessionKeyRegistry.sol.
  • Temporary session keys are held locally in your browser memory or secure agent runtime and are never exposed in plaintext to centralized loggers.
  • You can revoke or modify delegated session keys on-chain at any time, immediately invalidating downstream transactions.

5. User Rights & Data Deletion

You maintain the right to disconnect your wallet, purge local cache, or request the dissociation of off-chain profile links. Note that data permanently committed to the Monad blockchain cannot be modified or deleted due to decentralized consensus finality.

6. Security Contact & Inquiries

For data protection questions, privacy audits, or responsible disclosure, please reach out to our security team at developer@koliance.io or iasi777work@gmail.com.