01
Problem
Businesses want AI in their workflows but cannot send raw customer data to third-party models. PII leakage is a hard blocker, not a nice-to-have.
Available for software engineering roles - backend systems, production reliability, cloud deployment, and AI-assisted workflows.
Local PII scrubber that acts as a security guard in front of AI workflows, grounded in TDPI paper research (March).
Main outcome
Gives businesses an always-on privacy guard for AI-touched data.
Secondary signal
Lets teams adopt AI without routing raw customer data through external APIs.
Evidence count
3 proof points
01
Businesses want AI in their workflows but cannot send raw customer data to third-party models. PII leakage is a hard blocker, not a nice-to-have.
02
Built a local Dockerised blackbox that scrubs inbound data before it reaches a model and checks outbound responses before they reach the user, with deterministic rules independent of any specific model.
03
Privacy infrastructure builder · Dockerised guard-rail designer
Next field note
Open to software engineering roles across full-stack systems, platform and reliability work, workflow automation, and applied AI.
Write to Himanshu Lade →