Provider and scope
These terms apply to the public Bible Desktop API used by Georg-Kloster Calendar Workshop, including requests to bible-desktop.com/api/. Provider: Volodymyr Atapin, ATAPIN.DE, Neuhofer Straße 7, 16278 Angermünde, Germany. Contact: atapin@gmail.com. Provider information: Impressum.
Use of the API
The API supplies available Bible translations, books, chapters, liturgical texts, hagiographies and icon catalogues and images. Regular public reading endpoints are available without a user account; protected features may require separate authorization. Respect request limits, caching directives and access restrictions. Do not bypass safeguards or use the service to disrupt other users. API access does not transfer ownership of texts or images. Observe each material’s source, licence and rights information before reproduction or redistribution; API availability does not imply that all materials are public domain.
Availability and accuracy
Available translations, editions and media may change or be incomplete. Check information before publication or liturgical use. Continuous availability, completeness and suitability for a particular purpose are not guaranteed. Mandatory statutory liability and consumer rights remain unaffected. Report errors, rights concerns or access questions to the provider.
Data protection
Request processing is described in the API Privacy Policy. These API terms do not describe unrelated account, payment or OCR features. Updated: 7 October 2026.
Church Slavonic translation API
These terms also cover Church Slavonic Translator and requests to /api/v1/church-slavonic/translate and /api/v1/church-slavonic/status. Translation starts only when a visitor submits text. The free tier has installation-based usage limits; an optional Bible Desktop API key may enable higher limits. A connection check does not submit translation text or call OpenAI. Activation and displaying the WordPress form do not contact the service.
Biblical references, recognized quotations and cached results may be returned without a new AI request. Other texts may be sent to OpenAI to generate a translation, subject to the configured model and service limits. AI output can contain errors: review it before publication or liturgical use. Submit only text you are entitled to process and disclose; do not submit confidential or sensitive personal information. Site operators must inform visitors about external processing and obtain any necessary permissions before offering the form. API keys must remain on the server and request limits must not be bypassed. Downloading Monomakh Unicode is a separate browser request to /fonts/MonomakhUnicode.ttf; observe the font licence.
OpenAI API terms: OpenAI Services Agreement. OpenAI privacy information: Privacy Policy. Translation data processing is described in our API Privacy Policy. Updated: 7 October 2026.