Privacy Policy
Last updated: April 2026
RedactNow does not collect, store, or transmit any user data. This is not a simplified summary — it is the complete picture.
Data collection
None. The app makes zero network calls. There are no analytics, no crash reporting services, no cloud processing, no user accounts, and no telemetry of any kind.
Profile data
The personal information you enter into redaction profiles (names, phone numbers, email addresses, physical addresses, ID numbers) is stored exclusively in the device Keychain, protected by hardware encryption. This data never leaves your device and is not accessible to us or any third party.
Document processing
All redaction processing happens entirely on your device using Apple's native frameworks (PDFKit, Vision, CoreGraphics). No document content is ever uploaded, cached remotely, or transmitted off-device. Input files are processed in temporary directories that are cleaned up after each session.
Third-party code
RedactNow contains zero third-party libraries, SDKs, or frameworks. The entire app is built with Apple-native frameworks only. There are no advertising networks, analytics tools, or external dependencies of any kind.
App Store privacy label
RedactNow's App Store privacy label is "Data Not Collected." This reflects the fact that no data of any type is collected from the app.
Diagnostics
The app uses Apple's MetricKit framework to log performance and crash diagnostics locally to the device's Caches directory. These logs are never transmitted — they exist solely as a development aid and can be cleared by the system at any time.
Children's privacy
RedactNow does not collect data from anyone, including children. There are no accounts, no age gates, and no data collection of any kind.
Changes to this policy
If we ever change how the app handles data, this page will be updated. Given that the app's core design makes data collection architecturally impossible (no networking code exists), meaningful changes are unlikely.
Contact
Questions about this policy can be directed to the GitHub issues page.