How BlueList.ai protects its clients from coordination risk under federal election law.
BlueList.ai provides political data analytics, voter targeting, and media buying services to Democratic campaigns, committees, PACs, and independent expenditure organizations. Some of our clients operate in the same races. That creates a legal risk called coordination.
Under federal election law, if a vendor like BlueList passes strategic information from one client to another—even unintentionally—the resulting communication can be treated as an illegal in-kind contribution. The consequences fall on our clients as much as on us: contribution limit violations, prohibited contribution findings, FEC complaints, and reputational damage.
We maintain this firewall because protecting our clients from coordination risk is a non-negotiable part of the service we provide. It is not optional. It is how we operate.
This policy is built on the common vendor firewall safe harbor established by the Federal Election Commission at 11 CFR § 109.21(h). Here is what that regulation requires, in plain terms:
A commercial vendor that serves multiple political clients can avoid a coordination finding by designing and implementing a written firewall policy that prohibits the flow of information between the teams serving different clients—and distributing that policy to all affected employees, consultants, and clients.
The safe harbor is destroyed if, despite the firewall, information about a candidate’s campaign plans, projects, activities, or needs that is material to the creation, production, or distribution of a communication is used by or conveyed to another client. That is the line this policy exists to hold.
This policy applies to every person who performs work for or on behalf of BlueList.ai:
We refer to these individuals collectively as Covered Persons. Every Covered Person receives a copy of this policy and signs a written acknowledgment before beginning work.
Before accepting any new engagement, we evaluate whether the prospective client creates a coordination risk with any existing client—specifically, whether both clients reference the same federal candidate (as supporter or opponent) or are active in the same race. If a conflict exists that we cannot safely manage under this policy, we decline the engagement.
When we serve clients that present a coordination risk, we assign completely separate service teams to each client. We call these Walled Teams. The rules are strict:
The following categories of information may never flow between Walled Teams, in any form—verbal, written, electronic, or through shared system access:
Consistent with FEC rules, information obtained exclusively from public sources—FEC filings, public voter files, published news, public social media—is not subject to this firewall. However, public information that has been enhanced or analyzed using a client’s Protected Information is treated as Protected. When in doubt, we treat information as Protected.
The FEC’s common vendor standard looks back 120 days. If a Covered Person transitions from one Walled Team to another involving a conflicting client, they go through a documented debriefing and cannot begin work on the new team until the Compliance Officer confirms appropriate safeguards are in place.
Information barriers only work if the technology enforces them. Our data controls include:
Client data lives in separate, access-controlled environments. No shared repository holds Protected Information from conflicting clients.
Permissions are configured per Walled Team. Only team members can access their client’s data. Permissions are updated whenever assignments change.
All access to client data is logged with identity, timestamp, and nature of access. Logs are retained for at least three years.
Walled Teams use separate communication channels. No shared email threads, messaging channels, or project boards across conflicting engagements.
BlueList uses AI and machine learning in its political analytics work. AI models can inadvertently carry information between clients if not properly managed. We apply additional safeguards:
When you engage BlueList.ai, you receive:
We ask that clients also respect the firewall by not requesting information about other BlueList clients. Our engagement letters include this obligation.
Any Covered Person who becomes aware of a potential breach—any unauthorized disclosure, access, or use of Protected Information across Walled Teams—is required to report it to the Compliance Officer immediately. There is no retaliation for good-faith reporting.
When a potential breach is reported, we:
Remedial actions range from immediate reassignment and access revocation to engagement of outside counsel, client notification, and, in severe cases, withdrawal from conflicting engagements. Violations of this policy may result in termination of employment or contract.
If you have questions about this policy, how it applies to a specific engagement, or how BlueList.ai manages coordination risk, contact our Compliance Officer:
BlueList.ai LLC
Compliance Officer
compliance@bluelist.ai
This policy is reviewed and updated at least annually. Material changes are communicated to all Covered Persons and active clients. The internal version of this policy, which includes detailed operational procedures and the employee/contractor acknowledgment form, is available upon request to current and prospective clients.
Disclaimer. This policy reflects BlueList.ai LLC’s operational commitments under applicable FEC regulations as of the date above. It is published for transparency and does not constitute legal advice. Nothing in this policy creates an attorney-client relationship. Campaign committees and other political organizations should consult their own legal counsel regarding coordination compliance.