Broker OSEARLY ACCESS
Home / Legal / Security Overview

Security Overview

Effective date: November 17, 2026 Last updated: November 17, 2026

Provider: MF Automations LLC ("MFA"), 233 NE 27th St, Miami, FL 33137 Contact: Maui · (305) 216-3272 · maui@mfautomations.ai

This page describes the security controls that are built into Broker OS today. Broker OS is in early access. We list only what exists in the product. Where a control is planned but not yet in place, it appears under "On the roadmap" and is labelled as such.

Certifications. MFA does not currently hold, and does not claim, SOC 2, ISO 27001, PCI DSS, HIPAA or any other third-party security certification or attestation.

1. Encryption

Field-level encryption of personal data. Personal and sensitive fields are encrypted in the application before they are written to the database, using AES-256-GCM. This covers, among others, names, legal names, email addresses, phone numbers, postal addresses, dates of birth, IP addresses, device labels, notes and message bodies, and stored integration credentials (123 encrypted column definitions in the schema). Each ciphertext is bound to its tenant, table, column and row, so a value copied to another record or another customer's account cannot be decrypted.

Separate vault for the most sensitive identifiers. Social Security numbers and similar identifiers are tokenized into a separate database vault. The application role has no direct table access to the vault; it can only call controlled functions, and every read is logged.

Searching encrypted data. Exact-match lookups (for example, finding a duplicate phone number) use keyed blind indexes derived per customer, so the database never needs the plaintext value.

Files. Uploaded documents are encrypted with a random per-file key using AES-256-GCM. Download links are signed and expire within 5 minutes.

Key management. Each customer account has its own data-encryption keys (separate keys for fields, files and the vault). Those keys are stored only in wrapped (encrypted) form, wrapped with a per-environment key-encryption key using AES-256-GCM. Key-encryption keys and other root secrets are held in MFA's secret store, delivered to the application server at deploy time with restrictive file permissions, and are never stored in the database or in source code. The blind-index root key is separate from the key-encryption key, and the application refuses to start if they are the same.

Key rotation. The platform supports rotating a customer's data-encryption keys (new version becomes active, older versions are kept for decryption only until data is re-encrypted) and rotating the key-encryption key with a dual-key window. Session-signing secrets support rotation with an overlap period.

In transit. The Broker OS web server configuration accepts TLS 1.3 only, redirects HTTP to HTTPS, and sends HTTP Strict Transport Security. Browser security headers prevent framing and MIME sniffing and restrict camera, microphone and location access.

2. Customer isolation

Every customer is a separate tenant. Every database table that holds customer data carries a tenant identifier and is protected by PostgreSQL Row-Level Security, enabled and forced, so a database session can read or write only the rows of the tenant it is acting for. The policy is applied automatically to every new table when it is created, not maintained by hand.

The application connects with a restricted database role that cannot create objects, cannot truncate tables, and has read-only access to platform-managed tables.

3. Sign-in and accounts

Passwords. Passwords are hashed with Argon2id (64 MiB memory, 3 iterations, parallelism 1, 16-byte salt) plus a server-side secret ("pepper") that is not stored in the database. Passwords must be 12 to 128 characters, and new passwords are checked against known breached-password lists using a k-anonymity range query, so the password itself is never sent.

Multi-factor authentication. Broker OS supports time-based one-time passcodes (TOTP, from any standard authenticator app) and passkeys (WebAuthn). Passkeys are registered as discoverable credentials with user verification required. Ten single-use recovery codes are issued at TOTP enrollment and stored hashed. MFA is required for every staff role (owner, admin, compliance officer, manager, processor, underwriter, HR admin, finance, employee) and can be required for any other user.

Step-up verification. Sensitive actions (for example, exporting the audit log or rotating keys) require the user to re-verify with TOTP or a passkey; the step-up is valid for 5 minutes.

Sessions. Session cookies are HttpOnly, Secure and SameSite=Lax. Sessions expire after inactivity (by default 30 minutes for staff and client-portal users, 60 minutes for reps; adjustable per account within fixed limits) and after an absolute lifetime (by default 12 hours, maximum 24). Users can see and sign out their own active sessions, and a password reset signs out every other session.

Brute-force protection. By default an account is locked for 15 minutes after 10 failed sign-ins within 15 minutes, failed attempts from one network address across many accounts are also throttled, and password-reset requests are rate limited. The web server additionally rate limits sign-in and public form endpoints per IP address.

Cross-site request forgery. In addition to SameSite cookies, the application rejects cookie-authenticated requests whose Origin header does not match the site.

4. Access control

Access inside a customer account is role-based. Broker OS ships with defined roles (owner, admin, compliance officer, manager, rep, processor, underwriter, employee, HR admin, finance, auditor and others) and a permission matrix that is checked on the server for every request. Revealing masked personal data in admin views is recorded in the audit log.

MFA staff access. MFA's internal administration console is bound to MFA's private network only and is not reachable from the public internet. MFA administrators sign in with hardware-backed passkeys. Emergency ("break-glass") access by MFA staff to a customer account is time-limited, recorded in both the customer's and MFA's audit logs, and triggers a notice to the customer's account owners.

5. Audit log

Security-relevant and business actions (sign-ins, MFA events, permission changes, data reveals, call supervision, consent changes and more) are written to an append-only audit log. Each entry is chained to the previous one with a SHA-256 hash, the database rejects any update or deletion of audit entries, and a verification tool recomputes the whole chain to detect tampering. Audit entries are checked so that they do not contain personal data. Account administrators can search the log and, after step-up verification, export it.

6. Logging

Server logs are structured and designed to exclude personal data: code only logs approved identifier fields, and a redaction list removes names, emails, phone numbers, SSNs, EINs, dates of birth, addresses, message bodies, transcripts, passwords, tokens and authorization headers as a second line of defence.

7. Calling and messaging safeguards

Every outbound call, text and marketing email passes a compliance gate on the server before it can be placed. The gate checks the user's certification and licensing, the internal do-not-call list and consent-revocation ledger, federal and state do-not-call scrub results, known-litigator flags, the consent level required for the channel, reassigned-number data, permitted calling hours in every time zone that may apply to the number, attempt limits, caller ID and disclosure requirements. Each decision is recorded. If scrub data is missing or stale, marketing calls and texts are refused rather than allowed. Inbound STOP-type replies (English and Spanish) revoke consent for that number. A call cannot be started without a single-use, short-lived token issued by the gate.

8. Integrations and webhooks

Inbound webhooks from payment, telephony, e-signature and other providers are rejected unless their signature verifies (for example, Stripe signatures and Telnyx Ed25519 signatures), with a 5-minute replay window. Credentials that a customer stores for an integration are encrypted and are never shown again in the interface or the API.

9. Payments

Card payments for Broker OS subscriptions are processed by Stripe. MFA does not receive or store full card numbers.

10. Hosting

Broker OS runs on servers in the United States, currently in Vultr's Miami, Florida region. DNS is managed with Cloudflare.

11. Development practices

Source code changes go through pull requests and automated checks, including secret scanning on every change. Secrets are kept out of source code and delivered from a secret store at deploy time.

12. Your data

Client-portal users can submit access, deletion and correction requests inside Broker OS; each request is recorded and handled by MFA and the customer. Account owners can export reports as CSV. To request a full export or deletion of your account's data, email maui@mfautomations.ai. Data export and deletion timelines are set out in the Terms of Service and the Data Processing Addendum.

13. On the roadmap

The following are planned and are not in place today:

  • Automated, encrypted database backups with point-in-time recovery stored in a second region, and a monthly restore test. (Until then, backup frequency and retention are not guaranteed by this page.)
  • Malware scanning of uploaded files.
  • Automated dependency vulnerability scanning in the build pipeline.
  • An administrator view of every user's active sessions with per-session revocation, and sign-in history with device and network details.
  • Self-serve full-account data export and automated deletion on account closure.
  • Certificate pinning in the mobile apps.
  • An independent third-party penetration test.

14. Reporting a vulnerability

If you believe you have found a security vulnerability in Broker OS, email maui@mfautomations.ai with "Security" in the subject line. Please include a description, the steps to reproduce it, and the affected URL or feature. We will acknowledge your report within 3 business days and keep you informed as we investigate.

Safe harbor. We will not pursue legal action against, or ask law enforcement to investigate, anyone who in good faith: reports a vulnerability to us promptly; makes a reasonable effort to avoid privacy violations, data destruction and service disruption; accesses only the minimum data needed to demonstrate the issue and does not keep, share or use it; does not test against accounts other than their own without permission; does not use social engineering, physical attacks or denial-of-service testing; and gives us reasonable time to fix the issue before any public disclosure. This safe harbor applies only to MFA's own systems and does not authorize testing of third-party services.

15. Reporting a security incident

If you suspect unauthorised access to your Broker OS account, contact us immediately at maui@mfautomations.ai or (305) 216-3272. Our commitments on notifying customers of a security incident involving their data are set out in the Data Processing Addendum.

Questions: maui@mfautomations.ai