DRM3 Rails · for anyone who holds data

Your data stays yours.

Data you sell carries more risk than most. So the protection is part of how a desk works, and you can check each part.

One key per desk

A desk reads its dataset through the same metered door any outside app would use, with a key that belongs to that desk alone. Signal Desk holds no backstage key to your data. Revoke the key and the desk stops reading.

Private in the query

A customer's records are marked private where they are stored. Every public page asks for records that are not private, in the query itself. A setting flipped by mistake cannot put them on a public page.

Behind a sign-in

A desk sits behind a sign-in wall. Buyers are invited by email, and the roster is the customer's to manage. An address that is removed meets the wall on its next request.

Two-step sign-in for admins

A desk can require that its admins sign in with a passkey or an authenticator code. Admins are the people who invite buyers, export the audience and hold the API keys. With the rule on, a password alone opens nothing on that desk for an admin. Only an admin who already signed in that way can change the rule, and no API key can.

Never mixed with anyone else's data

A customer's records do not enter shared search, another desk, or any data pack. One desk reads one customer's data.

Yours to take back

Delete a dataset and every door to it shuts at once: the keys, the shares and the API. The data itself is removed right away, or after a one-day grace period if you want a way back.

The source on every signal

Each signal shows the source record it stands on, so a buyer can open it and compare. See where a signal comes from.

Questions from your security team? Send them to us.