Trust & transparency

What we run, how it's secured, what happens to your data, and what we've disclosed about how this page was built.

Infrastructure

• Services run on a single VPS at vps.open-data.world (OVH, EU region).
• Reverse proxy + automatic TLS via Caddy with Let's Encrypt.
• All service code runs in Docker containers; images pulled from upstream registries.
• Identity/SSO delegated to Keycloak at auth.unboxd.cloud.

Open source

The full deployment stack — compose files, landing page, this trust page — is public:

• github.com/opendataworld/data-platform
• github.com/opendataworld/OpenMetadata (fork of Apache-2.0 OpenMetadata)

Every component is itself open source: OpenMetadata, Airbyte, Zingg, Cube, Superset, Unomi, SurrealDB, TerminusDB, GraphDB.

Security posture

• TLS 1.2+ only; HSTS via Caddy defaults.
• Internal service ports (OpenMetadata 8585, MySQL 3306, Elasticsearch 9200, Airflow 8080) will be firewalled to localhost once production hardening lands.
• SSH access: key-authentication only (passwords accepted during the initial bring-up window, rotated after).
• Systems are patched on Ubuntu's unattended-upgrades schedule.

Data handling

• No visitor analytics or third-party tracking on this site or the landing page.
• No cookies set by site.open-data.world or trust.open-data.world.
• Logged-in data in OpenMetadata is stored in the VPS's MySQL + Elasticsearch volumes (persistent but not yet replicated or backed up off-box).
• Contact: open an issue on the data-platform repo.

AI disclosure

This site, its compose files, trust page, and initial OpenMetadata deploy were scaffolded with AI assistance (Claude Code, Anthropic) in collaboration with @opendataworld / AgentNxt / Autonomyx. Human review and approval gated each production action (repo transfer, deploy, TLS, DNS).

AI-generated content is marked where applicable. If you spot an error — in copy, links, or claims made on this page — please file feedback.