About Enprive
Have you ever installed an app, clicked "Agree", or allowed a permission without really knowing what you were agreeing to?
I started thinking about this because privacy decisions are part of our everyday lives, yet understanding them is not always easy. An educational app might ask for access to your contacts, or another app might request your location. Most people are left wondering why that information is needed. Privacy policies are often long, filled with unfamiliar terms, and difficult to understand.
I wanted to make that experience easier. That's how Enprive started.
Enprive helps people understand what apps say about their personal information before they agree to share it. Users can provide an app's privacy policy through a link, shared text or document. Enprive reviews the information, highlights important findings and shows the actual policy statements behind them. It can also inspect Android-reported app permissions locally, helping users compare what an app requests with what its developer discloses.
I built Enprive with Flutter and native Android integration using Kotlin. I combined policy retrieval and document extraction with AI-assisted analysis and a local rule-based scanner. I also created Deni, a friendly assistant that helps users understand findings in everyday language. Because privacy is the reason Enprive exists, I made local processing a priority and require users to give permission before a review sends information to cloud AI.
Building it taught me that identifying a permission is not the same as understanding how an app uses data. A permission does not prove that information was collected or shared, and a privacy policy does not prove that an app behaves exactly as described. That distinction became central to how Enprive presents evidence and uncertainty.
One of my biggest challenges was testing beyond sample data. Using real Android applications on a physical Realme device exposed problems I had not anticipated, including how Chrome shares links alongside preview images, cloud analysis getting stuck, and automated findings misinterpreting statements that explicitly deny data collection or sharing. These challenges pushed me to improve the app's reliability, make its explanations more careful and test it against real application behaviour.
I'm still working toward a more seamless experience where users can ask Deni questions at the moment an app requests sensitive information, rather than having to leave the app and investigate everything themselves.
Ultimately, I want people to feel more confident about the digital choices they make. Enprive doesn't decide what you should agree to. It helps you understand what you're agreeing to.
Enprive — Know what you're agreeing to.