Last updated: 29 July 2026
This policy covers everyone who uses BigP: members of a chama (savings group), treasurers, chairpersons, group admins and platform staff. Each group's data is kept separate from every other group's data.
To run your group's contributions, obligations and payments, we store: your name, phone number, email address, membership number, your contribution and payment history, obligation and fine records, and any payment proof documents you upload (e.g. M-Pesa screenshots). We do not collect your national ID, bank PIN, or M-Pesa PIN — never share these with anyone, including group officials.
Your data is used only to run the group's financial records: tracking what you owe, what you've paid, generating your statements, and letting your group's treasurer or admin reconcile payments. We do not sell your data or use it for advertising.
Your own contribution history is visible to you. Your group's treasurer, chairperson and group admin can see records for members in their own group only — never members of a different group. Platform staff can access data only to fix technical problems or respond to a support request you raise.
We use one essential cookie to keep you signed in. We do not use advertising or tracking cookies. If your group enables analytics in the future, this policy will be updated first.
Financial records are kept for as long as your group is active on the platform, since contribution history is part of the group's permanent financial record. If you leave your group, your historical contribution records stay as part of the group's accounts, but your login access is removed.
You can ask your group's treasurer or admin to correct inaccurate personal details (name, phone, email) at any time. Since contribution and payment records are shared financial records belonging to the whole group, individual members cannot unilaterally delete them.
Passwords are stored encrypted and are never visible to anyone, including platform staff. Payment proof documents and sensitive settings (like M-Pesa credentials) are encrypted at rest.
If this policy changes in a way that affects how your data is used, you'll be asked to review and accept the updated version the next time you sign in.
Questions about this policy can be raised with your group's admin, or through the Support section once you're signed in.