The market's own server: what it holds because you handed it over
A server cannot serve you without receiving what you send it. That is arithmetic rather than an accusation, and the useful work is in drawing the line precisely.
Every page you load from Awazon Market is assembled by a machine somewhere. For that machine to render a listing, a message thread or an order form, it has to receive the request you made and whatever you typed into it. There is no version of a website that shows you a page without first being told which page you wanted. This section is about the consequences of that, and about exactly where those consequences stop.
Three separate things get muddled together whenever people discuss what a market knows. The first is what the server necessarily receives, because the request could not have been answered otherwise. The second is what it retains, meaning what somebody chose to write down and keep. The third is what it cannot hold at all, because the information never reached it. Most arguments about market privacy are really arguments about the middle one, and the middle one is what nobody outside the server can inspect.
Received, retained, impossible
- Received
- Anything the server needed in order to answer. Which page you asked for, the contents of any form you submitted, and the fact that a request arrived at a particular moment.
- Retained
- Whatever someone decided to store, in what form, and for how long. A configuration decision and a business decision, set by whoever operates the platform and changeable without telling you.
- Impossible
- Anything that never crossed the wire. Your street, your legal name, the other tabs in your browser, the contents of your disk, who else lives in the building.
Readers get the boundary between the first two wrong in both directions. Some assume that because a field appears on a form, the value is filed forever and cross referenced. Others assume that because a market advertises a privacy posture, nothing is written down at all. Receiving is forced by the mechanics of serving a page. Retaining is optional, and invisible from where you sit.
What the onion address does, and what it leaves alone
An onion address is not a name pointed at a machine you could look up. It is a public key rendered as text, and reaching it involves a rendezvous inside the Tor network rather than a direct connection. Two things follow. You do not learn where the server is. The server does not learn where you are, because the connection arrives out of the Tor network and the address it sees does not lead back to your line. See exit relays and onion addresses.
Neither of those facts touches the content of the request. The concealment happens at the level of location, in both directions. It is not a filter on what you type. If a form asks for a delivery address and you fill it in, the onion address has done nothing whatever to that field. It arrives complete and readable, as does a chosen username, a passphrase, a message body, and the exact order in which you asked for pages. Mistaking location privacy for content privacy is the commonest misreading here, so every card below says which of the two is in play.
Retention is a decision, and you cannot audit it
This site makes no claim about what Awazon Market records, keeps or discards, because that is not observable from outside. A stated policy is a statement of intent, not evidence. An interface with a delete button proves the button exists, not what became of the row behind it. Nor does the absence of a field in the interface prove the absence of a column in the database. The honest position is the arithmetic one: assume the server received whatever it had to receive in order to work, and treat everything past that as unknown rather than as safe or as damning.
A record that exists can change hands
The observer list on these cards includes an entry that is easy to read past: anyone who later obtains the server. Data does not stay with the party that collected it as a matter of physics. Hardware gets seized, sold, rented, misconfigured, copied to a careless backup, or handed over by whoever holds the keys. A record made for one purpose is legible later to a different party, who is not bound by the intentions of the first.
This is why the reassurance that an operator has no interest in you is a comment about motive and not about exposure. Motive travels with the disk. The cards below therefore deal in what is structurally certain and leave the rest labelled as unknown.
The six actions in this section
Each card takes one thing you do against the market server and does the same four jobs: says what the action is, lists who observes it, states what they concretely learn, and states in the same detail what they do not. The order follows a first visit, from making an account through to funding a balance.
The market is one of seven observers here, and rarely the only one watching a given moment. The observers page puts all seven side by side, and the full catalogue lists every action. Two neighbouring sections matter most: the vendor section, because the person reading your order is not the platform, and the device section, because a copy on your own disk is outside the market's reach entirely.
Questions that come up
Does using Tor stop the market from seeing what I type?
No. Tor conceals where you are connecting from and, for an onion address, where the server is. The request itself still arrives intact, because otherwise there would be nothing to answer. Location privacy and content privacy are separate questions.