Trust & Compliance
Google Play Data Safety & Financial Features Disclosures
Prepared for PayVora / Dune Payments Limited · September 2026
1. Core Google Play Data Safety Answers
| Question | PayVora answer |
|---|---|
| Does the app collect or share required user data types? | Yes. PayVora processes identity, contact, financial, transaction and technical data to provide regulated financial services. |
| Is user data encrypted in transit? | Yes — all production APIs, SDKs and integrations transmit data using HTTPS/TLS. |
| Can users request deletion of their data? | Yes. Users can request deletion in-app or via our public account deletion request page. Certain regulatory records may still need to be retained. |
| Is most core data processed ephemerally? | No. KYC/KYB, account and transaction records are generally retained for operational, legal, fraud-prevention and compliance purposes. |
| Is core collection required or optional? | Required for legal identity, contact, KYC/KYB and financial account information necessary to operate the service. |
2. Data Types We Declare
| Data type | Collected | Shared | Typical use / purpose |
|---|---|---|---|
| Name | Yes | Yes | Account setup, KYC/KYB, compliance, payments |
| Email address | Yes | Yes | Login, communication, account management, verification |
| User IDs | Yes | Usually yes | Customer/account identifiers, authentication, security |
| Address | Yes | Yes | KYC/KYB, card/account onboarding, compliance |
| Phone number | Yes | Yes | Authentication, alerts, account management |
| Date of birth | Yes | Yes | KYC, identity verification, compliance |
| Other personal info | Yes | Yes where applicable | Nationality, business details or other identity attributes required for onboarding |
| Payment information | Yes | Yes | Funding, transfers, card/payment processing |
| Purchase / transaction history | Yes | Yes | Deposits, withdrawals, transfers, card transactions, fraud prevention |
| Other financial information | Yes | Yes | Account/routing details, balances, wallet/account information |
| Photos | If used | Yes if sent to verifier | ID/passport/selfie or verification images |
| Files and documents | If used | Yes if sent to verifier | Corporate documents, proof of address, KYB/KYC records |
| App interactions | Yes — page views (web app) | Not shared as telemetry | Authenticated page names are logged for platform analytics via in-app navigation tracking; there is no in-app opt-out. Retention is governed by the Base44 platform. |
| Crash logs | Not found in inspected web code | No | No crash-reporting SDK was found in the inspected web code. Collection by the Android native wrapper is not yet verified. |
| Diagnostics | Not found in inspected web code | No | No diagnostics or performance-monitoring SDK was found in the inspected web code. Collection by the Android native wrapper is not yet verified. |
| Device or other IDs | Not found in inspected web code | No | No device, installation, browser-fingerprint or session identifiers are collected by the inspected web code. Collection by the Android native wrapper is not yet verified. |
| Location — approximate (IP-derived city/country) | Yes | Yes — IP address is sent to ipapi.co, ipwho.is or ipinfo.io for the lookup | Automatically derived from IP address on signup/login for tracking, and to set the interface language. Stored in signup/login location records with no automatic expiry. Manual language selection skips only the language lookup, not login location tracking. |
Scoped facts from our code audit. Base44 operates as a processor for end-user data processed on our behalf under the Base44 Data Processing Agreement — this covers hosting, authentication and platform page-view analytics.
The external geolocation services used for IP lookup (ipapi.co, ipwho.is, ipinfo.io) are independent third parties, not processors under that agreement: they receive the visitor's IP address to return city/country under their own privacy policies.
The statements above reflect the inspected web application code only. Collection performed by the Android native wrapper or platform build tooling has not yet been verified, so no claim is made about collection across the whole mobile app.
3. Purposes We Select
- App functionality — data needed to operate accounts, wallets, cards, payments, transfers, deposits and withdrawals.
- Account management — registration, login, identity/account administration and customer service.
- Fraud prevention, security and compliance — KYC/KYB, AML controls, transaction monitoring, account security, identity verification and fraud prevention.
- Analytics — authenticated page names logged through in-app navigation tracking. No crash-reporting or performance tools were found in the inspected web code.
- Advertising or marketing — not selected for KYC or payment data unless that specific data is genuinely used for marketing or advertising.
4. Account Deletion and Retention
Because PayVora provides user accounts, users can request account deletion in two ways:
| Path | Details |
|---|---|
| In-app path | Profile > Settings > Account > Delete Account |
| Public web path | A dedicated account deletion request page at payvora.net |
| Retention notice | Certain records may be retained where required for AML, fraud prevention, tax, dispute handling, regulatory, contractual or other legal obligations. |
5. Financial Features Declaration
| Financial feature | Selection | Rationale |
|---|---|---|
| Mobile payments and digital wallets | Yes | PayVora provides wallet/account functionality through which users can hold or move funds. |
| Money transfer and wire services | Yes | Applies to ACH/wire transfers, withdrawals, user transfers and mobile-money payouts where live. |
| Banking | Review | Selected only where the live product fits the banking category. Regulated banking, card and payment services, where applicable, are provided through licensed or regulated partner institutions. |
| Cryptocurrency wallet | Only if live | Selected only where users can actually hold crypto in the production app. |
| Cryptocurrency exchange | Only if live | Selected only where users can actually buy, sell or exchange crypto in the production app. |
| Stock trading / portfolio management | No | Not offered. |
| NFT / tokenized digital assets | No | Not offered. |
| Loans / payday / credit / BNPL | No | Not offered. |
| Insurance / financial advice / crowdfunding | No | Not offered. |
6. Store Description
PayVora is a financial technology platform that provides digital account, payment, card and money-transfer functionality. Banking, card, payment and other regulated financial services, where applicable, are provided through licensed or regulated partner institutions.
This page summarizes PayVora's Google Play Data Safety and Financial Features disclosures for transparency. For full details on how we collect, use, share and retain your data, see our Privacy Policy.