Security aspects when logging in to ChurchDesk
Private mode serves as an ‘extra layer of protection’ that prevents the local storage of sensitive ChurchDesk session data on a potentially insecure or shared computer. It compensates for the device's lack of basic security measures, so to speak, by ensuring that no traces of your active session remain on the computer in use after you have finished working with ChurchDesk, which could be exploited by ‘third parties’.
Instructions for Chrome
Instructions for Firefox
Instructions for Edge
Instructions for Safari
ChurchDesk is designed to be used on your work computer (for full-time staff) or a personal computer (for volunteers) in a controlled access environment. Like any other computer used for church work, the computer must be protected with a secure password and locked each time it is left. Hard drive encryption should also be enabled.
Since ChurchDesk is an important work tool that is used several times a day, we allow users to stay logged in for their session even if they close the browser in between for the sake of user-friendliness.
However, in the event that basic security measures are not in place for the particular computer or work environment being used, we recommend using your browser's ‘Private Mode’ when accessing ChurchDesk, e.g. when using a shared computer.
Private mode prevents the storage of login data and session information on the device:
Even if ChurchDesk keeps users logged in, private mode ensures that no session cookies, login data or other session-related information remains stored on the computer after the private window is closed.
It prevents subsequent users of the computer (who may not have authorisation) from accessing your ChurchDesk session, even if you have forgotten to log out.
No storage in the browser history:
The pages visited within ChurchDesk are not stored in the browsing history of the computer being used. This contributes to discretion, especially when it comes to sensitive church work content.
Clean start for every session:
Each new private browser session starts ‘clean’ without accessing cookies or cache data from previous sessions. This can also help to avoid unexpected display errors or malfunctions that could be caused by old browser data (although this is not the main focus of the security note here, it is a pleasant side effect).
How to activate ‘Private Mode’ in your browser
Instructions for Chrome
Instructions for Firefox
Instructions for Edge
Instructions for Safari
Security aspects when logging into ChurchDesk
ChurchDesk is designed to be used on your work computer (for full-time staff) or a personal computer (for volunteers) in a controlled access environment. Like any other computer used for church work, the computer must be protected with a secure password and locked each time it is left. Hard drive encryption should also be enabled.
Since ChurchDesk is an important work tool that is used several times a day, we allow users to stay logged in for their session even if they close the browser in between for the sake of user-friendliness.
However, in the event that basic security measures are not in place for the particular computer or work environment being used, we recommend using your browser's ‘Private Mode’ when accessing ChurchDesk, e.g. when using a shared computer.
What are the advantages of using private mode?
Private mode prevents the storage of login data and session information on the device:
Even if ChurchDesk keeps users logged in, private mode ensures that no session cookies, login data or other session-related information remains stored on the computer after the private window is closed.
It prevents subsequent users of the computer (who may not have authorisation) from accessing your ChurchDesk session, even if you have forgotten to log out.
No storage in the browser history:
The pages visited within ChurchDesk are not stored in the browsing history of the computer being used. This contributes to discretion, especially when it comes to sensitive church work content.
Clean start for every session:
Each new private browser session starts ‘clean’ without accessing cookies or cache data from previous sessions. This can also help to avoid unexpected display errors or malfunctions that could be caused by old browser data (although this is not the main focus of the security note here, it is a pleasant side effect).
Updated on: 03/06/2025
Thank you!