Concept
Policy Versions
How policies are published with a version label and an effective date, how the public site shows earlier versions, and the cookie policy and privacy notice.
When a policy changes, readers need to see which rule applied when. That is why JournTech keeps policies in versions. Every published version carries its own label and effective date and is never changed afterwards.
Version label and effective date
A policy is published only when Version label and Effective date are filled in. Every published version has its own label, for example v2.0 and v2.1. A label that was published before cannot be used again. When you restore an old version, its label comes back too. In that case, enter a new label before publishing.
Versions on the public site
The public site shows the version of the policy in force, with its version label and effective date. At the bottom of the page is a list of earlier versions, and each earlier version can be read at its own link. Search engines do not index earlier versions.
Cookie policy and privacy notice
The institution's cookie policy and its KVKK privacy notice (the notice required by Türkiye's Personal Data Protection Law) are published as policies too. On a first visit to the public site, a short cookie note appears at the bottom of the page. The note says that the site uses only the cookies it needs to work and to stay secure, and it links to the Policies page. When the visitor presses OK, the note does not appear again in that browser. The site uses only strictly necessary cookies, so there is no consent dialog.
The steps for creating a policy are in Creating a Page.