OwlBoard stores the minimum amount of data necessary to provide its functions for your use. No personal data is stored unless you report an issue. To review the specific data that we store, please visit My Data.
OwlBoard does not utilize any cookies. IP addresses and browser fingerprints are not logged.
If you choose not to sign up, no personal data will be processed or stored unless you report an issue. Any personal settings are stored locally in your browser and do not leave your device.
If you sign up for the rail staff version of OwlBoard, we do require the storage of some data. However, none of this data can be used to personally identify you. Any personal settings are stored locally in your browser and do not leave your device.
During the sign-up process, you will be asked to provide a work email address, which will be checked to confirm its origin from a railway company. Once confirmed, an email containing a registration link will be sent to you. At this point, the username portion of your email address is discarded. For example, if your email address is 'a-user@owlboard.info', only 'owlboard.info' will be stored. This host portion of your email address is stored to filter and display relevant results prominently.
The email server may store the address and message content as part of its regular operation, and your consent to this is implied when you sign up.
In addition to the host portion of your email address, a randomly generated UUID is stored for the purpose of authorizing access to the rail staff data.
When you report an issue, certain data is collected, including your browser's User Agent string and the size of the window in which you are viewing the website.
Any data submitted when reporting an issue will be publicly viewable alongside the OwlBoard/backend git repository.