
What Is a PCB NDA and Why Does It Matter?
A PCB NDA (non-disclosure agreement) is a legally binding contract signed between a design owner and a fabrication or assembly partner before any Gerber files, stackup data, or BOM details change hands. It prevents the manufacturer from sharing, copying, or using your design information for any purpose other than producing your boards. For RF and microwave PCBs, where proprietary impedance structures, antenna geometries, and radar front-end layouts represent months of R&D investment, an NDA is not a formality—it is the first line of defense for your intellectual property.
Without a signed NDA in place before file transfer, you have no contractual recourse if your design leaks. Many engineers skip this step under schedule pressure, assuming that a manufacturer’s general terms of service cover confidentiality. They usually do not—at least not with the specificity or enforceability that RF IP demands.
When to Sign: Before Any File Leaves Your Control

The NDA must be fully executed (signed by both parties) before you upload Gerber files, send stackup drawings, share impedance requirements, or even discuss proprietary material choices in a quote request. The sequence matters:
- Initial inquiry — describe your project in general terms (layer count, frequency range, board size) without disclosing proprietary detail.
- NDA execution — both parties sign. Confirm the signatory has authority to bind the manufacturer.
- File transfer — upload design data through a secure channel for Gerber file review and pre-production checks.
- Quote and DFM review — the manufacturer can now examine your files under the NDA’s protections.
If a supplier asks you to send files before signing an NDA, treat that as a red flag. Reputable fabrication partners understand that a formal NDA policy is standard practice in defense, aerospace, automotive radar, and 5G infrastructure programs.
7 Clauses That Actually Protect RF PCB IP
Not all NDAs are equal. A generic template downloaded from the internet may leave critical gaps. For RF and microwave PCB work, these seven clauses carry the real weight:
1. Definition of Confidential Information
This clause must explicitly list the categories of protected data: Gerber and ODB++ files, stackup specifications, impedance control tables, drill files, BOM details, net lists, simulation results, and any verbal or written design discussion. Vague language like “proprietary information” without enumeration is harder to enforce.
2. Permitted Use
The manufacturer may use your data only for quoting, fabricating, and shipping your order. Any other use—benchmarking, training, showing to other customers, or feeding into an internal design library—must be explicitly prohibited.
3. Personnel Restrictions
Limit access to named roles (CAM engineer, process engineer, quality manager) on a need-to-know basis. In facilities that handle both commercial and defense work, this clause can align with IPC-1791 trusted electronics requirements for supply chain integrity.
4. No Reverse Engineering
State explicitly that the receiving party shall not reverse-engineer, decompile, or derive the design intent beyond what is necessary for fabrication. This is especially important if your boards include proprietary antenna array patterns, coupled-line filter topologies, or radar beamforming networks. Firms offering PCB reverse engineering services should be transparent about how they segregate customer data.
5. Return or Destruction of Data
After the order ships (or if the project is cancelled), the manufacturer must delete all electronic copies and return or destroy any physical samples, test coupons, or panel remnants. Set a concrete deadline—typically 30 to 90 days after final shipment—and require written certification of destruction.
6. Duration and Survival
The confidentiality obligation should survive termination of the business relationship. A three-to-five-year survival period is standard for commercial RF work; defense and aerospace programs often require longer, sometimes indefinite protection. The NDA’s duration is not the same as the project timeline—make sure the survival clause extends well beyond it.
7. Governing Law and Dispute Resolution
Specify which jurisdiction’s laws govern the agreement and whether disputes go to arbitration or litigation. If your manufacturer is overseas, consider specifying arbitration under rules recognized internationally, such as those of the ICC International Court of Arbitration. An NDA that cannot be enforced in the manufacturer’s country is essentially decorative.
Common Gaps Engineers Overlook
Even with all seven clauses present, these practical gaps undermine many PCB NDAs:
- Sub-contractors not covered. If your fabricator outsources drilling, plating, or testing, the sub-contractor must be bound by the same terms. Insist on a flow-down clause requiring equivalent NDAs with every sub-tier supplier.
- Verbal disclosures excluded. Some NDAs protect only written or electronic information. RF design discussions during DFM calls—where you might reveal operating frequency, target insertion loss, or impedance topology—should be captured by a clause that covers verbal disclosures confirmed in writing within a set period (typically 10 business days).
- No audit right. Without the right to audit the manufacturer’s data-handling practices, you rely entirely on trust. A short clause granting reasonable audit access, with notice, adds real teeth.
- Unclear ownership of tooling and test fixtures. Custom impedance test coupons, panel tooling, and RF test fixtures created for your project contain design information. The NDA (or a companion agreement) should state that these remain your property.
Practical Enforcement: What You Can Actually Do
An NDA is only as useful as your ability to detect a breach and act on it. Here is what experienced RF hardware teams do in practice:
Watermarking and Canary Traps
Embed unique, non-functional features in your Gerber files—a tiny trace segment in a ground pour, a specific via placement in a non-critical area—that differ between the files you send to different suppliers. If a design leaks, the watermark identifies the source. This does not replace an NDA, but it makes enforcement possible.
Secure File Transfer
Never send design files via unencrypted email. Use an encrypted file-sharing platform with access logging, download limits, and expiration dates. Some fabricators offer secure portals; verify that they log access by user and timestamp.
Staged Disclosure
For a first order with a new supplier, consider disclosing only the information needed for that phase. Share the full stackup and impedance table, but withhold the complete BOM or assembly drawings until the bare-board quality is proven. This limits exposure while you evaluate the relationship.
Linking the NDA to Payment Terms
Your payment terms agreement and NDA should reference each other. A breach of confidentiality can trigger payment holds or contract termination, giving you commercial leverage alongside legal remedies.
NDA Scope for Different Project Types

The depth of NDA protection you need scales with the sensitivity of the design:
| Project Type | Typical NDA Scope | Survival Period | Special Considerations |
|---|---|---|---|
| Commercial IoT / Wi-Fi | Standard mutual NDA | 3 years | Flow-down to assembly sub-contractors |
| 5G mmWave infrastructure | Enhanced NDA with audit clause | 5 years | Antenna array geometry, beamforming IP |
| Automotive radar (77 GHz) | Enhanced NDA + IATF 16949 alignment | 5-7 years | OEM flow-down requirements, PPAP data segregation |
| Defense / ITAR-controlled | NDA + ITAR/EAR compliance addendum | Indefinite | Personnel citizenship restrictions, facility clearance |
| Medical RF devices | Enhanced NDA + FDA design-history segregation | Life of product + 5 years | Design-history file access control |
For defense and ITAR work, the NDA alone is insufficient—you also need to verify that the manufacturer’s facility, personnel, and IT systems meet export-control requirements. The NDA should reference these obligations explicitly.
What a Good NDA Signals About a Manufacturer
A fabrication partner’s willingness to sign a well-structured NDA—and their process for handling it—tells you a great deal about their operational maturity. Manufacturers who have a standing NDA template, a named legal contact, and documented data-handling procedures are the same ones likely to have robust process controls for NDA terms that protect RF-specific IP. If a supplier resists signing, cannot name who will have access to your files, or has no documented data-destruction process, the risk extends beyond IP—it suggests broader quality-system gaps.
Checklist: Before You Send Your Next Design File
- NDA signed by an authorized representative of the manufacturer (not just a sales contact).
- Confidential information definition covers all file types you will send, plus verbal disclosures.
- Sub-contractor flow-down clause included.
- Data destruction deadline and certification requirement specified.
- Survival period appropriate for your industry (3 years minimum, longer for defense/medical).
- Governing law and dispute resolution clause enforceable in the manufacturer’s jurisdiction.
- Watermarks or canary features embedded in Gerber files.
- Files transferred via encrypted, logged channel—not email attachments.
- NDA cross-referenced in your purchase order and payment terms.
Frequently Asked Questions
Does a mutual NDA protect me as well as a one-way NDA?
Yes, provided the obligations are symmetric and the definition of confidential information is equally detailed for both parties. Mutual NDAs are standard when the manufacturer also shares proprietary process capabilities with you. The key is that the clauses protecting your design data are not weakened by the mutual structure.
Can an NDA prevent a manufacturer from making a similar board for a competitor?
An NDA prevents disclosure and misuse of your specific design data, but it does not grant you exclusivity over a product category. If a competitor independently designs a similar board, the manufacturer can legally produce it. To restrict competitive production, you need a separate non-compete or exclusivity agreement—which most manufacturers will resist or price into the contract.
What if my manufacturer is in a country with weak IP enforcement?
Choose arbitration under internationally recognized rules (ICC or UNCITRAL) and specify a neutral venue. Combine the legal agreement with practical measures: watermarked files, staged disclosure, and limiting the manufacturer’s access to only what they need for fabrication. No legal agreement substitutes for operational caution.
How does an NDA interact with ITAR or EAR export controls?
An NDA is a commercial confidentiality agreement; ITAR and EAR are federal regulations with criminal penalties. They operate in parallel. Your NDA should reference the applicable export-control regulations and state that the manufacturer will comply with them, but the NDA itself does not satisfy export-control obligations. You still need to verify the manufacturer’s registration, facility controls, and personnel eligibility independently.
Should I require an NDA for prototype quantities?
Absolutely. Prototype files often contain more sensitive information than production files because they reveal your design iterations, test structures, and performance targets. The volume of the order has no bearing on the sensitivity of the IP.
Ready for a quotation?
Send your requirements for a material, stackup and manufacturing review. Price and schedule are confirmed for your project.
