Privent × AmbactiBring Privent into
the flow of work.
A little less busywork with Privent.
Session1 capabilities+
- Open a session
Opens a Privent session vault at the start of your workflow. Place this node before any Tokenize operations. The sessionId output must be passed to all downstream Privent nodes.
Tokenize1 capabilities+
- Tokenize sensitive text
Replaces sensitive values with reversible [KIND_NNN] placeholders before the text reaches an LLM or external service
Detokenize1 capabilities+
- Detokenize text
⚠ Agent-reachable as a tool: an agent could un-mask data with this operation. Use Strict Mode + Trusted Sinks to control egress. Resolves [KIND_NNN] placeholders back to their original values before data leaves the workflow.
Risk Check1 capabilities+
- Score text risk
Scores text for data-leak risk using Privent ML. Returns risk_score (0–1), risk_level, and per-category probabilities.
Audit1 capabilities+
- Emit an audit event
Emits a Privent audit event for non-tokenization steps (LLM call cost tracking, policy decisions, egress, errors)
Handoff1 capabilities+
- Record an agent handoff
Marks an explicit agent → agent (or agent → external sink) handoff for the Trust Map
Frequently asked
questions.
What could an Ambacti integration do with Privent?
The documented operations include Session: Open a session; Tokenize: Tokenize sensitive text; Detokenize: Detokenize text; Risk Check: Score text risk.
Could I keep a workflow read-only?
For a read-only workflow, limit account permissions to reading data and exclude actions that create, update, or delete records.
Will every action run automatically?
Choose which steps could run on their own and which should pause for review. Changes should follow the permissions and approval rules you set.
Do I need to review actions in Privent?
Decide which work could run on its own and which steps need your review.