Legal
in plain words.
Every agreement that governs buying from Bridgemont or selling licences to it, written to be read rather than skimmed past. If something here is unclear, that's a problem with the document — tell us and we'll fix it.
Bridgemont Technologies LLC ("Bridgemont") is the seller on every sale. It buys licences for software and other digital products — the types listed in clause 12.1 of the Acceptable Use Policy — from a small, closed group of independent developers ("Suppliers"), and resells them to Buyers in its own name, as one-time purchases. The Buyer's contract is with Bridgemont alone: Bridgemont takes the payment, issues the receipt, delivers the product, answers all support, and handles refunds and complaints.
Every product Bridgemont sells has a public product page on checkout.bridgemont.io, and every product and its developer is listed on Bridgemont's Approved developers page. A Buyer usually finds a product on the developer's own website and clicks its Buy button, which opens Bridgemont's product page. That page shows the product, Bridgemont's price, that the product is sold by Bridgemont Technologies LLC, and Bridgemont's terms, licence, refund policy and support contact. The Buyer pays Bridgemont there, by card.
Suppliers are Bridgemont's vendors — companies and sole traders that make the products or hold the rights to sell them. Bridgemont works with them by invitation only. It checks every Supplier, and reviews every product and every Supplier website, before a product goes on sale. Each product has a fixed wholesale price written in the purchase agreement. Bridgemont sets every retail price, and a Supplier's price request is advice only. A Supplier is not the seller, does not take the Buyer's payment, has no contract with the Buyer, gets no Buyer data, and does not contact Buyers.
Card processing and acquiring are performed for Bridgemont by licensed payment institutions engaged by Bridgemont. Bridgemont does not perform those regulated payment services itself, and it takes payment only for its own sales, never for Suppliers or anyone else.
If you are a developer supplying Bridgemont: Bridgemont buys each licence at a fixed US dollar wholesale price for each product, written in your purchase agreement and changed only by written amendment signed by both parties, at most once a quarter. Bridgemont buys an opening block of about 20 licence keys for each product, prepaid and non-refundable. After that, Bridgemont pays against a monthly purchase statement: licences bought × wholesale price. Each statement is paid 30 days after the end of each month, paid in USDC, only to a wallet you have proved you own (a signed message from that wallet) and that passes sanctions screening. 10% of each statement is held as a reserve for 120 days. Bridgemont carries card-fraud chargebacks, goodwill refunds and its own promotions. You pay only for refunds and chargebacks caused by a fault in your product, and for fraud you caused. The Supplier Agreement sets out the detail.
Buyers buy from Bridgemont and contract with Bridgemont. Developers sell licences to Bridgemont, not to buyers, and have no contract with the buyer.
Bridgemont takes payment only for its own sales, on its own checkout. It does not take payments for developers or anyone else.
Buying from Bridgemont
The terms of every sale, getting your money back, and the licence that comes with each product.
Privacy
What personal data Bridgemont collects, why, and the few cookies it uses.
Developers
How Bridgemont buys licences from developers, pays for them, and checks their websites.
Rules
What Bridgemont will and will not sell, and how its websites may be used.
Rights
Intellectual property, and who Bridgemont is.
Report a problem with a product
An order that went wrong, a product that infringes someone's rights, a product Bridgemont should not sell, a scam, or a misleading product page. 9 categories. Bridgemont is the seller, so Bridgemont handles every report itself. A person reads each one, and Bridgemont tells you what it decided and why.
Ask a question
Contract questions, privacy and data requests, or a passage in one of these documents that reads ambiguously — if it does, that's our problem to fix. The Privacy Policy commits to answering data requests within one month. A person reads every message.
10 documents · Bridgemont Technologies LLC · United States