Privacy Policy
Azina365 (powered by Ciphercom Ltd) — how we treat data and what the app itself does and does not collect.
At-a-glance summary
Key point: Members must be pre-registered via your SACCO / chama back-office management system before they can log into the Azina365 app. The Azina365 mobile/web client itself does not collect or register personal identification data at login.
All member personal data and membership records are created and maintained in the organization's back-office (the management system used by your SACCO/chama). The app fetches and displays those records for authenticated users and forwards authorized transaction requests back to the back-office for processing.
Privacy Details
Detailed explanation of how Azina365 and Ciphercom Ltd handle data for members and organizations.
1. Registration & Personal Data
Pre-registration only: All member personal information (names, ID numbers, phone numbers, membership numbers, roles) is collected and stored by your SACCO/chama back-office system during the onboarding process. The Azina365 app does not provide a registration form for members and does not collect registration PII at login.
If your SACCO or chama needs to update member records, those updates must be performed in the back-office system by administrators. The app retrieves the data from the back-office for display and authorized transactions.
2. What the App Sends & Receives
- The app requests and displays member and account data served by the organization's back-office API.
- Authorized transaction requests (e.g., contribution, loan repayment requests) are forwarded to the back-office for processing — the app itself does not settle payments.
3. Data Storage & Responsibility
Member personal information and transaction history are stored and maintained by the organization's back-office (the primary source of truth). Ciphercom Ltd provides the Azina365 platform and may host infrastructure on secure cloud services (e.g., AWS) as part of the SaaS offering, but your organization controls membership and financial policy.
If you are an administrator and need details on where your group's data is hosted/configured, contact your Ciphercom account manager or support.
4. Security & Encryption
All communication between the app and backend APIs uses encrypted channels (TLS). Where Ciphercom Ltd operates hosting components, industry-standard controls (authentication, encryption in transit and at rest, RBAC) are used to protect data.
Administrators are responsible for managing user access, membership lifecycle, and retention policies in the back-office system.
5. Third-party Services
Where your organization enables integrations (for example M-Pesa or SMS gateways), transaction-related data may be shared with those service providers strictly to perform the requested payments or notifications. The app does not share member data for marketing or sale.
6. Data Access, Correction & Removal
Because membership data is created and controlled in your back-office system, requests to access, correct or delete personal information should be directed to your SACCO/chama administrator. If you need assistance contacting your organization's administrator or have questions about the back-office processes, contact Ciphercom support below.
7. Changes to This Policy
This policy may be updated to reflect changes in operations or law. The effective date will be shown at the top of the page when changes are made. Administrators will be notified for material changes.
8. Contact
Ciphercom Ltd — Azina365
For support or privacy questions: support@azina365.com
Website: www.azina365.com
Need help or want to update data handling?
Contact your SACCO administrator or reach out to Ciphercom support for assistance with membership records, integrations, or data requests.