Site policy

Editorial Disclaimer

Last reviewed October 20, 2026.

Independent and unofficial

SpatialAPI.xyz is an independent publication. It is not affiliated with, sponsored by, endorsed by, or an official documentation site for any company, standards organization, open-source project, device maker, engine, map provider, or AI platform referenced in its content.

References to third-party names describe technologies or sources. Readers should use current official documentation for implementation details and licensing requirements.

Technical and AI limitations

Architecture guidance cannot account for every product, jurisdiction, device, dataset, threat model, or runtime. AI, computer vision, GPS, localization, mapping, depth, and scene understanding can be uncertain or wrong. A fluent model response is not proof of geometry, identity, permission, safety, or physical truth.

Use deterministic validation, explicit confidence, human review, and fail-safe behavior appropriate to the impact of the application. Do not rely on the site for emergency navigation, medical decisions, public safety operations, or other high-consequence activity.

Physical-world safety

AR, VR, glasses, robots, maps, and location-based experiences can distract users or direct them through physical environments. Test for obstacles, traffic, boundaries, motion comfort, accessibility, bystanders, and changing conditions. Provide a safe non-immersive exit and do not encourage movement while attention is fully occupied by a display.

Persistent anchors and public overlays need moderation, provenance, removal, and abuse controls. Content placed in a location can become misleading or unsafe when the environment changes.

Corrections

Corrections can be sent to [email protected] with the page URL, the statement at issue, and a primary source when available. A correction request does not guarantee a particular editorial outcome, but supported factual issues should be reviewed.

This disclaimer is dated October 20, 2026.