| Terms Of Service For Contract Development |
|
|
|
|
Typical software development agreement concludes between VASoftOnline and its customer when he (she, they) orders development of any software or website. Read it before placing order.
A) Definitions 1. Term 'Service provider' means VASoftOnline. 2. Term 'Buyer' means person or organization that orders VASoftOnline for development of web or desktop application. 3. Term 'Software' means all source codes, binary files, documentation, multimedia content and other information in any form which is part of program product or web site. 4. Term 'Universal software component' means source code module(s) or result(s) of compiling such module(s) (WIN32 DLLs, COM components, .NET assemblies, PHP includes, command-line tools, etc) which perform common programmatic tasks and can be used in a wide set of applications. B) Service provider undertakes for: 1. On-time creation new software confirmed strictly to Buyer's task specification. 2. One-time installation software on Buyer's computer(server) if Buyer will supply Service provider with access to his(her) computer(server) via FTP, control panel, remote desktop or another tool. 3. One month free consulting in installation, managing and optimization new software. C) Buyer undertakes for: 1. On-time payment for software development. D) Procedural details. 1. Service provider and Buyer co-ordinate task specification before starting work. 2. New features can not be added to task specification when work was already started. That is Service provider and Buyer have to discuss all details of task before work will be started. Any new features can be added as new task only with separate task specification, price and payment. 3. Service provider creates demo version of a software and shows it to Buyer. If the software is a web application then demo version will be shown from Service provider's server and kept here during 5 days, and if it is a desktop application then 5-day trial version will be sent to Buyer via e-mail, FTP, HTTP or other way. 4. Buyer can test application and send any remarks or violation reports to Service provider. Service provider have to fix any buggs and unconformations with the task specification sent by Buyer and resend new demo version to Buyer. 5. When Buyer will consider the program confirmed to the task specification, he(she, they) makes payment. 6. When Buyer has made payment, Service provider sends software to Buyer and inslalls it to Buyer's computer(server) if Buyer wishes and supplies Service provider with access to his(her) computer(server) via FTP, control panel, remote desktop or another tool. 7. No claims or chargebacks can be done after project closing. Buyer fully understands that when he writes to Provider that testings are done and he thinks the product is fully compatible with task specification and bugs free, he closes project and resign any chargebacks and claims against Provider. All claims have to be done at testing time. E) Additional conditions 1. Service provider may refuse free fixing of bugs and(or) unconformations with task specification in the version of the software modified by any person who was not authorized obviously by Service provider to do such modification. 2. Buyer can resell software only entirely. No part of sortware can be reselled separately. 3. Service provider hands master resellers rights and copyrights over to Buyer. However, Service provider reserves a right to refer to the software as his work in his online portfolio. 4. Service provider can use third-party universal software components. This components have to be used according to their developer's licenses. Typically you will have rights to use these components in context of ordered software only. 5. Service provider can use own universal software components (WIN32 DLLs, COM components, .NET assemblies, etc). You will get rights to use this components only in a context of ordered software and Service provider will supply corresponding technical protection mechanism. Source codes of universal components are not handed over to Buyer if they were developed outside the bounds of current software development agreement. |



















