Your privacy,
in plain language.
Didentify Docs was designed so your sensitive documents never need to reach us in the first place.
- Your documents are processed entirely on your device. Didentify Docs never uploads them anywhere. We, the developer, never see them, store them, or have any way to access them.
- We don't run our own servers, accounts, or analytics. There's nothing to sign up for.
- Network access is limited. The App contacts RevenueCat to validate purchases and can download a PDF from an HTTPS link that you choose to share into the App. Didentify does not receive either request, and RevenueCat never receives document content. See Sections 3 and 4.
- The operating system itself does some of the work (on-device text recognition), and on Android that involves Google Play services. See Section 5 for exactly what that does and doesn't mean.
- You control sharing. Any time a file leaves the app, it's because you chose to send it somewhere using your device's own share sheet.
1. Who this policy covers
This policy describes how Motu Dev LLC ("we," "us") handles information in connection with the Didentify Docs mobile application (the "App"), available on the Apple App Store and Google Play. It applies to everyone who downloads or uses the App.
2. What the App does
Didentify Docs lets you compare PDF documents side by side and redact sensitive information from them, including names, Social Security numbers, dates, account numbers, and similar identifiers, before sharing or storing a document elsewhere. It reads text from your documents using on-device optical character recognition (OCR) and applies redaction rules you choose, entirely on your phone or tablet.
3. Information we collect
We don't collect any information about you or your documents on our own servers, because we don't operate any servers of our own that the App talks to. There is no account creation, no sign-in, and no Didentify backend service behind this App. The App contacts RevenueCat, a third-party subscription service, to validate purchases (see Section 4). If you choose to share an HTTPS link to a PDF into the App, the App also connects directly to the server at that link to download the PDF. That server may receive ordinary connection information such as your IP address under its own privacy practices; the download does not pass through Didentify or RevenueCat.
| What | Where it lives | Do we ever see it? |
|---|---|---|
| The documents you open or redact | Your device's local storage only, for as long as you keep them there | No |
| Text the App reads from your documents (OCR results) | Processed in memory and in a local cache on your device | No |
| Your redaction settings and rules (which identifier types to redact, colors, presets) | Local app storage on your device | No |
| Your free export count (3 exports per month on the free tier) | Local app storage on your device only | No |
| Subscription and purchase records | Apple or Google, and RevenueCat, tied to an anonymous app user ID | Subscription status and purchase history only, never documents (see Section 4) |
| Crash reports or usage analytics | Not collected. The App does not include any analytics or crash-reporting service. RevenueCat is used only to validate purchases, not for product analytics. | No |
Because your documents and anything derived from them never reach us, there's no database of user data for us to secure, sell, lose, or be compelled to hand over. It simply doesn't exist on our side.
4. Purchases and subscriptions
Didentify Docs is free to download. Didentify Pro is an optional subscription. Subscription terms are described in our Terms of Use.
- Apple and Google process payments. When you subscribe, the App Store or Google Play handles the payment under its own privacy policy. We never see your card details or other payment information.
- RevenueCat validates purchases. We use RevenueCat to validate purchases and unlock Pro features. RevenueCat receives: an anonymous, randomly generated app user ID (no name or email); App Store or Google Play purchase and receipt data (product, price, currency, purchase and expiration dates, and trial and renewal status); device and operating-system information and the App version; and your IP address, which is used to determine country and currency. See RevenueCat's Privacy Policy.
- What we can see. Through RevenueCat, we can see subscription status and purchase history tied only to that anonymous ID. It isn't linked to your name or email address.
- No document content, ever. RevenueCat never receives your documents, page images, recognized (OCR) text, or the names of documents in the App.
- This happens even on the free tier. When the App launches, it contacts RevenueCat to check subscription status. This happens even if you never open the subscription screen or buy anything, and it uses only the information listed above.
5. On-device processing, and what your operating system does
Reading text out of a scanned or photographed document is handled by your phone's own operating system, not by us. This is a meaningful distinction, so we're describing exactly what happens on each platform rather than making one blanket claim:
Text recognition uses Apple's own Vision framework, which runs fully on-device. No third-party or Google component is involved in iOS text recognition, and nothing related to document content is transmitted anywhere.
Text recognition uses Google's ML Kit, which is the standard on-device text-recognition library for Android and depends on Google Play services being present on the device (as most Android apps do, for one reason or another). The text-recognition model is bundled with the App. A separate entity-detection model is downloaded once at runtime. Neither model download includes your documents, document content, or recognized text. Google's own published documentation for ML Kit describes it as sending general API-level diagnostic information (such as whether a call succeeded and how long it took) as part of normal Play services operation. This does not include the content of your documents or the text recognized from them, which never leaves your device. If you'd like more detail on Google Play services generally, see Google's Privacy Policy.
6. Sharing your documents
The App will never automatically send a document anywhere. Any time a document leaves the App, such as when you use your device's share sheet to send a redacted PDF by email, message, or another app, that happens because you initiated it through your operating system's own sharing mechanism. We have no visibility into or control over what happens to a file after you share it that way.
The App also supports opening PDF files that other apps share with it (for example, receiving a file from Mail or Files). This uses your device's standard app-to-app sharing mechanism and doesn't involve us or any server.
7. Children's privacy
Didentify Docs is a general-purpose document utility not directed at children, and we do not knowingly collect information from children. Consistent with Section 3, we don't collect information from anyone, of any age, on our own servers. Limited network activity consists of the purchase validation described in Section 4, one-time model delivery described in Section 5, and an HTTPS PDF download only when you choose to share such a link into the App.
8. Your choices and control
- Deleting your data is as simple as deleting the App or the documents on your device. Since your documents and settings live locally, there's nothing of that kind stored elsewhere for us to delete on your behalf.
- Purchase records are kept by Apple or Google and by RevenueCat, as described in Section 4. You can ask us to delete the RevenueCat records associated with your anonymous app user ID through the contact page. Apple and Google keep their own records under their own policies.
- Subscriptions can be managed or cancelled in your App Store or Google Play subscription settings. Deleting the App does not cancel a subscription.
- Redaction rules and presets you've configured can be cleared from the App's Settings screen at any time.
- Uninstalling the App removes its local storage and cache along with it, per your operating system's normal app-removal behavior.
9. Changes to this policy
If we make material changes to this policy, we'll update the effective date above and, where required by the App Store or Google Play, make a new version available before the change takes effect.
10. Website delivery and security
This policy also explains the limited technical processing needed to deliver didentify.com. The website is hosted and protected by Cloudflare, our website infrastructure service provider and website sub-processor. When you visit, Cloudflare may process network information such as your IP address, request headers, and security signals to provide DNS, encrypted connections, content delivery, and abuse prevention. Cloudflare publishes a Data Processing Addendum (DPA) describing its data-processing commitments.
The website does not use advertising cookies or third-party marketing analytics. Cloudflare may use strictly necessary security mechanisms when a request appears automated or abusive. This website processing is separate from the Didentify Docs app, and document contents are never sent through the website. Learn more in Cloudflare's privacy policy.
11. Contact us
Questions about this policy or how the App handles information can be sent through the Didentify contact page.