Awazon Market Privacy Policy

What this directory stores

This clearnet directory collects minimal data. It does not store visitor email addresses. It does not place tracking cookies. It does not fingerprint visitors using JavaScript or canvas APIs. Server logs record IP addresses and request timestamps for security auditing. These logs retain for thirty days before automatic deletion. No other personal identifiers are captured. Analytics use privacy-respecting counters that aggregate traffic without identifying individuals. This approach respects user autonomy while maintaining basic operational insight. The absence of invasive tracking distinguishes this directory from typical web properties.

What the storefront stores

The actual marketplace operates differently. Upon registration, it stores a hashed version of your passphrase. The original phrase never appears in plaintext databases. It also retains keys derived from your recovery mnemonic. These cryptographic elements enable account restoration. Order history records transactions, item descriptions, and vendor interactions. Wallet addresses used for deposits and withdrawals remain linked to your account profile. Chat logs between buyers and vendors persist indefinitely unless deleted manually. Dispute documentation includes submitted evidence and panel rulings. All this data resides on encrypted servers within the Tor network.

Cookies and tracking

Session cookies maintain login state during active browsing. They expire when the browser closes or after twenty-four hours of inactivity. No persistent cookies track behavior across sessions. No third-party advertising networks access user data. Pixel tags from external services are blocked by default. Custom scripts execute only from the Awazon domain. This containment prevents leakage to outside entities. Users can inspect cookie settings in their browser to verify compliance. The footprint remains small and purpose-driven. No hidden trackers linger in the background. Cleanliness in code design supports long-term trust.

Data you provide

You supply specific inputs voluntarily. Username, passphrase, recovery mnemonic, and wallet addresses. Additional details appear in chat messages and dispute submissions. Vendor-facing data includes shipping addresses for physical goods. Digital goods involve file delivery mechanisms rather than postal info. Services may require skill verification documents. All provided data serves functional purposes. Nothing is collected for marketing campaigns or cross-site profiling. The dataset grows organically with usage. It does not expand artificially through aggressive capture forms. Transparency defines the relationship between user and platform.

Retention

Account data persists as long as the account remains active. Inactive accounts older than two years undergo archival procedures. Archival moves data to cold storage with restricted access. Deletion requests processed within seven business days. Complete erasure includes transaction histories and chat logs. Cryptographic keys regenerate upon re-registration if requested. No residual traces remain after confirmed deletion. Retention policies align with operational necessities. Excessive storage increases attack surface. Periodic pruning keeps systems lean. Users benefit from knowing exactly how long their information lingers in active systems.

Your choices

Users control their privacy posture. Use unique usernames unrelated to real identities. Rotate wallet addresses periodically. Encrypt chat messages for sensitive negotiations. Request deletion of specific records if needed. Adjust notification preferences to minimize email pings. Manage your own PGP key lifecycle carefully. Compromise in key management impacts data security directly. The platform provides tools; users exercise discretion. Active participation in privacy maintenance yields best results. Passivity accepts default settings. Defaults suit most scenarios but customization optimizes protection levels. Choose based on your comfort zone and threat assessment.