Data Processing Addendum
Effective date: November 17, 2026 Last updated: November 17, 2026
This Data Processing Addendum (the "DPA") forms part of the Broker OS Terms of Service (the "Agreement") between MF Automations LLC, a Florida limited liability company, 233 NE 27th St, Miami, FL 33137 ("MFA"), and the customer that accepted the Agreement ("Customer"). It applies automatically when Customer accepts the Agreement; no separate signature is required. If Customer needs a countersigned copy, email maui@mfautomations.ai.
1. Definitions
Capitalised terms not defined here have the meanings in the Agreement.
- "Applicable Data Protection Law" means all U.S. federal and state laws governing the privacy, security or processing of Personal Information that apply to a party's processing under the Agreement, including the California Consumer Privacy Act as amended by the California Privacy Rights Act and its regulations ("CCPA"), other comprehensive state privacy laws, the Gramm-Leach-Bliley Act and its implementing rules, including the FTC Standards for Safeguarding Customer Information (16 C.F.R. Part 314, the "Safeguards Rule") and Regulation P or the FTC Privacy Rule (16 C.F.R. Part 313), and state data-security and breach-notification laws, including Fla. Stat. § 501.171.
- "Customer Personal Information" means Personal Information within Customer Data that MFA processes on Customer's behalf under the Agreement.
- "Personal Information" means information that identifies, relates to, describes, or is reasonably capable of being associated with an identified or identifiable individual or household, and includes "personal information", "personal data" and "nonpublic personal information" as defined by Applicable Data Protection Law.
- "Processing" means any operation performed on Personal Information, such as collection, recording, storage, retrieval, use, disclosure, transmission, alteration, deletion or destruction.
- "Security Incident" means a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, Customer Personal Information in MFA's or its Subprocessors' possession or control. Unsuccessful attempts that do not compromise the security of Customer Personal Information (such as blocked log-in attempts, pings, port scans and denial-of-service attacks) are not Security Incidents.
- "Subprocessor" means a third party engaged by MFA that processes Customer Personal Information to help MFA provide the Service.
2. Roles of the parties
2.1 Customer as controller and business. Customer determines the purposes and means of processing Customer Personal Information and is the controller, the "business" under the CCPA, and the equivalent under other Applicable Data Protection Law.
2.2 MFA as processor and service provider. MFA processes Customer Personal Information on Customer's behalf as its processor, its "service provider" under the CCPA, and its equivalent under other Applicable Data Protection Law.
2.3 GLBA. Where Customer is a "financial institution" under the Gramm-Leach-Bliley Act, or a service provider to one, and Customer Personal Information includes "customer information" or "nonpublic personal information", MFA is Customer's "service provider" under the Safeguards Rule (16 C.F.R. §§ 314.2 and 314.4(f)) and will maintain the safeguards required by Section 7 of this DPA. MFA will use and disclose such information only to perform services for Customer and as permitted by 16 C.F.R. §§ 313.13 to 313.15, and not for its own purposes.
2.4 Customer responsibilities. Customer is responsible for: (a) the lawfulness of the Personal Information it submits and the means by which it was obtained; (b) providing all notices and obtaining all consents and authorisations required for MFA to process Customer Personal Information under this DPA, including consents to be contacted by call or text, consents to call recording, and permissible purpose and authorisation to obtain consumer reports; (c) honouring individuals' rights requests as the business or controller; and (d) its own compliance with Applicable Data Protection Law. Customer's instructions must comply with Applicable Data Protection Law.
3. Processing on instructions
3.1 Instructions. MFA will process Customer Personal Information only on Customer's documented instructions. The Agreement, this DPA, Customer's configuration of the Service, and actions taken by Customer and its Users in the Service are Customer's complete instructions. Additional instructions require MFA's written agreement and may be subject to additional fees.
3.2 Unlawful instructions. MFA will inform Customer if, in MFA's opinion, an instruction violates Applicable Data Protection Law, and may decline to follow it.
3.3 Legal requirement. MFA may process Customer Personal Information as required by law, in which case MFA will inform Customer of that requirement before processing unless the law prohibits it.
3.4 Details of processing. The subject matter, duration, nature and purpose of processing, and the categories of data and individuals, are described in Annex 1.
4. CCPA service-provider terms
To the extent the CCPA applies, MFA: (a) will process Customer Personal Information only for the limited and specified business purposes of providing, securing, supporting and maintaining the Service as described in the Agreement and Annex 1 (the "Business Purposes"); (b) will not sell or share (as those terms are defined in the CCPA) Customer Personal Information; (c) will not retain, use or disclose Customer Personal Information for any purpose other than the Business Purposes, including for any commercial purpose other than the Business Purposes, or outside the direct business relationship between MFA and Customer, except as the CCPA permits; (d) will not combine Customer Personal Information with personal information it receives from or on behalf of another person, or collects from its own interactions with individuals, except as the CCPA and its regulations permit; (e) will comply with the CCPA and provide the same level of privacy protection as the CCPA requires of businesses; (f) will notify Customer if it determines it can no longer meet its obligations under the CCPA; (g) grants Customer the right, on notice, to take reasonable and appropriate steps to stop and remediate unauthorised use of Customer Personal Information, and to take reasonable steps to ensure MFA uses it consistently with Customer's CCPA obligations, including through the assessments in Section 10; and (h) certifies that it understands and will comply with these restrictions.
MFA may create and use de-identified or aggregated data under Section 11.6 of the Agreement, provided MFA takes reasonable measures to ensure it cannot be associated with an individual, publicly commits to maintain and use it in de-identified form, does not attempt to re-identify it, and contractually requires any recipient to do the same.
5. AI processing
MFA does not use Customer Personal Information to train generally available AI models, its own or any third party's. Where MFA uses third-party model providers to deliver AI Features, they are Subprocessors bound by Section 8 and may process Customer Personal Information only to return output to MFA.
6. Confidentiality of personnel
MFA will ensure that personnel authorised to process Customer Personal Information are bound by written confidentiality obligations, receive appropriate privacy and security training, and have access only to the extent necessary to perform their duties.
7. Security
7.1 Information security program. MFA will implement and maintain a written information security program with administrative, technical and physical safeguards appropriate to the size and complexity of its business, the nature and scope of its activities, and the sensitivity of Customer Personal Information, designed to (a) ensure the security and confidentiality of Customer Personal Information, (b) protect against anticipated threats or hazards to its security or integrity, and (c) protect against unauthorised access to or use of it that could result in substantial harm or inconvenience to any individual. The measures in place on the effective date are summarised in Annex 2 and described in the Security Overview.
7.2 Changes. MFA may update its security measures, provided the updates do not materially reduce the overall level of protection of Customer Personal Information.
7.3 Certifications. MFA does not currently hold SOC 2, ISO 27001, PCI DSS or HITRUST certifications or attestations and does not process protected health information. MFA does not store full payment-card numbers; payment cards are processed by Stripe.
7.4 Customer security responsibilities. Customer is responsible for the security of its accounts and devices, for configuring User roles and permissions appropriately, for enabling available security features such as step-up authentication, and for protecting Customer Personal Information it exports from the Service.
8. Subprocessors
8.1 Authorisation. Customer gives MFA general authorisation to engage Subprocessors. The current list, with each Subprocessor's function and location, is at https://brokeros.mfautomations.ai/legal/subprocessors. Examples include providers of cloud hosting (Vultr), telecommunications (Telnyx), payment processing (Stripe), productivity and email (Google Workspace), content delivery and security (Cloudflare), e-signature (DocuSign) and push notifications (Apple Push Notification service and Google Firebase Cloud Messaging).
8.2 Subprocessor obligations. MFA will (a) carry out reasonable due diligence on each Subprocessor's security practices before engaging it, (b) impose by written contract data-protection obligations no less protective than this DPA to the extent applicable to the services it provides, and (c) remain responsible to Customer for its Subprocessors' performance of those obligations.
8.3 New Subprocessors. MFA will give at least 30 days' notice before a new Subprocessor begins processing Customer Personal Information, by updating the Subprocessor List and notifying Customer by email (to the account owner or a contact who subscribes at maui@mfautomations.ai) or in the Service. In an emergency, such as the unplanned failure of a Subprocessor, MFA may give shorter notice and will explain why.
8.4 Objection. Customer may object to a new Subprocessor on reasonable data-protection grounds by emailing maui@mfautomations.ai within 30 days after notice. The parties will discuss the objection in good faith. If MFA cannot offer a commercially reasonable alternative within 30 days of the objection, Customer may terminate the affected part of the Service by written notice and receive a refund of prepaid Subscription Fees for the terminated part for the remainder of the term.
9. Security Incidents
9.1 Notice. MFA will notify Customer of a Security Incident without undue delay, and in any event no later than 72 hours after MFA confirms it. Notice will be sent to the account owner's email address and any security contact Customer designates.
9.2 Content. To the extent known, the notice will describe the nature of the Security Incident, the categories and approximate number of individuals and records affected, the likely consequences, the measures MFA has taken or proposes to take, and a contact point. MFA will provide further information as it becomes available.
9.3 Response. MFA will take reasonable steps to contain, investigate and remediate the Security Incident, and will reasonably cooperate with Customer so Customer can meet its own notification obligations to individuals, regulators (including any notice Customer must give the FTC under 16 C.F.R. § 314.4(j)) and others. Unless the law requires otherwise, Customer decides whether and how to notify affected individuals and regulators, and MFA will not notify Customer's affected individuals directly without Customer's approval.
9.4 No admission. MFA's notice of or response to a Security Incident is not an acknowledgment of fault or liability.
10. Assistance and audits
10.1 Rights requests. Taking into account the nature of the processing, MFA will provide reasonable assistance, primarily through the Service's self-serve tools (search, export, correction and deletion of records), to enable Customer to respond to individuals' requests to exercise their rights under Applicable Data Protection Law. If MFA receives a request directly from an individual about Customer Personal Information, MFA will refer the individual to Customer, notify Customer, and not respond itself except to confirm the referral.
10.2 Assessments. MFA will provide reasonable information Customer needs to carry out any data-protection assessment Applicable Data Protection Law requires of Customer.
10.3 Security information. On written request no more than once in any 12-month period (or after a Security Incident, or where a regulator requires), MFA will (a) answer a reasonable written security questionnaire, and (b) make available summaries of its information security program, policies and relevant test results, subject to confidentiality. If Customer reasonably demonstrates that this information is insufficient to verify MFA's compliance with this DPA, the parties will agree on the scope, timing, cost and confidentiality of a remote or on-site review by Customer or an independent auditor bound by confidentiality, conducted during business hours with at least 30 days' notice and without access to other customers' data.
10.4 Service-provider oversight. MFA acknowledges that Customer may be required to oversee its service providers under 16 C.F.R. § 314.4(f), and will provide the information in Section 10.3 for that purpose.
11. Data location and restricted data
11.1 Location. MFA hosts Customer Data in the United States. Subprocessors may process limited Customer Personal Information outside the United States only as described on the Subprocessor List.
11.2 Restricted data. The Service is designed for U.S. commercial-finance businesses. Customer will not submit to the Service (a) Personal Information governed by the EU or UK General Data Protection Regulation or other non-U.S. data-protection law, (b) protected health information under HIPAA, (c) full payment-card numbers outside Stripe-hosted fields, or (d) Personal Information of individuals under 18, unless MFA agrees in writing.
12. Return and deletion
12.1 During the Subscription Term, Customer may export and delete Customer Personal Information using the Service.
12.2 On expiry or termination of the Agreement, MFA will provide an export of Customer Data in CSV or JSON format on written request made within 30 days, and will then delete Customer Personal Information from its production systems within 60 days, except that (a) any copies in backups are deleted as those backups roll off on their normal cycle, and (b) MFA may retain Customer Personal Information subject to a legal hold or as required by law. Retained information remains subject to this DPA. On request, MFA will confirm deletion in writing.
12.3 MFA will dispose of Customer Personal Information in accordance with the disposal requirement of 16 C.F.R. § 314.4(c)(6) where it applies.
13. Liability and order of precedence
13.1 Each party's liability arising out of or relating to this DPA is subject to the limitations and exclusions in Section 17 of the Agreement.
13.2 If this DPA conflicts with the Agreement regarding the processing of Personal Information, this DPA controls.
13.3 This DPA ends when MFA no longer processes Customer Personal Information. Sections 9, 12 and 13 survive for as long as MFA holds Customer Personal Information.
Annex 1: Details of processing
| Item | Description |
|---|---|
| Subject matter | Provision of the Broker OS platform to Customer under the Agreement |
| Duration | The Subscription Term, plus the export and deletion periods in Section 12 |
| Nature of processing | Hosting, storage, organisation, retrieval, transmission (including calls, texts and emails Customer initiates), encryption, analysis (including AI Features), display, export and deletion |
| Purpose | Providing, securing, supporting and maintaining the Service for Customer: lead capture and consent records; CRM and deal pipeline; dialer and messaging; borrower portal, document collection and e-signature; lender matching; commission calculation and payout records; rep, employee and contractor onboarding (including tax and employment-eligibility forms); training and certification; licensing and registration tracking; reporting and audit logs |
| Categories of individuals | Customer's Users (owners, managers, employees, independent reps, contractors); job applicants and onboarding workers; leads and prospective borrowers; business owners, officers and guarantors of borrower businesses; lender and funder contacts; vendors and referral partners; individuals who call, text or email Customer through the Service |
| Categories of Personal Information | Identifiers and contact details (name, phone, email, address); business details (company, title, ownership percentage); consent records (consent text, timestamp, IP address, page, channel) and opt-out records; call and message metadata and content (text-message content; call recordings and transcripts once those features are available); deal and application data (requested amount, use of funds, revenue, bank statements, tax returns, financial statements); credit-related information Customer uploads or obtains; government identifiers (Social Security number, taxpayer ID, driver's licence or other ID documents); financial account information for payouts and deposits; employment and tax forms (W-4, I-9, W-9); commission, ranking and payout data; training and certification records; device and log data; e-signature records |
| Sensitive Personal Information | Social Security and taxpayer identification numbers; government ID numbers and images; financial account numbers; account log-in credentials; citizenship or immigration status as recorded on Form I-9. Processed only to provide the Service as Customer configures it |
| Frequency | Continuous during the Subscription Term |
Annex 2: Summary of security measures
- Encryption. Encryption of data in transit using TLS; field-level encryption of personal information stored in the Service, including government identifiers and financial account numbers; any backups MFA maintains are encrypted.
- Access control. Role-based permissions configurable by Customer; least-privilege access for MFA personnel, limited to those who need it to operate and support the Service; step-up authentication for sensitive actions; credentials stored as salted password hashes; secrets held in a dedicated secrets store and not in source code.
- Audit logging. An owner-visible audit log of significant actions in the Service; logging of administrative access by MFA personnel.
- Network and application security. Edge protection and bot management; separation of production from development; code review before deployment; automated secret scanning of code changes; dependency updates.
- Availability and backups. Backup and restore measures as described in the Security Overview (automated backups with point-in-time recovery are on the roadmap and not yet guaranteed during Early Access); monitoring of availability against the SLA.
- Personnel. Confidentiality obligations and security training for personnel with access to Customer Data; prompt removal of access on role change or departure.
- Vendor management. Due diligence and contractual safeguards for Subprocessors (Section 8).
- Incident response. A documented incident-response process, including the notification commitments in Section 9.
- Program governance. A designated individual responsible for the information security program; periodic risk assessment; annual review of the program, as contemplated by 16 C.F.R. § 314.4.
Contact
MF Automations LLC, 233 NE 27th St, Miami, FL 33137 Maui · (305) 216-3272 · maui@mfautomations.ai
Questions: maui@mfautomations.ai