Trust
Security
How we think about protecting the LQDT Billing marketing site and the systems behind demo inquiries, without overstating certifications we have not claimed.
Marketing site
The public site is delivered over HTTPS via a CDN, with static assets hosted in a private object store. Unknown paths return a true not-found response rather than silent homepage duplicates.
Demo inquiries
Demo and contact submissions are processed through an API endpoint that emails our team. Form analytics are designed so names, emails, and phone numbers are not sent to analytics tools as event parameters.
Product direction
The LQDT Billing product is built around tenant boundaries, operational auditability, and careful handling of billing and access workflows. This page describes intent and website practices; it is not a customer security questionnaire or audit report.
What we do not claim here
This page does not assert SOC 2, PCI DSS, ISO, HIPAA, FedRAMP, or similar certifications. Ask us directly if you need a formal security review for a customer evaluation.
Report a concern
Security questions or reports: hello@lqdtbilling.io