NeatPass doesn't have user accounts. It doesn't run analytics. It doesn't track what you scan or when you use it. This isn't a limitation; it's a design decision. Here's how the architecture works and why I built it this way.
What Stays vs. What Leaves
When you scan a ticket, the entire ML pipeline runs locally on your iPhone's GPU. Your original document, extracted data, and generated pass never leave the device. There is exactly one exception:
- Original document (PDF, screenshot)
- Extracted text, dates, seat numbers
- Barcode data and pass content
- Scanning history and preferences
- A cryptographic hash for pass signing
- Required by Apple Wallet's signing protocol
- Verifies pass authenticity without exposing contents
Think of it like a notary
No Account, No Profile
NeatPass doesn't ask you to create an account because there's nothing to tie to one. There's no user profile, no usage history on a server, no recommendations engine that needs your data. You download the app, scan your tickets, and that's it.
No Account to Breach
No credentials stored anywhere means no credentials to leak in a data breach.
No Password to Manage
No password reset flows, no 2FA setup, no security questions to remember.
No Email List
No marketing emails, no newsletters, no 'we've updated our privacy policy' notifications.
Try the privacy-first pass manager
DownloadNo Analytics, No Tracking
I don't know how many times you open the app. I don't know which tickets you scan. That data would be useful for product decisions, but collecting it would mean building infrastructure to store and protect it, and asking you to trust me with it.
Instead, I rely on App Store reviews, direct support messages, and my own testing to guide development. Even bug reporting is built with privacy first. It's a slower feedback loop, but it's one that doesn't compromise your privacy.
The Business Case for Privacy
Simpler GDPR Compliance
No user data means the compliance burden is minimal. Nothing collected, nothing to protect.
No Breach Risk to Manage
No servers storing personal information means nothing for attackers to target.
One-Time Purchase Closes the Loop
No need to maximize engagement or optimize retention metrics. Just make a good app.
Why This Matters
Ticket scanning apps handle sensitive information by nature. Boarding passes contain booking references. Concert tickets have barcodes that grant entry. Membership cards link to personal accounts. The less of this data that exists on servers, the better.
I built NeatPass to prove that a utility app can be useful without being invasive. Your tickets are your business.
Have questions about your data?