Qizmoney Coin

Compliance & Regulations

An overview of compliance considerations and safeguards—not a legal opinion, license, audit report, or certification.

AML & KYC Compliance

Anti-Money Laundering (AML)

Anti-money-laundering requirements vary by service and jurisdiction. We may apply risk-based checks where required or supported by a payment partner; this page does not certify that every activity is monitored.

Know Your Customer (KYC)

Identity or customer checks may be requested for a specific service when required by law, a partner, or risk controls. The platform does not represent that all users or transactions are verified.

Data Protection & Privacy

Data Encryption

The Privacy Policy describes intended safeguards. Actual encryption and access controls depend on the system and provider; no transmission or storage method can be guaranteed completely secure.

GDPR Compliance

Where GDPR or another privacy law applies, the relevant rights and obligations are assessed for the particular processing. This statement is not a certification of GDPR compliance.

Regular Audits

Security reviews may be conducted as appropriate. No audit or certification is represented by this page; consult published reports or contact us for substantiated, current details.

Financial Regulations

Transaction Monitoring

Transaction monitoring may be applied by the platform or its payment providers where appropriate; coverage, timing, and thresholds vary and are not guaranteed to detect every issue.

Sanctions Screening

Sanctions screening may be required for particular services or payment flows. Do not treat this page as confirmation that every user or transaction has been screened.

Reporting Requirements

Reporting and recordkeeping duties depend on the service, entities involved, and applicable law. We respond to valid legal requirements as required.

Smart Contract Security

Code Audits

Do not assume a contract has been independently audited unless a specific audit report is published and identifies that exact contract version and network.

Multi-Signature Protection

Security controls depend on the specific contract and deployment. Check the verified source code and deployment details; this page does not assert that every function is multisignature-protected.

Upgradeable Architecture

Some deployments may use upgradeable contracts. Upgradeability can introduce additional administrator and technical risks; review the specific contract documentation and on-chain configuration.

Incident Response

Incident handling depends on the type and severity of an event. The following are response practices to establish and maintain, not a claim that each control is continuously staffed or independently certified:

  • Assessing suspected security and privacy incidents
  • Containing and investigating incidents where feasible
  • Providing notices to affected people or authorities when required by law
  • Reviewing causes and corrective actions after significant incidents
  • Coordinating with relevant infrastructure and payment providers
Regulatory Jurisdictions

The company lists an address in Zambia. This page does not establish regulatory authorization or licensing in Zambia or elsewhere. Laws that may apply depend on the user, product, transaction, and provider. Relevant areas to assess include:

  • Local rules on digital assets, payments, money transmission, and financial promotions
  • Risk-based AML, counter-terrorist-financing, sanctions, and recordkeeping obligations where applicable
  • Privacy, data security, consumer rights, marketing, and electronic communications laws
  • Cross-border transfer, tax, and reporting rules applicable to a specific service
  • Partner, app-store, wallet, and blockchain-network requirements
Google Sign-In and Google User Data

The code currently reviewed for this site does not implement Google Sign-In or Google API access. If Google authentication or API access is introduced, launch readiness should include an approved OAuth consent screen, verified domains and public policy links, accurate disclosure of each requested scope and its purpose, and a request for only the minimum scopes needed.

Any Google user data must be handled consistently with the disclosures shown before consent and Google's applicable user-data policies. Access, use, storage, sharing, retention, deletion, security, and any transfer to service providers should be documented and implemented before enabling the feature. This page does not claim Google verification or approval.

Global Privacy and Consumer Law

There is no single global legal-compliance status. Requirements may depend on where the company, user, payment provider, or infrastructure is located and on whether a specific product constitutes a regulated service. Laws may address data protection, consumer notices, digital-asset offers, financial promotions, payment services, sanctions, AML, tax, accessibility, and cross-border transfers.

Before offering a feature in a country, the operator should assess local licensing and marketing restrictions, eligibility and geographic limits, mandatory disclosures, privacy roles and lawful bases, processor contracts, transfer safeguards, retention schedules, complaint handling, incident notification, tax treatment, and any required regulator filings. These pages are general information and do not establish that those assessments have been completed.

Google OAuth review is a separate process from legal compliance. Publishing a privacy policy and terms page alone does not guarantee OAuth verification, regulatory approval, or permission to operate a financial or digital-asset service.

Regulatory Contact

For questions about these general disclosures, or to request substantiation for a specific claim, contact:

Email: compliance@qizmoney.site

Phone: +260 963 460 556

Address: 52 Watch It Grow, Buteko Avenue, Ndola, Zambia