How it works, and how to check it yourself
“Private” is easy to write on a website. Here is the architecture, and a test you can run in about a minute without trusting a word of this page.
Test it in airplane mode
Turn on airplane mode. Scan a document, run OCR, export a searchable PDF, use the PDF tools. Everything works, because none of it needs a network. An app that quietly depends on a server cannot do that.
What the app is built from
Privascan is native Swift and SwiftUI. Everything it does comes from frameworks Apple ships inside iOS:
| Job | Framework |
|---|---|
| Camera capture and document detection | VisionKit |
| Edge and rectangle detection | Vision |
| Text recognition (OCR) | Vision |
| Perspective correction and enhance filters | Core Image |
| PDF creation, assembly and encryption | PDFKit |
| File-name suggestion | On-device models, with an OCR fallback |
| The Pro purchase | StoreKit |
Zero third-party dependencies
The project has no Swift Package Manager dependencies. No analytics SDK, no crash reporter, no advertising or attribution library, no networking library. There is no code in the app from anyone other than Apple and us.
That is not a policy setting that could be flipped quietly: there is no networking code for us to point at a server. Exporting and sharing, which you trigger yourself, go through the system share sheet.
The one time data leaves
When you export or share a file. At that point it goes wherever you send it — Mail, Files, iCloud Drive, another app — and it follows that destination’s rules, not ours. Privascan never initiates it.
What about the purchase?
Buying Pro goes through Apple’s StoreKit, which talks to Apple. We receive no personal data from it — the app only ever learns whether this Apple ID owns the unlock. There is no Privascan account and no server on our side to store anything in.
Free beta. Privascan is in App Store review; the beta is the current build.