Add bus & ferry to public ldb

src/routes/more/privacy/+page.svelte

@@ -6,7 +6,48 @@
 </script>
  
  <Header {title} />
- 
+<div>
+ <p>OwlBoard stores as little data as possible to offer its functions for you to use.
+    OwlBoard does not use any cookies, any data that is required is stored in your browser.
+ </p>
+ <p>Owlboard does not log IP addresses or browser fingerprints.</p>
+ <h2>If you do not sign up</h2>
+ <p>If you do not sign up, no personal data is processed or stored unless you report an issue.
+ </p>
+ <h2>If you do sign up</h2>
+ <p>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.
+ </p>
+ <p>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.
+ </p>
+ <p>The email-server may store the address and message content per it's usual operation and you consent to this 
+    when you sign up.
+ </p>
+ <p>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.
+ </p>
+ <h2>Reporting an Issue</h2>
+ <p>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.</p>
+ <p>Any data that is submitted when you report an issue will be publically viewable alongside the 
+    <a href="https://git.fjla.uk/owlboard/backend/issues" target="_blank">OwlBoard/backend git repository</a>.</p>
+</div>
+ <Nav />
 
- 
- <Nav />
+<style>
+    div {
+        text-align: left;
+    }
+
+    h2 {
+        color: var(--second-text-color);
+    }
+
+    p {
+        color: white;
+    }
+</style>