Legal
Review our terms of service, privacy practices, and other important legal agreements.
Terms of Service
The terms governing subscriptions, invoicing operations, merchant processing, and accounts.
Privacy Policy
Learn how we collect, store, and protect data with zero retention of full card numbers or security codes.
Data Processing Addendum
Our GDPR Article 28 commitments, technical safeguards, and international data transfer clauses.
Acceptable Use Policy
Rules governing platform conduct, anti-fraud standards, and autonomous AI assistant guardrails.
Service Level Agreement
Our 99.9% availability target for the REST API, client portal and pay pages: a goal, not a commitment.
Cookie Policy
Details on our cookieless default, analytics opt-in toggle, and browser session storage.
Subprocessors
The complete list of third-party infrastructure and service providers that process platform data.
E-Sign Consent
Your consent to receive records electronically and to sign estimates and payment authorizations online.
Text Message Terms
What texts are sent through BillingMart, how you opt in, and how STOP and HELP work.
Accessibility Statement
The accessibility standard we aim for, what we do, and how to report a barrier.
US State Privacy Rights
A privacy notice for each US state with its own privacy law, from California to Virginia.
Data Removal Request
Ask us to delete, copy or correct your personal information, or appeal a decision.
Partner Program Agreement
The terms a referral partner signs: attribution, commission, statements, payouts, conduct rules and termination.
Security Architecture
Our security safeguards: AES-256-GCM encryption, isolated card entry, and write-once audit trails.
Contractual commitments backed by code
Unlike platforms that rely solely on policy documents, BillingMart enforces its legal and privacy commitments at the compiler, database rules, and architecture level.
Zero Card Storage
Full card numbers and security codes exist solely as volatile memory variables in the charging function. We store only the card type and last 4 digits, and card entry is isolated on a separate payment page.
Server Arithmetic
Totals cannot be tampered with on client devices. Invoices and charges re-derive all sums server-side in integer minor units from verified line items.
Verified Contacts Only
Invoices and payment links resolve only through cryptographically verified customer email or phone contacts, preventing unauthenticated access or misdelivery.
Human approval and Auto rules
AI assistants connected over MCP, and the built-in BillingMart Agent, can read, draft and request actions. Sending to a customer or moving money happens only when a signed-in person approves it, or when the workspace owner's capped Auto rules cover it. Starting a card or bank payment, and every administrative action, always needs a person.
Need enterprise legal terms or custom agreements?
Enterprise customers can contact us to discuss agreement terms.