Why We Build Privacy-First Apps
Privacy isn't a feature we bolt on - it's the foundation of everything we build. Here's why and how.
## The State of App Privacy
Most apps collect far more data than they need. Analytics SDKs, advertising identifiers, location tracking - it's become the default. But it doesn't have to be.
At Maktek, we take a different approach. We don't collect data we don't need, and we process everything on-device whenever possible.
Our Principles
### 1. On-Device First
Swipi analyzes your photos entirely on your device. No images are uploaded to any server. SpendWise stores your financial data locally and syncs only through your private iCloud container.
### 2. No Third-Party SDKs
We don't use Firebase, Mixpanel, Amplitude, or any third-party analytics. This means we know less about how people use our apps, but it also means your data isn't being sent to a dozen companies you've never heard of.
### 3. Minimal Permissions
Our apps only request the permissions they absolutely need. Swipi needs photo access - nothing else. SpendWise needs iCloud for sync - nothing else.
The Trade-offs
Building privacy-first apps means accepting some trade-offs:
- **Less data**: We can't A/B test features or track conversion funnels - **Harder debugging**: Without crash analytics, we rely on user reports - **No ad revenue**: Without tracking, targeted ads aren't possible
But these trade-offs are worth it. Our users trust us with their photos and finances, and that trust is earned by respecting their privacy.
How You Can Verify
Both SpendWise and Swipi have detailed privacy nutrition labels on the App Store. We encourage you to check them - you'll find that we collect no data linked to your identity.