What happens to
your information.
A plain-language walk-through of how Denxor Labs applications handle your data — what's collected, where it's processed, and what stays on your device. Every claim here links back to the full, legally-worded policy behind it.
The short version
Processing happens on your device
ProofPay parses supported payment messages locally and stores the resulting records in encrypted on-device storage. There's no account to create and no server your transaction data is uploaded to.
You hold the key
App access sits behind a PIN (salted PBKDF2‑HMAC‑SHA256, high iteration count) or your device's biometric unlock. Sensitive data is encrypted with Android Keystore–backed mechanisms rather than stored in plain form.
Nothing is sold
Denxor Labs does not sell user information, and does not currently use a third-party analytics platform or data processor for ProofPay. If that changes, the policy below will name exactly who and why.
This page summarizes the policy in plain language — the Privacy Policy and Data & Security Policy are the governing documents if the two ever appear to disagree.
Where your information actually goes
Using ProofPay as the example, since it's the application currently in active development. See the product page's How it works section for the same flow from a product perspective.
SEND_SMS permission requested.Verifying a receipt is a separate flow: scanning a receipt's QR code opens the Denxor Labs verifier, which checks the receipt's cryptographic signature entirely in your browser — no data is sent to a Denxor server to perform that check. See Verification claims for what that check does and doesn't confirm.
How we approach this
Data minimization
We'd rather not collect information a product doesn't need to function. Where a feature can work with less data, that's the version we build.
Local-first where it makes sense
If something can be processed and stored on your own device without losing the functionality you actually need, that's the default we design toward.
Honest status, not marketing language
We don't describe security as "unhackable" or "100% secure" — no system honestly is. What you'll find here is what's actually implemented, described accurately.
Placeholders instead of guesses
Where a detail — like an exact data-retention period — isn't finalized yet, the policy says so explicitly rather than implying an answer that hasn't been decided.
Software isn't infallible
Message parsing can fail on unsupported formats. A receipt scan can misread a blurry image. A biometric sensor can misfire. None of this is unique to Denxor Labs — it's true of software generally — but we'd rather say it plainly than let a bug feel like a broken promise. If something looks wrong, tell us.
Two versions, two policies
ProofPay Basic and ProofPay Premium acquire SMS data differently, so each has its own governing Privacy Policy below. If you're unsure which applies to you, it's the one matching the version you're using.
ProofPay Basic Privacy Policy
Manual, user-initiated SMS sharing and local processing — currently a direct release, with a Google Play Store listing planned.
Automated tierProofPay Premium Privacy Policy
Permission-enabled automated SMS processing — a different data-acquisition model from Basic.
These two documents are the governing policies for their respective versions — they take precedence over the plain-language summary on this page if the two ever appear to disagree. ProofPay's separate Web / Off-Store Privacy Policy covers the browser-based, automated receipt-extraction version, which is a distinct product from both Basic and Premium.