By accessing and using this service, you accept and agree to be bound by the terms and provision of this agreement. In addition, when using these particular services, you shall be subject to any posted guidelines or rules applicable to such services. Any participation in this service will constitute acceptance of this agreement. If you do not agree to abide by the above, please do not use this service.
This BibleGet website, service endpoints, and relative published plugins do not in any way collect or store any personal information of it’s users, and no personal data is relayed in any way by the plugins to the bibleget.io server. The BibleGet I/O website may make use of Google Analytics services in order to evaluate the usage of the website. It does not however collect or store any kind of personal information from its users, to which it has no access. The source code for the BibleGet service endpoints is disclosed in the BibleGet-I-O/endpoint repository on Github.
The BibleGet I/O service provides bible texts only from reliable sources. These sources are disclosed on the BibleGet website https://www.bibleget.io/bible-versions-supported/ . The BibleGet I/O service endpoint however is not responsible or liable in any event for the accuracy of the information provided, as such accuracy is dependent on the accuracy of the sources utilized. In the event that the user believes there may be an inaccuracy not due to the sources utilized, he/she is invited to send feedback to the BibleGet I/O creators at email@example.com so that the issue may be looked into.
The BibleGet I/O service endpoint engine (https://query.bibleget.io/), the BibleGet I/O website https://www.bibleget.io and its original contents, the BibleGet I/O logo, and the BibleGet I/O plugins and add-ons (BibleGet I/O Plugin for Google Docs, BibleGet I/O Plugin for Open Office, BibleGet I/O Plugin for Microsoft Word, BibleGet I/O Plugin for Wordpress) are the sole property of their creator John R. D’Orazio, a priest in the Diocese of Rome (firstname.lastname@example.org). The BibleGet I/O project has been created as an educational resource by Rev. John Romano D'Orazio (https://www.johnromanodorazio.com). All of the above mentioned BibleGet I/O officially released plugins together with service endpoint engine at https://query.bibleget.io are open sourced and released to the public on Github at https://github.com/BibleGet-I-O/ and are licensed under the Open Source Apache 2.0 license as can be found at http://www.apache.org/licenses/LICENSE-2.0. This means that this software can be freely distributed, incorporated in other projects, and modified, as long as the original source and author are provided in the source code and in the usage of the software. Any software or plugins of third parties that utilize the BibleGet I/O service endpoint https://query.bibleget.io must disclose their usage of the service endpoint to any users that download or install or utilize the third party software, and must provide in every query directed to the service endpoint the “appid” parameter with a unique id of the software application.
The biblical texts that are available from the service endpoint are the sole property of their respective copyright holders. Some of the texts provided are in the public domain, others however are covered by copyright law and are provided solely with usage granted by their copyright holders to the BibleGet I/O project in the person of John R. D’Orazio, priest of the diocese of Rome. Access to any copyrighted texts made available by the project may be limited by their respective copyright holders (for example, a maximum number of verses that can be retrieved in a single query).
This software is free to use as an educational resource without any charge for usage. No payments are required for queries to the service endpoint. No direct advertiser relationships are entertained by BibleGet I/O, no advertisements are presented in any of the plugins provided. The BibleGet I/O website https://www.bibleget.io makes use of the Amazon Affiliate Program offering users of the website the possiblity of purchasing products on Amazon through the affiliate links published in order to subsidize the costs of the service provided, however BibleGet I/O has not sold any advertising space neither on the website nor in the plugins. BibleGet I/O does not endorse any single products or services through the affiliate links unless directly related to the finality of the project.
The BibleGet I/O project and its creators will not be liable for any downtimes on the project’s servers resulting in loss of service at the BibleGet I/O service endpoint. If the user believes that any damage may have been caused in any way by the software provided by this project, or if the user believes that the software is lacking in the functionality that it is purported to offer, he/she is invited to send feedback to email@example.com indicating the kind of functionality that he/she believes was declared but is lacking, or the kind of damage that was caused and why he/she thinks it may have been caused by the BibleGet I/O software. The BibleGet I/O creators will look into the issue with care to determine if there are any shortcomings in the provided software that may be patched so as to provide a better service.
The Google Docs Add-on as published to the Gsuite Marketplace discloses it's source code in the BibleGet-Google-Docs-Addin repository on Github. Installation of the Add-on in Google Docs requires the following permissions:
The WordPress Plugin as published to the WordPress plugin directory discloses it's source code in it's WordPress svn repository.
The OpenOffice Extension as published to the OpenOffice Extensions directory discloses it's source code in the BibleGet-I-O/bibleget-openoffice repository on Github.
The LibreOffice Extension as published to the LibreOffice Extensions directory discloses it's source code in the BibleGet-I-O/bibleget-libreoffice repository on Github.
The Microsoft Word add-on as published on the BibleGet website discloses it's source code in the BibleGet-I-O/bibleget-msword-addin repository on Github. While no kind of personal information from end users is collected, the domain from which requests are generated is however collected and stored in order to help monitor usage of the endpoint, seeing that registration is not required, authentication is not required and API keys and secrets are not issued.
Date published: August 27, 2015
Date updated: August 1, 2020