Privacy policy
Last revised: 2026-11-13
1. Who is responsible for this site
Founded and owned by the Holy Dormition Kyiv-Pechersk Lavra (male monastery) of the Ukrainian Orthodox Church, a registered non-profit religious organization, EDRPOU 14351528, 15 Lavrska St., bldg. 42, Kyiv, 01015, Ukraine. "Monastic Herald of Ukraine" is a project of the Holy Dormition Kyiv-Pechersk Lavra, carried out by the UOC Synodal Commission for Monasteries.
The Lavra is the owner of personal data within the meaning of the Law of Ukraine "On the Protection of Personal Data" and the data controller within the meaning of the General Data Protection Regulation of the European Union (GDPR).
2. The essentials, in brief
This site is purely informational. It has no registration, no user accounts, no subscriptions and no mailing lists. On the site itself you send us data in only four ways: by sending a message through the "Send feedback or ask a question" form (section 3.1), by rating an article or a video (section 3.4), by leaving a comment on them and by voting "like" or "dislike" on someone else's comment (section 3.5). The search field on the "Monasteries" page and the "Search" field on the "Map" page work inside your own browser and send us nothing; but the name typed there and the filters chosen in the "Search by filters" tab on the "Map" page are sent to the server as part of the page address, like any page request; Google Analytics receives this address, as it does the address of any other page. We do not sell, transfer or exchange users' personal data; which third-party services receive technical browser data is stated in section 5.
At the same time we should say plainly: visiting any website involves the technical processing of certain data — without it the site does not work. What data, and for what purpose, is described below.
3. What data is processed
3.1. Data you send us yourself. This happens when you choose to write to us by e-mail, to contact us through the "Contacts" page, or to send a message through the "Send feedback or ask a question" form. In the form you give the text of your message and an e-mail address for the reply; your name is optional, and depending on the subject the form may have extra fields (for example a link to a photograph or coordinates). The site does not store the text of your message: it reaches the editorial office as an e-mail. In that case we see your address, the name you signed with, and the content of your message. We use them solely to reply to you. The message is also accompanied by the address of the page the form was sent from, the kind of form, the page language and the time of sending (UTC). Messages from the form arrive in the same editorial mailbox, which is hosted by Google.
3.2. Data collected automatically. While you browse the pages, the following is processed: IP address, browser type and language, device type and operating system, the address of the page you came from, the date and time of the request, and the pages viewed. This data is processed in an anonymised, aggregated statistical form and is not used to identify an individual visitor; the exception is the security log and the call log (section 3.7).
3.3. We do not process special categories of personal data — in particular data concerning health, political opinions or the religious beliefs of identified individuals. The site's subject matter concerns monasteries and church life, but we draw no conclusion about a visitor's beliefs from the fact that a page was viewed, and we store none.
3.4. Ratings of materials. When you rate an article or a video, we store the rating itself (1 to 5), the material it concerns, the time and a rater key. The key is an irreversible code: the server computes it from a random identifier it places in your browser (section 4) and a few general traits of that browser — the type of operating system, the browser's name and its interface language. It exists so that one person can rate a material only once, and it does not reveal your name, your IP address or your device model. We do not write the IP address itself or the full browser string into the ratings database; for protection against abuse the server keeps, separately from the ratings, only a hash of the address and the times of requests (for ratings, comments, the feedback form, the view counter and the technical own-device mark; the files for comments and votes are also named by the beginning of the rater key) — they are used only to limit the number of attempts and are deleted automatically, usually within a day or two after the last request. Other visitors are shown only the average rating and the number of ratings. A rating belongs to the material, not to a language version of the page: it applies equally in the Ukrainian, Russian and English versions. The legal basis is our legitimate interest in counting ratings honestly (Article 6(1)(f) GDPR). If you delete the skm_rid cookie, the key stops being linked to your browser and we cannot tell which rating is yours.
3.5. Comments. When you leave a comment on an article or a video, we store the name you gave, the text of the comment, the material it concerns, the language it was written in, the time it was sent and the same key as for ratings (section 3.4) — it is needed for protection against abuse. We do not write the IP address or the full browser string into the comments database. Every new comment is also sent to the editorial office by e-mail. This copy is kept in the editorial office's mailbox (the mailbox is hosted by Google) as correspondence and is not deleted together with the comment. A comment appears on the site only after an administrator has reviewed it, and is shown to all visitors together with the name given; it belongs to the material, not to a language version of the page, so it is visible in the Ukrainian, Russian and English versions. The editorial office may correct or shorten a comment before or after publication; its original text and the name are kept with it until the comment is deleted. The legal basis is your consent, expressed by sending the comment (Article 6(1)(a) GDPR). To have your comment corrected or deleted, write to us (section 10). Your "like" or "dislike" vote on a comment is stored in the same way — the vote itself, its time, the comment it concerns and the same key; to vote for the first time you may need to pass a check (section 5.6).
3.6. Page view counter. Next to a page's title the site may show how many times the page has been viewed. To count a view once a day per visitor, the server computes, from your IP address (for IPv6, from its network part), your browser string and the page address, three irreversible codes that change every day, and keeps them no longer than until the next day; the counter does not store the IP address or the browser string itself and writes nothing to your browser. So that robots are not counted, the page in your browser notes whether the visitor did anything on it (a movement, a touch, a key press) or whether it stayed open long enough, and reports to the server only one of two marks — "action" or "no action"; the movements and key presses themselves are not sent anywhere. Only the number of views of each page per day, the total number of its views for the period from 30 May 2023 to 5 October 2026, transferred from Google Analytics, and the daily totals for the whole site (for example, how many views were counted from computers and from phones and from which browsers) are kept indefinitely; these data are not linked to any visitor.
3.7. Security, call and change logs. To protect the site, the server keeps an event log: it records break-in attempts detected by the built-in protection (IP address, browser string and the address of the request), as well as the actions of the site's administrators. Entries are kept for six months and then deleted automatically. The site's closed programming interface (API), open only to administrators with a service key, keeps a log of its calls: it records the IP address and the time of the calls; these entries are also kept for six months and then deleted automatically, and the counter of failed access attempts works on a code derived from the address, not on the address itself. Separately, the change log of the service page for the site's administrators, on which the directory's tables are edited (in particular monasteries, dioceses and regions), records who changed what and when (the previous and the new value of the cell), together with the IP address and the browser string of the person who made the change; these entries are kept indefinitely because they allow a change to be undone and to be traced to whoever made it. The legal basis for the security and call logs is our legitimate interest in the security of the site; for the change log, our legitimate interest in the integrity of the site's data, in particular in being able to undo a change and to see who made it (in all cases Article 6(1)(f) GDPR).
4. Cookies
Cookies are small text files that a site stores in your browser. We use:
- technical — the session identifier (
PHPSESSID), required for the pages to work correctly; - functional — the
langcookie: a technical mark of the page's language, valid for one hour; the browser remembers that you closed the cookie notice not in a cookie but in local storage (thecookieAcceptedentry), until you clear the site's data; - for ratings and comments — a random browser identifier (
skm_rid): it appears only when you leave a rating, a comment or a vote on a comment, lasts one year and is needed so that one person rates a material once and so that comments are protected from abuse (sections 3.4 and 3.5); - analytics — files of the Google Analytics service (section 5.1); they are set immediately when the page opens, before you press the button in the cookie notice.
Separately, the site's administrator sets an own-device mark on their own devices (skm_own, up to 400 days) so that their own views are kept out of the statistics; it is not issued to visitors. More about cookies and their terms is on the page "Cookies Policy".
You may delete cookies at any time or block them in your browser settings. Technical cookies cannot be blocked without harming the site's operation; analytics cookies can be declined by enabling third-party script blocking in your browser or by installing Google's official opt-out add-on for Google Analytics.
5. Third-party services
The site uses services provided by other companies. When a page contacts such a service, that service sees your IP address and technical browser data. Each of them has its own privacy policy, and in that respect the processing follows their rules, not ours.
5.1. Google Analytics 4 — anonymised visit statistics: how many people come to the site, from which countries, and which pages they read. We receive no names, no addresses and no telephone numbers through it. Google Privacy Policy. The site is advertised in Google Search under the Google Ad Grants programme. If you came to the site from such an ad, Google Analytics stores an identifier of that click-through (gclid) in its cookies, and two actions on the site — starting to watch a broadcast and pressing the donate button — are passed to Google Ads as conversions, so that we can see whether the ads are useful.
5.2. YouTube — the "UOC Live" page, the video pages and some individual publications show broadcasts and recordings from YouTube. On the pages of individual channels, the channel's picture is loaded from Google's servers as soon as the page opens. Video is embedded in privacy-enhanced mode (youtube-nocookie.com). Watching video is governed by YouTube's terms and by the Google Privacy Policy. You may review and revoke the access you have granted to Google applications at security.google.com/settings/security/permissions. The YouTube player may store its own data in your browser's local storage.
5.3. Google Maps — the monastery map, directions and, in some individual publications, a map image. Google Privacy Policy.
5.4. Facebook — the site has links to Facebook pages and a "Share" button: they open Facebook only after you click. On some video pages a Facebook player is embedded: it loads together with the page, so Facebook sees your IP address and the browser's technical data even before you start the video. Meta Privacy Policy.
5.5. monobank (send.monobank.ua) — acceptance of charitable donations. The button leads to the bank's own page; you enter your card details on the bank's side, and we neither see, receive nor store them.
5.6. Cloudflare Turnstile — the "I am not a robot" check you pass when you choose a rating for a material, open the comment window or a window with a message form, start writing a message in the form at the bottom of the page or vote on a comment; a vote on a comment needs the check if there is no service record that the key has passed it (the record is made with a comment or a first vote). During the check Cloudflare sees your IP address and technical browser data and decides whether you are a person; to verify the answer, our server passes your IP address to Cloudflare; we receive from it only the answer "passed" or "not passed". Cloudflare Privacy Policy.
5.7. Other "Share" links — the "Share" row also has a link to Telegram and a button "Add our site as a source in Google": they open those services only after you click.
5.8. OpenStreetMap — on the monastery pages and on the "Contacts" page the map types include an OpenStreetMap layer; if you choose it, the map images are loaded from the servers of the OpenStreetMap Foundation, which sees your IP address and technical browser data. OpenStreetMap Foundation Privacy Policy.
5.9. Links to other sites — the pages of the site contain links to monasteries' own sites, reference sites and maps (for example Wikimapia, GeoHack, OpenStreetMap); they open those sites only after you click, and from then on those sites' own rules apply.
There is no advertising on our site: we display no ad blocks and build no profiles for ad targeting. At the same time, "Google signals" is enabled in Google Analytics and ad personalisation is allowed: if you are signed in to a Google account and have allowed ad personalisation in it, Google may link your visits to the site with that account and take them into account in its own advertising services. You can manage this in the ad settings of your Google account (myadcenter.google.com).
6. Purpose of processing and legal basis
Data is processed so that the site works technically, so that we understand which materials are being read, and so that we can answer your message. Legal bases: our legitimate interest in operating and improving the site (Article 6(1)(f) GDPR), for technical and analytics data, including the Google Analytics cookies that are set immediately when the page opens, before you press the button in the cookie notice; and your own enquiry, for correspondence.
7. Retention period
The technical cookie PHPSESSID is kept for up to eight hours, the lang cookie for one hour, and the record that the cookie notice was closed in the browser's local storage until you clear the site's data; Google Analytics cookies last up to two years (browsers may shorten this period), and the event data in Google Analytics is kept for fourteen months. Correspondence is kept for as long as it is needed to reply and for church record-keeping, after which it is destroyed.
A rating and its rater key are kept indefinitely: without them the average rating of a material cannot be counted. The skm_rid cookie lasts one year.
A comment and the name given in it are kept for as long as the comment is published or awaiting review; a comment rejected or removed by an administrator is deleted from the site's database for good 30 days after the rejection or removal. Together with it, the replies to it and all votes on these comments are deleted for good. The comment's key is kept with it to protect against abuse.
Your "like" or "dislike" vote on a comment is kept with the key until you withdraw it by pressing the button again or until the comment itself is deleted.
A service record that your browser's key has already passed the "I am not a robot" check (the key itself and the time of the first pass) is kept indefinitely — it is needed so that a forged key cannot be used to vote without the check. A browser key that an administrator has blocked is kept with the time of the block until the block is lifted.
The counter's daily codes are deleted the next day; the number of views of each page per day and the daily totals for the whole site are kept indefinitely.
Entries in the security log and in the call log of the closed programming interface are kept for six months.
Entries in the change log of the directory's tables (in particular monasteries, dioceses, regions) are kept indefinitely: they allow a change to be undone and to be traced to whoever made it.
8. Your rights
You have the right to: learn which of your data we process; request its correction or erasure; object to processing; withdraw consent; obtain a copy of the data; and lodge a complaint with the Ukrainian Parliament Commissioner for Human Rights or, if you are in the European Union, with the supervisory authority of your country.
To exercise any of these rights, write to us (section 10). We will reply within thirty calendar days.
9. Data protection and children
The site operates exclusively over a secure HTTPS connection. Access to the site's administrative area is limited to authorised persons.
The site is not intended for children under fourteen and does not knowingly collect their data. If you become aware that a child has sent us their data, please tell us and we will delete it.
10. Contacts
For any question concerning personal data, please write to info (at) inok.info — the same address is also given on the Contacts page. Postal address for correspondence: 15 Lavrska St., bldg. 42, Kyiv, 01015, Ukraine.
11. Changes to this Policy
We may change this Policy — for example when a new service appears or the law changes. The version in force is the one published on this page; the date of the latest revision is given at the top. Material changes will additionally be marked by a notice on the site.
A separate privacy policy applies to the online broadcasting service — UOC Live: it concerns the use of YouTube API Services and supplements this Policy without superseding it.


