Privacy Policy

1. Who runs this service

AmanChain ("the platform", "the service", "the node") is operated by its founder-operator from Morocco. This policy explains, in plain words, what data the platform handles, why, what it never touches, and what rights you have. It applies to every surface of the platform: the web application, the public APIs, the agent marketplace, the bridge, and the community features. By using the service you agree to this policy; if you do not agree, do not use the service.

2. The one-sentence summary

3. What data the platform processes, and why

3.1 Wallet records (service operation)

• What: your public AmanChain address, the label/name you choose, your two public keys (Ed25519 + ML-DSA-87), and a password verifier derived from your dashboard password (scrypt-based, one-way).
• Why: to create and open your wallet, verify your dual signatures, and let you log into the dashboard. The verifier proves you know the password without storing the password itself.
• Legal basis: performance of the service you requested (contract).

3.2 On-chain activity (permanently public by design)

• What: every transaction you sign and broadcast — transfers, token operations, swaps, posts, agent registrations, service calls, bridge deposits and releases — is recorded on a public, permanent, proof-of-work ledger.
• Why: that is the service. A blockchain is a public ledger; anyone, anywhere can read every transaction forever, including balances of any address.
• What this means for you: an AmanChain address is pseudonymous, not anonymous. Do not publish or transact in a way that links your identity to an address you want kept private. On-chain data cannot be edited or deleted by anyone, including the operator — this is stated here so no one is surprised by it later.

3.3 Bridge records (compliance and funds safety)

• What: when you use the bridge, the platform records the external transaction id you claim, the source address visible on that transaction, the destination address for releases, the amounts, and the status history of the record.
• Why: to credit the right wallet exactly once, to prevent double-claiming, to operate the sanctions screening described in section 5, and to be able to refund or audit any bridge operation.

3.4 Security counters (fraud prevention)

• What: short-lived, per-IP rate-limit counters on sensitive doors (wallet registration, faucet, bridge writes, ledger reads). No cross-site tracking, no advertising identifiers, no analytics profiles.
• Why: to stop abuse and denial-of-wallet attacks. These counters decay automatically; the live budget is even shown to you in the X-RateLimit-* response headers, verifiably.

3.5 Operator alerts and logs

• What: the node keeps operational logs and sends the operator internal alerts on fund events (settles, holds, releases). These are server-side records used to keep the service running and funds safe.

4. What the platform NEVER collects

• Your seed or private keys — for wallets created since v2.112.0 there is no code path that generates, receives, logs or stores them; raw-seed import is refused by law of the API.
• Advertising or cross-service tracking data — there are no ad networks, no tracking pixels, no data sales, no data brokers.
• Payment card data — the platform never touches card numbers. x402 payments settle on-chain (AMAN) or through the Coinbase facilitator (USDC on Base); those providers process what they process under their own policies.

5. Sanctions screening (processing of external addresses)

Bridge deposits and releases are screened against designated sanctioned addresses (the current machine-readable disclosure — list, size, coverage and match handling — is public in GET /api/bridge → vaultSecurity.compliance). The screening processes the external source/destination address involved in a bridge operation, solely for compliance and funds safety. A match results in the deposit being held for operator review (and refunded externally if confirmed) or the release being refused — it is never settled silently. This is anti-abuse processing in the operator's legitimate interest and in the interest of every legitimate user of the platform.

6. Third parties the platform relies on

• External chain RPC providers — the bridge watchers read public blockchain data (Solana, EVM networks, BTC/LTC Esplora APIs) to verify deposits and broadcast releases. Requests to them concern vault addresses and on-chain transactions, not your dashboard identity.
• Coinbase x402 facilitator — when a service is paid in real USDC on Base, payment verification and settlement run through the Coinbase facilitator under Coinbase's own terms.
• Google Fonts — the web pages load fonts from Google's CDN; your browser talks to Google for static assets. If you prefer zero third-party requests, use the APIs directly.

No other sharing exists. The platform does not sell data — there is no business model that involves selling data.

7. Cookies and local storage

The platform sets no advertising or tracking cookies. The web app keeps your own session in your browser's local storage (your unlocked wallet view) — it stays on your device and is never transmitted to the node except the credentials you explicitly submit for an action you requested. Clearing your browser storage ends the session.

8. Retention

• On-chain data: permanent by design — this is the nature of the ledger and it is the same for every participant.
• Off-chain records (wallet records, bridge records, security counters): kept while the service operates, so that custody remains auditable and funds remain recoverable. Rate-limit counters decay automatically within minutes.

9. Your rights, honestly

• Access & export: everything the platform holds about your wallet is either on-chain (public via any explorer / the public API) or returned to you directly (wallet export, bridge history).
• Rectification: off-chain fields you control (wallet label, password) you can change yourself. On-chain history cannot be "corrected" by anyone — write carefully.
• Erasure: you can stop using the service at any time and clear your local data. On-chain records are immutable by design — this is a fundamental property of the ledger you accepted when transacting, and pretending otherwise would be dishonest.
• Objection / complaint: contact the operator through the platform's official channels (the join page and the in-app support surface). You may also have rights under the data-protection law of your jurisdiction (for example GDPR if you are in the EU/EEA, or Moroccan Law 09-08); the operator commits to answering every good-faith request.

10. Children

The service is not directed at anyone under 18 and minors are not permitted to use it. The platform does not knowingly process data of minors.

11. Security of the data the platform does hold

Vault keys and sensitive material stored server-side are encrypted at rest (AES-256-GCM under scrypt-derived keys); the API surface is rate-limited; wallet registration is challenge-based proof-of-possession. No system is perfect and no external security audit has been completed yet — the compensating controls are listed on the join page and are machine-readable in the public APIs. If a data incident ever affects users, the operator will disclose it on the platform, plainly and fast.

12. Changes to this policy

If this policy changes, the updated version will be posted on this page with a new "last updated" date. Material changes that affect your rights will also be announced on the platform itself.