Terms & Conditions :: Page 1/2
Starting any work with Krenky Studio, you agree that it is in compliance with the general rules and guidelines as follows.
Standard Media Delivery
This Agreement assumes that all text is provided by the Client in electronic format (.txt on CD/DVD, e-mail or ftp retrievable), all photographs and other graphics are provided in high quality print suitable for scanning or in a .gif, .jpeg, .bmp, .tif, .psd, .eps, .ai or editable fla format. Additional expenses may be incurred and will be invoiced accordingly for corrective work, conversion of media and outside facility charges.
Permission and Copyright
The Client will obtain all the necessary permissions and authorities in respect of the use of all copy, graphic images, registered company logos, names and trademarks or any other supplied material. Every contract for page design and placement shall be regarded as a guarantee by the Client to Krenky Studio that all such permissions and authorities have been obtained. Evidence of permissions and authorities may be requested.
Licensed Code
This Agreement includes code elements being custom created for the Client and is based on toolboxes of techniques and pre-developed code that is property of Krenky Studio. This software technology is licensed to the Client for a one-time fee and is limited to installation and usage by that Client only on one "site" of connected documents on one "server". Such code is not owned by that Client and may not be distributed, modified or re-licensed without the express written consent of Krenky Studio.
Right to Pull
The Client agrees to give Krenky Studio "on demand" access to the installed designs and the Client further agrees that Krenky Studio shall have the right to remove that design from public posting for failure to adhere to the terms of this Agreement, including violating any licensing agreements or failure to pay fees duly assessed.
Access Requirements
In order to install the design in question, Krenky Studio must be granted read/write access to the Client's storage directories; those directories must be accessible via FTP. Depending on the project, other resources might have to be configured on the server end (for scripts, imagemaps, etc.).
• Next Page
