Satellite Imagery Licensing, Restricted Areas, and Export Compliance
Essential legal and technical controls governing imagery redistribution, derived AI products, restricted-area screening, and audit trails.
Commercial EULAs vs. Derived Vector Products
Licensing commercial satellite imagery does not transfer copyright; usage follows each provider's End User License Agreement (EULA). Standard seats allow internal analysis while barring raw pixel resale or unrestricted public tiling.
Many EULAs distinguish raw pixels from non-reversible derived products—such as vessel counts or congestion charts—letting teams share analytics externally without exposing licensed imagery.
- Verify internal seat caps and affiliate sharing clauses before deploying dashboards.
- Check AI training clauses before fine-tuning external foundation models on pixels.
- Enforce required copyright attributions and zoom caps on public visuals.
Government Sharing and Multi-Agency Rights
Public agencies coordinate across coalition partners, civil responders, and contractors. Standard single-entity licenses break down unless upgraded to interagency or enterprise sharing tiers.
Embedding license tags directly inside STAC item metadata enables automated gateways to enforce who views raw chips versus derived vectors.
- Tag every scene with license tier, expiry, and authorized partner groups.
- Verify sub-contractor processing clauses for third-party AI hosting.
- Separate open-data public tiles from restricted commercial imagery.
Conflicted, Sanctioned, and Restricted-Area Screening
Satellite operators comply with national space laws—such as U.S. 15 CFR Part 960—plus international sanctions and Acceptable Use Policies. Platforms screen tasking polygons against geofenced restricted territories and shutter-control rules.
Automated pre-tasking gates validate polygon intersections, user KYC tiers, and legitimate operational purpose before submitting collection commands.
Immutable Audit Trails for Geospatial Evidence
Insurance, regulatory, and strategic briefs increasingly require verifiable provenance. Immutable logs link every finding to scene ID, provider license, file hash, DEM version, AI model version, and analyst sign-off.
Automated lineage tracking safeguards both regulatory compliance and evidentiary credibility.
Imagery License Rights & Controls
| Scenario | Raw Pixels | Derived Stats/Vectors | Governance Control |
|---|---|---|---|
| Internal Portal | Permitted (seat/tier) | Permitted | RBAC & seat tracking |
| Contractor Processing | Needs explicit clause | Usually permitted | DPA + isolated bucket |
| Public Report Visual | Resolution-capped + credit | Permitted w/ attribution | Auto watermark & zoom cap |
| SaaS API Resale | Needs OEM license | Depends on reversibility | Legal review of derivatives |
| Restricted Zone Tasking | Regulatory & AUP gate | Subject to export rules | Automated KYC + geofence |
Verify exact permissions against governing provider EULAs and national remote sensing rules.
Worked Illustration: Multi-License Isolation in a Shared Hub
A platform ingests open Sentinel-2 data plus two commercial sub-meter feeds, serving internal analysts and external port clients.
- Tag Metadata: Each STAC item receives a `license_policy` label (`OPEN_CC`, `COMMERCIAL_INTERNAL`, or `DERIVATIVE_OK`).
- Gate Tile Server: External clients view open basemaps and derived GeoJSON vessel counts while raw commercial sub-meter pixels stay restricted internally.
- Screen Tasking: Compliance microservices intersect requested polygons against restricted-area geofences pre-submission.
- Embed Provenance: Exported briefs stamp scene IDs, license tags, and UTC timestamps automatically.
Worked Outcome: Policy-as-code metadata prevents accidental commercial pixel leakage while preserving unbroken audit trails.
Licensing & Compliance Checklist
- Audit every EULA for seat limits, AI training rules, and derivative rights.
- Embed license-tier tags inside STAC metadata at ingestion.
- Enforce RBAC separation between raw pixels and derived statistics.
- Run automated geofence and KYC screening on new tasking polygons.
- Stamp required sensor attributions automatically on exported imagery.
- Log scene hashes, calibration versions, and analyst reviews.
Frequently Asked Questions
Can commercial satellite screenshots be published freely?
Not without checking the EULA; most require specific attribution and cap public resolution or raw file downloads.
What is shutter control?
Regulatory authority—such as provisions under U.S. 15 CFR Part 960—allowing governments to temporarily restrict collection or distribution over sensitive areas.
Do imagery licenses restrict AI-extracted counts?
Non-reversible aggregated statistics or vector counts are frequently permitted externally, though EULA derivative clauses vary.
Why automate license enforcement in STAC metadata?
Tagging permissions in metadata lets tile APIs block unauthorized sharing automatically rather than relying on manual checks.
Primary Standards & References
- U.S. Department of Commerce / NOAA CRSRA — Licensing of Private Remote Sensing Space Systems (15 CFR Part 960)
- United Nations — Principles Relating to Remote Sensing of the Earth from Outer Space (Resolution 41/65)
- ISO 19115-1 — Geographic Information Metadata (Constraints & Legal Access Elements)