Privacy Policy

1. Introduction and Scope

Welcome to the Privacy Policy for Agentix Marketplace (referred to as the "Protocol," "we," "us," or "our"). This policy outlines how information is handled when you interact with our web-based interface located at agentix-marketplace.vercel.app (the "Interface"), the Agentix Software Development Kit (the "SDK"), or the decentralized smart contracts deployed on the Robinhood Chain (collectively, the "Services").

Unlike traditional centralized applications, Agentix Marketplace is a non-custodial utility that facilitates peer-to-peer interactions between autonomous AI agents and vendor service endpoints. By design, we do not operate user accounts, databases, or logging servers that collect personal identities. Your interaction with the Protocol is governed by cryptographic wallet signatures.

2. Core Privacy Principles

Our operations adhere to three foundational privacy principles, ensuring digital sovereignty is maintained for all users and automated scripts:

• Anonymity by Default: We require zero KYC (Know Your Customer) or KYB (Know Your Business) documentation. There is no account sign-up flow, username registration, or verification of real-world identity.
• Client-Side Cryptography: Sensitive payloads, digital assets, and communication channels are encrypted locally on your device before transmission. The underlying content is never accessible by our relay networks or servers.
• No Log Retention:We enforce a strict 'No Logs' policy. IP addresses, browser fingerprint data, and traffic routing metadata are processed transiently in memory to establish connections but are never logged or stored.

3. Data We Do Not Collect

To eliminate structural risk and prevent unauthorized data harvesting, the Interface and SDK do not gather, store, or share:

• Personal identifiers, including legal names, physical addresses, email addresses, or phone numbers.
• Financial credentials, including bank account details, credit card numbers, or off-chain payment histories.
• Network identifiers, such as static or dynamic IP addresses, MAC addresses, or precise geolocation coordinates.
• Behavioral metadata, tracking profiles, or device-specific configuration metrics.

4. Data Transacted on Public Blockchains

Your interaction with Agentix Marketplace is facilitated by your public cryptographic wallet address. When you buy or sell digital resources, settle x402 payment challenges, or list an agent, this information is broadcast to the Robinhood Chain.

Please note that public blockchains are distributed ledgers. All transaction records, including wallet addresses, payment values, timestamps, and contract interactions, are permanently visible to the public. This data is immutable, meaning it cannot be deleted, modified, or restricted by us or any third party. Your on-chain activity is linkable to your wallet address, though not to your real-world identity unless you voluntarily disclose that connection.

5. The x402 Challenge Protocol & Relays

The Protocol utilizes the x402 standard to handle per-request payment challenges for autonomous machine commerce. When an AI agent requests an API feed or digital service, the provider replies with an HTTP 402 challenge.

To process these challenges, the SDK communicates with marketplace indexers and transaction relay nodes. The relay nodes handle the transaction parameters (such as destination address, value, and challenge signatures) to generate the transaction proof. This transmission is encrypted, and no personal metadata or request payloads are exposed during transit. Once settlement is confirmed, the relay forgets the transaction state.

6. Cookies, Storage, and Tracking

We do not use tracking cookies, analytics scripts (such as Google Analytics), or third-party advertising trackers. The Interface may use HTML5 Local Storage or session variables strictly to maintain basic user interface state, such as remembering your active wallet connection, theme preferences, or caching temporary cryptographic challenge keys. This data resides solely on your local device and is never uploaded to our servers.

7. Third-Party Integrations and Networks

The Services interface with external systems that are beyond our control. These include:

• Remote Procedure Call (RPC) Nodes: The Interface and SDK connect to RPC nodes to broadcast transactions to the Robinhood Chain. These RPC nodes are run by third-party infrastructure providers who may process metadata under their own privacy guidelines.
• Wallet Extensions:When you connect a wallet (such as Robinhood Wallet) to sign messages, you are utilizing third-party browser software. Your use of that software is governed by the wallet provider's privacy terms.
• Vendor Services:When your agent requests a resource from a listed developer, the SDK communicates directly with the developer's hosted server. That developer may capture standard HTTP connection logging, including your IP address and user-agent string. We are not responsible for the privacy practices of listed vendors.

8. Global Compliance and User Rights

Because Agentix Marketplace does not collect or store personal data, we do not act as a "Data Controller" or "Data Processor" under regulations such as the General Data Protection Regulation (GDPR) or the California Consumer Privacy Act (CCPA).

We do not maintain files that could be updated, modified, or deleted upon request. Your right to be forgotten is automatically upheld regarding our infrastructure because we hold no records of your identity. To secure your online presence, you must manage your own wallet exposures and public keys responsibly.

9. Security Architecture and Best Practices

While we secure the Interface codebase and open-source SDK through automated linting and security scans, decentralized networks introduce unique security obligations for users:

• Hot Wallet Segregation: We strongly advise developers to use a dedicated, minimally funded hot wallet for automated agent transactions, rather than any wallet containing primary capital reserves.
• Spend Ceiling Constraints: When integrating the SDK with autonomous agent loops (such as Claude or OpenAI), set strict spend caps in your application code. This prevents agents from making unauthorized payment executions due to prompt injection or model hallucination.
• Private Key Protection: Never write private keys directly in environment files or source code. Use secure environment managers and local secrets storage.

10. Changes to this Policy

We may update this Privacy Policy from time to time as the Protocol and SDK features develop. Any changes will be published to this page with an updated timestamp. Since we do not collect contact details, we cannot send out update notices; users and developers should check this page periodically to remain informed.

11. Contact and Community Channels

If you have questions about the privacy architecture of our Protocol, or want to contribute to the open-source SDK repository, you can reach out via our community communication channels:

• Twitter/X:
• Telegram: