The terms, policies and commitments for HeliosDB Cloud, commercial licences of HeliosDB Lite and HeliosDB Full, support, partners and visitors of this site. Each document is versioned: this site shows the version in force, and the HeliosDB legal register keeps every version with the exact text for download.
How HeliosDB uses personal data on its websites, the Cloud Service, the Partner Portal and AI Support, and your rights.
Licence terms for HeliosDB Lite and Full under a commercial licence: PDUs, evaluation, refunds, price protection and taxes.
Terms of HeliosDB Cloud: business accounts only, no trial, the free Experimental Period, durability instead of uptime, export and suspension.
GDPR Article 28 terms for personal data HeliosDB processes on your behalf, with transfer clauses and the sub-processor list.
Best-effort, AI-coordinated support from a pool of workers, prioritised per customer, with non-binding targets and no service credits.
Acknowledged commits are not lost because of HeliosProxy in the path or the HeliosDB Full version in use (in the Cloud, the engine version HeliosDB runs); scope, exclusions and remedies.
How the Release and Capability Matrix and the Compatibility Matrix are built, what each status means and how they bind HeliosDB.
What an integration must show to be certified, how certificates expire and are renewed, and how the certification name may be used.
How HeliosDB names and logos may be used, by everyone and by partners.
HeliosDB is a trading name of Dimen Sigon OÜ, a private limited company registered in Estonia under registry code 16757774, Ahtri 12, 10151 Tallinn, Estonia. Questions about these documents: support@heliosdb.com (subject “Privacy” for data protection). Security reports and suspected personal-data breaches: security@heliosdb.com.
HeliosDB Nano and HeliosProxy are licensed under Apache 2.0, and HeliosDB Lite and HeliosDB Full are source-available under SSPL-1.0. The Customer Terms add a commercial licence for Lite and Full for organisations that want one; they do not limit rights anyone has under those licences.
A published text is never edited. A change of wording is a new version with its own effective date, change log and SHA-256 fingerprint, announced with the notice the document itself requires; earlier versions stay readable and downloadable in the register.