Skip to content
Collectby IKANISA
Group SavingsInsuranceCRaaSCommunity GroupsOur PartnersTrust & Security
Get the App Email Collect support
Get the App

PRIVACY AND TRUST

Your data. Your choice. Your financial journey.

Collect uses personal data to operate accounts, maintain group-contribution records, review contribution evidence, protect the service and respond to support requests.

Get the App Email Collect support
The Privacy Policy screen in the Collect app
Collect interface preview · Example data

Last updated: 20 October 2026

Privacy At A Glance

Account and group records

Member screens use Collect IDs. Sign-in numbers, MoMo details and raw receipt evidence are private.

Evidence has limits

A receipt or recorded contribution alone does not verify provider settlement. Authorised operators review attribution separately.

Planned services are unavailable

Credit readiness, lending, insurance, collateral and related professional-service handoffs are planned directions. They are not services available through the current Collect app. Do not send loan, insurance, identity-document or medical files for those services.

Ask about your data

Contact info@ikanisa.com to ask for access, correction, a copy or deletion. A request receipt does not mean data has been erased.

Collect does not hold funds

Members authorise MoMo payments with their provider. Collect keeps contribution records and does not hold customer funds.

1. Who we are

Collect is operated by:

Legal Entity
IKANISA
Email
info@ikanisa.com

For the personal data described in this Policy, IKANISA acts as the data controller unless another organisation is identified as the controller. A partner bank, insurer or professional service provider may act as a separate data controller for the products and services it provides.

2. What this Policy covers

This Policy applies when you:

  • Visit the Collect website
  • Use an available Collect member or Admin application
  • Create or join a group where supported
  • Submit contribution evidence through an authorised, consented route
  • Manage authorised group, roster or reconciliation records
  • Contact Collect support

Credit readiness, lending, insurance, collateral and related professional-service handoffs are planned directions. They are not services available through the current Collect app. Do not send loan, insurance, identity-document or medical files for those services.

3. Personal data we may collect

Member account and contact information

  • Numeric Collect ID and the phone number or email used to sign in
  • Google account identifier and verified email if you choose Google where enabled
  • Rwanda country and currency profile
  • MoMo provider, number and pay code
  • Account, session, verification and notification-preference records

The member app does not ask for or display personal names. Admin operator accounts and authorised Direct-member or receipt records may contain names and contact details.

Group and contribution records

  • Group title, purpose, description and selected cover
  • Membership, role and invitation records
  • Contribution intents, amounts, currency and recorded status
  • Ledger entries, reconciliation decisions, reasons and signed correction or reversal records

Ledger totals are contribution records, not money held in a Collect account.

Receipt and roster evidence

  • Raw receipt text and related payer, receiver, amount, reference and time facts
  • Source files and reviewed rows supplied through authorised roster imports
  • Consent, access, review and audit records

Raw evidence may contain personal names or telephone numbers. It is restricted to authorised operational access. Receipt evidence alone is not independent proof of settlement.

Authentication and security information

  • Sign-in challenges, session identifiers and abuse-prevention signals
  • Email-code delivery and verification records; a sign-in code expiring does not delete these records
  • Google sign-in verification and account-linking records where enabled
  • Protected Admin password and authenticator records
  • Device or integrity-verification results where that capability is enabled

Collect does not ask for a MoMo PIN or payment-provider OTP. Your Collect sign-in code is for signing in to Collect.

Technical and support information

  • App or browser version and relevant device information
  • Network, error, audit and security records
  • Information you provide in a support, correction or deletion request

Planned services

Credit readiness, lending, insurance, collateral and related professional-service handoffs are planned directions. They are not services available through the current Collect app. Do not send loan, insurance, identity-document or medical files for those services.

4. How we obtain personal data

We may obtain information:

  • Directly from you
  • From an authorised group leader or operator handling group, receipt or roster evidence
  • From enabled authentication, hosting or communication services
  • From Google if you choose Google sign-in where enabled; Collect requests OpenID identity, email and basic profile access
  • From your device when an enabled feature requires it and applicable consent is provided

Where another person provides information about you, we may ask that person to confirm that they are authorised to do so.

5. How we use personal data

We use personal data to:

  • Create and secure your account
  • Create, join and administer groups where supported
  • Record contribution intents and review evidence
  • Maintain contribution ledgers and reasoned reconciliation history
  • Manage available notification preferences and service channels
  • Prevent misuse and investigate security incidents
  • Handle support, correction, privacy and dispute requests
  • Meet applicable legal obligations

We do not use personal data for an unrelated purpose without an appropriate legal basis.

6. Our legal bases

Depending on the service and your location, we process personal data because:

  • It is necessary to provide the service you requested
  • You have given consent
  • We must comply with a legal or regulatory obligation
  • Processing is necessary to protect you, another person or the platform
  • We or a partner have a legitimate interest that does not override your rights
  • Processing is necessary to establish, exercise or defend a legal claim

You may withdraw consent where processing depends on consent. Withdrawal does not affect processing that was lawful before withdrawal.

7. How information is shared

Group visibility

Member screens use Collect IDs and permitted contribution status. Detailed amounts are restricted by membership and owner permissions. Sign-in phones, MoMo details and raw receipt text are not public group-card or share-link content.

Authorised operators

Operators with the required permissions may review member, roster, receipt and reconciliation records for their assigned work. Sensitive actions require additional authentication and retained audit records.

Technology and operational providers

Supabase provides Collect authentication, database and private evidence storage. Cloudflare provides web hosting, API forwarding and security challenges. Records and recovery copies from the earlier Cloudflare backend may remain in retained systems or archives; changing providers does not erase them. Google provides identity verification if you choose Google sign-in where enabled. Other enabled communications or support providers receive only the information required for that service. Contact info@ikanisa.com for the applicable provider and processing details.

Public authorities and legal claims

Information may be disclosed where a specific legal obligation or lawful request requires it, or where needed to establish, exercise or defend a legal claim.

Planned partner services

Credit readiness, lending, insurance, collateral and related professional-service handoffs are planned directions. They are not services available through the current Collect app. Do not send loan, insurance, identity-document or medical files for those services.

8. Data processing location

Collect serves Rwanda users. Cloudflare and other enabled service providers may process information outside Rwanda. This notice does not claim that all information is stored in Rwanda. Contact info@ikanisa.com for the applicable processing locations and transfer arrangements.

Read about service providers and data sharing

9. AI and automated processing

AI document extraction is not enabled for production without approved provider, processing, retention and human-review controls. Automated receipt parsing or a ledger record does not by itself authenticate provider settlement. Collect does not offer automated lending, insurance or eligibility decisions.

You may ask support to review inaccurate information or a disputed contribution record.

10. How long we retain information

We keep personal data only for as long as needed to:

  • Operate the account and the requested group-record service
  • Maintain contribution and audit history where a justified retention basis applies
  • Prevent misuse and investigate security incidents
  • Handle requests, disputes and legal claims
  • Meet an identified applicable legal obligation

Retention depends on the record category, purpose and any applicable obligation or legal hold. Contact support for the period and basis applying to your records. Submitting a request is not confirmation that profiles, evidence, exports or secured backups have been erased. Check request status or contact support for the outcome and retained records.

11. Your privacy rights

Depending on applicable law, you may request to:

  • Access personal data we hold about you
  • Receive a copy of your data
  • Correct inaccurate or incomplete information
  • Export data in a structured format
  • Object to certain processing
  • Restrict processing
  • Withdraw consent
  • Stop direct marketing
  • Request deletion
  • Challenge a decision based solely on automated processing
  • Ask who has received your data
  • Complain to a data-protection authority
Email
info@ikanisa.com
Privacy requests
Email info@ikanisa.com about a privacy request

We may need to verify your identity before completing a request.

12. Account deletion and data deletion

Delete your account in the Collect app

  • Open Collect and sign in.
  • Go to Settings.
  • Select Security.
  • Select Delete data.
  • Choose a reason if you want to provide one.
  • Select Send verification code.
  • Enter the code sent to the phone number or confirmed email used for your Collect account and select Verify code.
  • If verification is unavailable, select Get help.
  • Select Submit request.
  • Review the confirmation and select Submit request.
  • Check or refresh request status in the app.

Settings → Security → Delete data

Request deletion without the app

Contact Collect support to request account deletion. You do not need to reinstall the app to submit a deletion request.

Open the account-deletion page

Email: info@ikanisa.com

Email help and follow-up

  • If no email app opens, copy info@ikanisa.com into your email service.
  • Keep a copy of your email. If sending fails, check your email service before trying again.
  • For a follow-up, reply in the same conversation and include any request reference already supplied.

A sent email is not an acknowledgement from Collect or confirmation of deletion.

What happens after a deletion request

  • Verify your identity before submitting your request.
  • Submit your request for review.
  • Keep your request reference. In the app, check or refresh request status; by email, reply in the same support conversation.

Submitting a request does not delete your account or records. Your account remains accessible while review is pending. Check request status or contact support for the outcome and any records that need to be retained.

What may need to happen first

  • Resolve pending contribution records, reversals or disputes
  • Arrange a group-owner or administrator handover where required
  • Keep a copy of records you need
  • Discuss an active security investigation or legal hold with support

What account deletion does not do

  • Move money or reverse a payment with your MoMo provider
  • Confirm erasure of retained contribution evidence, audit records or secured backups
  • Delete records independently held by another service

Data we may retain

  • Contribution, reconciliation and audit records where a justified retention basis applies
  • Account and security records needed for an active investigation
  • Records needed to resolve a dispute or legal claim
  • Records subject to an identified applicable retention obligation or legal hold

A deletion request is not confirmation that ledger records, profiles or secured backups have been erased. Ask support which records are retained and why.

13. Security and trust

We use safeguards designed to protect personal data, including:

  • Encryption in transit
  • Encrypted retained evidence and private objects
  • Permission and session controls
  • Additional authentication for sensitive Admin actions
  • Retained audit and request records
  • Software checks and backup controls

No technology system is completely risk-free. If a breach affects your rights or legally requires notification, we will notify affected users and the appropriate authority.

  • We do not sell personal data.
  • Collect does not hold customer funds.
  • Raw receipt and roster records are not public group-card content.
  • A request receipt is not confirmation of deletion or provider settlement.

14. Cookies and website analytics

Current service technologies include:

  • Authentication and security cookies used by the Admin workspace
  • Browser storage needed for the available app or website functions

For questions about cookies and website technologies described in this notice, contact info@ikanisa.com.

Read about cookies and website analytics

Collect's public website uses Cloudflare Web Analytics to measure page usage and performance. It sends page and referring-page addresses, a temporary page-load identifier, browser information and performance measurements to Cloudflare.

Cloudflare states that the analytics script does not read or write cookies or browser storage. This is separate from the authentication and security technologies listed above. Read Cloudflare's RUM privacy information.

15. Children

Do not submit children’s personal information through Collect. Contact support if an account or record concerns a child so the request can be reviewed under the applicable requirements. Collect does not offer a youth financial product.

16. Marketing

Contact info@ikanisa.com to ask about communication preferences or to object to direct marketing. An optional promotional message is separate from an essential account, security or support communication.

17. Changes to this Policy

We may update this Policy as Collect, our partners or legal requirements change. Material changes will be communicated through the app, website, email, SMS or another appropriate channel. The latest version will always show its effective date.

18. Contact and complaints

Email
info@ikanisa.com

You may also lodge a complaint with the competent data-protection authority.

Download Collect or Get in Touch

Get the App Email Collect support
Collect by IKANISA

IKANISA Ltd.

IKANISA Ltd. is a technology company. Collect records group contributions; it is not a bank or wallet and does not hold customer funds. Credit and insurance directions require separate licensed-provider arrangements and are not available through the current app.

Support: info@ikanisa.com · WhatsApp+250 795 588 248

© 2026 IKANISA Ltd.. All rights reserved.

Privacy Terms Account deletion Data deletion Trust