Legal & Disclaimers

NOTICE 01 Nominative Fair Use & Trademark Disclosures

All product names, logos, brands, service marks, and registered trademarks cited across this website and its affiliated demonstration platforms are the property of their respective owners. All company, product, and service names used on this website are for identification, interoperability, compatibility, and comparative benchmarking purposes only under the doctrine of nominative fair use.

Use of these names, logos, and brands does not imply endorsement, affiliation, sponsorship, or certification by their respective trademark holders. Below is an explicit schedule of trademark acknowledgments:

NOTICE 02 Data Provenance & Public Scientific Corpuses

UniDB field tests utilize open-source, academic, and public-domain data corpuses to evaluate real-world storage density, graph traversal speeds, and vector search latencies:

• Space Weather Telemetry (UniDB-SpaceWeather): Solar wind plasma observations, interplanetary magnetic field orientation ($B_z$), Kyoto $D_{st}$ indices, and GOES X-ray flux are ingested from open public scientific data feeds provided by the NOAA Space Weather Prediction Center (SWPC) and the NASA Space Weather Database of Notifications, Knowledge, Information (DONKI).
• Kernel Threat Telemetry (UniDB-Hunter): Kernel telemetry schemas and attack behavioral profiles are modeled after the public BETH (Behavioral eBPF-based Threat Hunting) honeypot dataset developed by researchers at Imperial College London and KTH Royal Institute of Technology, capturing real-world eBPF syscall events from decoy container workloads exposed to the internet.
• Code & Symbol Topologies (UniDB-PyAtlas): Symbol definitions, abstract syntax trees, and type annotations are derived from publicly distributed packages indexed from the Python Package Index (PyPI) and public type stubs (such as Typeshed) strictly for transformation, symbol discovery, and relationship navigation. Original package source codes remain subject to their respective open-source licenses.

NOTICE 03 Engineering Benchmark Methodology Disclaimers

All performance figures, latency measurements (e.g., sub-microsecond point lookups, nanosecond bitemporal horizon queries), ingestion rates, and detection metrics (recall, precision, F1-scores) published on this website and in field test scorecards reflect specific, reproducible engineering benchmark environments:

• Hardware Environment: Benchmarks are conducted on dedicated x86_64 hardware utilizing AVX2/AVX-512 SIMD vector register instructions and NVMe memory-mapped storage. Performance in virtualized environments, multi-tenant cloud instances, or architectures lacking SIMD extensions may vary.
• Comparative Tests: Comparisons against third-party systems (such as SQLite, DuckDB, RocksDB, or Redis) reflect specific workloads, data layouts, and configurations described in respective benchmark whitepapers. They do not constitute universal claims of absolute superiority across all possible production scenarios.
• Zero-Knowledge Evaluation: Security detection benchmarks are evaluated blindly against external ground-truth oracles. No detection model achieves 100% precision without overfitting; false positives and known limitations are transparently cataloged in respective field test dashboards.

NOTICE 04 Non-Operational & "AS-IS" Software Warranty Disclaimer

UniDB and its field test applications are independent software systems and engineering demonstrations provided on an "AS IS" and "AS AVAILABLE" basis, without warranties of any kind, whether express, implied, statutory, or otherwise, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, non-infringement, or uninterrupted availability.

Critical Operations Notice: Neither UniDB nor its field test applications are certified for use in safety-of-life systems, primary aviation navigation, medical devices, emergency response, nuclear facility controls, or official governmental hazard warnings. Users are solely responsible for evaluating the suitability of the software for their intended use cases.