Trust & Security

BailLink handles sensitive information at every step of the bail process — personal identifiers, signatures, payment details, and legal documents. Trust is not a marketing word for us; it's the table stakes of operating in this industry. This page describes how we approach security, what our infrastructure looks like at a high level, and how compliance responsibilities are divided between BailLink, our vendors, and our Agency Customers.

Our Security Philosophy

• Built on SOC 2-compliant infrastructure providers. We select vendors that publish audited security reports and maintain industry-recognized certifications, rather than building security-sensitive components from scratch.
• Payments handled by Stripe, a PCI Level 1 Service Provider. Card and bank-account numbers never touch our servers.
• Designed with security-focused vendors and best practices. We use mainstream, well-audited components for identity, storage, messaging, and monitoring.
• Least exposure of sensitive data. We avoid logging or persisting information that doesn't need to be retained, and we encrypt what does.
• Shared responsibility. Compliance is shared between our platform, our vendors, and our customer's own configuration and operational practices.

What We Protect Against

The threats we design against include credential theft, unauthorized access between tenants, leakage of sensitive identifiers (SSN, ID images, signatures), payment fraud, abuse of public endpoints, phishing of indemnitors, and accidental exposure through misconfiguration.

Architecture, at a High Level

We avoid publishing low-level architecture details, but here is what is relevant to assessing our posture:

Tenant Isolation

Every Agency Customer operates within its own logical tenant. Tenant isolation is enforced at the database level using row-level security policies — not just at the application layer — so queries cannot accidentally cross tenant boundaries. Storage objects are scoped to tenant paths and accessed only through short-lived signed URLs.

Authentication

Agency users authenticate through a dedicated identity provider with support for strong password policies, email verification, and multi-factor authentication. Platform administrators authenticate separately, with role-based access controls. Bond parties (indemnitors, defendants) do not have permanent accounts — they access the Service only through single-use, time-limited, IP-bound magic links sent by the Agency Customer.

Data Encryption

• In transit: All connections use TLS.
• At rest: Sensitive fields, including Social Security numbers, are encrypted at the application or database layer.
• Storage: Private buckets only. File downloads are issued as signed URLs with short TTLs (approximately 10 minutes).

Payments

Card and bank data are collected, tokenized, and processed by Stripe. BailLink never sees a full card number. Funds flow directly to the Agency Customer's Stripe Connect account; BailLink does not hold customer funds and is not a money transmitter.

Document Integrity

Generated documents (applications, indemnity agreements, receipts) are immutable once executed and are payment-gated when applicable, meaning final documents are not released until the associated premium is paid.

Abuse Prevention

We rate-limit public-facing and signing endpoints, use bot-protection challenges on public forms, monitor for anomalous traffic, and operate background jobs in an isolated job runner.

Monitoring

Application errors and security-relevant events are tracked. We deliberately exclude the following from operational logs: full Social Security numbers, full dates of birth, signature images, and uploaded government-ID images.

Subprocessors

We rely on a curated set of third-party providers, each chosen for its security track record. These include providers for identity, database and file storage, payment processing, transactional email, SMS messaging, mapping, background processing, rate limiting, hosting, error monitoring, and bot protection. A current named list is available on request at support@baillinkusa.com.

Compliance Framework

BailLink itself is not a certifying body, and the bail industry does not have a single overarching federal compliance framework comparable to HIPAA in healthcare. Our compliance posture is built on:

• Selection of SOC 2-compliant and PCI-compliant infrastructure providers
• Adherence to PCI-DSS scoping practices (we do not store cardholder data)
• Compliance with U.S. consumer-protection and electronic-signature laws (E-SIGN, UETA)
• Compliance with the Telephone Consumer Protection Act (TCPA) and CTIA/carrier 10DLC requirements for SMS
• Compliance with applicable U.S. state privacy laws (including CCPA/CPRA, CPA, VCDPA, and others)
• Reasonable safeguards consistent with the Federal Trade Commission's expectations under Section 5

Where Agency Customers operate in states with bail-specific recordkeeping or licensing requirements, the Agency Customer remains responsible for that compliance; BailLink provides tools (audit logs, document retention, exports) that support those obligations.

Shared Responsibility

Security and compliance work because every party does its part:

BailLink's responsibility:

• Secure platform engineering and operation
• Tenant isolation, encryption, and access controls
• Vendor selection and oversight
• Logging and alerting
• Incident response on the platform layer

Vendor (subprocessor) responsibility:

• Physical and infrastructure security
• Their own certifications (SOC 2, PCI, etc.)
• Service-level reliability

Agency Customer responsibility:

• Protecting login credentials and using MFA
• Promptly removing users who leave the agency
• Verifying the identity of indemnitors and defendants
• Sending magic links to the correct contact details
• Lawful collection and use of bond-party information
• State licensing, surety, and recordkeeping compliance
• Appropriate retention configuration for their jurisdiction

Reporting a Vulnerability

If you believe you have found a security vulnerability in the Service, please email support@baillinkusa.com with details. We ask that you give us reasonable time to investigate and remediate before public disclosure, and that you do not access or alter data belonging to anyone other than yourself during testing.

Reporting an Incident or Suspected Account Compromise

If you suspect your account has been compromised, or you believe sensitive information has been exposed, contact us immediately at support@baillinkusa.com or 954-860-8225.

Updates

We update this page as our practices evolve. The most recent revision date is reflected at the bottom of each major section in our policies. For specific questions, reach out at the contacts above.

Bail Link LLC Phone: 954-860-8225 General: info@baillinkusa.com Security & Technical: support@baillinkusa.com