Proof you can check.
For privacy, compliance and governance teams: what the engine will not do, how each decision is checked, and what its output is ready for.
Try it: the note on the right hides a relative’s name in plain prose. Compare pattern-based masking with Tidegate.
Six things the Tidegate engine will not do.
- {{ n.n }} {{ n.k }}{{ n.v }}
Ready for your expert, not a substitute for one.
The life of one decision, on the record.
Each step records who or what acted, the evidence, and the versions in force. Merges can be reversed, and the reversal is recorded too.
-
{{ e.k }}{{ e.when }} {{ e.v }} {{ e.meta }}
What we report, in the order we report it.
Every result is tested against records labeled by trained reviewers, every release. A missed identifier is treated as a safety event.
- {{ m.n }} {{ m.k }} {{ m.v }}
Your environment. Your keys. Our evidence.
Tidegate runs in a cloud account you control, under your encryption keys. We never pool or sell data. The security packet gives your review team the detail behind every claim in this section.
Request the security packetWhat’s in the security packet
Organized the way security, privacy and procurement teams review a vendor. We send a short NDA first, then the packet.
- {{ it }}
Report a security issue
Email compliance