OwlBoard stores as little data as possible to offer its functions for you to use. OwlBoard does not use any cookies. To see the exact data that we store go to My Data.
Owlboard does not log IP addresses or browser fingerprints.
If you do not sign up, no personal data is processed or stored unless you report an issue. Any personal settings are stored in your browser and do not leave your device.
If you do sign up for the rail staff version of OwlBoard, then we do need to store some data but none of it can be used to personally identify you. Any personal settings are stored in your browser and do not leave your device.
When you sign up, you will need to provide a work email address which is checked to confirm that it originates from a railway company. You are then sent an email with a registration link, OwlBoard at this point, the username portion of the email address is discarted - for example 'a-user@owlboard.info' would be stored at 'owlboard.info'. This host part of your email address is stored so that the data that is displayed to you can be filtered, showing relevent results more prominently.
The email-server may store the address and message content per it's usual operation and you consent to this when you sign up.
Alongside the host poriton of your email address, we store a randomly generated UUID which is used to authorize access to the rail staff data.
When you report an issue, some data is collected - This data is: your browsers User Agent string and the size of the window you are viewing the website in.
Any data that is submitted when you report an issue will be publically viewable alongside the OwlBoard/backend git repository.