Security you can check, and a plain list of what we do not claim

Everyone has their own named login. There are no shared accounts.

• Two-factor authentication (an authenticator app) is required for every login.
• Passwords must be at least 12 characters and are stored only as salted hashes. Accounts lock after repeated failed logins.
• Roles for owner, admin, staff and viewer. Only owners and admins manage users, connections and keys.
• An audit log records logins, failed logins, role changes, label creation and views of buyer details, with the person, time and address.
• Each customer account is kept in its own separate data space.

Data is encrypted on the way in and while it is stored.

• Everything travels over HTTPS. Cloudflare sits in front of the application with a web application firewall.
• Marketplace and courier logins you save are encrypted and are never shown again.
• Buyer names, addresses, emails, phone numbers and notes are encrypted in the database with a separate key.
• The database is not reachable from the internet. Only web traffic and key-only administrator access are open on the server.

A full scan runs every week, not once a year.

• It checks open ports and service versions, known weaknesses in the software libraries and operating system, secrets left in code, code analysis against the OWASP Top Ten rules, and the website itself.
• A second weekly job runs a server hardening audit, a malware scan and a package check.
• A serious finding raises a critical alert. Our targets are to fix critical findings within 7 days and high findings within 30 days.
• Reports are kept as evidence for each scan.

Each release is scanned before it goes live.

• The exact release is checked with code analysis (OWASP rules) and a dependency, secret and configuration scan.
• Error-level or high and critical findings stop the release until they are dealt with.
• Every release is logged with the reason for the change and who approved it.

The whole database and the uploaded files and labels are backed up every night.

• Backups are encrypted with AES-256.
• Each backup is checked straight after it is made: it must decrypt, read, and contain every customer account's orders. A failed check raises an alert.
• Backups are kept for 14 days. A restore test runs monthly, and the restore steps are written down.

Security pages are easy to inflate, so here is what is not true.

• We hold no security certification, such as ISO 27001 or SOC 2.
• No independent penetration test has been carried out yet. One is planned before October 2027.
• We do not claim an off-site backup copy. The tool for it is built, but we will not say it is in place until it is.
• None of this is an Amazon, eBay or other marketplace approval.