Store console reminder: This page is a public summary. The final Google
Play Data safety form and Apple App Privacy answers must be completed in each
store console and must match the actual binary, SDKs, permissions, countries,
payment providers, identity providers, and production configuration submitted.
High-level safety disclosures
- No custody EpsilonPAY does not hold customer balances. Payments run directly through linked Mobile Money, card, or bank accounts; the app keeps transaction records only.
- Collected EpsilonPAY collects personal, financial, identity, biometric, transaction, merchant/POS, support, device, and technical data needed to provide the service.
- Shared Data is shared with payment processors, banks, mobile-money operators, KYC/KYB providers, notification providers, cloud providers, support providers, merchants, regulators, courts, and fraud/dispute handlers where needed.
- Encrypted Data is transmitted using HTTPS/TLS.
- Deletion Users can request account and data deletion in the app or at account-deletion.html.
- No sale EpsilonPAY does not sell personal or sensitive user data and does not use it for third-party ad networks.
Likely Google Play Data safety categories
| Data type | Collected? | Shared? | Purpose | Required or optional |
|---|---|---|---|---|
| Personal info: name, email, phone number, user IDs, address, date of birth | Yes | Yes, where needed for payment, KYC, merchant, support, legal, and safety purposes | Account management, identity verification, payments, support, fraud prevention, compliance | Required for most account and payment features |
| Financial info: transaction history, linked Mobile Money or bank payout details, payment references (no stored balances) | Yes | Yes, with payment processors, banks, mobile-money operators, merchants, regulators, and dispute handlers | Payments, payouts, settlement, receipts, disputes, fraud prevention, legal compliance | Required for payment features |
| Photos and videos: ID documents, selfies, proof of address, merchant product/store images, support attachments | Yes, when provided or captured | Yes, with identity providers, storage providers, support, or merchant tools where needed | KYC/KYB, account verification, merchant catalog, support | Required for KYC/KYB or optional for merchant/support uploads |
| Files and docs: proof of address, business documents, uploaded attachments | Yes | Yes, where needed for KYC/KYB, support, storage, legal, or compliance | Identity verification, business verification, support, audit | Required for some account tiers or optional support uploads |
| App activity: transactions, payment actions, QR/NFC/Palm Pay events, merchant POS actions, support messages | Yes | Yes, with counterparties, merchants, providers, support, and compliance parties where needed | Core app functionality, analytics for service reliability, fraud prevention, support | Required for using those features |
| App info and performance: diagnostics, logs, crash or error context, API status metadata | Yes | Yes, with cloud, monitoring, and support providers where configured | Diagnostics, security, fraud prevention, service reliability | Required for secure operation |
| Device or other IDs: push tokens, device type, NFC/card IDs, QR tokens, payment references | Yes | Yes, with notification, payment, merchant, and security providers where needed | Notifications, NFC/QR payments, fraud prevention, authentication, support | Required for specific features |
| Biometric data: palm template/embedding and match scores | Yes, only if Palm Pay is linked or used | May be shared with biometric/security processing providers where configured | Palm Pay authentication, liveness and fraud prevention, dispute audit | Optional for users; required only for Palm Pay |
| Approximate location | May be inferred from IP or compliance metadata | May be shared for fraud, payment, compliance, or legal purposes | Fraud prevention, compliance, support, availability | Required for secure operation where used |
Data categories not collected
As currently built, EpsilonPAY does not collect contacts, SMS inbox content, call logs, microphone audio, health data, background GPS location, browsing history, or advertising identifiers.
Apple App Privacy details guide
The following Apple App Privacy data types are likely relevant and should be reviewed in App Store Connect:
- Contact Info: name, email address, phone number, physical address where collected.
- Financial Info: payment information, transaction history, credit or risk context where applicable.
- Sensitive Info: government ID, KYC/KYB and sanctions data.
- User Content: photos, documents, product/store images, support messages.
- Identifiers: user ID, device push token, app account identifiers.
- Usage Data: product interaction and transaction activity.
- Diagnostics: crash, performance, and operational logs where collected.
- Other Data: palm biometric template/embedding and fraud/risk records.
Public URLs for store metadata
- Privacy Policy URL: /privacy-policy.html
- User Privacy Choices URL: /account-deletion.html
- Google Play account deletion URL: /account-deletion.html
- Support URL: /support.html
- Terms URL: /terms-of-service.html