Engineering Digital Discretion
16/08/2026 · 10 min read
In luxury real estate, discretion is not a luxury. It is part of the service.
A property listing may appear public, but the information surrounding it often is not. Behind a single enquiry can sit a buyer's identity, their preferences, their budget, their search history, conversations with an agent, saved properties, geographic interests and, in some cases, information relating to an entire property portfolio.
For an agency, the information can be even more commercially sensitive.
Listings. Leads. Client relationships. CRM integrations.
The more useful a property platform becomes, the more important it becomes to protect the information that makes it useful.
That is why security at Domus Inventum is not treated as something that sits behind the platform. It is part of the platform itself.
Our technology division, TDV Labs, approaches information security on the same principle that governs the rest of Domus Inventum: trust has to be earned.
We do not expect users to trust us simply because we tell them that their information is safe. We try to show them how we protect it.
Security begins beneath the application
Domus Inventum is built on modern cloud infrastructure and managed services designed around established information-security and privacy practices.
Our application architecture uses encrypted connections for data transmitted between users, the platform, external services and integrated property feeds.
Authentication and authorisation are handled independently from the public-facing property experience, while administrative operations are subject to additional server-side controls.
This matters because security cannot depend upon what happens in the browser.
A button being hidden does not make something secure.
A page being inaccessible does not make the underlying function secure.
Every sensitive administrative operation therefore remains protected at the server level, independently of what the interface happens to display.
The interface can provide another layer of protection, but it can never be the only one.
Two-factor authentication, by choice
Security should not become an obstacle to using the platform.
At the same time, users should have the ability to protect their accounts beyond a password.
Domus Inventum therefore provides optional TOTP two-factor authentication through the Privacy Centre.
Users can enrol an authenticator application using a QR code or manual setup key and confirm the enrolment using a six-digit verification code.
Once enabled, the factor can be used to provide an additional layer of assurance when accessing the account.
There is also an important distinction between ordinary account activity and actions that have greater consequences.
For billing changes, Domus Inventum uses step-up authentication.
If two-factor authentication has not been configured, a user attempting to change their subscription is directed to enrol first.
If it has been configured, the user is asked to provide their current authenticator code before the billing action proceeds.
Once recently verified, the session can remain elevated for the appropriate period rather than forcing the user through the same process repeatedly.
The principle is simple:
the more consequential the action, the greater the assurance we should require.
The administrative system is different
There is another problem with security that is often overlooked.
The people who administer a platform have access to considerably more information than ordinary users.
That makes the administrative interface itself a particularly important security boundary.
At Domus Inventum, administrator access is already protected by server-side authorisation.
But we decided that this was not enough.
So we added another layer.
We call it the JIT Admin Panel Lock.
JIT means Just-In-Time.
The idea is straightforward: administrative access should not simply remain permanently available because an administrator is already authenticated.
Instead, access to the sensitive administrative interface can be locked.
When it is locked, the administrator can be authenticated and still be unable to access the protected administrative environment.
The interface itself is deliberately obscured behind a restricted-access screen.
To enter, a fresh one-time code must be requested.
The unlock code does not appear in the application. When an administrator requests access, Domus Inventum generates a temporary, single-use verification code. The code is delivered through a separate, private authentication channel rather than being exposed within the application itself.
This is deliberately more cumbersome than simply clicking an "Unlock admin" button.
That is the point.
Administrative access is not something we want to make unnecessarily convenient.
The JIT mechanism does not replace authorisation. It adds another security boundary on top of it. That distinction matters.
If the JIT layer were somehow bypassed, the underlying administrative functions would still require their own authorisation.
There is no single switch on which the security of the entire system depends.
Access expires
Unlocking the administrative panel is not intended to create a permanent administrative session.
The current implementation permits an active unlock grant to remain valid within a defined maximum period, while the interface monitors administrator activity.
After a period of complete inactivity, the administrative interface locks again.
The screen is obscured and a fresh unlock code is required.
The lock state is also revalidated when navigating between administrative routes and when the browser regains focus.
In other words: being authorised to administer Domus Inventum does not mean the administrative panel has to remain permanently open.
Oraculum has a role in security too
Oraculum is not simply the conversational intelligence layer of Domus Inventum.
It also forms part of the platform's internal operational architecture.
The Oraculum Executive capability has a narrowly defined role in the JIT administrative process: delivering one-time administrative unlock codes through the founder's private Telegram channel.
That capability does not give Oraculum unrestricted administrative authority.
The principle remains the same elsewhere in the system: intelligence should assist people without quietly acquiring powers that it does not need.
This distinction becomes increasingly important as AI becomes more deeply integrated into software platforms.
An AI system does not become safer simply because it is intelligent.
It becomes safer when its permissions are deliberately constrained.
Your conversations with Oraculum are not our product
Oraculum is designed to work with Domus Inventum's own property and geographic intelligence rather than turning user interactions into a source of training data for public AI models.
User queries, searches and conversations therefore need to be treated as information belonging within the platform's privacy architecture.
That principle becomes particularly important as Oraculum develops further.
A buyer might ask about a particular neighbourhood. An investor might explore a particular market.
Those interactions can reveal considerably more than a simple property search.
The platform should therefore treat the intelligence generated through those interactions with the same discretion as the property data itself.
For agents, security is commercial protection
For a property professional, data security is not an abstract technical concern.
Your listings represent relationships, your enquiries represent potential clients. Your reputation is attached to all of them.
A property platform should therefore never treat an agency's data simply as something it is entitled to exploit because the agency has uploaded it.
At Domus Inventum, we believe the opposite.
The agency is entrusting that information to us.
That creates an obligation. And that obligation becomes greater as the platform becomes more useful.
For buyers, privacy should not require a premium
The same principle applies on the other side of the transaction.
A buyer should be able to explore property without feeling that every interaction is becoming another commercial asset to be traded.
Searches, conversations, saved properties and interactions with Oraculum can reveal preferences that a buyer may reasonably expect to remain private.
That does not mean pretending that data does not exist.
It means being clear about what happens to it and giving users meaningful controls.
And it means building deletion, anonymisation and account-management processes that respect the fact that people can change their minds.
Because they do.
Even leaving is part of security
Trust is not tested only when someone joins. It is tested when someone leaves.
A user can close their Domus Inventum account.
Their profile and listings are removed from public visibility.
Their active platform activity is stopped.
And, rather than pretending that deletion is an instantaneous and irreversible event with no room for human error, Domus Inventum provides a defined period in which the account can be restored before permanent anonymisation takes place.
The user is reminded before that deadline and the account remains deactivated during the period.
Restoration requires an intentional action through the Privacy Centre. That is deliberate.
People make decisions quickly. Sometimes they make them when they are frustrated, angry or simply having a bad day.
A good privacy system should respect the user's decision to leave while also recognising that a person changing their mind is not the same thing as a security failure.
Transparency is part of the architecture
There is a temptation in technology to make security sound mysterious. Complex terminology can create the impression that something must be sophisticated because nobody can understand it. We take a different view.
The more important the system, the more clearly its principles should be explained.
Two-factor authentication. Step-up verification. Server-side authorisation. Time-limited administrative access. Hashed one-time codes.
Automatic re-locking. Privacy controls. Data export. Anonymisation.
These are not particularly glamorous technologies, but they are sensible ones.
The important part is putting them together deliberately.
Security is not a claim. It is a process.
No platform can honestly promise that it will never experience a security incident. No responsible technology company should make that promise.
Security is a continual process of reducing risk, monitoring systems, reviewing architecture and improving controls as the platform evolves.
That is particularly true for Domus Inventum because the platform itself is evolving. The property industry is changing. Artificial intelligence is changing it.
The information being created by property searches is becoming richer. The expectations of buyers, sellers and agents are changing. The attack surface changes with them.
Our security architecture has to change too.
Why we publish this
We could simply put a padlock icon somewhere on the site. We could say that security is important. We could use phrases like enterprise-grade, bank-level or military-grade and leave people to assume that they mean something.
We would rather show you what we actually do.
Because this is ultimately the same philosophy behind Domus Inventum itself.
We do not believe that trust should be manufactured through marketing.
It should be created through behaviour, visible in the product and the policies.
It should particularly be visible in the way we treat your information.
And, when something goes wrong or something changes, it should be visible in the way we respond.
Trust is not something we ask you to give us. It is something we believe we have to earn.
FAQ
Does Domus Inventum offer two-factor authentication?
Yes. Users can enable TOTP two-factor authentication through the Privacy Centre. Two-factor authentication is also required before making subscription changes to an account where it has not already been verified.
How is administrative access protected?
Domus Inventum uses a Just-In-Time administrative access layer in addition to existing server-side authorisation. Privileged access requires a temporary, single-use verification code and automatically returns to a locked state after inactivity.
How does Domus Inventum protect Oraculum interactions?
Oraculum is designed as a private intelligence layer within Domus Inventum. User interactions and platform intelligence are not provided to external public AI models for the purpose of training those models.
What happens when I close my Domus Inventum account?
Your account is immediately closed and removed from public visibility. A defined period follows during which you can download your data or explicitly restore the account before permanent anonymisation takes place.
Does Domus Inventum publish its security architecture?
We explain the principles and safeguards we use because we believe transparency builds trust. We deliberately do not disclose operational details that could provide a blueprint for circumventing those safeguards.
Useful Links
Domus Inventum. Home, found.