# Protect your ClientDB like your mail server

> Your ClientDB holds the keys that let it speak as your company. Give it the same protection as your DNS and your mail server, and know what to do if it leaks.

Source: https://idtruster.com/business/how-it-works/protecting-clientdb/
Language: en

1.  [Business](https://idtruster.com/business/)
2.  [How it works](https://idtruster.com/business/how-it-works/)
3.  Protect your ClientDB like your mail server

How it works

Your ClientDB holds the keys that let it speak as your company. Give it the same protection as your DNS and your mail server, and know what to do if it leaks.

Last updatedNovember 16, 2026

Key takeaways

-   Both of your private keys are stored only in your ClientDB. Anyone who can call your ClientDB can speak as your company in the app.
-   Protect ClientDB at the same level as your DNS and your mail server, with the same owners, access rules, and monitoring.
-   If you suspect misuse, contact us. We can close your company's access to the ecosystem until your systems are under control again.

On this page

1.  [Why ClientDB speaks for your company](#why-clientdb-speaks-for-your-company)
2.  [The same level as your DNS and mail server](#the-same-level-as-your-dns-and-mail-server)
3.  [What to protect](#what-to-protect)

Your ClientDB holds both of your signing keys. Anyone who can call it can issue trust codes and answers that the app shows as coming from your company. That makes ClientDB as important as your DNS and your mail server. How the keys work is in [How your two signing keys work](https://idtruster.com/business/how-it-works/signature/).

## Why ClientDB speaks for your company

The app trusts an answer when it is signed with your answer key and the signature matches the public key in your DNS. Both private keys are stored only in your ClientDB. That is why ID-Truster cannot fake an answer from you.

It also means that the protection of ClientDB is in your hands. If someone else gets access to call your ClientDB, the app shows what they send with your business card.

## The same level as your DNS and mail server

You already protect the systems that show who you are online. Whoever controls your DNS or your mail server can send email in your name. ClientDB belongs in the same group. Give it the same owners, the same access rules, and the same monitoring.

## What to protect

-   **Who can call it.** Only your own systems, such as your CRM and your newsletter system, should be able to call your ClientDB.
-   **Passwords, tokens, and keys.** Store them in a secret manager, not in code or shared documents.
-   **Network access.** Limit which networks and servers can reach your ClientDB.
-   **Admin access.** Use multi-factor sign-in for everyone who can administer your ClientDB or your Supabase account, and keep the list short.
-   **Updates.** Install new ClientDB versions when we release them.
-   **Logs.** Keep logs of calls to your ClientDB and review them, as you do for your other critical systems.

## Questions about protecting your ClientDB

-   ### Does ID-Truster protect our ClientDB?

    No. You host and operate your ClientDB, and ID-Truster has no access to it. We test every ClientDB version before we release it, and you are responsible for the parts you host yourself.

-   ### Is a stolen password enough to speak as our company?

    Not towards the ID-Truster Hub. Every call to the Hub must also be signed with your connection key, and that key is stored only in your ClientDB. That is why access to ClientDB itself is what you need to protect.

-   ### What happens to our emails while our access is closed?

    They still go out as usual, because ID-Truster runs alongside your systems. Your customers just cannot check your trust codes until your access is open again.

See how your two keys are checked, and why ID-Truster cannot fake an answer from you.

[How your two signing keys work ](https://idtruster.com/business/how-it-works/signature/)

How it works

## More on how it works

-   ### [How your two signing keys work](https://idtruster.com/business/how-it-works/signature/)

    Your connection key and your answer key, who checks each one, and why ID-Truster cannot fake an answer from you.

-   ### [The ID-Truster stack](https://idtruster.com/business/how-it-works/stack/)

    What the app, the ID-Truster Hub, and ClientDB are built on, and how we test and release.

-   ### [How the ID-Truster ecosystem fits together](https://idtruster.com/business/how-it-works/architecture/)

    One app, the ID-Truster Hub in the middle, and a ClientDB at every company. The map of what runs where, and how it connects.
