CHINKY License & Third-Party Notices
**Last updated: 15 August 2026**
CHINKY application license
Unless a file, package, or component states otherwise, the CHINKY application source code, CHINKY-specific user interface code, product copy, branding, and original service materials are proprietary to their respective CHINKY rights holder(s).
No permission is granted by this notice to copy, redistribute, publish, sublicense, sell, reverse engineer, or create derivative commercial products from CHINKY proprietary materials except where applicable law or a separate written agreement permits it.
This notice does **not** change or restrict the rights granted by third-party open-source licenses.
Open-source and third-party software
CHINKY uses third-party software. Those components remain governed by their own licenses and attribution requirements. Copyright in third-party components remains with their respective authors and contributors.
The mobile app exposes package license information through **About CHINKY > License & Notices > Open-source licenses**.
The backend currently declares the following direct Node.js dependencies:
| Package | Installed version | Declared license |
|---|---:|---|
| `@socket.io/redis-adapter` | 8.3.0 | MIT |
| `axios` | 1.19.0 | MIT |
| `bcryptjs` | 3.0.3 | BSD-3-Clause |
| `cloudinary` | 2.10.0 | MIT |
| `cors` | 2.8.6 | MIT |
| `crypto` | 1.0.1 | ISC |
| `dotenv` | 17.4.2 | BSD-2-Clause |
| `express` | 5.2.1 | MIT |
| `firebase-admin` | 14.2.0 | Apache-2.0 |
| `jsonwebtoken` | 9.0.3 | MIT |
| `mongoose` | 8.24.1 | MIT |
| `multer` | 2.2.0 | MIT |
| `node-cron` | 4.6.0 | ISC |
| `nodemailer` | 7.0.13 | MIT-0 |
| `otp-generator` | 4.0.1 | MIT |
| `razorpay` | 2.9.8 | MIT |
| `redis` | 4.7.1 | MIT |
| `socket.io` | 4.8.3 | MIT |
| `uuid` | 11.1.1 | MIT |
Transitive dependencies are not exhaustively reproduced in this summary. Their applicable license information remains available in the package metadata distributed with the dependency tree.
External services
CHINKY may integrate external service providers for functions such as payments, notifications, media delivery, analytics, calling, LIVE streaming, cloud infrastructure, or authentication. Use of those services may also be subject to the provider's terms, privacy policy, SDK license, or platform rules.
User content
Users retain rights they may have in content they create or upload, subject to the CHINKY Terms of Service and applicable law. Users are responsible for ensuring that uploaded media, music, images, video, text, and other materials do not infringe third-party rights.
Trademarks and branding
CHINKY names, logos, product names, and original branding are not licensed for third-party commercial use by this notice.
Third-party names and marks, when referenced for compatibility, integration, attribution, or legal notice purposes, remain the property of their respective owners.
No transfer of third-party rights
Nothing in this notice grants ownership of third-party open-source software, SDKs, APIs, trademarks, or other external intellectual property to CHINKY.
Contact
Questions about licensing or attribution: