How to Secure a Flow So It Can't Be Viewed or Copied After Deployment?

We're building a Flow in a scoped app, and we'd like to ensure that when it's deployed to a different instance (such as a customer or client environment), the Flow remains protected. Ideally, we want to prevent even system admins in that instance from accessing or copying the Flow logic.

Has anyone implemented this kind of protection before? Is there a way to make the Flow or its components read-only, hidden, or otherwise secure through scoped app settings or protection mode? Any best practices or suggestions would be appreciated!