Our approach
Coopsphere is a multi-tenant platform used by cooperatives and member-based organizations to manage members, finances and governance. Security is treated as a core part of how the product is designed, built and operated rather than an add-on.
This overview describes the safeguards we operate. It does not assert any certification, audit outcome or regulatory approval.
Access control
- Role-based access control: users receive permissions based on the role assigned to them within their organization.
- Every organization has a creator (super admin) whose role cannot be altered or removed by other administrators.
- Sensitive records such as KYC documents, audit logs and financial records are restricted to the record owner and to authorized administrative roles.
- Data access rules are enforced at the database layer so that requests are always scoped to the requesting user and their organization.
Authentication
- Passwords are stored using industry-standard one-way hashing and are never visible to administrators or to Coopsphere staff.
- Multi-factor authentication is supported for accounts that enable it.
- Self-service password reset is available from the sign-in page; reset links are single-use and time limited.
- Sessions can be revoked by signing out, and administrators can deactivate a user's access at any time.
Encryption
All traffic between your browser and Coopsphere is encrypted in transit using TLS. Data stored by our infrastructure providers is protected using the encryption-at-rest capabilities those providers make available.
Tenant isolation
Coopsphere is designed as a multi-tenant platform with logical separation between organizations. Users of one organization should only be able to reach data belonging to that organization, or information explicitly shared with them. Notifications and deep links are context-gated: opening a notification that belongs to another organization requires an explicit context switch.
Monitoring and audit trails
- Administrative, financial and governance activity is recorded in audit logs with actor and timestamp information.
- Audit records are restricted to authorized roles and are not editable through the application.
- Application and infrastructure logs are monitored for operational anomalies and security events.
Secure development and testing
Changes go through review before release. Automated dependency and configuration checks run against the codebase, and findings are triaged and remediated based on severity. Independent assessments will be published here if and when they are completed.
Reporting a problem
Suspected vulnerabilities should be reported to security@coopsphere.org. See the Vulnerability Disclosure Policy for details.