bullionOS / Security
Review security before you deploy.
Last updated September 22, 2026
Security review information for teams evaluating bullionOS workflows and access requirements.
Updated: September 22, 2026
Dealer operating system
Keep evaluation, rollout and contact pages inside the bullionOS design system.
Access and permissions
Define who can view, create, approve and reconcile operational records. Separate daily desk actions from administrative controls so users only receive access needed for their work.
Sensitive operational data
Dealer workflows can involve customer, invoice, shipment and payment-adjacent information. Do not submit passwords, payment card data, identity documents or privileged records through public website forms.
Vendor and hosting review
Evaluate hosting, backups, retention, integrations, email delivery and support paths as part of your onboarding review. Confirm any formal security documentation required by your organization before launch.
Incident routing
Report suspected unauthorized access, misdirected data or security concerns through your account contact or the published contact route so the issue can be triaged with the right operational context.
Deployment readiness
Before production use, confirm user lists, role assignments, import scope, support owners, fallback processes and any required contractual security commitments.
See bullionOS against your dealer day.
Bring the workflow you want to pressure-test and we will map appointments, inventory, invoices, shipping and payments.