PRIVACY & CREDITS.
A clear description of what this website does and the external services it may contact.
Personal data
This initial version does not include user registration, advertising tracking, analytics trackers or a marketing database. It does not intentionally set profiling cookies. Standard server access logs may be retained by the hosting provider for security and operations.
External data requests
The Space Newsroom retrieves headlines, summaries, publication times and article image URLs from Spaceflight News API, using our optional ASP relay or a direct browser request if available. When article thumbnails load, browsers may connect to external image hosts owned by the publisher; opening articles leads to external sites with their own privacy policies. No reader account or MARTE-D tracking is required.
Orbital data is loaded through a MARTE-D server endpoint that requests public datasets from CelesTrak and caches them. The space-weather page first uses the website's server endpoint; if it is unavailable, the browser may request public NOAA SWPC data directly. The Deep Space Observatory first uses a MARTE-D GWOSC proxy, with direct requests to GWOSC on failure. In those fallback cases, your IP address may be visible to NOAA or GWOSC respectively. Browser network requests use the provider's own terms and privacy arrangements. New scientific sections use NASA/JPL close-approach predictions through a server-side read-only proxy and external article listings from Spaceflight News API. Their respective providers have their own data and publishing policies.
Fonts
The interface can request display fonts from Google Fonts. This involves contacting Google's font delivery services. System fonts are used as a fallback when unavailable.
Cookies and storage
MARTE-D does not require registration or profiling cookies. Mission Operations saves user-created research events and watchlists in browser localStorage where permitted. The V9 Mission Assurance page may store a small summary of the most recent manual API audit locally in the browser; no raw provider dataset is stored by that function. Clearing site data removes these local records. Reports and calendar files are downloaded only when the user requests export. The V9 Mission Briefing does not submit research selections or its reports to a MARTE-D account or database. Hosting provider access logs may still apply. Some data and font requests may contact third-party services as described above.
Scientific integrity
Software models are educational approximations, not real-time spacecraft telemetry, safety-critical orbital predictions or operational flight plans. Data sources may fail, become stale or be temporarily unavailable. MARTE-D is an independent project and is not affiliated with NASA, ESA, SpaceX, NOAA, CelesTrak, GWOSC, the LIGO/Virgo/KAGRA collaboration or Einstein Telescope.
Images and attributions
Space Newsroom thumbnails belong to external publishers and are shown for source-linked previews; fallback imagery is local to MARTE-D. Third-party article text and imagery are not original MARTE-D reporting.
Earth imagery: NASA Blue Marble (via Matplotlib Basemap’s bundled bmng.jpg). Mars surface graphic: custom procedural, illustrative reconstruction created for MARTE-D, not scientific terrain imagery. Page graphics, orbital visualization and UI are original programmatic renderings. No organizational logos or official insignia are implied.
External data: CelesTrak and NOAA SWPC. Gravitational-wave events: GWOSC (CC BY 4.0, credit to LIGO/Virgo/KAGRA). Scientific context: NASA Science.
Additional V5 sources and calculations
MARTE-D V5 contacts The Space Devs (Launch Library 2) for launch schedules, NASA/JPL CNEOS Sentry for planetary-defense records, NASA GIBS for public satellite images, and NOAA SWPC for solar bulletins and flare summaries. When server relays are unavailable, direct browser requests to public APIs may occur; the provider may log your IP address. Image loads for NASA GIBS are browser-to-NASA requests. See each provider's own privacy terms.
Navigation and simulation inputs are processed locally in your browser. The mission transfer engine uses approximate circular coplanar orbits; orbital separation uses simplified two-body propagation; rover terrain is synthetic. MARTE-D is independent and is not affiliated with NASA, ESA, SpaceX, NOAA, JPL, CelesTrak or The Space Devs.
V6 scientific source and attribution
The ephemeris tool requests public state vectors from NASA/JPL Horizons through MARTE-D's same-origin ASP relay. NASA/JPL operates the scientific dataset; MARTE-D independently visualizes results. None of these components represent an official NASA, ESA or SpaceX operation.
Scientific runtime and uploaded data
The Space Traffic page loads the pinned open-source satellite.js 6.0.1 (MIT) SGP4/SDP4 library from the Cloudflare cdnjs content delivery network. This connects your browser to an independent third party, which may receive standard request information such as your IP address. If loading fails, MARTE-D suppresses model results rather than pretending SGP4 is active. The other calculation modules do not require this library.
The Earth NDVI analysis reads CSV reflectance pairs locally in your browser; it does not upload the file to MARTE-D or a third party. The demonstrated example is synthetic and not derived from real Sentinel observations. JPL Horizons vectors and launch data are requested through the existing same-origin ASP relays, subject to source availability.
In Space Traffic V7, SGP4 replaces the two-body separation approximation of the initial V5 view when the library loads. It does not add collision probability modeling, operational reliability, or proprietary flight data.
Mission Operations Desk stores your milestones and selected mission references in browser local storage when enabled. Files selected for the trajectory, terrain and propulsion laboratories are processed within your browser; they are not automatically uploaded to MARTE-D. You can export your data and clear this site's browser storage. External publisher and data-provider links have their own policies.
