Skip to main content
Skip to the page

Security

How the record is built, and what is not available yet.

Domavia is in pre-launch. The example tour uses representative records and browser-local sample state.

Public accounts, uploads, source connections, billing, and customer data workflows are not available.

Current public-site controls

Data minimization

The early-access request asks for an email address, an optional audience category, and explicit contact consent. It does not collect documents, payment information, tax information, or identity records.

Public-site protection

HTTPS, hosting-provider controls, security headers, and bounded abuse controls protect deployed public routes. Optional analytics initialize only after consent.

Preview boundary

The product tour is a guided made-up example. It does not create an account, accept uploads, connect to external sources, persist sample edits, or process payments.

How the record is built

No public account exists yet, so nothing below is a service you can use today. These are the properties the record is built on, and the reasons Domavia is willing to be measured against them later.

Append-only history

Record events are added, never edited or removed in place. Correcting a fact appends the correction and keeps what came before it. The event tables carry database triggers that refuse an update or a delete, rather than trusting application code to be careful.

Hash-chained events

Each event carries the hash of the event before it, and the database refuses an event that does not extend the current head of its chain or whose own hash does not match its contents. An event that was altered or put out of order does not link up, so it is rejected when it is written.

No direct table access

The application connects to the database as a role that holds no privilege on any customer table. It can only call named database functions from a fixed list that is declared in code and checked against the live database, so it has no way to run its own query against customer records, and the set of things it can do is a list rather than open-ended.

Sources stay authoritative

A record is designed to hold a reference, its provenance, and its review state beside the question it belongs to. The system that already owns a document keeps owning it. Domavia is not designed to become a second copy of every drive, mail account, or property system.

Figures carry a receipt

A calculated figure is published with the rule set that produced it, that rule set’s version, and a digest of the reading itself. The digest identifies that reading rather than addressing it: nothing here resolves one, so it is a fingerprint to compare, not a reference to look up. The same reading also names what it declines to determine. Each published rule set says in its own scope text that it makes no residency, tax, immigration, or compliance determination, and the day-count readings also carry a fixed flag that they are not a residency or compliance determination.

Compute is pinned to one region

The infrastructure configuration pins the product’s compute to one Hetzner datacenter in Nuremberg, Germany. That is a recorded configuration default, not a data-residency guarantee: the set of regions this platform accepts also includes datacenters in the United States, and this public site is served from a global edge network rather than from that datacenter.

Report a security issue

Email [email protected] with a clear, non-sensitive description, reproduction steps, and potential impact. Do not include credentials, documents, payment information, tax information, identity data, private keys, authentication codes, financial records, or medical records.

Privacy and certification boundary

The public privacy policy explains collection, consent, retention, and removal requests for the early-access form. Domavia does not claim SOC 2, ISO 27001, HIPAA, or PCI DSS certification.

Read the privacy policy