bullionOS / Policies
Billing & Refund Policy
Last updated September 22, 2026
How fees, renewal, cancellation and refund requests relate to your subscription agreement.
Last updated: September 22, 2026
Policy center
Review website, service, billing, accessibility and cookie notices without leaving the bullionOS design system.
1. Agreed charges
Your accepted order form, statement of work or agreement states the price, currency, billing interval, service term, setup fees, migration fees, customization charges, usage charges, taxes and payment method. Requesting a demo, viewing this website or submitting a form does not start a paid subscription or authorize payment.
If a quote, order form or invoice conflicts with this website policy, the signed or accepted customer agreement controls, subject to mandatory law.
2. Setup, onboarding and custom work
Setup, onboarding, migration, training, configuration, integration and custom-development charges are governed by the agreed scope. Fees for work already started, reserved resources, delivered milestones or third-party costs may be non-refundable where agreed and permitted by law.
Customer is responsible for timely access, data, approvals and decisions needed for onboarding. Delays caused by missing customer inputs do not automatically extend payment deadlines unless the agreement says so.
3. Recurring billing, renewal and price changes
Recurring charges require an accepted subscription and payment authorization. Billing frequency, renewal term, cancellation deadline, notice period and any price-change process must be disclosed in the accepted order, signup terms or agreement.
bullionOS will not treat a public website visit or demo request as consent to auto-renewal or recurring billing. Renewal and cancellation rights required by applicable law remain available even if not repeated in this policy.
4. Cancel a subscription
Use the cancellation method stated in your agreement. If no method is stated, email billing@bullionos.co from an authorized company address with the company name, account email, requested effective date and enough information to identify the subscription. Do not send payment-card details.
Cancellation stops future renewal only as provided in the agreement and applicable law. It does not automatically refund fees for the current paid term, completed work, setup, usage, third-party costs or custom work unless the agreement or law requires otherwise.
5. Refunds, disputes and chargebacks
Unless your agreement or applicable law provides otherwise, fees are non-refundable once service starts or work begins. Refunds, credits or service extensions are discretionary unless required by the agreement or law.
Report suspected billing errors promptly to billing@bullionos.co with the invoice number, amount, date and reason. Customers should cooperate in good faith before initiating a chargeback. A chargeback does not cancel the agreement, waive amounts owed or resolve disputed services unless required by law.
6. Late payments and additional use
Overdue charges may lead to late fees, collection costs, restricted access or suspension as permitted by the agreement and applicable law, including any required notice or cure period. bullionOS may restore access after payment and resolution of the underlying issue.
Additional storage, users, locations, integrations, market-data connections, support, migration, training or custom work is chargeable only under disclosed, accepted rates or separately agreed work.
7. Taxes, records and policy changes
Quotes and orders should state whether applicable taxes are included. Customer is responsible for taxes, duties, withholding or similar charges except taxes based on bullionOS income, unless the agreement says otherwise.
Keep invoices, receipts and account notices for your records. Updates to this policy apply prospectively and do not retroactively change agreed fees, renewal terms, cancellation rights, refund rights or tax obligations. Where this policy conflicts with a signed agreement, the agreement controls, subject to mandatory law.
Need help finding the right policy?
Bring the question to a bullionOS walkthrough and we will route it to the right team.

