Sovereign Immunity Not Existent in Trade Secrets Case

Some legal headlines stroll into the room politely. Others kick the door open, spill coffee on the carpet, and announce, “Sovereign immunity is not existent!” This case lands somewhere in the second category. But once the drama settles down, the real story is even more interesting. In AQuate II, LLC v. Myers, the U.S. Court of Appeals for the Eleventh Circuit did not erase tribal sovereign immunity from the map. It did something narrower and more important: it held that, in this dispute, a tribally owned contractor had already waived immunity for claims related to its participation in the Small Business Administration’s 8(a) Business Development Program.

That distinction matters. A lot. Tribal sovereign immunity remains a powerful doctrine in American law. But powerful does not mean magical, and it definitely does not mean immune to the tribe’s own waiver language. When a tribally owned business joins the SBA’s 8(a) program, it must include specific “sue and be sued” or waiver language in its organizing documents for matters relating to SBA programs. In AQuate II, that requirement became the hinge on which the trade secrets lawsuit swung wide open.

For businesses, government contractors, HR teams, compliance officers, and lawyers who live in the land of bids, proposals, confidential information, and employment exits, this case is a flashing neon sign. It says: read the waiver language, understand the program rules, and do not assume sovereign immunity will rescue a company from a trade secrets claim tied to federal contracting activity. Courts, it turns out, can read plain English too.

What Happened in the Case?

The dispute arose between two tribally owned government contractors competing in the SBA’s 8(a) program. AQuate II alleged that a former employee, Jessica Myers, left the company with confidential information and later used that information to help a competing tribal contractor, Kituwah, pursue the rebid of a federal security services contract. According to the allegations, the information included contract terms, proposals, compensation details, personnel information, and bidding strategies related to the Sea-Based X-Band Radar-1 vessel, commonly called SBX-1.

AQuate sued under the federal Defend Trade Secrets Act and the Alabama Trade Secrets Act, along with a breach of contract claim against the former employee. Kituwah responded with a sovereign immunity defense. The district court initially accepted that argument, reasoning that the claims did not sufficiently “relate to” participation in the 8(a) program. The court also dismissed related claims against the former employee and relied on a forum-selection clause for the contract claim.

Then the Eleventh Circuit stepped in and said, in essence, not so fast. The appellate court took a broader and more practical view of the phrase “related to.” If the alleged misuse of trade secrets was aimed at winning an 8(a) contract, the court reasoned, the claims were related to the contractor’s participation in the 8(a) program. Put less formally: if you allegedly grabbed confidential bid intelligence to compete for an 8(a) contract, you cannot pretend the fight has nothing to do with the 8(a) program. That argument did not survive contact with common sense.

Why Sovereign Immunity Usually Matters So Much

Tribal sovereign immunity is no minor procedural speed bump. The U.S. Supreme Court has repeatedly recognized that federally recognized tribes generally enjoy immunity from suit unless Congress authorizes the suit or the tribe clearly waives immunity. Cases such as Kiowa Tribe of Oklahoma v. Manufacturing Technologies and Michigan v. Bay Mills Indian Community confirm how broad that protection can be, including in commercial settings. In other words, sovereign immunity is not a dusty museum artifact. It is alive, well, and capable of shutting down litigation fast.

At the same time, the Supreme Court has also made clear that a tribe can waive immunity through clear contractual or organizational language. That principle appeared in C & L Enterprises, Inc. v. Citizen Band Potawatomi Tribe of Oklahoma, where the Court held that the tribe had waived immunity through the contract structure it adopted. So the big rule is actually a two-step dance: immunity is strong, but waiver is real.

That legal background explains why AQuate II is important. The case did not invent a new exception out of thin air. Instead, it applied an old and familiar principle to a modern government-contracting dispute involving confidential information, competitive bids, and program-specific waiver language. No legal sorcery, just document reading with consequences.

The 8(a) Program Is the Plot Twist

The SBA’s 8(a) Business Development Program is designed to help socially and economically disadvantaged businesses compete in the federal marketplace. It offers training, technical assistance, and access to contracting opportunities. It also extends eligibility to certain businesses owned by Indian tribes, Alaska Native corporations, community development corporations, and Native Hawaiian organizations.

But participation is not a free buffet with no fine print. For tribally owned concerns, the SBA regulations require organizing documents to contain express sovereign immunity waiver language, or a “sue and be sued” clause, designating U.S. federal courts as courts of competent jurisdiction for matters relating to SBA programs, including 8(a) participation, loans, and contract performance. That language exists because the federal contracting system needs a functioning legal forum. Otherwise, disputes tied to the program could vanish into a jurisdictional fog bank.

In AQuate II, that waiver language mattered more than any dramatic litigation speech about sovereignty. Kituwah’s own organizational documents contained the required language. Once the court concluded that the trade secrets dispute was related to Kituwah’s participation in the 8(a) program, the immunity defense lost its protective shine. The shield was still a shield, but the company had already cut a program-specific window into it.

Why the Court Read “Related To” Broadly

Lawyers adore the phrase “related to” because it is broad enough to host an entire family reunion. The Eleventh Circuit leaned into that breadth. The court explained that the alleged misconduct was tied directly to Kituwah’s effort to compete for the same 8(a) contract. The supposed trade secret misappropriation was not random, accidental, or floating somewhere out in legal outer space. It was allegedly aimed at gaining an advantage in an 8(a) procurement.

That made the connection straightforward. The court essentially said that but for the attempt to win the 8(a) contract, Kituwah would not have allegedly used the information in that way. Therefore, the claims related to participation in the 8(a) program. That reasoning is significant for future disputes because it suggests courts may interpret similar waiver language pragmatically rather than hyper-technically.

This also means companies should not assume a waiver applies only when someone is directly arguing about a line item in the SBA rulebook. A dispute can be related to 8(a) participation if the conduct is tied to bidding, performance, contract competition, or other commercial activity wrapped around the program. In the world of legal drafting, broad language usually shows up wearing broad consequences.

Trade Secrets Law Was the Engine Under the Hood

While sovereign immunity stole the headline, trade secrets law supplied the engine. The federal Defend Trade Secrets Act allows an owner of a trade secret to sue in federal court when a trade secret tied to interstate or foreign commerce is misappropriated. Alabama law likewise protects trade secrets and provides remedies for misappropriation. So AQuate did not stroll into court with vague hurt feelings and a dramatic PowerPoint. It brought recognized statutory claims rooted in both federal and state law.

That matters because trade secrets disputes often move quickly and hit hard. The information at issue can include pricing, proposals, staffing models, technical methods, and bid strategy. In government contracting, that kind of data can be the commercial equivalent of a team’s playbook, scouting report, and secret sauce all stuffed into one folder. When a former employee changes sides, the risk is not merely awkwardness at LinkedIn update time. The risk is competitive harm in real dollars and real contract opportunities.

AQuate II shows how trade secret claims can intersect with tribal law, federal procurement rules, employment agreements, and jurisdictional questions all at once. It is a legal turducken. Tasty for scholars, stressful for clients.

The Forum Clause Added Even More Drama

The case also involved a separate wrinkle over the former employee’s contract. Myers argued that a forum-selection clause required disputes to be heard in the Alabama-Quassarte Tribal Town court. AQuate argued that this designated court did not actually exist. That is the kind of sentence that makes litigators sit up straighter.

The Eleventh Circuit did not definitively resolve that issue, but it held that the district court should have first analyzed whether the forum-selection clause was valid and enforceable before dismissing the case on forum non conveniens grounds. The appellate court signaled serious concern that an illusory forum would be unreasonable to enforce. Translation: a forum clause cannot do much good if the forum is basically a legal unicorn.

This part of the ruling is a useful reminder for employers and contractors. Boilerplate dispute clauses should not be copied, pasted, blessed, and forgotten. They need to point to a real tribunal, with real procedures, in a real place where a claim can actually be heard. Otherwise, what looks like tidy contract drafting may turn into expensive courtroom embarrassment.

What This Means for Tribal Businesses and Government Contractors

1. Waiver language is not decorative.

If your company participates in the 8(a) program, your organizational documents matter. A sovereign immunity waiver inserted to satisfy program requirements can become outcome-determinative in later litigation. Businesses should review the exact text, understand its reach, and align internal risk planning accordingly.

2. Trade secret protection needs operational discipline.

Confidentiality agreements, access controls, exit procedures, device return protocols, and bid-data security are not compliance wallpaper. They are the factual building blocks of a future trade secrets case. Without them, even a strong legal theory can wobble.

3. Employee transitions are high-risk moments.

Many trade secrets disputes begin with a familiar story: a key employee leaves, joins a competitor, and suddenly confidential information seems to have grown legs. Companies in federal contracting should treat departures from proposal, pricing, and operations staff as sensitive transitions, not casual farewells with sheet cake.

4. Courts will favor practical reasoning over word games.

The Eleventh Circuit’s analysis suggests that judges are willing to look at the real-world connection between the conduct and the federal contracting program. If the alleged misappropriation is tied to winning or performing an 8(a) contract, a narrow semantic dodge may not get very far.

Practical Experiences and Lessons from the Field

In real life, disputes like this rarely begin with someone announcing, “Today seems perfect for a sovereign immunity showdown.” They usually start with smaller warning signs. A former employee asks oddly specific questions about pay scales. A competitor suddenly mirrors staffing assumptions that were never public. Internal files that once sat quietly in shared folders become the stars of an emergency meeting. Executives, HR leaders, and contract managers often describe the same experience: first confusion, then suspicion, then a frantic effort to reconstruct who had access to what and when.

For companies in federal contracting, the emotional experience can be as intense as the legal one. Bid teams work under deadlines, and when sensitive proposal information appears to travel across the street to a competitor, it feels less like routine business friction and more like someone borrowed your playbook, your cleats, and maybe your quarterback. The pressure becomes even greater when the contract at issue is a major revenue source or a flagship federal relationship.

Lawyers who handle these matters often see a common pattern. The companies with the strongest early position are not always the ones with the fanciest legal memos. They are the ones that documented confidentiality, limited access to critical files, preserved evidence quickly, and took exit interviews seriously. They can show that the information was treated like a secret before the lawsuit ever began. Courts tend to appreciate that. Opposing counsel, for obvious reasons, appreciate it much less.

There is also a governance lesson here for tribally owned businesses and their advisers. Many leaders enter the 8(a) program focused on opportunity, growth, and access to set-aside contracting. That makes perfect sense. But the legal architecture of participation should receive equal attention. Waiver clauses, dispute provisions, and forum language are not sleepy appendices living at the back of the binder. They can shape the entire litigation landscape years later, long after the original application paperwork has been forgotten in a digital folder named something heroic like “final_final_REALfinal.”

Another recurring experience involves internal education. Business teams may assume sovereign immunity is an all-purpose defense that automatically blocks every lawsuit. Compliance teams may assume a waiver only applies to direct SBA disputes. Neither assumption is safe. AQuate II shows why training matters: operational leaders, HR personnel, and in-house counsel need a shared understanding of what immunity does, what waiver does, and where trade secrets law enters the picture. That shared understanding can prevent bad decisions before a dispute ever reaches a courthouse.

In the end, the most valuable experience-based lesson is simple. When a company handles trade secrets carefully, drafts agreements thoughtfully, and respects the real scope of program-based waiver language, it reduces the odds of a catastrophic surprise. And in government contracting, reducing catastrophic surprises is not glamorous, but it is beautiful.

Final Takeaway

Sovereign Immunity Not Existent in Trade Secrets Case makes for a spicy headline, but the real legal takeaway is more precise. The Eleventh Circuit did not declare tribal sovereign immunity dead, missing, or out grabbing lunch. It held that a tribally owned contractor participating in the SBA’s 8(a) program had waived immunity for claims related to that participation, and that alleged trade secret theft aimed at winning an 8(a) contract fell within that waiver.

That ruling matters because it blends federal procurement rules, tribal business structures, trade secrets law, and contract drafting into one practical lesson: words in governing documents count, and courts will read them in light of how the business actually operates. For contractors, the case is a wake-up call. For lawyers, it is a precedent worth bookmarking. For anyone who thought a trade secrets suit could not also become a tutorial on sovereign immunity, welcome to federal litigation, where the plot is always overachieving.