Space and Satellite IP Toolkit: Jurisdiction, Payloads, Launch, and Earth Observation Data

By Casey Scott McKay · 2023-12-22

Patent law is territorial and space is not anyone's territory, which is the structural problem underneath every intellectual property question in this sector. This toolkit assembles the working material for practitioners advising satellite operators, payload developers, launch providers, and downstream data businesses. It covers the registry-based jurisdictional fiction that fills the gap, why the ground segment is usually the better place to sue, how hosted payload and rideshare arrangements allocate rights among parties who never contract directly, and what a customer actually buys when it buys earth observation data. It sets out the launch cross-waiver regime that displaces ordinary liability allocation, the export control layer that is stricter here than almost anywhere, and the in-orbit servicing question that has no settled answer.

IP and Technology > Patent Counseling Transactions | Toolkit | Published 22 December 2023 - Updated 8 August 2026 | Casey Scott McKay - marksy.us

Summary. Patent law is territorial and space is not anyone's territory, which is the structural problem underneath every intellectual property question in this sector. This toolkit assembles working material for practitioners advising satellite operators, payload developers, launch providers, and downstream data businesses: the registry-based jurisdictional fiction, why the ground segment is usually the better place to sue, how hosted payload and rideshare arrangements allocate rights among parties who never contract directly, what a customer buys when it buys earth observation data, the cross-waiver regime that displaces ordinary liability allocation, and the servicing question that has no settled answer.

Keywords: space IP · satellite patents · registry jurisdiction · quasi-territoriality · payload rights · hosted payload agreements · launch services · cross-waivers · earth observation data · remote sensing licence · ground segment · constellation operations · spectrum coordination · export control · in-orbit servicing

Start Here

Everything in this toolkit descends from one sentence: patent rights are territorial, and outer space is expressly not subject to national appropriation.

That is not a technicality. A patent grants the right to exclude others from making, using, offering to sell, or selling the invention within a country, and importing it into that country. A satellite in orbit is not within any country. Neither is the manufacturing that happens in orbit, the use of an instrument in orbit, or the computation performed by a processor in orbit.

The gap is filled, imperfectly, by two devices. The first is a statutory quasi-territoriality provision extending patent law to space objects under the jurisdiction or control of the country, subject to international agreement — which makes the registry entry, not the physical location, the operative fact. The second is the practical observation that space businesses are ground businesses: the commands are sent from a ground station, the data is received at a ground station, processed on terrestrial servers, and sold to terrestrial customers, and every one of those is an act within a territory.

The practical instruction that follows is the most useful single point in this toolkit. Claim the ground segment. A claim drafted to the space segment alone may be unenforceable in practice; the same invention claimed as a ground-station method, a processing pipeline, or a system including terrestrial elements is enforceable in an ordinary court against an ordinary defendant.

Four further questions structure the practice.

Which registry, and therefore which law? Registration determines jurisdiction and control, and the registering state is a matter of the operator's choice within limits, which makes it a planning decision rather than a fact.

Who owns what on a shared platform? Hosted payloads, rideshares, and constellations put multiple parties' hardware, software, and data on or around a single asset, frequently without direct contractual privity.

What was actually licensed in the data? Earth observation is sold under terms drafted with wildly varying care, and the derived-product question is where value is created and lost.

What is the export position? Space technology sits at the strict end of the export control system, and the classification question governs whether a technical conversation may happen at all.

Jurisdiction, registration, and the fiction that fills the gap

The treaty framework establishes three propositions that matter here. Outer space is not subject to national appropriation. The state on whose registry a space object is carried retains jurisdiction and control over that object and any personnel. And the launching state bears international liability for damage caused by its space objects.

Layered on top, domestic patent law in several jurisdictions extends the reach of the patent statute to inventions used or made on a space object under the jurisdiction or control of that state — with a carve-out for objects there under an international agreement.

Four working consequences.

The registry entry is the choice of law. An operator choosing where to register is choosing which patent regime notionally applies in orbit, alongside licensing, liability, and regulatory consequences. That decision is frequently made by a regulatory team without patent input.

A satellite is not a ship. The maritime analogy is tempting and misleading; the flag-state analogy holds for jurisdiction and breaks for almost everything else, including salvage, boarding, and the treatment of objects that stop functioning.

Multi-state constellations fragment the analysis. A constellation registered across three states, controlled from two ground networks, serving customers in fifty, has no single answer to any jurisdictional question.

The launching state concept is broader than the operator expects, capturing states that procure a launch and states from whose territory it occurs, which brings parties into the liability framework who thought they were customers.

For the underlying doctrinal treatment, see Owning Something in Orbit, and for the operational sequence, Advising a Space or Satellite Business.

Drafting patents for a sector with a jurisdictional hole

Claim drafting in this sector is a legal-strategy exercise rather than a technical one, and the differences from ordinary practice are substantial.

Claim the ground segment wherever the invention permits it. A method performed at a ground station, a system comprising terrestrial and space elements, a data processing pipeline, and a scheduling algorithm executed terrestrially are all enforceable in an ordinary forum.

Claim the manufacture rather than the use. A satellite built in a country and launched from it involves a making within that country, which is an infringing act under 35 U.S.C. § 271 regardless of where the article ends up.

Watch the divided infringement problem. A claim requiring steps performed by a satellite operator, a ground station provider, and a customer may be infringed by no single party, which is the recurring structural defect in space claims and is addressed by drafting each claim from the perspective of one actor.

Consider component supply. 35 U.S.C. § 271 reaches supply of components from a country for combination abroad in circumstances that would infringe if the combination occurred domestically, which is a genuine route where hardware is exported for integration.

File where the ground stations are, not only where the company is, since enforcement will happen where the terrestrial acts occur.

Mind the secrecy and export overlay before any foreign filing, since space technology is precisely the category where a foreign filing licence question is live.

See Freedom to Operate, the Patent Prosecution Toolkit, and the International Patent Toolkit.

Payloads, hosting, and rideshare

A modern space asset is rarely a single party's hardware. Hosted payload arrangements place an instrument belonging to one party on a platform belonging to another. Rideshare places many satellites on one launch. Constellations serve many customers from shared infrastructure. Each configuration puts parties in proximity without privity.

The hosting agreement must allocate: ownership of the payload and of any modifications required to accommodate it; ownership of data produced by the payload; access to platform telemetry needed to operate the payload; rights on platform failure or early deorbit; and what happens to the payload's intellectual property if the host is sold.

Interface control documents are technical and legal. The ICD defines the mechanical, electrical, thermal, and data interfaces. Producing it requires exchanging design information, which raises both confidentiality and export questions, and the ICD itself is a jointly created document with an ownership question that is usually unaddressed.

Rideshare aggregation adds a party. The aggregator contracts with the launch provider and with each payload, and the payload customers have no contract with each other despite sharing a fairing, a separation sequence, and a set of environmental risks.

Constellation-as-a-service arrangements are the hardest, because the customer supplies an instrument or an application and the operator supplies everything else, and the resulting data is generated by an interaction neither party fully controls.

Improvements and derivatives need explicit treatment. A platform provider that adapts its bus to accommodate a payload has created something; whose it is, and whether it may be offered to the next customer, should be a term rather than a dispute.

See the Joint Development Agreement Checklist, the Confidentiality and NDA Toolkit, and Contracting With a Manufacturer.

Launch, and the cross-waiver that displaces ordinary risk allocation

Launch contracts are unlike other supply contracts because the industry operates on reciprocal waivers of liability rather than on ordinary allocation.

The structure is that each party — launch provider, customer, and typically their contractors and subcontractors at every tier — waives claims against the others for damage to its own property and injury to its own personnel arising from launch activities. The waiver flows down and flows across. Governments frequently require it as a condition of licence.

Three intellectual property consequences follow.

Damage to a payload is not compensable through the ordinary route, which changes how a payload developer values its work and how insurance is structured.

Confidentiality survives the waiver. The cross-waiver addresses property damage and injury, not misuse of technical information, and a launch integration process involves substantial disclosure. Confidentiality obligations must be drafted independently and must survive.

Third-party liability sits above the waiver. Damage to persons and property on the ground engages the launching state framework and domestic licensing regimes with their own financial responsibility requirements, and the indemnification arrangements are statutory rather than negotiated.

Add the practical points: launch delays are the norm and their contractual treatment is where disputes actually arise; a payload developer whose satellite is stranded on the ground has an intellectual property asset with an expiring commercial window; and re-manifesting to a different launch provider requires re-doing the interface work with a new counterparty, which is where confidentiality obligations are most often breached inadvertently.

Earth observation data, which is the commercial heart of the sector

Most space businesses that make money make it selling data, and the data is the least well-drafted asset in the sector.

The imagery is a work, in the copyright sense, to the extent it involves original expression — and a raw sensor readout arguably involves very little, which puts much of it in the thin-protection territory of Feist Publications v. Rural Telephone Service. Processed products involving choices about correction, fusion, colour, and interpretation are stronger.

Facts about the earth are not owned. The position of a ship, the extent of a flood, the health of a crop: these are facts, and a competitor who derives the same facts from its own imagery owes nothing.

Which means the protection is contractual. Licence terms, access controls, and — where the corpus is treated as confidential — trade secret protection under 18 U.S.C. § 1839 do the work that copyright does not.

The derived-product question is the commercial crux. A customer buying imagery to produce an analytic product is buying the right to make derivatives, and the licence must say so, define the boundary, and address whether the derived product may be resold, whether it must be attributed, and whether the underlying imagery may be reconstructed from it.

Refresh and archive rights determine whether a customer with a lapsed subscription may continue using what it downloaded, which is the most common post-termination dispute in data licensing.

Resolution restrictions and shutter control are regulatory, arising from remote sensing licensing conditions, and they constrain what may be sold, to whom, and when — which makes them contract terms as well as licence conditions.

Government data has different rules. Publicly funded imagery may be outside copyright under 17 U.S.C. § 105, while contractor-produced material may not be, and the terms of any public data programme control.

See the Data Licensing and Rights Toolkit, the Data Licensing Checklist, Information the Government Holds, and Building a Product on Public Data.

The ground segment, spectrum, and the terrestrial reality

The space segment attracts attention; the ground segment carries the value and the enforceable acts.

Ground stations as a service have converted a capital asset into a rented one, which means an operator's commands and data now pass through a third party's infrastructure under terms addressing security, data handling, and — critically — what the provider may do with telemetry.

Spectrum coordination is a regulatory process with intellectual property consequences, since filings disclose technical parameters and since orbital and frequency assignments are the scarce resource the business depends on.

Processing pipelines are software with ordinary copyright and licensing positions, frequently built on open source with obligations nobody tracked. See Copyleft and Consequences and the Software, Data, and Open Source Toolkit.

Telemetry, tracking, and control interfaces are where security and intellectual property meet, and where a compromise is simultaneously a safety event and a trade secret event.

Standards participation in ground and space communications brings declaration obligations. See the Standard Essential Patents and FRAND Toolkit.

Export control, which is stricter here

Space technology sits at the strict end of the export control system, and practitioners should assume control until classification shows otherwise.

The jurisdictional split between the defence trade regime and the dual-use regime has moved over time for satellites and components, and the current position for any given item must be determined rather than remembered. The deemed export concept applies with full force: an engineering discussion with a foreign national employee, a shared design repository, or a technical exchange with an international partner is a release.

Sector-specific pressure points: launch integration involves detailed technical exchange with a provider who may be foreign; constellation manufacturing is frequently distributed across countries; ground station operators are international by nature; and the customer base for imagery includes governments whose access is itself restricted.

See Building an Export Compliance Program for a Technology Company and the Export Control Checklist.

In-orbit servicing, debris, and the questions with no settled answer

A growing set of activities has no clean legal treatment, and practitioners should advise accordingly rather than pretending otherwise.

Servicing and refuelling. A servicer that approaches, docks with, and repairs a satellite is performing an act on an object under another state's jurisdiction. If the servicing embodies a patented method, where did the infringement occur? If the servicing requires reverse-engineering the target's interfaces, is that permitted? The contracts between servicer and owner can answer the second question and cannot answer the first.

Repair versus reconstruction, in orbit. The terrestrial distinction — a purchaser may repair a patented article but may not reconstruct it — has an obvious application to a serviced satellite and no authority applying it there.

Debris removal. An object that has stopped functioning remains under its registering state's jurisdiction and remains its property. Removing it without permission is interference with property; leaving it is a hazard. The intellectual property question — whether examining or capturing it discloses anything — is secondary to the property question and is rarely addressed.

In-orbit manufacturing. Making an article in orbit is a making, but not within any country. The registry fiction may reach it; the analysis is untested; and the resulting article's status on return is a further question.

Autonomous operations. Constellations increasingly operate under autonomous collision avoidance and scheduling, which raises the same authorship, liability, and control questions treated in The Machine That Decides and the Robotics and Autonomous Systems IP Toolkit.

The professional answer to all of these is the same: identify the terrestrial acts, contract around the orbital ones, and tell the client which parts of the advice rest on analogy rather than authority.

The economics that shape the legal work

Space businesses have a financial structure that determines which legal problems actually matter, and practitioners who ignore it give advice that is correct and useless.

Capital is raised against a mission, not a portfolio. Investors in this sector fund a launch, a constellation build-out, or a first commercial contract. The intellectual property position is diligenced but rarely priced, which means the legal work that gets funded is the work that unblocks a milestone: an export licence, a launch contract, a customer's data terms. Framing a patent programme as milestone-enabling rather than as asset-building is the difference between a budget and a deferral.

Hardware costs dominate until they don't. Early-stage space companies spend on hardware and treat legal as overhead. Once a constellation is operating, the cost structure inverts: the marginal satellite is cheap and the data business is everything. That inversion is when the licensing terms drafted three years earlier start to matter, and it is why a data licence written by a hardware company in its first year is almost always wrong for its fifth.

The commercial window is short and the asset is unreachable. A satellite has a design life, cannot be recalled, and cannot be modified beyond what its software permits. An intellectual property problem discovered post-launch has a narrow set of remedies, none of which involves fixing the article. This argues for front-loading freedom-to-operate work in a way that feels disproportionate at the time.

Insurance is a structural participant. Launch and in-orbit insurance shape contract terms throughout the chain, and insurers ask about intellectual property risk in the same breath as technical risk. A clean rights position is, as in aerospace generally, partly an insurance-procurement exercise. See the IP Insurance and Risk Transfer Toolkit.

Government is customer, regulator, and competitor at once. The same agency may fund the technology, license the operation, buy the data, and operate a comparable capability. That triple role affects data rights assertions, publication timing, and the practical willingness to litigate.

Consolidation is constant. The sector acquires and merges continuously, which means the diligence questions in this toolkit are asked about most companies eventually, and the answers are determined by contracts signed years before anyone imagined an exit.

Trade secrets and the distributed build

A constellation is manufactured differently from a traditional satellite. Where a bespoke geostationary platform was built once, slowly, by a small team, a constellation is built repeatedly, quickly, often across multiple sites and multiple countries, with production processes that are themselves the innovation.

That changes the secrecy analysis in five ways.

The process is the asset. How to build a satellite for a tenth of the historic cost is worth more than any individual component design, and it is not patentable in any useful way because it is a thousand small choices rather than one invention.

The population of people who know is large. Production staff, contract manufacturers, test houses, and integrators all hold pieces. Reasonable measures under 18 U.S.C. § 1839 must be designed for a manufacturing organisation rather than for an engineering department.

Supplier access is structural. A supplier producing a component to a rate specification learns the rate, which is itself commercially sensitive.

Departures move production knowledge. The competitor hiring a production engineering lead acquires far more than a resume, and the inevitable-disclosure argument is unavailable in many jurisdictions. See the Trade Secret Protection and Departure Checklist and Where an Employee Can Go.

Export control does part of the work. Access restrictions imposed for classification reasons frequently satisfy the reasonable-measures standard as a by-product, which is a rare instance of two compliance regimes reinforcing rather than conflicting. Document the overlap deliberately so that the export controls can be pointed to as secrecy measures if a misappropriation claim is ever brought.

Brands, mission names, and the marketing layer

Trademark work in this sector is small in volume and unusual in character.

Mission names are announced before they are cleared. A constellation, a spacecraft, or a programme acquires a name in an engineering meeting, appears in a press release, and is on a launch fairing before anyone searches it. The clearance is cheap and the rebranding is not. See the Trademark Clearance and Brand Selection Toolkit.

The data product carries the commercial brand. Customers buy an analytic product with a name, not a satellite, and that name is the registrable asset. File for it in the classes that matter — data services, software, analysis — rather than for the spacecraft.

Imagery is used in marketing by everyone. A striking image of the earth circulates far beyond its licence, and the operator's position depends on whether it registered the imagery and whether it has any enforcement appetite. Registration in batches under 17 U.S.C. § 412 is the precondition to any meaningful remedy.

Government mission imagery is frequently free of copyright and is used commercially on that basis. Confirm the source before relying on it, since contractor-produced material within a government programme may not share the status.

Sponsorship and payload naming rights exist and are undocumented. A payload named for a sponsor, a launch carrying branded hardware, and a mission patch used in merchandise all raise ordinary licensing questions in a setting where nobody expects them.

Domain and handle protection matters more than in most sectors because mission names are highly searchable and speculative registration is quick. See the Domain Name and Digital Identity Toolkit.

A short glossary

Space object. The satellite, its components, and its launch vehicle and parts, for treaty purposes.

Registry. The national register on which a space object is carried, determining jurisdiction and control.

Launching state. A state that launches, procures a launch, or from whose territory or facility a launch occurs — a broader category than the operator expects, and the basis of international liability.

Quasi-territoriality. The statutory extension of patent law to space objects under a state's jurisdiction or control, subject to international agreement.

Space segment and ground segment. The orbital assets and the terrestrial infrastructure. The value and the enforceable acts are mostly in the second.

Hosted payload. An instrument belonging to one party carried on a platform belonging to another.

Rideshare and aggregator. Multiple payloads on one launch, contracted through an intermediary with whom each payload has privity and the payloads do not have privity with each other.

Interface control document. The jointly created specification of mechanical, electrical, thermal, and data interfaces between payload and platform.

Cross-waiver. The reciprocal waiver of liability among launch participants and their contractors at every tier, covering damage to their own property and injury to their own personnel.

Shutter control. Regulatory authority to restrict imaging or dissemination, typically flowing from remote sensing licence conditions.

Telemetry, tracking, and control. The command and monitoring link, and the point at which security and trade secret exposure coincide.

Derived product. An analytic output built from imagery, and the category where most commercial value and most licensing disputes sit.

In-orbit servicing. Approach, docking, repair, refuelling, or relocation of an existing object, currently governed by contract and analogy rather than by settled law.

Deorbit and disposal. The end-of-life obligation, and the point at which an object that is still property becomes debris that is still someone's responsibility.

Keeping those fourteen terms straight resolves most confusion in this sector, because nearly every error is a conflation of the object, the registry, the segment, and the party.

What good looks like

A well-run space intellectual property position has eight visible features, and a practitioner can assess a company against them in an afternoon.

A registry and jurisdiction memorandum exists, one page per asset, and someone in the legal function can explain why each asset is registered where it is.

Claims are drafted to the ground segment wherever the invention permits, and the invention disclosure form asks the engineer where each step is performed.

No claim requires two actors. Divided infringement has been considered at drafting rather than discovered at enforcement.

Every hosting, rideshare, and integration agreement allocates data ownership expressly, and telemetry access is a stated right rather than an operational courtesy.

The data licence contemplates derivatives, states the boundary, addresses archive rights on termination, and passes regulatory restrictions through as contractual terms.

Export classification precedes disclosure, with a written basis per item and per data category, and access controls that implement it — which also serve as documented secrecy measures.

Mission and product names are cleared before announcement, and imagery is registered in batches so that enforcement is economically rational.

The transaction questions have been answered in advance: which licences, registrations, spectrum assignments, and ground agreements transfer, by what mechanism, and on what timeline.

Companies with those eight features negotiate from a position. Companies without them discover, usually during diligence and always at the worst moment, that the answers were determined years earlier by clauses nobody read and by a claim set drafted for a place where no court sits.

Advising the three kinds of client in this sector

The hardware company. Builds spacecraft, buses, or components and sells them. Its questions are supplier terms, manufacturing secrecy, export classification, and freedom to operate before design freeze. Its characteristic error is treating data licensing as somebody else's problem, which becomes its own problem the moment it starts operating what it builds. Its patent programme should be small, tightly targeted at the things a competitor would copy, and filed in the manufacturing jurisdictions.

The operator. Owns and flies assets and sells capacity or data. Its questions are registry choice, hosting and rideshare terms, ground segment agreements, spectrum, and the data licence. Its characteristic error is inheriting a hardware company's contracts and never revisiting them, so the terms governing the most valuable part of the business were drafted when that part did not exist. Its patent programme should be concentrated on ground-segment methods and processing, where it can actually enforce.

The downstream analytics business. Buys imagery and sells insight. Its questions are the derived-work clause, archive rights, attribution, source diligence, and whether its own outputs are protectable. Its characteristic error is building a product on licence terms it has not read, from a source whose own rights are unverified, and discovering both at the point of acquisition. Its protection is mostly contractual and trade secret, with copyright reaching the presentation layer rather than the facts.

Three clients, three sets of questions, one shared structural fact: the enforceable acts happen on the ground, the value sits in the data, and the contracts that determine both are signed early by people optimising for something else.

The first meeting

For a practitioner taking on a space client for the first time, six questions asked in the first meeting will surface almost everything that matters, and none of them requires technical knowledge.

Where is each asset registered, and who decided that? If the answer is a regulatory manager acting alone, the patent, liability, and licensing consequences were not weighed.

Where are your ground stations, and do you own them? This is where enforcement happens and where an increasing share of the operational risk sits.

Show me the data licence you send to customers. If it does not mention derived products, the most valuable question in the business is unanswered.

Who else's hardware is on your platform, and whose is yours on? Every hosting relationship is a rights allocation, and most are governed by a document the engineering team negotiated.

What is your export classification, and when was it last reviewed? A classification determined at incorporation and never revisited is a classification that no longer describes the product.

What was announced before it was cleared or filed? Mission names, technical papers, and investor decks are the three most common sources of both trademark conflict and prior art in this sector.

Six questions, twenty minutes, and a work plan. Everything else in this toolkit is detail hung on those answers.

A seventh question is worth adding where an exit is foreseeable: what does an acquirer have to obtain from a regulator before it can operate what it buys? The answer is never nothing, and it is almost never in the data room.

An eighth, for operators approaching end of life on their first generation: what is the disposal plan, and who owns the object once it stops working? Both answers are contractual and regulatory rather than intuitive.

A ninth, for anyone selling into government: which of your data rights assertions were made, when, and by whom? Unasserted restricted rights are lost, and the assertions table is routinely completed by a proposal team with no view of the development history.

A Suggested Reading Path

Starting a space venture: read Owning Something in Orbit, then Advising a Space or Satellite Business, then work the Space and Satellite IP Checklist.

Filing strategy: the Patent Fundamentals Toolkit, the Patent Priority and International Filing Checklist, and the Freedom to Operate Checklist.

Export first, always: Building an Export Compliance Program for a Technology Company and the Export Control Checklist.

Data business: the Data Licensing Checklist, the Data Licensing and Rights Toolkit, and the Public Data and Open Information Toolkit.

Supplier and hosting agreements: the Contract Manufacturing IP Checklist and the Contract Manufacturing, OEM, and Private Label IP Toolkit.

Aviation adjacency: the Aviation, Aerospace, and Drone IP Toolkit and the Aerospace and Drone IP Checklist, since the technical data and supplier analysis is shared.

Secrecy programme: Building a Trade Secret Program That Survives Litigation and the Trade Secret Protection Toolkit.

Transactions: the IP Due Diligence Toolkit, with attention to registry, licence, and spectrum assignments that do not transfer automatically.

Primary Authorities

| Authority | Use | |---|---| | 35 U.S.C. § 105 | Inventions in outer space on objects under jurisdiction or control | | 35 U.S.C. § 271 | Making, using, selling; component supply abroad | | 35 U.S.C. § 101 | Eligibility for processing and scheduling methods | | 35 U.S.C. § 102 | Conference and mission-announcement disclosures | | 35 U.S.C. § 103 | Obviousness in an incremental engineering field | | 35 U.S.C. § 112 | Enablement for systems spanning segments | | 35 U.S.C. § 184 | Foreign filing licences | | 35 U.S.C. § 181 | Secrecy orders | | 35 U.S.C. § 287 | Marking where the article is inaccessible | | KSR International Co. v. Teleflex Inc. | Combination obviousness | | Impression Products v. Lexmark International | Exhaustion on hardware sold into a programme | | Aro Manufacturing v. Convertible Top Replacement | Repair and reconstruction, by analogy to servicing | | eBay Inc. v. MercExchange | Injunctions against an operating constellation | | 17 U.S.C. § 102 | Imagery and software as works | | 17 U.S.C. § 103 | Derived products and compilations | | 17 U.S.C. § 105 | Government imagery | | 17 U.S.C. § 201 | Ownership of contractor-produced pipelines | | 17 U.S.C. § 204 | Signed writings behind data transfers | | 17 U.S.C. § 412 | Timely registration of processed products | | Feist v. Rural Telephone | Thin protection in raw sensor output | | Google LLC v. Oracle America | Interfaces in ground software | | 18 U.S.C. § 1836 | Federal misappropriation claim | | 18 U.S.C. § 1839 | Reasonable measures across distributed manufacturing | | 18 U.S.C. § 1831 | Economic espionage exposure | | 8 U.S.C. § 1324b | Nationality screening constraints under deemed export control | | 15 U.S.C. § 1125 | False association in imagery resale | | FRCP 26 | Protective orders over mission data | | FRCP 65 | Injunctive relief against operations |

Search the underlying materials directly for space object registry jurisdiction patent, hosted payload agreement data rights, launch cross waiver liability, remote sensing licence shutter control, and satellite imagery derived product licence.

Forms and Templates

A registry and jurisdiction memorandum, recording where each asset is registered, why, which patent regime notionally applies in orbit, where the ground stations are, and which forums are realistically available. This is a half-page per asset and it prevents the most common category error in the sector.

A claim-drafting brief for the engineering team, explaining in plain terms why ground-segment claims matter, why single-actor claims matter, and why a mission announcement is a disclosure. Engineers who understand the reason draft better invention disclosures.

A hosted payload agreement schedule covering payload ownership, accommodation modifications, telemetry access, data ownership, platform failure, early deorbit, change of control of the host, and confidentiality surviving the arrangement.

An interface control document ownership clause, since the ICD is jointly created, contains both parties' technical information, and is regularly reused with the next customer.

A launch services rider confirming that the cross-waiver does not touch confidentiality, that technical information exchanged for integration is returned or destroyed on re-manifest, and that delay remedies are stated.

A data licence built for derivatives: field of use, permitted derived products, resale, attribution, reconstruction prohibition, archive rights on termination, refresh obligations, and regulatory restrictions passed through as contract terms.

A shutter-control and restriction annex, translating remote sensing licence conditions into terms the customer is bound by, because the operator's regulatory obligation becomes a contractual failure if the customer is not constrained.

An export classification memorandum per item and per data category, with basis, date, and owner.

A deemed export access matrix for repositories, ground systems, and integration facilities.

A ground station services agreement checklist covering security, telemetry handling, what the provider may retain, and what happens on provider insolvency.

An in-orbit servicing consent and interface protocol, for operators who expect to be serviced or to service, addressing reverse engineering, data capture during approach, and the treatment of anything learned.

For general drafting starting points, see the Draft License Agreement and the License Agreement Template.

Five recurring matters

A payload developer is asked to sign the host's standard hosting agreement. The three clauses to change are data ownership, telemetry access, and change of control of the host. Everything else can usually be lived with; those three determine whether the payload is an asset or a hostage.

An imagery customer builds an analytics product and the operator objects. Read the derived-work clause first, and expect it to be silent or ambiguous. Where it is, the fallback arguments are that facts are not owned and that the analytic product does not reproduce protectable expression — arguments that are strong on the law and weak on the relationship. Settle on forward-looking terms.

A constellation operator wants to sue a competitor. Identify the terrestrial acts: the ground station, the processing pipeline, the sale to a domestic customer. A claim aimed at the space segment invites a jurisdictional fight that adds cost and uncertainty; the same dispute framed terrestrially is an ordinary patent case.

A launch slips and the payload's commercial window closes. The cross-waiver does not help; the delay provisions do or do not exist. Check whether re-manifesting triggers a new integration cycle with a different provider and whether the confidentiality terms permit the necessary disclosures.

Diligence on an acquisition finds spectrum and licence assignments that do not transfer. Registry entries, remote sensing licences, spectrum authorisations, and ground station agreements each have their own transfer mechanics, and none follows an asset purchase automatically. Raise it in week one.