Security
How your inventory is kept separate, and what we have not settled.
You are being asked to put your entire parts inventory into software from a company you have not heard of. Here is what is actually built, in enough detail to check.
One yard cannot see another
This is the guarantee everything else rests on, so it is enforced in more than one place rather than promised in a paragraph.
- Enforced at the database, not in the application
- Every tenant-scoped record carries the yard it belongs to, and every query is filtered by it by a fail-closed database plugin - not by a check somewhere in application code that a future refactor can drop. A query that arrives without a yard is refused rather than answered broadly.
- Uniqueness is per yard
- Every unique index is compound on the yard plus the business key, so two yards can hold the same SKU without colliding and neither can overwrite the other.
- It is tested per module, not once
- No module ships without its own tenant-isolation test. Isolation that is verified once during a review is isolation that stops being true the following month.
Every change has a record
Used parts move money, and disputes are settled by whoever can show what happened.
- Append-only audit trail
- Who approved a listing, where it sold, and the moment each channel ended. Rows are added, never edited or deleted - including by us.
- Kept ninety days past the sale
- Long enough to cover eBay returns and most payment disputes, then removed. See /limits if you need a longer archive.
- Nothing publishes without a named human
- The approval gate is a security property as much as a product one: every live listing traces to a person who approved it.
Accounts and access
- Your channel accounts stay yours
- YardTerminal connects to your eBay and Shopify accounts. It does not list under ours, and if you leave, your live listings keep running on your own accounts. We do not hold your storefront hostage to a renewal.
- Roles are per yard
- Staff are members of a yard with a role, and permissions are checked per action. Someone who can draft is not automatically someone who can approve.
- This site holds none of it
- The page you are reading is a separate application on a separate deployment. It has no access to the product database and never calls the product API. The only thing it collects is a waitlist email.
Not settled yet
In private beta, and stated plainly rather than left for you to discover during a procurement review.
- Hosting region and provider
- Not finalised. If data residency matters to you, ask before you commit and we will tell you where it stands that week.
- Backup and recovery targets
- No published RPO or RTO. There is no number here because there is not yet a number we would be willing to be held to.
- No third-party certification
- No SOC 2, no ISO 27001, no penetration test report. A pre-launch company claiming any of those is telling you something else about itself.
- No security contact process
- If you find something, email us and it reaches a person. There is no bug bounty and no formal disclosure timeline yet.
Ask us something specific.
Vague reassurance is worth nothing to an operator. A direct question gets a direct answer, including "we have not done that yet".