Privacy

Privacy Policy

This policy explains the identity, payment, marketplace, analytics, and verification data NairaTag collects and why it is used.

Updated April 26, 2026Name policyPrivacyTerms

1. Data we collect

Depending on the product surface, NairaTag may collect phone numbers, OTP events, claimed handles, bank-linking metadata, verification state, wallet addresses, social-link records, Telegram-bot interaction metadata, payment or marketplace activity, referral activity, API logs, device metadata, and support or review notes.

We intentionally limit what appears on public profile surfaces. Sensitive values such as full BVN, raw bank account numbers, and private transaction histories are not meant for public display.

2. Why we use it

  • To create and secure handle claims.
  • To verify identity and payout destinations.
  • To reduce impersonation, wrong transfers, fraud, and abuse.
  • To operate payments, marketplace review, referrals, and notifications.
  • To analyze reliability, product performance, and policy enforcement.

3. Sharing and processors

NairaTag may use regulated infrastructure and service providers to support verification, hosting, messaging, payments, marketplace review, analytics, and identity operations. Public profile surfaces may expose limited trust signals and approved social or ENS-linked metadata.

If you explicitly publish a public alias like Telegram to an ENS text record, that record is public onchain by design and should be treated as public identity metadata rather than private account data.

We do not treat reserved-name review, verification, or payment integrity data as open marketing data. It is used to operate and defend the product safely.

4. Security, retention, and review

We apply access controls, audit logging, classification rules, and storage-layer protections appropriate to the product stage. Data may be retained for security, payment operations, dispute review, legal compliance, and fraud prevention.

We may preserve evidence linked to impersonation claims, marketplace disputes, verification abuse, or legal requests.

5. Your controls

You can update certain profile, wallet, pay link, and social settings in-product. Some records may remain retained where required for audit, security, fraud prevention, or legal review.

Reserved-name and enforcement decisions may require manual review rather than automatic self-service changes.