FairScan · Legal

Privacy Policy

Effective 25 September 2026 · Applies to FairScan for iPhone and Mac (version 1.8 and later)

The short version: FairScan has no account, and your documents never leave your device. Scans, imported files, recognised (OCR) text, document and folder names, signatures, ID card copies and PDF passwords are processed and stored only on your iPhone or Mac. To run and improve the app, FairScan does send a limited amount of other data to service providers: usage analytics and crash reports (Google Firebase), a push-notification token (Firebase Cloud Messaging and our own notification server), purchase status (Apple and RevenueCat), and — only if you choose to send it — feedback you write in the app. There are no ads, no tracking across other companies' apps or websites, and we never sell data. Every detail is below.

1. What stays on your device

The following is handled entirely on your device and is never sent to us or to any third party:

Your documents — camera scans, photos you import, PDFs and images you open in FairScan, and every PDF the app creates, merges, compresses, redacts or edits.
Document text — text recognition (OCR) uses Apple's on-device Vision framework. The recognised text is never uploaded.
Names — document names, file names, file paths and folder names.
Signatures you draw, and the areas you redact.
ID card copies — the card images and anything printed on them.
QR and barcode contents you scan.
PDF passwords — when you export a password-protected PDF, the password is used on your device to encrypt that copy. It is not stored or sent anywhere.
Scan reminder schedule — the optional scan reminder is a local notification scheduled by your device. Its day and time never leave your device.

Your library is stored in FairScan's private storage on your device. FairScan does not sync your documents through iCloud or any other cloud service. A document only leaves the app when you choose to share it or save it elsewhere (for example with the Share sheet or “Save to Files”). It then goes only to the destination you pick, and that destination's own privacy terms apply.

Permissions. FairScan asks for the camera (to scan documents), photo library access (to import photos you pick) and Face ID (for the optional App Lock). App Lock uses Apple's Face ID, Touch ID or device passcode prompt. iOS and macOS handle that check and only tell FairScan whether it succeeded. FairScan never receives your face, fingerprint or passcode. You can change any permission at any time in your device's Settings.

2. What we collect and why

Nothing in this section ever includes your documents, their text, their names, folder names, signatures, ID card images, barcode contents or passwords. Our automated privacy tests check the real scan, import, export and barcode code paths to confirm that none of this user content reaches analytics or crash reporting.

a) Usage analytics — Google Analytics for Firebase

We record app events so we can see which features are used and where the app goes wrong. Examples: a scan was started, completed, cancelled or failed; a document was imported (from Files, Photos or “Open in”); a signature was added; a password-protected copy was exported; the paywall was shown; a purchase completed; notification settings were changed. Event details are limited to fixed labels, counts and yes/no values (for example “source: photos” or “reminder: weekly”). We also record whether Pro is active and whether the app came from the App Store or TestFlight. Firebase also collects some data automatically: an app-instance identifier, device model, operating-system and app version, language and region settings, session information, and an approximate location (country or city level) worked out from your IP address.

b) Crash reports and diagnostics — Firebase Crashlytics

If FairScan crashes or an operation fails, a report is sent so we can fix the bug. It contains the technical error details and stack trace, a Crashlytics installation identifier, device model, operating-system and app version, basic device state (such as free memory and disk space) and a short log of recent app activity. That log contains screen names and fixed messages such as “Scan cancelled” or “OCR run on 3 pages”, never document content or names.

c) Push notifications — Firebase Cloud Messaging and our Engagement server

When FairScan starts on iPhone, it registers with Apple's push service, which gives the app a push token. iOS issues this token even if you have not allowed notifications. FairScan can only display notifications if you allow them. The token is sent to:

Google Firebase Cloud Messaging, which delivers the optional “App announcements”. Announcements are opt-in: you are subscribed only if you allow notifications on the screen that says announcements are included, or switch them on in Settings › Notifications — and you can switch them off there at any time.
Our Engagement server (engage.puzzpics.com, which we operate), which sends our own announcements and in-app messages. It receives: a random identifier that FairScan creates for this purpose (not Apple's advertising identifier or device identifier), the push token, whether notifications are allowed, whether you switched on announcements, platform, operating-system and app version, language/region code and time zone. It also receives simple activity events: when the app is opened (at most once every 30 minutes), when you open one of our notifications, and when one of our in-app messages is shown, tapped or dismissed. FairScan also downloads current in-app messages from this server using the same random identifier.

Notification text is written by us and never contains your documents or anything you scanned.

d) Purchases — Apple and RevenueCat

FairScan Pro is sold through Apple's App Store: a one-time lifetime unlock, or a monthly or yearly subscription. Apple processes every payment. FairScan never sees your card, billing details or Apple Account. We use RevenueCat to verify purchases, unlock Pro on your iPhone and Mac, and restore purchases. RevenueCat receives your App Store purchase information (which product, purchase and renewal dates, price and subscription status), an anonymous app user ID created by RevenueCat, and basic device, operating-system and app version information. We do not give RevenueCat your name or email address.

e) Optional feedback — “Suggest a feature”

If you choose to send feedback from Settings › Suggest a feature, we receive the text you type (up to 1,000 characters), the category you picked, the price you said you would pay (if you entered one) and your email address, only if you enter it so we can reply. The same record includes whether Pro is active, a random install identifier, device model, operating-system and app version, and your language/region code. It is stored in a Google Cloud Firestore database that we control. Sending feedback is entirely optional. Please don't put sensitive information in it.

f) “More from KenzieApps” — promoting our own apps

Settings shows a few of our other apps. To measure this, FairScan records when a card is shown or tapped. It also records when that app is later installed, by checking whether our own apps are present on the device; FairScan does not check for any other company's apps. These events are stored in the same Firestore database with the same random install identifier, the app and placement names, operating-system and app version, and language/region code. They are used only to promote our own apps and are not shared with any advertising network.

How these records relate to each other. None of the identifiers above is your name, your Apple Account or Apple's advertising identifier. However, the feedback form and the “More from KenzieApps” events share one random install identifier. If you include your email in feedback, those records could therefore be associated with that email. For that reason, this data is treated as linked to you in FairScan's App Store privacy details.

3. Service providers

Google Firebase (Analytics, Crashlytics, Cloud Messaging, Cloud Firestore): Firebase privacy and security and Google Privacy Policy.
RevenueCat (purchase verification): RevenueCat Privacy Policy.
Apple (App Store payments, push delivery, Face ID / Touch ID): Apple Privacy Policy.

These providers process data on our behalf to provide the services described above. We do not sell personal data, share it with data brokers, or combine it with other companies' data for advertising.

4. What we never do

We never upload your documents, their text, their names or your folder names.
We never receive your signatures, ID card images, barcode contents or PDF passwords.
We never receive biometric data. Face ID and Touch ID are handled by Apple.
There is no FairScan account and no login.
There are no ads. FairScan never asks to track you, does not use Apple's advertising identifier, and does not track you across other companies' apps or websites.
We don't access your contacts, calendar, health data or precise location.
We never sell your data.

5. Data retention

On your device: your documents and settings stay until you delete them or delete FairScan.
Analytics: kept by Google Analytics for no longer than 14 months, then deleted or aggregated.
Crash reports: Crashlytics keeps crash details for 90 days.
Push and Engagement records: kept while you use the app, so we can deliver notifications and messages. Push tokens that stop working are discarded.
Feedback and “More from KenzieApps” events: kept only as long as they are useful for planning and measuring the app, or until you ask us to delete them.
Purchase records: kept by Apple and RevenueCat as needed to provide your purchase and meet legal and accounting obligations.

6. Your choices and rights

Notifications: you can decline notification permission or turn it off at any time in your device's Settings. “App announcements” and the scan reminder each have their own switch in FairScan › Settings › Notifications. Announcements are off unless you turn them on.
Feedback: entirely optional. The email field is optional too.
Analytics and crash reports: FairScan does not have an in-app switch for these. Deleting the app stops all further collection.
Access or deletion: email us and we will help. Because this data is not tied to your name, include the email address you used in feedback (if any) so we can find it. Data linked only to random identifiers may not be traceable to you.

Where laws such as the GDPR apply, we rely on our legitimate interest in keeping the app reliable and improving it (analytics, crash reports, promoting our own apps), on performance of our contract with you (purchases), and on your consent (notifications, announcements and feedback). You may also have the right to complain to your local data-protection authority.

7. Children

FairScan is a general productivity app and is not directed at children under 13. We do not knowingly collect personal information from children.

8. Changes to this policy

If this policy changes, we will update this page and the effective date above. Significant changes will also be noted in the App Store release notes.

9. Contact

FairScan is made by Moath Othman. For questions about this policy or a privacy request, email kenz@kenzapps.com. We aim to reply within two business days.