Disclaimer

Disclaimer for OpenAI APIs

  • API Integration: Our project utilizes APIs developed and maintained by OpenAI, such as ChatGPT, among others. The performance and limitations of these APIs, which we integrate, are governed by OpenAI and are outside our control.

  • Client Responsibilities: Clients who purchase our project and opt to integrate OpenAI APIs must obtain their own API access directly from OpenAI. Clients are responsible for adhering to all terms and conditions set by OpenAI for the use of these APIs.

  • Accuracy and Reliability: Responses generated by OpenAI APIs are dependent on the data and training up to the last update provided by OpenAI. We do not guarantee the accuracy, reliability, or suitability of the information provided through these APIs and recommend that users independently verify such information.

  • No Endorsement: Incorporation of OpenAI APIs within our project does not constitute an endorsement of the content generated by these APIs. Users are advised to use the APIs at their own risk and discretion.

  • Intellectual Property: Content produced through OpenAI APIs may contain proprietary information belonging to OpenAI or third parties. Users are responsible for ensuring that they have the appropriate rights to use the content in compliance with all applicable copyright and intellectual property laws.

  • Limitation of Liability: We shall not be liable for any direct, indirect, incidental, consequential, or punitive damages arising from or related to the use of OpenAI APIs in our project. This limitation applies irrespective of the type of claim (contract, tort, strict liability, or any other legal theory) and even if advised of the possibility of such damages.

  • Data Privacy: Clients are accountable for ensuring that any data used with OpenAI APIs complies with all relevant privacy and data protection laws. Clients must secure the necessary consents and authorizations concerning data use.

  • Changes to Disclaimer: We reserve the right to amend this disclaimer at any time. Updates will be communicated through our project documentation. Clients should review this disclaimer periodically to stay informed of any changes.

Disclaimer for API Key Security

  1. Security Responsibilities: Users are solely responsible for the security and confidentiality of their API keys associated with our project. Users must take all necessary precautions to protect their API keys from unauthorized access, use, or disclosure.

  2. API Key Misuse: We are not responsible for any misuse of API keys. If a user believes their API key has been compromised, it is their responsibility to immediately revoke the compromised key and issue a new one, if applicable.

  3. Notification of Breach: In the event of any breach of security or unauthorized use of an API key, users must promptly notify us. However, we are not liable for any loss or damage arising from your failure to comply with this security obligation.

  4. Limitation of Liability: We shall not be liable for any direct, indirect, incidental, special, consequential, or exemplary damages, including but not limited to, damages for loss of profits, goodwill, use, data, or other intangible losses (even if we have been advised of the possibility of such damages), resulting from the unauthorized use, disclosure, or loss of your API key.

  5. Security Best Practices: We strongly recommend that users follow security best practices such as regularly rotating API keys, restricting key permissions to the minimum required for functionality, and using environment variables to store keys securely. It is the user's responsibility to implement such measures.

  6. Changes to Security Practices and Disclaimer: We reserve the right to modify our security practices and this disclaimer at any time, as necessary. Changes will be posted on our website or communicated to users through other appropriate channels. We encourage users to review our security practices and disclaimer periodically.

Disclaimer

Please be advised that it is the client's responsibility to conduct comprehensive testing of the project in both technical and non-technical aspects before making it live. We emphasize the importance of ensuring that all functionalities, integrations, and performance metrics meet your requirements and standards prior to deployment. We shall not be held responsible for any issues, errors, or discrepancies that arise after the project has gone live, including those that impact performance, functionality, or overall system operation.

Please note that we are not responsible for any kind of data loss or server crashes that may occur during the installation, updating, bug fixing, use, or maintenance of our software. We strongly recommend that all users take comprehensive backups of their data and server settings before sharing cPanel/Plesk Panel/FTP/SFTP/Cyber Panel/AA Panel/PhpMyAdmin, Server details or making any changes to their server configuration. By providing Server details or any other sensitive access credentials, you acknowledge and agree that you do so at your own risk, and it is your responsibility to ensure that your data is backed up and secure. We advise taking all necessary precautions to safeguard your data to avoid any potential data loss or service interruptions.

Disclaimer For Envato API

This product incorporates the use of the Envato API, but is not endorsed or certified by Envato. All Envato trademarks used in this product are the property of Envato Pty Ltd.

This product uses the Envato API but is not endorsed or certified by Envato. Our application utilizes official Envato APIs, but the functionality and content accessed through these APIs are controlled by Envato. As such, we are not responsible for any discrepancies, errors, or disruptions in the data provided by Envato's APIs.

Please note that all data fetched via Envato APIs are subject to change and may be discontinued at any time without notice. It is also subject to the terms and conditions as specified by Envato. We advise you to review Envato's terms of service and privacy policy before utilizing this feature in our product.

Last updated