Find the identifiers
Inspect detected names, contact details, and other supported identifiers alongside their confidence scores.
CLINICAL RESEARCH · PRIVACY PROTOTYPE
Useful insights.
Fewer identifiers.
A clearer view of what your clinical text contains. Detect sensitive information, explore masking, and review every step in one research workspace.
Bring your tester API key. No account signup needed.
A LITTLE LESS IDENTIFYING 01 / 02
SYNTHETIC INPUT01
Patient Alex Morgan attended a routine follow-up.
Contact: alex@example.com
↓Detect & replace
MASKED FOR REVIEW02
Patient [PERSON_001] attended a routine follow-up.
Contact: [EMAIL_ADDRESS_001]
Synthetic example.
Research demo hosted on AWS. Use synthetic or de-identified notes only.
RESEARCH DEMOFROM TEXT TO TRANSPARENCY
Follow the information.
Understand the decision.
Two ways to explore: analyze a note, or simulate a round trip to see how tokens are restored.
Make the replacement visible
Compare the masked text and policy decision. See which details were replaced and review for anything missed.
Test the return journey
Simulate a response and restore its tokens within the gateway. A blocked policy skips restoration. No cloud LLM is called.
THOUGHTFUL BY DEFAULT
Small details.
Meaningful safeguards.
Built to make testing easier to understand, with clear boundaries around access and data handling.
Explore the API documentation ↗Your key. Your access.
Processing requests require a tester API key, with request limits enforced by the gateway.
A session that clears itself
Keys, notes, and results clear after five idle minutes. End your session at any time.
A record without the note
Audit records capture processing metadata. Clinical text and API key values are excluded from audit logs.
READY TO TAKE A CLOSER LOOK?
Start with a synthetic note.
Load the example in the workspace and follow what happens.