Privacy

ZephiPay is being designed around transparent data use, limited collection, secure handling, and meaningful user control.

Pre-launch draft • Legal review required before production

Scope

This page describes ZephiPay's current pre-launch privacy direction. It is not a final privacy policy and may change as the company, product, providers, and legal obligations are established.

Information that may be collected

Depending on the service used, ZephiPay may need account information, contact details, identity-verification records, business information, payment instructions, transaction records, device data, security events, and support communications.

Why information may be used

Information may be used to create and protect accounts, provide payment services, verify participants, coordinate compliance, evaluate risk, enforce policy, execute settlement, produce receipts, prevent abuse, provide support, and improve reliability.

Verification and compliance providers

Identity, business verification, sanctions screening, transaction monitoring, banking, card, blockchain, and settlement providers may process information when required to provide a requested service.

Payment and economic-event records

ZephiPay is designed to preserve structured records including payment identifiers, Runtime decisions, policy outcomes, settlement details, receipts, timestamps, and technical evidence required for reliability, support, reconciliation, and security.

Sharing

Information should be shared only when necessary to provide the service, comply with law, protect users or the platform, investigate abuse, complete settlement, or support authorized business operations.

Retention

Retention periods will depend on the type of information, operational needs, security requirements, contractual duties, dispute handling, and applicable legal or regulatory obligations.

Security

ZephiPay is being designed around access controls, authentication, device and session visibility, policy enforcement, auditability, secure infrastructure, provider oversight, and incident-response procedures.

User controls

Planned controls include account settings, communication preferences, connected-service management, data export, correction, and deletion requests where legally and operationally permitted.

Blockchain records

Transactions submitted to a public blockchain may become permanently visible and cannot generally be altered or deleted by ZephiPay. Public addresses and transaction details should not be treated as private.

Children

ZephiPay is not intended for children. Final eligibility and age requirements will be defined before public production use.

Changes and contact

This framework will be updated as ZephiPay approaches launch. A formal privacy contact, effective date, company identity, jurisdictional disclosures, and request process will be published before production availability.