Most apps collect data about you the moment something goes wrong. Tools like Crashlytics and Sentry gather crash reports automatically, often including device identifiers, usage patterns, and sometimes even session replays of your screen.
NeatPass takes a fundamentally different approach. Bug reports only happen when you choose to send them, and even then, your sensitive data stays protected.
What Typical Apps Collect
When an app crashes or encounters an error, most use third-party services that collect extensive data automatically:
Automatic collection
Data sent without asking, starting from first launch
Detailed breadcrumbs
User actions, screens visited, buttons tapped
Device identifiers
Installation IDs and device details used to group reports
Session replays
Some SDKs like Sentry record screen activity around crash time
This data gets sent to company servers where it may be stored indefinitely, analyzed, or even shared with third parties for debugging or analytics purposes.
The hidden tracking problem
The NeatPass Approach
NeatPass has no automatic crash reporting. Nothing is collected unless you actively choose to report a bug. When you do, we collect only what's necessary to diagnose the issue.
What We Collect
When you submit a bug report, we receive:
You can review exactly what will be sent before submitting. See our bug reporting guide.
What We Never Collect
These items are never included in bug reports, even if you attach a document:
Your barcodes
Automatically redacted on your device before upload across 18 supported formats
Pass contents
Event names, dates, venues, seat numbers
Personal information
Names, emails, booking references, addresses
Usage analytics
No tracking of how you use the app
Privacy you can verify
NeatPass makes it easy to convert any ticket, pass, or loyalty card to Apple Wallet.
Automatic Barcode Redaction
If you need to attach a document to help us reproduce an extraction issue, NeatPass attempts to automatically redact barcodes and QR codes on your device before transmission.
This happens automatically. You don't need to manually redact anything. The document we receive shows the layout and formatting that caused the problem, but with barcode data removed. Redaction covers all 18 supported barcode formats, though it may not catch every personal detail visible in the document, so we recommend reviewing attachments before submitting.
content.barcodeRedaction.barcodesBefore content.barcodeRedaction.barcodesLinkcontent.barcodeRedaction.barcodesAfter
You control attachment
Comparing Approaches
Here's how NeatPass bug reporting differs from typical app crash reporting:
- Automatic collection without asking
- Detailed user behavior tracking
- Device identifiers for grouping and profiling
- Session replays capturing screen activity
- Data sent to third-party servers
- Often stored indefinitely
- Only when you choose to report
- No behavior or usage tracking
- No device identifiers collected
- Barcodes automatically redacted
- Sent directly to our support system
- Used only for fixing your issue
You're in Control
Every aspect of bug reporting in NeatPass is under your control:
- Opt-in only: Nothing is collected unless you tap "Report Bug"
- Preview before sending: See exactly what diagnostics will be included
- Choose attachments: Documents are only attached if you enable them
For more details on NeatPass's overall privacy approach, see our Privacy FAQ.
Why This Matters
Your tickets and passes contain sensitive information. A concert ticket has your name and a unique barcode. A boarding pass shows your flight details. An event pass might include seat locations or membership numbers.
Barcodes are access tokens
A leaked barcode could let someone else use your ticket
Personal details matter
Names, dates, and booking refs reveal your activities
Device-only processing
Your passes never leave your iPhone during normal use
Minimal diagnostics
We only collect what's needed to fix bugs
This philosophy extends to all of NeatPass. Your passes work offline because they're stored locally, not on our servers. When you need help, contact support.
Frequently Asked Questions
Bug reports you can trust
DownloadTransparency by Design
Bug reporting shouldn't be a privacy tradeoff. When something goes wrong, you shouldn't have to choose between getting help and protecting your data.
NeatPass shows you exactly what's collected, redacts sensitive information automatically, and only sends data when you ask. It's the same privacy-first philosophy that guides everything we build.
Learn more about privacy