Home / Your shop stays yours. Full stop. / Data protection
Data protection
What happens to your data, from login to backup.
Your keys, your orders and your backups are kept apart, checked on every request, and never handed to anyone else. Here is exactly where.
Data protection is not a page of certifications — the meaningful parts are boring, specific and checkable. Where your key goes when it is renewed, what happens to an account that is not approved yet, and whether anybody has ever actually restored a backup to find out whether it works.
Where the sensitive things live.
- Keys in a locked vault — When the system starts, it fetches your marketplace and supplier keys from a locked vault — never writing them to the machine it runs on. Keys renewed while it runs go back there, so a restart never loses the connection.
- Your own developer keys — For eBay you connect your own developer application. That means the key is yours, revocable in your marketplace account at any time, and never a shared secret standing between your shop and a third party.
- A system the internet cannot reach — The system answers only to the machine it runs on, behind one gate on one address. The internet cannot reach it, and administrative access arrives through an identity check rather than a password.
On every request.
- First who you are, then whether you belong — Your key proves who you are; the second check runs on every request and asks whether you should be here at all. Two separate checks, deliberately.
- Kept apart in the database — Your data is separated at the database level, not by trusting whatever the browser claims.
- Nothing counts before approval — An account that is pending or blocked is refused before it can reach anything that returns data.
- Every door has its limit — Every door has its limit, and callers are told when to try again. Nothing can knock so hard that the load lands on a marketplace in your name.
- Refuses to start open — A build started with authentication disabled will not come up in production. Failing to start gets noticed; serving everybody does not.
Backups that are checked, not assumed.
The uncomfortable question about a backup is not whether it runs. It is whether it would work on the morning it is needed, and almost nobody finds out until then. So verification is part of the backup itself: an archive that is suspiciously small or structurally wrong is discarded rather than stored, because a bad backup that looks successful is worse than no backup at all.
A silent alarm covers the other failure — the backup that quietly stops running. When a scheduled run does not report in, the absence is noticed before the day it matters. And a restore has a trial mode that changes nothing, which means the restore has been practised instead of merely described.
We keep logs for ninety days. Every account sees its own entries; administrators see the rest. Nothing is logged that could be used as a key.
Questions, answered
What data does 40thieves keep about my shop?
The copies of your listings and orders, your cost and pricing settings, your processed images and your system logs. It is your marketplace data reflected back to you, not a profile built around it.
Could an operator read my keys?
Your keys live in a locked vault; the system fetches them when it starts. They are never written to disk, and they never appear in user-facing errors or logs.
What happens if I am not approved yet?
You are refused before reaching any route that returns data. The access decision runs on every request, so an unapproved account cannot reach data through a direct call the interface does not show.
How long are my logs kept?
Ninety days, per account. Errors are notified as they happen rather than waiting to be found in a list, because a log nobody reads is not an audit trail.
Go deeper
- Trust and security — The overview: isolation, operating discipline and failure handling.
- The eBay integration — What your connection reads, and the two writes it can perform.
- Operations — What all of this protects: your orders, costs and listings.
Back to trust-and-security
Ask the questions you would ask any vendor.
Where the keys live, how accounts stay apart, whether a restore has been tested. The answers are here, not on request.
Get Started