deadstockdb
FeaturesPricingFAQ
Sign inSign up

Product

FeaturesPricingFAQ
Sign in

Trust

How deadstock-db keeps your collection private, safe and yours, said plainly, with what it doesn’t do yet.

The short version

  • Export everything, or delete your account, from Settings, any time.
  • Nothing is public until you turn your public page on.
  • Each account can reach only its own pairs, photos and receipts.
  • We don’t sell your data, show you ads, or use your collection to train AI.
  • One person runs deadstock-db. There’s no security certification yet, and this page says what else is missing.

Contents

  1. Your collection is yours
  2. Private until you say
  3. How it’s protected
  4. The label reader
  5. What we see
  6. Who runs it with us
  7. When something goes wrong
  8. What we don’t have yet
  9. Report a security problem

Your collection is yours

  • Take it with you. Settings › Export downloads everything you’ve entered, as JSON, or your pairs as a CSV that opens in any spreadsheet. No request, no wait, no limit on how often.
  • Bring it in. Import reads the spreadsheet you already keep, saved as a CSV, and our own CSV reads back in unchanged.
  • Leave whenever you like. Settings › Account deletes your account and everything in it straight away: pairs, photos, proof of purchase, passkeys. Copies in our database provider’s backups expire within 7 days.
  • No surprises. If we remove a feature you rely on, or close deadstock-db, we’ll tell you at least 30 days before, so you can export your data. We’ll never charge you without a plan you chose.

Private until you say

A new account has no public page. Turn one on in Settings › Privacy and anyone with its link sees your profile and the pairs you haven’t hidden or sold. Pair photos show only if you turn them on as well. Prices, stories, proof of purchase and your email never appear on it, whatever you switch on, and turning it off takes it down at once.

The Privacy policy lists exactly what it shows and what it never does.

How it’s protected

  • Your rows are yours. Rules in the database itself let each account read and change only its own data, and automated tests fail if any table is left without them.
  • Photos stay private. Pair photos and proof of purchase sit in private storage and open through links that expire within an hour. Visitors to a public page never reach that storage; its photos are passed on by our server, one checked photo at a time.
  • No location in your photos. Your browser re-encodes a photo before uploading it, which removes the location and camera details a phone writes into it.
  • Sign-in that can’t be read back. Passwords are stored only as one-way hashes. Add a passkey in Settings and you can sign in with your face, fingerprint or device PIN instead; we keep only its public key.
  • Keys kept server-side. The one key that can get past the database rules never reaches a browser, and is used only for deleting an account and passing on public photos.
  • Everything travels over encrypted connections (HTTPS).
  • Only the person who runs deadstock-db has administrative access.

The label reader

When you scan a box, its barcode is read on your phone or computer, and a pair you already have with that barcode fills the form from your own collection. Only when it doesn’t is the label photo sent to Anthropic’s Claude to read.

  • It gets the label photo only, with nothing about you or your account.
  • We don’t store or log the photo. Anthropic keeps it up to 30 days and doesn’t use it to train its models.
  • Every field it reads is checked before it reaches your form, and you see which ones came from the label until you change them.
  • Your collection itself is never sent to an AI.

What we see

  • Error reports carry your account id, never your email, and leave out cookies, what you send us, and searches in page addresses. Nothing you do in your collection is recorded on video.
  • Analytics count pages and buttons without their words, and strip searches and filters from addresses. Until you accept analytics cookies, analytics stores nothing on your device and ties no visit to you. Recordings, after you accept, cover only the home page and public collection pages.
  • Change your answer any time on the Cookies page.

Who runs it with us

These companies run parts of deadstock-db, each only on our instructions. The Privacy policy says what each one gets and where.

Supabase
Our database, sign-in, file storage and sign-in emails.
Netlify
Hosts the website and runs its server code.
Anthropic
Reads the box labels you scan, with its AI model Claude.
Sentry
Error reports.
PostHog
Usage analytics.
Google Fonts
Serves the typefaces the site uses.

When something goes wrong

  • System status checks the collection, sign-in, photos and label reader live, each time you open it.
  • Our database provider backs up your data every day and keeps each backup 7 days.
  • An import saves every pair in the file or none of them, never half.
  • If a breach puts your data at risk, we’ll tell you, and the authorities where the law requires, without undue delay.

What we don’t have yet

deadstock-db is new and run by one person. So, today:

  • No independent security audit or certification, such as SOC 2 or ISO 27001. We won’t show a badge we haven’t earned.
  • No one on call around the clock; an outage at night may wait for morning.
  • Photo files aren’t in the export yet. Ask and we’ll send them (see Contact).
  • Two-step sign-in codes aren’t offered; a passkey is the strongest way in.
  • Sign-in history isn’t deleted automatically yet; ask and we’ll delete yours.

So keep your own copy of anything you can’t lose: an export takes a second.

Report a security problem

Found a way into data that isn’t yours? Write to support@deadstockdb.com with “Security” in the subject. The Contact page says how we ask you to go about it.

Product

  • Pricing
  • FAQ
  • Privacy
  • Sign up
  • Sign in

Resources

  • Getting started
  • Condition guide
  • Blog
  • Collector stories
  • Compare deadstock-db

Support

  • Contact us
  • System status
  • Trust
  • Code of conduct

Contact

dbDeadstock

©2026 deadstock-db. All rights reserved.

  • Privacy policy
  • Terms and conditions
  • Cookie policy
  • Cookie settings