Legal

Data & account requests

Account closure for Afrigora (customer delete) and Afrigora Pro (business deactivate), how to request full data erasure via support@afrigora.biz, plus third-party collection and sharing disclosures for app stores.

Last updated: July 28, 2026

01

Overview

This page explains how to exercise privacy and account choices on Afrigora. It supplements our Privacy Policy and Terms & Conditions — it does not replace them.

Use this URL in Google Play (and similar stores) as your account or data deletion help link for both Afrigora and Afrigora Pro.

Many actions can be completed in the app without emailing support. When you need full erasure beyond in-app delete or deactivate, contact us using the details below.

Privacy Policy: https://afrigora.biz/privacy. Partner collection/sharing list is also on this page for data-safety alignment.

02

Account closure — Afrigora vs Afrigora Pro

Google Play and other app stores require a clear account and data deletion story. This section is the primary reference for both store listings. Our Privacy Policy repeats the same rules at https://afrigora.biz/privacy#account-closure.

Two apps — which flow to use

  • Afrigora (customer app / customer web): for shoppers and personal accounts. Use Profile → Delete account when you want to close your customer account.
  • Afrigora Pro (vendor, tailor, producer app): for business accounts. Use Deactivate account in Settings. Pro does not offer the same in-app Delete account button as the customer app — deactivation is the self-service closure path for business users.
  • Both apps connect to the same Afrigora account platform. If one login has customer and business roles, you may need both flows or support help to close everything.

Customer app — delete account (not hard delete)

  • Where: Afrigora → Profile → Delete account (or the supported web flow when available).
  • Web reference: https://afrigora.biz/privacy#account-closure (this section).
  • Before you can delete: no open orders and no open Save Small goals (active or paused).
  • Security: email OTP to your registered email (send OTP from the closure flow, then confirm delete).
  • If you cannot use the in-app flow, email support@afrigora.biz from your registered address with your deletion request — we will verify you and guide you through closure or erasure where permitted.
  • Google Sign-In: if you registered with Google, deleting your Afrigora account closes access to Afrigora only — it does not delete your Google account.
  • Effect: account is soft-deleted or anonymized for login — you cannot sign in again, sessions end. This is account closure, not immediate erasure of every database row.
  • We may retain order, payment, wallet/KYC, chat/dispute, and fraud-prevention records as described below and in our Terms.

Afrigora Pro — deactivate account (not delete)

  • Where: Afrigora Pro → Settings → Deactivate account (not “Delete account”). Pro does not use the customer Delete account API.
  • Before you can deactivate: no open orders to fulfill and no customers with open Save Small goals on your products (active or paused).
  • Security: email OTP to your registered email, same as other closure actions.
  • Effect: you lose access immediately — sessions end, you cannot sign in until support reactivates where appropriate. Store and tailor listings go offline; new customers generally cannot discover those listings while inactive.
  • Profile and business data: your account is marked inactive; public storefront presentation is removed or hidden as the product implements. We do not promise immediate erasure of all profile, listing, message, or media rows.
  • Messages: past peer threads may remain visible to other participants; your ability to send new messages stops with access.
  • Wallet: wallet balance, transaction history, and payout-related records typically remain for accounting, tax, AML, and dispute purposes after deactivation — withdrawal or settlement may be required before deactivation where the app enforces it.
  • Reactivation: contact support@afrigora.biz if you believe deactivation was in error or you need your business account restored.
  • Deactivation is not full data erasure. Request additional erasure via https://afrigora.biz/privacy/data-request where the law allows.

What we keep after delete or deactivate

  • Transaction and wallet ledgers, BVN/KYC audit trails, order and payout history, and records needed for tax, accounting, anti-money-laundering, chargebacks, or disputes.
  • Content tied to legal holds, open investigations, or completed orders that other users or regulators reasonably expect to remain auditable.
  • Data that no longer identifies you may be kept in aggregated or anonymized form for analytics and service improvement.

Staff-initiated deactivation

  • Afrigora staff may deactivate accounts for policy, safety, fraud, or operational reasons, with effects similar to self-deactivation for business users.
  • Staff action does not erase all historical records. Contact support if you believe a deactivation was made in error.

Request full erasure or additional data rights

  • After delete or deactivate, you may still ask us to limit processing or erase personal data where the law allows and retention is not required.
  • Use this page (https://afrigora.biz/privacy/data-request) or email **support@afrigora.biz** from your registered email. Say whether you use **Afrigora**, **Afrigora Pro**, or both.
  • Include: full name, account email, request type (access, correction, erasure, export, objection), and any order or wallet context.
  • We will verify you own the account (email reply, OTP, or other reasonable check). We aim to respond within a reasonable time; wallet/KYC/dispute cases may take longer.
  • We cannot guarantee immediate hard deletion of all copies when law, fraud prevention, or backup systems require retention — we will explain what was erased, anonymized, or kept and why.
03

Quick reference — in-app steps

Same rules as the section above; use this checklist when implementing or testing Settings flows.

Afrigora (customer) — Delete account

  • App: Afrigora → Profile → Delete account.
  • Clear open orders and open Save Small goals first.
  • Confirm with email OTP. Account login stops; this is soft closure, not instant erasure of all records.

Afrigora Pro — Deactivate account

  • App: Afrigora Pro → Settings → Deactivate account (not Delete account).
  • No open orders to fulfill and no open Save Small on your products.
  • Confirm with email OTP. Listings go offline; compliance data may be retained.

Profile, permissions, and wallet

  • Update profile in account settings where available.
  • Revoke camera, microphone, location, or notification permissions in device settings.
  • Settle wallet balances before closure where possible; KYC and transaction history may still be retained by law.
04

Data collection & sharing (third parties)

The list below names main third parties that collect or receive personal data when you use Afrigora features. Use the same names and purposes when completing app-store data safety or similar disclosure forms. Details for sensitive categories (BVN/KYC, camera, chat, financial data) are in the sections above.

Paystack (payments)

  • Role: Payment processor when you pay by card, bank transfer, or other Paystack-supported methods at checkout (including international USD checkout where offered).
  • Data collected or shared: Name, email, phone, order amount and currency, transaction references; payment credentials you enter on Paystack-hosted checkout (Afrigora does not store full card numbers).
  • Purpose: Authorize payment, prevent fraud, and return payment status to Afrigora so orders can be fulfilled.
  • When it applies: Only when you select Paystack (or are redirected to Paystack) — not for wallet-only checkout.

Xpress Payments (wallet & bills)

  • Role: Licensed wallet infrastructure and bill-payment (airtime, data, utilities, cable, etc.) partner when wallet features are enabled.
  • Data collected or shared: KYC fields (including BVN where required), name, phone, date of birth, address, wallet and transaction amounts, bank details for withdrawals, bill account numbers you submit.
  • Purpose: Create and operate your wallet, process transfers, withdrawals, bills, and regulatory identity checks.
  • When it applies: When you create or use an Afrigora wallet, pay bills, or move money through wallet rails — not for browsing-only use.

Google — Sign-In (optional)

  • Role: OAuth sign-in if you choose “Continue with Google” on web or supported apps.
  • Data collected or shared: Google account identifier, name, email address, and profile image as permitted by Google and your account settings.
  • Purpose: Register or sign in without a separate password; link your Google identity to your Afrigora account.
  • When it applies: Only when you initiate Google sign-in — not required to use email/password registration.

Google Firebase Cloud Messaging (FCM)

  • Role: Push notification delivery infrastructure.
  • Data collected or shared: Device or browser push token, notification payload (titles, bodies, deep-link metadata), and delivery metadata.
  • Purpose: Send transactional alerts (orders, wallet, chat, security) and, where permitted, promotional pushes.
  • When it applies: After you enable notifications on a device or browser that registers for FCM.

Google Workspace (transactional email)

  • Role: Email delivery provider for service messages sent by Afrigora (SMTP).
  • Data collected or shared: Your email address and message content such as OTP codes, password-reset links, order or account notices we send.
  • Purpose: Deliver verification, security, and transactional email you request or that is necessary to operate your account.
  • When it applies: When we send email to the address on your account (registration, login OTP, account closure OTP, support replies, etc.).

OpenAI (AI Assistant)

  • Role: Large language model provider when the in-app AI Assistant cannot answer from local FAQ/knowledge.
  • Data collected or shared: Your question/prompt and limited session context sent by Afrigora backend; response text returned to display in the assistant.
  • Purpose: Generate helpful marketplace answers; not used to sell ads.
  • When it applies: Only when you use the AI Assistant and the backend escalates beyond local knowledge — not for peer-to-peer chat.

Bodygram (optional body scan)

  • Role: Third-party body-scanning service for camera-based measurements.
  • Data collected or shared: Scan session token, age (16+ required), gender, height, weight, and camera input processed on Bodygram systems; measurement outputs returned to Afrigora.
  • Purpose: Generate tailor measurements when you choose scan instead of manual entry.
  • When it applies: Only when you start a Bodygram scan in the measurements flow — optional; users under 16 must not use this feature.

GIG Logistics (shipping)

  • Role: Delivery and logistics partner for domestic and international shipments where GIG is used.
  • Data collected or shared: Recipient and sender names, phone numbers, delivery addresses, order/shipment references, and package details needed to quote and ship.
  • Purpose: Price delivery, book shipments, and provide tracking updates.
  • When it applies: When your order includes delivery fulfilled through GIG (or related logistics flows).

OpenStreetMap Nominatim (geocoding — web)

  • Role: Reverse geocoding on the website when you use location-based features (for example “near me” on consultation).
  • Data collected or shared: Latitude and longitude coordinates you allow the browser to share for that request.
  • Purpose: Convert coordinates into a readable area label; coordinates are sent to Nominatim under their usage policy.
  • When it applies: Only when you use features that call our reverse-geocode proxy with your coordinates.

Cloud hosting & object storage

  • Role: Infrastructure providers (for example Linode Object Storage and related hosting) that store app data and user-uploaded media under contract.
  • Data collected or shared: Account data, chat and listing media, profile images, and other files you upload, stored encrypted in transit (HTTPS) and protected by access controls.
  • Purpose: Host the platform, serve images and attachments, and run backups.
  • When it applies: Throughout normal use of Afrigora when content is saved to our systems.

Marketplace counterparties (not ads)

  • Role: Sellers, tailors, producers, and customers involved in your orders — not third-party advertisers.
  • Data collected or shared: Order details, relevant measurements, delivery contact info, chat messages, and payment status needed to complete the transaction.
  • Purpose: Fulfill orders, consultations, and custom work you request.
  • When it applies: When you place orders, book services, or message other users about a transaction.

We do not sell personal information to third-party advertisers. Optional features (Google sign-in, Bodygram scan, push notifications, wallet) only share data when you use those features. For access, correction, or deletion requests, see Data & account requests.

05

Requests by email

Send privacy, erasure, or account-closure questions to support@afrigora.biz. State whether you use Afrigora, Afrigora Pro, or both.

Include in your message

  • Your full name and the email or phone number on your Afrigora account.
  • The type of request: access, correction, full erasure, export, objection, or help with delete/deactivate.
  • Which app you used (Afrigora customer vs Afrigora Pro).
  • Enough detail to locate the account (order numbers optional).

Typical response times

  • We aim to acknowledge requests within a reasonable period and complete verifiable requests as required by applicable law.
  • Complex requests involving wallet, KYC, or open disputes may take longer while we balance your rights with legal retention and fraud prevention.
06

What we may retain

Even after account deletion (customer) or deactivation (Pro), we may retain information where required for tax, accounting, anti-money-laundering, payment disputes, chargebacks, fraud investigation, or enforcement of our Terms.

Anonymized or aggregated data that no longer identifies you may be kept for analytics and service improvement.

We do not promise hard delete of every backup or ledger copy on delete/deactivate alone; additional erasure is handled case-by-case when you contact support.