Data and Device Protection

1. Introduction

Phonix Pay is a smartphone financing and device-management platform operated by Apex Arbitrage Ventures. This Data and Device Protection Policy explains how Phonix Pay protects customer data, merchant data, payment records, documents, device records, DPC app operations, device security controls, audit logs, and related platform information.

This document applies to:

• Customers using financed devices;
• Merchants and approved retailers;
• Staff and admin users;
• The Phonix Pay Admin Platform;
• The Phonix Pay DPC App;
• The Phonix Pay marketing website;
• Device provisioning, policy, telemetry, payment, document, and support systems.

This policy is read together with the following Phonix Pay documents:

• Privacy Policy;
• Terms and Conditions;
• Cookie and Similar Technologies;
• Device Management Consent;
• Customer Financing Agreement;
• Merchant Agreement;
• Acceptable Use Policy.

Part A: Purpose of this Policy

2. Why this policy exists

Phonix Pay handles sensitive information and device operations, including:

• Customer identity information, Ghana Card information, and passport pictures;
• Customer contact and emergency contact information;
• Merchant records;
• Device IMEI and serial numbers;
• Financing contracts, repayment schedules, and payment records;
• DPC app policy status, lock/unlock events, Lost Mode events, and factory reset protection records;
• Audit logs.

Phonix Pay manages financial data and financed Android devices to protect:

• Data confidentiality and integrity;
• Device security and DPC app reliability;
• Payment accuracy;
• Customer rights and merchant accountability;
• Admin access;
• Audit evidence;
• Release after full payment.

3. Core protection principles

Phonix Pay adheres to these core principles:

• Data Minimization: collect only what is necessary.
• Purpose Limitation: use data only for clear business, legal, payment, support, and device-management purposes.
• Security: protect customer and merchant data with appropriate technical and organisational controls.
• Access Control: restrict access based on roles and business need.
• Accountability: keep sensitive actions auditable.
• Authorized Usage: use device controls only as allowed by contract, consent, and policy.
• Release: release financing controls when the customer fully completes payment.
• Ethical Use: prohibit misuse of device management tools.

Part B: Data Protection

4. Data we protect

Phonix Pay protects the following categories of data:

4.1 Customer identity data

Includes full legal name, phone number, WhatsApp number, email address, residential address, passport picture, Ghana Card details, signature, and customer account ID.

4.2 Customer financing data

Includes contract ID and type, selected device details and price, deposit amount, outstanding balance, installment amount, payment cycle, due dates, grace period, repayment schedule, payment history, receipts, completion certificate, and device release status.

4.3 Emergency contact and guarantor data

Includes emergency contact name, relationship to customer, phone number, and address.

4.4 Merchant and staff data

Includes merchant name, business registration details, branch information, owner details, staff names, emails, phone numbers, roles, permissions, login records, MFA status, and admin/report logs.

4.5 Device data

Includes device brand, model, IMEI, serial number, stock unit ID, Android version, DPC app version, Device Owner status, policy version, lock status, Lost Mode status, last sync time, battery/network/SIM status, and security or tamper signals.

4.6 Payment data

Includes payment amount, reference, channel, date, status, receipt number, transaction reference, failed payment reason, and refund or reversal status.

5. How Phonix Pay protects data

Phonix Pay implements layered controls to protect platform data, including:

• Role-based access control and least-privilege access;
• Multi-factor authentication for admin users;
• Session timeouts;
• Comprehensive audit logging;
• Secure password storage;
• Access approval for sensitive actions;
• Device command and payment verification;
• Data backup and recovery procedures;
• Merchant-level data isolation;
• System health monitoring.

6. Role-based access control

Access to platform data is strictly dependent on the user role.

7. Sensitive data handling

Sensitive data, such as Ghana Card information, IMEI, and lock/unlock history, is:

• Hidden by default and masked in lists or previews;
• Shown only to authorised users with valid permission;
• Logged whenever it is viewed, copied, exported, or changed;
• Excluded from unnecessary exports and protected from unauthorized access.

Part C: Device Protection

8. Why device protection is needed

Device protection safeguards the financed asset, prevents unauthorised bypass, enforces repayment contracts, supports device recovery, prevents fraud, and ensures proper device release. It is governed by customer agreements, consent, DPC policy, applicable law, and audit requirements.

10. Mandatory Device Owner baseline

The DPC app enforces a mandatory baseline that cannot be disabled by staff, including:

• Device Owner requirements;
• Factory reset restrictions and FRP support;
• Disabling USB debugging and restricting developer options;
• Blocking safe boot and unknown sources;
• DPC uninstall protection;
• Policy drift detection and integrity/security monitoring;
• Command reporting.

14. Lock and unlock protection

Lock and unlock actions are sensitive and controlled.

• Lock Verification: the system verifies the contract is active, payment is overdue, grace period has expired, consent exists, the lock policy applies, the device is assigned to the customer, and the command is authorised with an audit log.
• Unlock Verification: the system verifies payment is confirmed and meets minimums, no payment reversal is pending, contract status allows unlock, the device is reachable, and the command is authorised with an audit log.
• Manual Unlocks: require specific permission, a documented reason, MFA for critical cases, and manager approval for high-risk cases.

15. Lost Mode protection

Lost Mode is used exclusively when a device is reported lost, stolen, or in a valid recovery scenario. Actions may include ringing the device, requesting location, showing messages, and tracking the recovery timeline. Actions require an authorised staff role, linked records, an audit log, and a review process. Location data is collected only where allowed and supported by proper notice or consent.

16. Enterprise FRP protection

Phonix Pay uses Enterprise Factory Reset Protection. Account groups are managed in a secure Enterprise FRP Account Vault. Vault rules include:

• No storage of actual Google account passwords;
• Storage of account identifiers and policy mappings only;
• Masking identifiers by default;
• Requiring MFA and documented reasons for any reveal or copy;
• Auditing every reveal, update, rotation, or recovery use;
• Using dedicated recovery accounts, not personal staff accounts;
• Verifying FRP before device handover and clearing or transitioning FRP after payment.

17. Release after full payment

Upon full payment, the device is no longer treated as an active financed asset. The release process includes:

• Confirming final payment and a zero balance;
• Generating a completion certificate and marking the contract as completed;
• Sending a release command to the DPC and disabling financing enforcement;
• Unlocking the device, stopping reminders, and removing financing restrictions;
• Clearing or transitioning FRP;
• Recording an audit log and notifying the customer.

Part D: Customer Transparency

18. What customers must be told

Customers receive clear information regarding:

• Total price, deposit, installment amounts, payment cycles, and due dates;
• Grace periods and consequences of missed payments;
• Application of device management controls and potential restrictions;
• Payment methods, support channels, and post-payment procedures;
• Access to documents and receipts.

19. What customers can access in the DPC app

Customers can view payment status, balance, history, receipts, assigned documents, signed agreements, device status, support contacts, and the completion certificate. Customers do not see internal technical logs, raw telemetry, FRP vault details, or merchant-only notes.

20. What Phonix Pay does not do

Phonix Pay does not use the DPC app to:

• Read private messages;
• Listen to calls or record conversations;
• Access private photos or files;
• Monitor unrelated web browsing;
• Sell personal data;
• Use controls for harassment;
• Track customers without a valid legal basis.

Part E: Merchant and Staff Responsibilities

21. Merchant obligations

Merchants must collect data lawfully, explain terms clearly, upload accurate documentation, verify device identity, obtain consent, record payments honestly, and train staff. Merchants are prohibited from creating fake records, misusing identity information, locking devices outside of policy, or harassing customers.

22. Staff responsibilities

Staff must use individual accounts, maintain credential privacy, use MFA, access only necessary records, and follow approval workflows. Prohibited actions include sharing passwords, exporting data without authorization, or altering audit evidence.

Part G: Payment Protection

25. Payment security

Phonix Pay uses trusted provider references and transaction IDs for verification. Controls include duplicate payment detection, reversal or refund tracking, receipt generation, manual payment approval, and audit logs for all payment edits.

26. Payment data handling

Records are limited to the payment provider, transaction reference, amount, date, status, receipt number, and customer or contract link.

Part I: Retention and Deletion

29. Retention principles

Data is kept only as long as necessary for contract administration, payment tracking, device management, support, legal and accounting compliance, audit logging, dispute resolution, and fraud prevention.

30. Retention examples

• Customer financing records: during contract and required legal or audit periods.
• Payment records: according to accounting, tax, and dispute requirements.
• Signed contracts: contract period plus legal retention period.
• Ghana Card images: only as long as necessary for identity, fraud, legal, or audit purposes.
• DPC telemetry: during active financing and required audit periods.
• Device release records: kept to prove full payment and release.
• Audit logs: kept according to security and compliance retention policies.
• Marketing leads: retained for a limited lead-management period.
• Support tickets: retained for support and dispute history.

31. Deletion and restriction

Data is deleted, anonymised, or restricted when no longer needed. Certain data may be retained for legal claims, contract enforcement, payment evidence, or regulatory compliance.

Part K: Contact

For questions regarding this policy, contact:

Apex Arbitrage Ventures / Phonix Pay
Email: info@phonixpay.one
Phone: 0556516139
Address: HNO. CM26 Love Avenue, Amasaman
Website: phonixpay.one

Customers may also contact their approved retailer for assistance with payment, device, document, or contract issues.