Controller and scope
This policy covers public Bible Desktop API requests from Georg-Kloster Calendar Workshop and the calendar service. Controller: Volodymyr Atapin, ATAPIN.DE, Neuhofer Straße 7, 16278 Angermünde, Germany; contact: atapin@gmail.com. It covers bible-desktop.com/api/ and does not describe unrelated account, payment or OCR features.
Data received and when
When a calendar block requests icons, or a reader opens a Bible chapter or liturgical library, the requesting WordPress or calendar server sends selected dates or month/day, language or translation, book/chapter, work or image identifiers, filters and pagination. Cache misses and scheduled media revalidation may download an image or font or send conditional ETag/Last-Modified headers. The service receives the requesting server IP address, request time, resource and technical HTTP headers. The calendar plugin does not send visitors’ IP addresses, names, email addresses, post contents or WordPress passwords. Its calendar API key is not sent to Bible Desktop. Direct requests to this service from a browser expose that browser connection’s IP address and technical headers.
Purpose, legal bases and retention
We process request data to deliver the requested public resources, maintain technical caches, troubleshoot failures and prevent excessive or abusive traffic. The legal bases are service provision where Article 6(1)(b) GDPR applies and the legitimate interests in service operation and security under Article 6(1)(f) GDPR. Technical logs and security counters may contain request metadata. Retention depends on operational necessity, security investigations and statutory obligations; no fixed automatic deletion period is promised. Authorized administrators and infrastructure providers may process technical data as necessary to operate the service. Public reading requests do not ask the plugin to submit text to AI, OCR or translation providers.
Your rights
Where applicable, you may request access, correction, deletion, restriction or portability, and object to processing based on legitimate interests. Contact the controller at the address above. You may complain to a data protection supervisory authority, including LDA Brandenburg, Stahnsdorfer Damm 77, 14532 Kleinmachnow, Germany, Poststelle@LDA.Brandenburg.de. API Terms of Service. Updated: 7 October 2026.
Church Slavonic translation data
This policy also covers Church Slavonic Translator and /api/v1/church-slavonic/translate and /api/v1/church-slavonic/status. When a visitor submits the WordPress form, the WordPress server sends the source text, source language and orthography options (accents, titlo, breathings and Slavonic numbers). Headers include the plugin client name, a persistent installation UUID, a pseudonymous visitor identifier computed by WordPress as an HMAC of the visitor IP address using a WordPress secret, and an optional Bible Desktop API key. The UUID and visitor identifier support quotas and abuse prevention; they are not anonymous data. The plugin does not send the original visitor IP to the translation API. Bible Desktop receives the WordPress server IP and technical request information. An administrator-triggered status check sends the client name, installation UUID and optional API key, but no source text or visitor identifier and makes no OpenAI request. Activation and viewing the form do not contact Bible Desktop. Clicking Download font sends a direct browser request, revealing the visitor IP and ordinary browser request information.
OpenAI processing and translation retention
For text not resolved by the local biblical corpus or an existing cached result, Bible Desktop sends OpenAI the source text, source and target languages, orthography options, translation instructions and a hashed safety identifier derived from the request actor. The WordPress API key is not forwarded to OpenAI. OpenAI processes this information to generate the translation. Bible Desktop requests store: false, which does not guarantee zero retention by OpenAI. Provider retention, processing locations and any international transfers depend on the applicable OpenAI API terms, data protection arrangements and account configuration. See the OpenAI Services Agreement, Data Processing Addendum and Privacy Policy.
Bible Desktop caches translated results using a key derived from the source text and translation settings for the cache duration configured by its administrator. Quota and rate-limit counters retain pseudonymous identifiers and usage counts for their configured expiry periods. Translation completion logs contain technical metadata such as language, character count, processing duration, access tier and cache status, rather than the source text or translation. Infrastructure logs and backups may retain technical records according to operational and statutory requirements; no universal deletion period or zero-retention promise is made. Authorized administrators, hosting providers and OpenAI may process the data as needed to deliver the service and protect it from abuse. Processing is for the requested translation and service operation/security under the legal bases described above where applicable. Site operators must explain this processing to visitors and establish the applicable permissions or legal basis. Do not submit confidential or sensitive personal information. The rights and controller contact listed in this policy also apply to translation requests. Updated: 7 October 2026.