Status of this policy
This policy describes what Account Market collects, why, and what it does with it. It is marked as a draft because the processing that will happen once trading is enabled has not been reviewed and finalised, and because the lawful basis and retention periods for each category still need to be settled.
What is true today is narrower and is stated first, because a policy that describes a future system as though it is running is a document nobody can rely on.
What is collected today
An account holds your username, your email address and a password hash. An order holds the product, the amount, the status and the delivery for that order. A wallet holds the entries that make up your balance. Two browser preferences are stored locally: your theme, and nothing else that matters.
The server records ordinary request information such as an address and a timestamp, in the way any web server does. That is described in the cookie policy.
What will be collected, and why
Trading requires identifiers that a marketplace cannot function without. The categories below are the ones the design requires, and each is listed with its purpose, so that a collection can be challenged by category, not as a vague whole.
| Category | Why it is needed | Retention |
|---|---|---|
| Account identifiers | Username, email address and a password hash, used to identify and authenticate you. | Until you delete the account, plus the period needed to settle an open dispute |
| Email verification and recovery tokens | To confirm an address and to allow a password reset. Stored as hashes and expiring. | Minutes to hours, then deleted |
| Session records | Device, creation and last-activity metadata for each signed-in session, so you can revoke one. | Until the session is revoked or expires |
| Order records | Product, quantity, quote, price, status, delivery reference and terms version. | The period required for disputes and for tax records |
| Payment evidence | The reference, amount and time of a payment, and the outcome of matching it. Never a banking credential. | The period required for dispute and reconciliation |
| Wallet ledger | Holds, captures, releases, credits and debits, each a separate entry. | As long as the account exists |
| API key metadata | Key name, scopes, spend limit, public identifier and activity. The secret itself is stored only as a hash. | Until the key is archived |
| Support records | Your messages, the references you attach and the outcomes. | The period required to resolve and defend a claim |
| Security metadata | Rate limiting, audit and abuse-prevention signals, kept minimal. | Short, defined periods |
| Delivery data | Session files, numbers and codes, held against an order and an owner. | Until the delivery window closes, then deleted |
Sessions and how to end one
Signing in creates a session for that browser. Sessions are revocable, and a password reset link works once and then stops working. Signing out ends the session on that device.
Payment evidence
You supply a payment reference. You never supply a banking credential, a one-time password, a UPI PIN or a mailbox password to this platform, and no part of the design asks you to.
Where a receipt-matching service is used to verify a payment, it is a third party that receives the reference, the amount and the time, and it is the operator of that service, not this platform, that holds any mailbox access. The trust arrangement, the transport and the evidence format for such a service must be confirmed before it is used. Until they are, the design is to read the evidence directly, and the choice between the two is not made silently.
Credit is granted only on matched evidence: the amount, the time and the sender must agree, and the reference must be bound to your order uniquely. A bare confirmation that something was found is never sufficient on its own.
Suppliers and other recipients
Suppliers receive what they need to fulfil an order, and no more: the product, the quantity and the target you supplied. They do not receive your account details, your email address or your wallet balance. Where a supplier is itself a processor of personal data, the arrangement is recorded and published before the supplier is enabled for a product that involves personal data.
Other recipients are limited to the infrastructure required to operate the service, such as hosting, email delivery and payment processing. Each is identified by category in the published list of processors, which is added before the corresponding integration is enabled.
- The named processor list for hosting, email and payment settlement
- Whether any supplier processes personal data beyond the order fields, and under what terms
Private delivery data
Phone numbers, session files, codes, email addresses and order targets are private to the buyer. They do not appear in a public review, a public listing, a public message, an analytics event, a structured-data block or a URL. Support requests that contain delivery data are handled by the reviewer who needs it and by nobody else.
Retention and deletion
Delivery data is deleted when its delivery window closes. Order and ledger records are kept for the period required to settle a dispute and to meet tax and accounting obligations. Security metadata is kept for short, defined periods. Deleting your account requires the current password, your exact name, a zero balance and no open order or pending deposit, and it removes the personal data while retaining the records that must be kept for legal reasons.
Your rights
You can see the personal data associated with your account, correct it, export it, object to its processing and ask for it to be deleted. Requests are authenticated before they are actioned, so that nobody can ask for a stranger's data. Where a request cannot be honoured, the reason is given in writing, not as a generic refusal.
- The supervisory authority and the jurisdiction that applies to this policy
- The exact response period for each type of request
Cookies and local storage
The only local storage is your theme choice. One essential cookie keeps you signed in. There is no advertising storage and no tracking script. The full list is in the cookie policy.
Changes to this policy
This policy is versioned. A change that affects what is collected, why, or who receives it is published before it takes effect, and where it is material, you are asked to acknowledge it. The previous version remains available so that a question can be assessed against the policy that actually applied.
Contact and complaints
A privacy contact is published once one is confirmed, and a complaint route to the relevant supervisory authority is published alongside it. Until then, the general support path applies, and it never asks for credentials.