Privacy

License

Ricoh Print Cloud Virtual Printer uses a number of third-party libraries to provide its features. The list of third-party libraries include QT, OpenSSL, and GhostScript.

QT

The Qt framework is dual-licensed, available under both commercial and open-source licenses. 
The commercial license is recommended option for non-open source projects. If you consider 
using Qt under any open source licenses, please read this document carefully.
The primary open-source licenses are the GNU Lesser General Public License v. 3 and the GNU 
Lesser General Public License v. 2.1 (both jointly “LGPL”). In addition to LGPL, the Qt 
libraries and tools are available under commercial license terms from The Qt Company. The Qt 
documentation is licensed under the GNU Free Documentation License version 1.3. LGPL can be 
converted to GNU General Public License (“GPL”).
LGPL has been chosen as the primary open-source license for Qt, because it provides the following 
four degrees of freedom:
    1. The freedom to run the program for any purpose.
    2. The freedom to study how the program works and adapt it to specific needs.
    3. The freedom to redistribute copies so you can help your neighbor.
    4. The freedom to improve the program and release your improvements to the public, 
       so that the whole community benefits.
These four degrees of freedom are very important for the success of the open-source Qt Project, 
and it is important that all users of Qt under LGPL adhere to these and fully meet all the 
requirements set by the LGPL. It is recommended that a thorough legal analysis is conducted 
when choosing to use any open-source licenses. In many cases, the LGPL is a viable solution to use, 
but it is important that the freedoms of the LGPL are not restricted from the user of an application 
or device using an LGPL library such as Qt, which may be difficult to achieve in some use cases. For 
such cases the commercial licensing option is typically a better choice.
The following requirements should be fulfilled when, for example, creating an application or a device 
with Qt using the LGPL:
    1. Complete corresponding source code of the library used with the application 
       or the device built using LGPL, including all modifications to the library, should 
       be delivered with the application (or alternatively provide a written offer with 
       instructions on how to get the source code). It should be noted that the complete 
       corresponding source code has to be delivered even if the library has not been modified at all.
    2. In case of dynamic linking, it is possible, but not mandatory, to keep application 
       source code proprietary as long as it is “work that uses the library” – typically 
       achieved via dynamic linking of the library. In case of static linking of the library, 
       the application itself may no longer be “work that uses the library” and thus become 
       subject to LGPL. It is recommended to either link dynamically, or provide the application 
       source code to the user under LGPL.
    3. The user is allowed to change and re-link the library used in the application or device – 
       including reverse engineering. With LGPLv3 it is explicitly stated that the user also needs 
       to be able to run the re-linked binary, and that sufficient installation information must be 
       provided. In LGPLv2.1 it is not clearly stated whether or not the user has to be able to place 
       the modified library back into the device, and run it, preferably it should be enabled.
    4. If the application or device is not fully following all requirements of the LGPL, it is not 
       allowed to be distributed at all. This includes, for example, possible patent license 
       restricting distribution of the application in which case there is no right to distribute.
    5. The freedoms provided by the LGPL license cannot be in any way negotiated upon or restricted 
       from any of the recipients – i.e. it is not possible to make such terms for an application 
       or a device using theLGPL library that would in any way restrict the rights provided by the 
       LGPL. For example some means of distribution, such as online application stores, may have rules
       that are in conflict with LGPL, in which case those cannot be used with the LGPL licensing 
       option of Qt.
    6. The user of an application or device created with LGPL library has to be notified of their 
       rights by providing a copy of the LGPL license text to the user and displaying a prominent 
       notice about using the LGPL library – i.e. it is not allowed to hide the fact the 
       LGPL library is used.
This is not a complete list of LGPL requirements – please refer to the LGPL for complete list 
of requirements – it is always recommended to contact an experienced legal counsel to clarify 
detailed licensing suitability. Please note that The Qt Company does not offer legal guidance on 
whether or not a certain license is suited for your need, or if your application or device meets 
the LGPL requirements. In case there is any doubt whether or not the requirements of LGPL can be 
met in full, the commercial licensing option of Qt is often the best choice. The Qt Company has 
made the following exceptions from LGPL licensing:
    1. Third party software already included in Qt is governed by the separate Open Source license
       terms under which the third party software has been distributed. All third party software 
       is listed in the documentation, along with their licensing terms. For example, 
                                here you can find list of third party licenses used in Qt.
    2. Libraries that must be statically linked, such as the QtMain Library (QaX Server, QaX 
       Container) have been licensed under a BSD-style license.
    3. Application code as part of examples, which can be used by Qt contributors in the application
       creation is generally licensed under a BSD-style license.
    4. Documentation is licensed under the GNU Free Documentation License
	                

OpenSSL

	    
  LICENSE ISSUES
  ==============
  The OpenSSL toolkit stays under a dual license, i.e. both the conditions of
  the OpenSSL License and the original SSLeay license apply to the toolkit.
  See below for the actual license texts. Actually both licenses are BSD-style
  Open Source licenses. In case of any license issues related to OpenSSL
  please contact openssl-core@openssl.org.
  OpenSSL License
  ---------------
/* ====================================================================
 * Copyright (c) 1998-2016 The OpenSSL Project.  All rights reserved.
 *
 * Redistribution and use in source and binary forms, with or without
 * modification, are permitted provided that the following conditions
 * are met:
 *
 * 1. Redistributions of source code must retain the above copyright
 *    notice, this list of conditions and the following disclaimer. 
 *
 * 2. Redistributions in binary form must reproduce the above copyright
 *    notice, this list of conditions and the following disclaimer in
 *    the documentation and/or other materials provided with the
 *    distribution.
 *
 * 3. All advertising materials mentioning features or use of this
 *    software must display the following acknowledgment:
 *    "This product includes software developed by the OpenSSL Project
 *    for use in the OpenSSL Toolkit. (http://www.openssl.org/)"
 *
 * 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to
 *    endorse or promote products derived from this software without
 *    prior written permission. For written permission, please contact
 *    openssl-core@openssl.org.
 *
 * 5. Products derived from this software may not be called "OpenSSL"
 *    nor may "OpenSSL" appear in their names without prior written
 *    permission of the OpenSSL Project.
 *
 * 6. Redistributions of any form whatsoever must retain the following
 *    acknowledgment:
 *    "This product includes software developed by the OpenSSL Project
 *    for use in the OpenSSL Toolkit (http://www.openssl.org/)"
 *
 * THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY
 * EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
 * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
 * PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE OpenSSL PROJECT OR
 * ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
 * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
 * NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
 * LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
 * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
 * STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
 * ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
 * OF THE POSSIBILITY OF SUCH DAMAGE.
 * ====================================================================
 *
 * This product includes cryptographic software written by Eric Young
 * (eay@cryptsoft.com).  This product includes software written by Tim
 * Hudson (tjh@cryptsoft.com).
 *
 */
 Original SSLeay License
 -----------------------
/* Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com)
 * All rights reserved.
 *
 * This package is an SSL implementation written
 * by Eric Young (eay@cryptsoft.com).
 * The implementation was written so as to conform with Netscapes SSL.
 * 
 * This library is free for commercial and non-commercial use as long as
 * the following conditions are aheared to.  The following conditions
 * apply to all code found in this distribution, be it the RC4, RSA,
 * lhash, DES, etc., code; not just the SSL code.  The SSL documentation
 * included with this distribution is covered by the same copyright terms
 * except that the holder is Tim Hudson (tjh@cryptsoft.com).
 * 
 * Copyright remains Eric Young's, and as such any Copyright notices in
 * the code are not to be removed.
 * If this package is used in a product, Eric Young should be given attribution
 * as the author of the parts of the library used.
 * This can be in the form of a textual message at program startup or
 * in documentation (online or textual) provided with the package.
 * 
 * Redistribution and use in source and binary forms, with or without
 * modification, are permitted provided that the following conditions
 * are met:
 * 1. Redistributions of source code must retain the copyright
 *    notice, this list of conditions and the following disclaimer.
 * 2. Redistributions in binary form must reproduce the above copyright
 *    notice, this list of conditions and the following disclaimer in the
 *    documentation and/or other materials provided with the distribution.
 * 3. All advertising materials mentioning features or use of this software
 *    must display the following acknowledgement:
 *    "This product includes cryptographic software written by
 *     Eric Young (eay@cryptsoft.com)"
 *    The word 'cryptographic' can be left out if the rouines from the library
 *    being used are not cryptographic related :-).
 * 4. If you include any Windows specific code (or a derivative thereof) from 
 *    the apps directory (application code) you must include an acknowledgement:
 *    "This product includes software written by Tim Hudson (tjh@cryptsoft.com)"
 * 
 * THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND
 * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
 * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
 * ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
 * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
 * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
 * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
 * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
 * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
 * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 * SUCH DAMAGE.
 * 
 * The licence and distribution terms for any publically available version or
 * derivative of this code cannot be changed.  i.e. this code cannot simply be
 * copied and put under another distribution licence
 * [including the GNU Public Licence.]
 */
	    

GhostScript

Licensing Information   
 
Important information about distributing software from Artifex
If you want to distribute Ghostscript® technology or make it available to your customers as a 
software-as-a-service (SaaS) or application service provider (ASP), you've come to the right 
place: Artifex is the exclusive commercial licensing agent for Ghostscript software and MuPDF. 
You should know that there is no "public domain" version of Ghostscript or MuPDF. All versions 
of Ghostscript and MuPDF are provided under one of two licenses described below. If you plan to 
distribute Ghostscript or MuPDF or make them available to your SaaS or ASP customers, you should 
understand the differences between these licenses. The kind of distribution or use you plan to make 
of Ghostscript or MuPDF, as explained below, will determine whether you need a commercial license 
from Artifex. Please note that the following rules apply even if you ship or make available a free 
demonstration version of your own product or application. An "application," as referenced below, 
can be any type of software product or application, tool, system or utility.
Versions of Ghostscript and MuPDF are licensed under two types of licenses...
    1. Artifex Ghostscript and Artifex MuPDF. Artifex Ghostscript and Artifex MuPDF is any 
       version of Ghostscript or MuPDF licensed for commercial use and distribution under 
       an Artifex Commercial License. Artifex is the exclusive commercial licensing agent 
       for Ghostscript and MuPDF technologies.
    2. AGPL Ghostscript and AGPL MuPDF. AGPL Ghostscript and AGPL MuPDF are distributed under 
       the GNU Affero General Public License (the "AGPL").
PLEASE NOTE: 
Artifex offers a private version of Ghostscript optimized for embedded use.  AGPL Ghostscript 
is not optimized for the stringent resource requirements of embedded environments such as laser 
printer or MFP applications.  The private embedded Ghostscript distribution includes additional 
engineering work that makes this distribution commercially competitive for these environments.  
To obtain this distribution for evaluation at no cost, please contact sales@artifex.com
If your entire application is licensed to the public under the GNU Affero General Public 
License (AGPL), you can provide AGPL Ghostscript or AGPL MuPDF with your application without a 
commercial license...
If your application, including all of its source code, is licensed to the public under the AGPL, 
you are authorized to ship AGPL Ghostscript and AGPL MuPDF with your application, and to allow 
your users to remotely interact with AGPL Ghostscript and AGPL MuPDF along with your application, 
under the terms of the AGPL license agreement. You do not need a commercial license from Artifex. 
The terms of the AGPL include the requirement that your application be licensed as a whole at no 
charge to all third parties. Moreover, the entire application must be licensed to the public 
under the AGPL.
If your application is not licensed to the public under the AGPL and you plan to provide 
Ghostscript of MuPDF software...
If your application (including its source code) is not licensed to the public under the AGPL, 
you are not authorized under the terms of the AGPL to ship AGPL Ghostscript or AGPL MuPDF with 
your application, or to allow your users to remotely interact with AGPL Ghostscript and AGPL 
MuPDF along with your application, if any one of the following is true:
    1. your application contains a copy of some or all of AGPL Ghostscript or AGPL MuPDF; 
    2. your application is derived from, is based on, or constitutes a revision of some or 
       all of AGPL Ghostscript or AGPL MuPDF; 
    3. your application includes one or more functions that use some or all of AGPL Ghostscript 
       or AGPL MuPDF.
These criteria apply to your application as a whole. Even if only one section of your application 
satisfies one of these criteria, you are not authorized under the terms of the AGPL to ship AGPL
Ghostscript or AGPL MuPDF with your application, or to allow your users to remotely interact with 
AGPL Ghostscript and AGPL MuPDF along with your application, unless your application (including all 
of its source code) is licensed to the public under the AGPL.
If your application (including its source code) is NOT licensed to the public under the AGPL and you 
intend to distribute Ghostscript or MuPDF to a third party for use with and usable by your application
or to allow your users to remotely interact with AGPL Ghostscript and AGPL MuPDF along with your 
application, you MUST first obtain a commercial license from Artifex.
Examples of Distribution/Network use requiring a commercial license:
    1. Distributing Ghostscript (or any component thereof) within your non-AGPL application.
    2. Distributing Ghostscript on the same media with your non-AGPL application for use with 
       and by your application.
    3. Distributing Ghostscript embedded within hardware.
    4. Running Ghostscript on your network servers and permitting your users to interact with 
       Ghostscript as part of your non-AGPL application.

Does Artifex recommend the commercial license? Artifex recommends that all commercial entities that wish to either distribute Ghostscript or MuPDF, or to make them available to their SaaS or ASP customers, to enter into the Artifex Commercial License with Artifex. Not only does it free you from having to conform to the requirements and restrictions of the AGPL licenses, but it also provides you with additional protections and rights, such as support. AGPL Ghostscript and AGPL MuPDF are provided "AS-IS" without warranties or support of any kind.
Note: Past open source licenses Artifex has distributed Ghostscript and MuPDF in the past under two other open source licenses: The GNU General Public License (GPL), and the Aladdin Free Public License (AFPL). Future open source versions of Ghostscript and MuPDF will only be available under the AGPL.

Page Top