CrediLoop · Effective 7 October 2026

Privacy Policy

CrediLoop helps a shop and its customer record goods supplied on credit, agree on terms, and track repayments. The shop provides the goods and decides whether to extend credit. Optional online repayments are processed by Paystack and settled to the shop’s configured bank account. CrediLoop does not fund purchases or operate a customer wallet.

This policy describes the CrediLoop app and related account services operated by Oluwapemisin Paul-Daniel Awolesi. For privacy questions or requests, email oluwapemisinawolesi@gmail.com.

CrediLoop is intended for adults aged 18 and over.

During setup, your birth date is used to calculate whether you are eligible. The date is sent securely to our API for this check, but the full date is not stored; we retain only the eligibility result. This is a self-reported age check, not identity verification.

Information we use

• Account and identity: name, email address, account type, Firebase account identifier, email-verification status, and any phone number you provide. Google sign-in may supply your name and email. Firebase handles passwords; CrediLoop's API does not receive them.
• Shop and customer details: shop name, business category, address or area, shop identifier, connections and access settings.
• Guarantor details: the name, email and relationship supplied by the customer, invitation delivery status, and the guarantor's accept or decline response. The guarantor receives an email and can decide without creating an account.
• Credit records: requested products, preferred brands, units, prices, quantities, agreed terms, balances, repayment entries, dates, and related account notifications.
• Service and security data: app version, build and platform sent with API requests, authentication identifiers, request timing, error codes and limited rate-limit records. Our infrastructure may process IP addresses and basic connection logs.

Shop owners who enable online repayments provide a bank name, account number and confirmation that they are authorised to receive money into that account. These details and the shop’s existing name and owner contact information are sent securely to Paystack for bank-account validation and payout setup. CrediLoop retains the recipient identifier, bank and account name, last four digits, setup history and consent record. Online repayment records include the payment reference, debt portion, processing fee, total charged and verification status.

CrediLoop does not ask for a NIN, bank password, PIN, card number, precise device location, contacts/address book, SMS or call logs. Paystack independently collects the payment details needed on its hosted checkout. CrediLoop does not store card details. Read Paystack’s privacy policy before using online repayments.

Why we use it and who can see it

We use account information to sign you in, verify your email, provide support and prevent misuse. Shops and connected customers see the details needed to make and manage their own credit agreements. A shop can see the customer's request and credit history with that shop; a customer can see the shop's offer and the resulting balance. A guarantor sees the named request and can respond. We use email to send verification and consent messages. We do not sell personal information or use it for advertising.

Firebase/Google provides authentication and data storage, Render hosts the API, the configured email-delivery service sends account and consent messages, and Paystack processes optional online repayments and shop payouts. Paystack receives the customer’s email address, payment amount, reference and shop payout recipient to provide this service. These providers process information needed to run CrediLoop. A user's choice to share an account-data export through their device is controlled by that user.

Security and retention

Account and credit API calls require Firebase authentication and are sent over HTTPS. The server checks account and shop ownership before returning or changing records. Guarantor decisions use expiring, one-time links. Access to infrastructure credentials is restricted to the server.

We retain account information while the account is active. After a deletion request, we review and delete or de-identify information that is no longer needed. Shared credit and repayment records may need to remain temporarily to resolve an outstanding balance, disputes, security issues or a legal obligation. We explain any such retention when responding to a request. Operational backups, if enabled, follow the same retention and deletion review rather than being used as a permanent copy of deleted accounts.

Your choices

You can request a copy of your account data from Profile in the app. You can request account and associated-data deletion from Profile or through our public deletion page, including after uninstalling the app. A request is not instant erasure; we may need to verify your identity and review shared credit records. You may also email us to correct inaccurate information or ask a privacy question.

Updates

We will update this page when the app's data practices materially change. The effective date above identifies the current version.