Trust
Security
How Bridge to Brands handles dealer-portal credentials, API keys, tenant isolation, consumer data and portal traffic. Written for procurement and security reviews.
Portal credentials stay in the web app
Dealer-portal logins are entered only at app.brdg2b.ai, encrypted at rest, and decrypted only inside the worker that talks to that portal. API keys and MCP tokens can never read, change or mint them.
Orders placed only within your limits
Every order is staged first and read back line by line. It is placed only for brands verified on a live account, where you turned submitting on, within your caps and confirmation settings. One submit per order, never retried blind; an unknown outcome is checked in the portal before anything else happens.
Tenant isolation
Every database statement is scoped to the account (tenant) that owns the data, and every repository is tested to prove one account cannot read another’s data.
Keys you can scope and revoke
API keys carry scopes (read, orders), optional brand and IP allowlists and expiry. OAuth tokens for ChatGPT and Claude are bound to a key; revoking the key disconnects them.
Consumer data is redacted
Consumer name, address, phone, email and drop-ship PO are redacted from every log line and error message, and sent only to the brand portal that ships the order.
Polite to the brands
One live session per dealer connection on one worker, and every portal call is paced. Your volume never turns into a burst against a brand’s portal.
Every action is metered
Searches, results, orders and lines are recorded per key, success or failure, so you can see exactly what each integration or agent did.
Report a vulnerability: see security.txt.