1. About these Terms
These Terms describe the intended product behavior visible in the Solar Equb implementation. Binding legal details that cannot be established from source code remain marked for legal review.
2. Product purpose
Solar Equb is designed to coordinate Equb-style group participation around the acquisition of selected solar products. It is not presented as a cash-loan product and does not promise a cash payout, investment return or interest income.
3. Accounts
The current application uses Firebase phone OTP authentication. Users are responsible for maintaining control of the phone number and device used to access their account and for providing accurate profile information.
Age/eligibility requirements and any legally required identity checks: [TO BE VERIFIED FROM BACKEND / LEGAL REVIEW]
4. Equb groups and participation
The application uses invitation-based groups connected to a selected solar product. Group records include member capacity, contribution frequency, agreement state, cycles and allocation state.
- Only invite people you know and trust.
- Membership is handled through invitation and acceptance flows rather than public group discovery.
- Users must review and accept the applicable approved group agreement where required.
- Group chat and member actions must not be used for harassment, fraud or unlawful conduct.
Binding group-agreement text: [TO BE VERIFIED FROM APPROVED AGREEMENT]
5. Solar products and catalogue information
The catalogue supports published solar packages, specifications, package contents, installation scope, warranty summaries, availability information and approved price versions. Availability and operational fulfilment can change.
Approved sale, supplier, tax, warranty and cancellation terms: [TO BE VERIFIED]
6. Contributions and payment status
The application models contribution obligations and payment records. Payment state is designed to be confirmed through backend/provider processing rather than by a client screen declaring itself paid.
The inspected source contains a non-production sandbox payment adapter but no approved production payment provider configuration. Approved payment methods, fees, refunds and disputes: [TO BE VERIFIED]
7. Cycle allocation
The inspected group and cycle code uses a server-controlled random-draw allocation policy for the current implementation. Final eligibility, missed-contribution, redraw and dispute rules must be stated in the approved group agreement and operating rules.
8. Notifications, group chat and support
The application includes operational notifications, group chat, support tickets, support attachments and message-reporting flows. Users are responsible for the content they submit.
9. Orders, installation, handover and warranty
Solar Equb contains workflow records for orders, installation, handover and warranty. These modules do not by themselves create a warranty duration, delivery deadline or supplier commitment. Approved fulfilment terms: [TO BE VERIFIED]
10. Suspension and deletion
The backend data model includes account status and an account-deletion request workflow. Exact suspension grounds, termination rules and retention consequences require approved policy.
11. Intellectual property
Ownership and licensing language for the application, brand and third-party materials: [TO BE VERIFIED BY LEGAL REVIEW]
12. Disclaimers and liability
Any disclaimer, limitation, indemnity or allocation of risk must be approved for the applicable jurisdiction and cannot be inferred from product code. [APPROVED LEGAL LANGUAGE REQUIRED]
13. Governing law and disputes
Governing law, courts/arbitration process, consumer-law disclosures and complaint escalation: [TO BE VERIFIED BY LEGAL REVIEW]
14. Changes to these Terms
The application is structured to use versioned legal/consent records. An approved version number, effective date and notice process should be established before these Terms are used for binding consent.