Copyright and Content Removal Requests
Our policy regarding content disputes, intellectual property claims, and removal procedures.
At Konthora, we respect the intellectual property rights of others. We expect our users to display the same level of respect when uploading content or using our synthesis workspaces.
Policy Overview
Because our platform is designed around temporary local processing, we do not host a public database of user files, nor do we run a index page of public user audio or transcripts. When the backend launches, uploaded files and generated outputs will be processed temporarily and automatically deleted after a short processing window.
However, if you believe that any content generated or processed through our services infringes on your intellectual property rights, you can submit a removal or dispute notice to our team.
Procedure for Submitting a Request
To report a copyright issue or request content removal, please send an email to our support team at: hello@konthora.dev.bd
To expedite your request, please include the following details in your message:
- Identification of the Work: A description of the copyrighted work that you claim has been infringed.
- Details of Infringement: Details explaining how the material processed through our tools infringes your copyright.
- Contact Details: Your full name, mailing address, telephone number, and email address.
- Ownership Declaration: A statement indicating that you have a good-faith belief that use of the material is not authorized by the copyright owner, its agent, or the law.
- Truth Declaration: A statement certifying that the details in the notice are accurate, and under penalty of perjury, that you are the owner or authorized to act on behalf of the owner of the copyright.
Review Process
Once a valid dispute notice is received, our team will review the claim and take appropriate measures, which may include disabling temporary features or restricting specific access keys. Because all user files are deleted automatically, many disputes are resolved immediately through system-level file expirations.