We use InPrivy for a narrow job: securely sharing information when a full client portal or collaboration platform would be unnecessary.
That focus is what we like about it. Sometimes the right experience is not “create an account, join a workspace, learn a portal.” It is simply “here is the protected information you need, through a controlled sharing surface.” InPrivy fits that use case well.
We also value the ability to use our own branded custom domain for the sharing experience. That makes a focused secure-share tool feel like part of our normal client-facing workflow instead of sending someone to an unrelated third-party URL.
We are intentionally not trying to make InPrivy our document-management system or client-operations platform. We already have broader tools for those jobs. Its value is that it stays comparatively simple and gives us a purpose-built option when secure sharing is the actual requirement.
The biggest improvement for our use would be deeper automation and audit integration: an API/webhook path to create and expire shares, retrieve current state, and read view/access events would make it much easier to use InPrivy inside a governed workflow while keeping the provider as the secure execution layer.
For the focused job it solves, InPrivy has been a useful addition to our stack. I would rather have a small tool that does this job cleanly than force every occasional secure exchange into a much heavier portal.