Bug reporting usually works against your privacy. When something goes wrong, most apps silently send device data, usage patterns, and sometimes screen recordings to third-party servers. You never opted in, and you never saw what was sent.
NeatPass handles this differently. Bug reporting is built around one idea: you decide what leaves your device, and you see exactly what it is before it goes.
You Decide What Gets Sent
Nothing is collected in the background. NeatPass has no analytics SDK running silently on launch. When you encounter an issue and want to report it, you initiate the process yourself.
Nothing automatic
No data leaves your device unless you tap Report Bug and confirm.
Full transparency
You preview every piece of diagnostic data before it's sent.
Minimal by design
Device model, iOS version, app version, and recent logs. That's it.
Attachments are optional
Documents are only included if you explicitly choose to add them.
Your Barcodes Never Leave
Sometimes reproducing a scanning issue requires the original document. A boarding pass, a concert ticket, a membership card. But those documents contain barcodes that grant real-world access.
When you choose to attach a document, NeatPass scans it for barcodes across all 18 supported formats and redacts them on your device before anything is transmitted. The layout and formatting that caused the issue are preserved, but your barcode data is removed.
On-device redaction
Try privacy-first bug reporting
DownloadNo Account, No Email Required
Submitting a bug report doesn't require creating an account or providing an email address. Each report generates a reference ID in the format NP-XXXXXX that you can use if you need to follow up.
Reports are delivered directly to the support system over an encrypted connection. No intermediary analytics platform, no third-party data processor touches your report.
What Stays Private
Without an attachment, bug reports contain only technical diagnostics: device model, iOS version, app version, and recent logs. No personal data, no barcodes, no document content.
If you choose to attach a document, barcodes are automatically redacted before transmission. Other content in the document, like event names or dates, will be visible since that context helps diagnose layout and extraction issues. That's why attachment is always opt-in and you preview everything before sending.
Learn more about bug report privacy