ProofPay Basic — Privacy Policy
Simple. Private. In your hands.
Applies to ProofPay Basic, the manual-sharing edition of ProofPay currently available as a direct release, with a Google Play Store listing planned.
Effective date: 25 August 2026 · Last updated: 25 August 2026
In one sentence: ProofPay processes payment messages that you choose to share with the app. Nothing is collected unless you hand it over.
ProofPay is also available as ProofPay Premium, which adds optional automated payment-message processing on top of what's described below. Premium is a distinct product with its own Privacy Policy — this document describes Basic only.
1. Introduction
This Privacy Policy explains how ProofPay Basic, a Denxor Labs product, processes information on your device when you use it to capture, organize and preserve payment records.
2. Scope
This policy applies only to ProofPay Basic, the manual-sharing edition of ProofPay (currently distributed as a direct release; a Google Play Store listing is planned and this policy will be updated to reflect it once live). It does not apply to ProofPay Premium, which offers optional automated payment-message processing and is covered by a separate policy. It does not cover third-party payment providers, banks, or telecom carriers whose messages you may choose to share with ProofPay.
3. SMS acquisition
ProofPay Basic does not automatically collect SMS. It does not continuously monitor
your SMS inbox, does not automatically read incoming SMS in the background, and does not use the
READ_SMS or RECEIVE_SMS Android permissions for automatic SMS collection.
ProofPay processes payment messages that you choose to share with the app — nothing more.
4. User-initiated Share Intent
ProofPay Basic uses Android's built-in Share functionality (the system Share Intent). When you receive a payment-related SMS, you manually select it and choose to share it with ProofPay — the same way you'd share a message to any other app. ProofPay only receives the content you explicitly chose to share; it has no visibility into any other message on your device.
ProofPay Basic does not require, and does not request, the SEND_SMS permission, and does
not send messages on your behalf.
5. Transaction information
Once you share a payment message, ProofPay extracts transaction-related details — such as merchant, amount, date and reference — to build a structured transaction record.
6. Receipt / evidence information
You may also add evidence by scanning a receipt with your camera or importing an image, PDF or DOCX file. This, too, is an action you initiate — ProofPay does not access your camera, photo library or files without you starting that flow.
7. Local processing
Content you share or import is processed on-device. The shared message or document is parsed locally, held briefly in an encrypted queue while relevant details are extracted, and converted into a structured transaction record for you to review before it's saved.
8. Local storage
Transaction records, and the underlying evidence you provided, are stored locally on your device using encrypted local storage. ProofPay Basic does not operate a remote database containing your locally stored transaction history, and does not upload it to Denxor Labs or any third party as part of ordinary use.
9. Encryption / security
Locally stored data uses encrypted storage backed by Android Keystore mechanisms. App access can be protected with a PIN, authenticated using salted PBKDF2‑HMAC‑SHA256 with a high iteration count; repeated failed attempts trigger escalating lockout behaviour. See the Data & Security Policy for further detail. None of this is described as "military grade," "unhackable," or "100% secure" — these are the mechanisms actually implemented, not a guarantee.
10. Permissions
ProofPay Basic requests only the permissions its implemented features actually need. It does not request broad SMS-read permissions, and does not request the Advertising ID.
11. Notifications
ProofPay's notification design is intended to reduce exposure of sensitive transaction amounts in notification previews — for example, on a lock screen someone else might glance at.
12. Camera, gallery, OCR and file processing
Where you use the camera-scan or file-import flow, the resulting image, PDF or DOCX is processed on-device to extract transaction details. You review the extracted details before anything is saved. Temporary files created during this processing are removed once no longer required.
13. Data retention
Because ProofPay Basic's transaction data is stored locally on your device rather than on a Denxor Labs server, records persist on your device until you delete them yourself or uninstall the app — there is no separate, automatic expiry applied by Denxor Labs.
14. Data deletion
You can delete individual records from within the app. Deleting a record removes it from local storage on your device. Uninstalling ProofPay Basic removes its local application data from your device entirely. Because there is no remote account or server-side database behind ProofPay Basic, there is no separate server-side deletion request process to describe — deletion happens on-device, under your control.
15. User control
You decide which messages to share with ProofPay and which receipts to import. Because the resulting data lives locally on your device, you retain direct control over it at all times, including exporting, deleting, or removing it by uninstalling the app.
16. Third-party services
ProofPay Basic does not currently use a third-party backend, hosting provider, or data processor to store or process your transaction records — that processing happens on-device. The receipt-verification feature, where a generated receipt's cryptographic signature can be checked, runs entirely in the browser via the public verifier and does not require an app, account, or server round-trip to perform the check; see Verification claims. If this changes in a future release, this section will be updated to name the service and what it receives.
17. Analytics / crash reporting
ProofPay Basic does not contain third-party analytics or crash-reporting SDKs. Any in-app analytics (for example, spending patterns or transaction distribution shown to you) are computed from your own locally stored records, for your own viewing — this is not shared analytics, and it is not sent anywhere.
18. Advertising ID
ProofPay Basic does not use the Android Advertising ID and does not contain advertising SDKs.
19. Children's privacy
ProofPay Basic is not designed or directed at children, and we do not knowingly collect personal information from children in circumstances prohibited by applicable law.
20. Changes to this policy
This policy may be updated as ProofPay Basic's functionality changes. Material changes will be reflected on this page, with an updated "Last updated" date above.
21. Contact
Questions about this policy: denxorpraxis@gmail.com or WhatsApp.
Looking for the Premium policy instead? Read ProofPay Premium — Privacy Policy, or go back to the Privacy & Legal hub.