PRIVACY DRAFT
Privacy policy draft
This draft separates what is already verified from what still needs legal and operational approval. It is not yet a published policy.
Draft date: 14 August 2026How the current app uses data
- The camera starts only after the user actively enters the scan flow and is used to read a QR code.
- Raw QR content is currently processed briefly in memory. It is not shown in the UI, written to logs or sent to analytics.
- The app currently stores one non-sensitive camera-purpose acknowledgement on the device.
What the current build does not do
- The current build has no live Backend, payment-provider, Apple Pay or card-transaction connection.
- It does not create user accounts or store full card numbers, CVV, customer balances or provider secrets.
- This draft website has no analytics cookies, trackers, contact form or sign-in.
What must be completed before launch
- The formal legal name, address and contact details of the data controller.
- The data received by the Backend, VietQR validation and payment provider, including purpose, legal basis, region and retention.
- Formal procedures for access, correction, deletion, complaints and withdrawal of consent.
- Processors, cross-border transfers, security incident notices and policy for minors.
Security principles
- The app must not store full card data or payment-provider secrets.
- Payment authorization is not merchant settlement; completion requires trusted Backend evidence.
- This policy and App Privacy answers must be reviewed again after external services are integrated.
