This explains what MDN STACKMART does with personal data — yours as a buyer, and yours as a seller. It covers the whole site: browsing, buying, downloading, and submitting a project through the seller form.

The short version: we collect what we need to deliver purchases, verify listings, pay sellers, and support both sides. We do not collect data to profile you, and we do not sell personal data to anyone.

Account data (buyers). Your name, your email address, and a password. The password is hashed — it is never stored in plain text, and nobody at MDN STACKMART can read it. If you forget it, we can only help you set a new one.

Order data. Which product you bought, what you paid, when, the status of the payment, the license key issued to you, and how many times the deliverable has been downloaded. The download count exists so that we (and you) can see when a key is being used in a way that does not look like you.

Payment data. Your card details go to our payment provider, not to us. We store the outcome — paid or not, the amount, and a reference — never your card number.

Seller submissions. Your contact details, everything you tell us about the project (description, category, tech stack, metrics, demo and repository links), the files you upload, and your payout details.

Payout details are the most sensitive thing a seller gives us, and they are handled accordingly.

• They are admin-only. Only our review and payout team can see them.
• They are never shown on a listing. A published listing carries the product, not the person behind it.
• They are never returned by any public API. There is no request a buyer or a visitor can make that will hand back a seller’s payout information.
• The payout identifier itself is encrypted at rest in our database.

We use them for exactly one thing: sending you the 80% you are owed when your product sells.

A submission carries three kinds of file, and they are not treated the same way.

Product images are public — that is their entire purpose. They appear on the listing for everyone to see. Do not upload anything into the image slots that you would not want on a public page: no screenshots with real customer data, credentials, or anything private in the frame.

Each thing we hold maps to something we have to do:

• To deliver your purchase — issue the license key, gate the download to you, and email you both.
• To verify listings — read the code, follow the README, check the metrics, so that what we publish is true.
• To pay sellers — transfer the 80% and send proof of it.
• To support both sides — answer questions, investigate a broken delivery, resolve a dispute.
• To keep the marketplace safe and lawful — detect abuse of license keys or downloads, and meet our accounting and tax obligations.

That is the list. We do not build advertising profiles, and we do not run behavioural tracking on you.

We do not sell, rent, or trade personal data. We share it only with the parties that make the service work, and only as far as they need it:

• our payment provider, to take the payment and confirm it
• our email provider, to deliver the transactional emails below
• our hosting and storage providers, which run the site and hold the files
• professional advisers or authorities, where the law actually requires it

A buyer never receives a seller’s personal contact details from us, and a seller never receives a buyer’s. Where an introduction is genuinely needed — a handover question, for instance — we ask both sides first.

Everything we send is transactional — it is triggered by something you did:

• Purchase delivered — your license key and the link to download your deliverable, sent the moment your payment is confirmed.
• Submission received — confirmation that your project reached us and is queued for review, plus anything the reviewer needs to ask you.
• Payout confirmed — proof that your 80% has been transferred, for your records.

We do not add you to a marketing list because you bought or submitted something. If we ever start a newsletter, it will be something you opt into.

When you sign in, we store an authentication token in your browser so that you stay signed in as you move between pages. That is what keeps Purchases and downloads working without asking for your password on every click. Signing out removes it.

We do not run advertising cookies or third-party trackers on this site. Our hosting and payment providers may set the strictly technical cookies they need to function.

• Account data: while your account exists.
• Orders, license keys, and payout records: kept after the sale — they are the record that a licence is valid, and we have accounting obligations that outlast the transaction.
• Declined or withdrawn submissions, and the files attached to them: kept only while there is a reason to (an appeal, a re-submission, a dispute), then deleted.
• Deliverable ZIPs for live and sold listings: kept for as long as buyers are entitled to download what they paid for.

You can ask us to:

• show you what we hold about you
• correct anything that is wrong — including your payout details
• delete your data

Email support@mdnstackmart.com and a human will handle it. We will confirm it is really you before we act.

One honest caveat on deletion: we can remove your account and your personal details, but we cannot erase the record that a paid order and a license key exist. That record is what makes a buyer’s licence provable and what our books are built on. We keep it minimal and we keep it out of sight.

• Passwords are hashed, never stored in plain text.
• Payout identifiers are encrypted at rest and visible only to admins.
• Deliverable ZIPs and verification READMEs live on a private disk with no public URL.
• Every download is gated: signed in, order is yours, order is paid, license key matches.
• Traffic to the site is served over HTTPS.
• Access to the admin tools is limited to the people who need it to review listings and run payouts.

No system is perfect. If a breach ever affects your data, we will tell you what happened, what it touched, and what to do — promptly and without spin.

If what we collect or how we handle it changes, we update this page and change the “last updated” date at the top. Material changes will be stated plainly rather than buried.

Questions about any of this — or a request about your data — go to support@mdnstackmart.com. The rules of the marketplace itself are in the terms & conditions.