Quick Answer
Federal civilian executive agencies must remove and stop procuring DeepSeek products, including certain third-party tools built with DeepSeek implementations, under a DHS order published October 20, 2026. The order does not direct US consumers to delete DeepSeek from personal devices. Federal contractors and agency IT teams should identify affected software and follow their agency’s removal and procurement instructions.
Key Takeaways
- Federal civilian executive agencies must remove covered DeepSeek products and services.
- The order also covers third-party products and services developed using DeepSeek implementations.
- The restriction applies to federal civilian IT systems and procurements, not personal consumer devices.
- The published notice followed a Federal Acquisition Security Council recommendation and related evidence.
- Federal contractors should review AI software dependencies and confirm agency-specific compliance instructions.
What does the DeepSeek federal ban require agencies to do?
The DeepSeek federal ban requires civilian executive-branch agencies to exclude and remove covered DeepSeek products and services from federal information technology systems and procurements. The Department of Homeland Security published the notice on October 20, 2026, under the title “Notice of Order Regarding Exclusion and Removal of DeepSeek Products From Federal Civilian Executive Branch Information Technology Systems and Procurements.” The DHS Federal Register notice defines the order’s scope.
The order applies to IT products and services developed by Hangzhou DeepSeek Artificial Intelligence Co. Ltd. and affiliated entities. This matters because the restriction is not limited to one consumer chatbot or one model download. Federal organizations need to treat DeepSeek as a procurement and software-inventory issue across covered systems.
The federal action was taken under the Federal Acquisition Supply Chain Security Act of 2018, 41 U.S.C. 1321-1328. The notice says the order followed review of a Federal Acquisition Security Council recommendation and related evidence. The practical response for agencies is to use their own authorized compliance process rather than make informal removal decisions on production systems.
Which DeepSeek tools and third-party services are covered?
The DeepSeek federal ban covers DeepSeek-branded IT products and services, affiliated entities, and third-party products and services developed using DeepSeek implementations. The third-party language is significant because a federal software inventory cannot stop at applications labeled “DeepSeek.” Agencies and contractors may need to determine whether another vendor’s product relies on a DeepSeek implementation.
| Product or service category | How the order describes it | Practical review question |
|---|---|---|
| DeepSeek products and services | Products and services developed by Hangzhou DeepSeek Artificial Intelligence Co. Ltd. | Does the agency use a DeepSeek product in a covered IT environment? |
| Affiliate-developed products | Products and services developed by affiliated entities | Does the supplier list an affiliated DeepSeek entity in its product documentation? |
| Third-party AI tools | Products and services developed using DeepSeek implementations | Does a vendor-built tool use a DeepSeek implementation underneath its own interface? |
The table describes the categories stated in the DHS notice, not a complete list of every affected product. Federal organizations should request clarification from the relevant agency procurement or security office when a vendor’s technical documentation does not clearly identify its underlying AI implementation. Organizations evaluating AI systems also need governance for tools that can take actions, including browser-controlling AI agents, because software dependencies can extend beyond a visible chat interface.
Which federal organizations does the order affect?
The DeepSeek federal ban applies to federal civilian executive-branch information technology systems and procurements. The order therefore directly concerns civilian agencies and the contractors, vendors, and procurement teams supporting those agencies. The DHS notice does not itself establish a general ban on DeepSeek use by state governments, private businesses, schools, or ordinary consumers.
The scope matters because “federal government” can describe many different institutions in ordinary conversation. The published order uses the narrower phrase “federal civilian executive branch,” so readers should not assume that every public-sector organization faces the same directive. Agency-specific implementation instructions can determine how an affected organization identifies products, handles contract obligations, and documents removal.
Federal contractors should not treat the public notice as a substitute for instructions from their contracting officer, agency security office, or legal team. Contractors often operate systems and services under defined contractual terms. The most sensible approach is to identify potential exposure, preserve relevant records, and obtain the applicable direction before changing a production environment.
When was the DeepSeek order signed and published?
The DeepSeek order was signed July 24, 2026, while the Federal Register notice was posted publicly October 19 and published October 20, 2026. Bloomberg Law’s report on the order identifies the July 24 signature date and the contract restriction.
The difference between the signature date and publication date matters because the October 20 notice is the public document that sets out the exclusion and removal action. A reader seeing headlines on October 20 is learning about a federal action that had already been signed months earlier. The notice also makes the covered third-party implementation language especially important for procurement reviews.
The order does not provide a consumer-facing installation deadline in the published facts available here. Federal teams should therefore rely on formal agency notices and contract communications for timing, rather than infer a deadline from the public publication date alone. A careful software inventory remains useful even when a specific removal schedule has not been publicly described.
Does the DeepSeek federal ban require consumers to delete the app?
The DeepSeek federal ban does not itself order ordinary US consumers to delete DeepSeek from personal devices. The DHS notice concerns federal civilian executive-branch IT systems and procurements. Personal use, private business use, and state or local government use are outside the order’s stated scope.
That limitation does not mean consumers should ignore normal privacy decisions. Consumers should consider what information they enter into any AI service, particularly work documents, financial details, health information, passwords, and other sensitive material. Questions about user data can remain important even when a federal procurement order does not apply to a personal phone.
Consumers who want to reduce exposure can review installed apps, account permissions, and the information already saved in AI conversations. Users should avoid entering sensitive information into a service when they do not understand how that information will be handled. Similar concerns about retained conversations have appeared in discussions of user chat data on other AI platforms.
Why did DHS issue the DeepSeek exclusion order?
DHS issued the DeepSeek exclusion order after review of a Federal Acquisition Security Council recommendation and related evidence, according to the Federal Register notice. The order relies on the Federal Acquisition Supply Chain Security Act of 2018. The available public notice establishes the legal authority and review process, but it does not require readers to draw conclusions beyond the scope stated in the order.
The order is a supply-chain security action affecting federal procurement and IT systems. Supply-chain reviews matter because organizations can acquire software directly, through resellers, through cloud providers, or as a component inside another product. The inclusion of third-party tools developed using DeepSeek implementations reflects that broader technical procurement chain.
China criticized the US action and warned of possible retaliatory measures, according to AP reporting on China’s response. That response is a diplomatic position, not a change to the published federal scope. Federal agencies and contractors should focus on the DHS notice and any subsequent agency-specific compliance instructions.
How should federal contractors and agencies respond?
Federal agencies and contractors should begin with a documented software and vendor review, then follow the instructions issued by the agency responsible for the affected system or contract. The order’s coverage of third-party services means an inventory should include direct applications, embedded AI features, vendor integrations, and relevant procurement records. Do not remove production software without approved change controls and agency authorization.
- Identify DeepSeek products, services, and AI-enabled vendor tools used in covered federal environments.
- Request technical documentation from vendors if an AI implementation is unclear.
- Document affected contracts, system owners, data flows, and dependency relationships.
- Follow written removal, replacement, and procurement guidance from the relevant agency office.
Federal IT teams should preserve configuration records and assess operational dependencies before disabling a service. Removing an AI component without understanding its connections can interrupt a workflow or service that depends on it. Security inventories should also account for ordinary software maintenance, including critical browser security updates, because an organization’s risk posture depends on both supplier decisions and timely patching.
Federal contractors should stop and contact the contracting officer, agency cybersecurity office, or legal counsel when a product’s implementation cannot be confirmed or when removal could disrupt a mission-critical system. The public notice establishes the exclusion and removal policy, but agency-specific direction determines how a particular environment should comply.
FAQ
Is DeepSeek banned in the United States?
DeepSeek is not banned for all US users by the October 20, 2026 DHS notice. The published order applies to federal civilian executive-branch IT systems and procurements, not ordinary personal devices.
Do federal agencies have to remove third-party tools that use DeepSeek?
Federal agencies must address third-party products and services developed using DeepSeek implementations when those products fall within the order’s scope. Agencies and contractors should verify underlying AI dependencies with vendors and follow agency-specific compliance instructions.
Does the DeepSeek order apply to federal contractors?
Federal contractors can be affected when they provide covered IT products or services to civilian executive-branch agencies. Contractors should review contract requirements and obtain direction from the relevant contracting officer or agency security office.
Does the order require consumers to uninstall DeepSeek?
The DeepSeek order does not require ordinary consumers to uninstall the app from personal devices. Consumers can still make their own privacy decisions and should avoid entering sensitive information into AI services without understanding the data-handling implications.
Why was the DeepSeek order made public in October?
The DeepSeek order was signed July 24, 2026, and the Federal Register notice was posted publicly October 19 and published October 20. The public notice describes the exclusion and removal action for federal civilian executive-branch systems and procurements.