Security and controls
Last updated 1 September 2026
What this page is
RadarCipher reads your customer conversations and your pipeline. Everything below is a property of code that exists today, not an intention — each one can be checked against the running product, and several are enforced by the database rather than by the application that talks to it.
The controls
Your data is separated in the database, not just in the code
Every table holding a customer’s data is under PostgreSQL row-level security, and the role the application connects as cannot switch it off. A query that forgets to filter by organisation returns nothing rather than somebody else’s findings. The rule is enforced by the database and tested against it.
forced row-level security
Permission is checked on the server, every time
What a person can do is decided by their role in that organisation, and it is decided by the API rather than by which buttons the interface happens to show. Billing and team controls are not visible to an ordinary member, and are refused if requested directly.
capability checks, not hidden buttons
Nothing consequential happens without a person
RadarCipher drafts, recommends and waits. Approving a draft a colleague has since revised is refused rather than guessed at, and approving the same thing twice does not do it twice.
recommendation ≠ approval ≠ execution
It tells you what happened, not what it attempted
A queued message says queued. A failed one says why. An action carried out by a system that contacts nobody says exactly that, rather than reporting success. If RadarCipher cannot prove an outcome, it does not claim one.
queued ≠ sent ≠ received
Every consequential action is written down
Who approved what, when, and what came of it — kept as an append-only history that the application cannot rewrite. Changing a role, connecting a system, or ending a subscription all leave a record.
append-only audit history
Support access is granted, not assumed
RadarCipher’s support tools do not show your organisation’s business content by default. Viewing it needs a support session opened with a recorded reason: read-only, limited to your organisation, ended automatically within eight hours or sooner by hand, and recorded — and while it is open, the person using it sees a banner naming whose data they are looking at.
reason required, read-only, time-limited
Your account is yours
Password changes sign out every other device. Two-step sign-in with an authenticator app is supported, and removing it requires the password. You can see every device signed in as you and end any of them.
two-step sign-in supported
Detection is a judgement, and it shows its working
RadarCipher can raise something you decide is not important. That is why every finding carries the evidence it was built from and the reasons behind its score — so you can disagree with it on the specifics rather than on faith.
evidence, not a black-box score
What RadarCipher does not claim
RadarCipher holds no SOC 2 report, no ISO 27001 certification, no third-party penetration-test certificate and no compliance attestation of any kind, and it publishes no uptime guarantee.
It is a new product, and those things take time and independent auditors. This page will say so when they exist and not before. If your procurement process needs any of them today, write to support@radarcipher.com and you will get a straight answer about where we are rather than a brochure.
Reporting something
If you believe you have found a security problem in RadarCipher, write to support@radarcipher.com. Tell us what you found and how to reproduce it. There is no bounty programme and this page will not pretend otherwise; there is a person who will read it and reply.
Related
Questions about this document: support@radarcipher.com.