<?php $root=$_SERVER['DOCUMENT_ROOT'];$wroot=dirname($_SERVER['SCRIPT_NAME']);while((strlen($wroot)>1)&&(!file_exists($root.$wroot.'/main')))$wroot=dirname($wroot);if($wroot=='/')$wroot='';require_once($root.$wroot.'/main/app/App.php');
	$app->heads('Privacy');
	$app->header();
?>
<section>
	<article>
		<h1 class='article'>Privacy</h1>
		<h4>About Auranos.org</h4>
		<p>Auranos.org is a provider of "Software as a Service" (SaaS). As part of
		our service we share the data of our associates according to their own
		deliberation. In order to provide the service we provide we neccessarily
		collect information regarding our associates accounts with the various
		platforms in their cluster. We absolutely do not share the private data
		of our associates which have been entrusted to our protection. Any law
		enforcement agencies seeking such information will be required to have a
		court order in their favour from the Sheriff of Lanark, Scotland before
		any of the information of our associates will be shared. Under no other
		circumstances will the private data of our associates be provided to any
		party.
		</p>
		<h4>Protecting your Privacy</h4>
		<p>It is the responsibility of Auranos.org to protect your privacy in
		regards to any information that may be acquired from you.
		</p>
		<p>The information we collect falls into four categories.
		</p>
		<ol>
		<li><p>The least secured category of information is the content that your
		create and opt to share across your cluster of platforms. Due to the
		nature and purpose of this data, we neccessarily share it but only with
		the websites that are within your own deliberated cluster of websites you
		wish to share that data with.
		</p></li>
		<li><p>There may be some content that you upload or create on auranos.org
		that you do not wish to share to other platforms. In these circumstances
		we will not share this data until you agree that the content is to be
		published.
		</p></li>
		<li><p>In order to access the website as an associate, able to share your
		content to the various websites in your cluster, you must provide some
		credentials for each of the platforms in your cluster. This information
		will be treated as strictly private and will never be shared.
		</p></li>
		<li><p>To use the website, an associate needs a username and a password so
		as to protect their own assets on the Auranos website as their own unique
		belongings. This information will not be shared and to the best of our
		ability we will collect this information at account creation time with the
		view that each of our associates should be able to be anonymous while
		using our website avoiding the use of gmail or other services known to
		have data privacy issues for our members. We believe that freedom of
		expression is at the current time best guaranteed by those who would
		infringe upon free speech being unable to determine who it was that said
		something. While the nature of the software in regards to its cluster
		post mechanisms to third party websites makes this philosophy to some
		considerable extent redundant, we believe that employing this philosophy
		at the current could potentially prove useful should the internet resolve
		to its more freedom of expression style beginnings.
		</p></li>
		</ol>
		<p>There is a fifth category of data which we have left out simply because
		we do not collect this data, albeit that it may appear that we are doing
		so. This data is your bank details or credit card information. We employ
		a third party to carry out financial transactions on our behalf. At the
		current time, the third party is likely paypal but we are considering the
		use of Stripe as a more convenient means of doing this.
		</p>
		<p>The way we have integrated this third party facility into our website
		may make it appear that you are communicating directly with the website
		in regards to any payments you make to us but in reality you interact
		directly with the paywall providers software in a way that merely appears
		to be part of our software. In short, we are not the ones collecting this
		information but of course we do have access to the data that the paywall
		provider gives us so that we can honour our agreement to fulfill whatever
		it is you are paying for.
		</p>
		<hr/>
		<p>Auranos.org will not disclose any information to third parties without
		your deliberate affirmative request that we do so. That is to say that
		there is an expectation that we will share the content you ask us to
		share with multiple online platforms. We will not share your credentials
		for these platforms nor will we share any private information to the
		extent that to all intents and purposes, you are an anonymous user of the
		auranos website and the credentials for the platforms in your cluster you
		provide to the application will be stored in such a manner that they will
		not be available even to the highest ranking user of the website and in
		anycase will require some advanced technological engineering to decrypt
		by any party which gains nefarious access to the physical server.
		</p>
	</article>
	<article>
		<h1 class='article'>Our Cookies</h1>
		<p>If you already have a basic understanding of cookies and just want
		information on the cookies this web application generates, you can skip
		the primer by clicking on these links to go to the appropriate subsection.
		</p>
		<ul class='center'>
			<p class='center'><a href='#1stpc'>Cookies set by this web application</a></p>
			<p class='center'><a href='#3rdpc'>Cookies which may be set by third parties through the application</a></p>
			<p class='center'><a href='#3rdpr'>Other threats to your online privacy and how to prevent them</a></p>
		</ul>
		<h2>Quick Cookie Primer</h2>
		<article>
		<h4>About Cookies</h4>
		<p>Cookies are data which are specific for a particular website which are stored
		on a users browser and sent by the browser to the particular website anytime the
		user attempts to access the website. They are usually created and altered by the
		website according the way the user interacts with the website and the user then
		seamlessly tells the website all the information it has stored in the form of
		cookies every time they access the website.
		</p>
		<p>Cookies are the primary means by which internet sites "remember" each user
		between browsing sessions. (A session is the time from when a user browses to
		a site to the time the user closes all windows and tabs associatied with the
		site.) By the use of cookies, a website can remember who a user is despite that
		the previous session may have ended days ago.
		</p>
		<p>Cookies are used for a variety of purposes. The most common purpose they are
		used for is to remember the User Identity (UID) of a user for a particular website
		which in turn can allow the website to look up the data it has stored internal
		to itself about the user who has the cookie that the server created on their
		browser for them. This internal data can include anything from the version of
		browser and the dimensions of the screen upon which the website renders content,
		to user options like the preferred colours of the user, text-size or options
		that are specific to certain types of site.
		</p>
		<h4>Malignant Cookies</h4>
		<p>They can also be used to track user activities not only on the site that the
		user is visiting but on third party websites which are able to read cookies set
		by a website for other websites to read. Tracking cookies do not only store your
		options for a website but can identify across a huge swathe of websites and such
		sites can target content at those they track which can include advertising for
		commercial purposes by people who know you clicked on an advert for a train trip
		or a political candidate and are capable of being used for targeted propaganda
		at dissidents, people of influence and even people who some organisations may
		wish to keep in a bubble of false and misleading information for purposes which
		may not involve financial gain or profits as would fit into categories imagined
		by ordinary people where money is a scarce and all important matter to those who
		cant imagine a world composed of those who have never lacked money.
		</p>
		<p>On this website, we tick the legal boxes of ensuring your privacy but then so
		do all the organisations showing privacy popups telling you they care so much 
		about your privacy they are only going to share with their partners as soon as
		you click the annoying button preventing the flow of your browsing session. We
		don't share your data with anyone except the "authorities" and only then once
		the said "authorities" have fulfilled the legal requirements they need to follow
		like getting a court order and such like, indemnifying us from being sued by you
		because we gave away your private information to those who were not legally
		entitled. We will co-operate with the "authorities" but we strike a balance that
		the "authorities" must themselves be in compliance with the law.
		</p>
		<p>We reserve a right to reveal your data without your permission in situations
		or imminent threat of death or torture, terrorism, state corruption and war.
		Outside of that, only if the law says we are <u>required</u> to divulge it.
		</p>
		</article>
		<h2>Cookies Types</h2>
		<article>
		<p>We separate cookies into four simple categories in describing who can see
		the cookies which are on your browser.
		</p>
		<h4>Session Cookies</h4>
		<p>These cookies are deleted at the end of every session and it would be rare
		for them to contain anything that could seriously violate your privacy. Perhaps
		the server wants to know what your screen size is during the current session so
		it can generate pages appropriate to the device dimensions. This could be stored
		in a session cookie but the next you access the website, the server will create
		a brand new session cookie serving the same purpose. Prior to version 3.0 of
		this web application, the "chatrooms section visiblity" and the "theme"
		being light or dark were stored on a session cookie which reset back to default
		values if the user left and came back again.
		</p>
		<h4>Third Party Cookies</h4>
		<p>Third party cookies are traditionally cookies which created for websites
		other than the website you are currently visiting. For example, you visit the
		example.com website and it puts a cookie on your browser that can be read by
		any website and is intended that freindsofexample.com can read that cookie and
		make the connection that you exist elsewhere anytime you visit a whole range of
		websites.
		</p>
		<p>Third party cookies were heavily exploited by organisations during the late
		HTTP 1.1 era and many browsers continue to allow users to block third party
		cookies with the caveat that on the modern internet, some sites may not work at
		all.
		</p>
		<h4>Samesite Cookies</h4>
		<p>A samesite cookie is a cookie which is created by a website specifically
		forbidding the cookie to be read by any website other than itself. These types
		of cookies are used by almost all websites which employ the use of cookies. The
		ability to be remembered by a site you signed up to logged into before is most
		often provided by samesite cookies.
		</p>
		<h4>Samesite Cookies by Third Parties</h4>
		<p>Social media and external authentication has encouraged techniques which were
		previously considered dangerous since they allowed third party websites to run
		programs on a website which was not their own. This was traditionally described
		as a cross site scripting XSS attack and far from a website just deliberately
		running a script from another site, alot of effort was made by maligned hackers
		to cause an external script to run on a website that was not their own such that
		alot of underlying technology had to be rewritten to prevent people from getting
		their scripts to run on someone elses website.
		</p>
		<p>Samesite Cookies by Third Parties are a type of Samesite cookie which are 
		appear to be created by the site that you are visiting and will not flag up as
		a third party cookie in a users browser but the cookies are ultimately being
		created by a script which is hosted on a third party website but is being run
		by the site you are visiting. This web application at the current
		time can run a script which is hosted by Facebook that creates cookies appearing
		to be created by the instance of the web application that a user is
		visiting. That is to say that a user visits this site, logs in using the
		facebook button and ends up with a samesite cookie for this site which were
		actually created by the script which was being hosted by facebook during the
		login procedure.
		</p>
		</article>
	</article>

<div class='anchor' id='1stpc'></div>
	<article>
	<h1 class='article'>Cookies by Auranos.org</h1>
	<article>
		<q>theme</q>
		<p>The "theme" cookie is a samesite cookie which remembers the theme
		preferred by both members and anonymous users. At the current time (2025)
		there are two themes installed, a dark theme and a light theme.
		</p>
	</article>
	<article>
		<q>sidebar</q>
		<p>The "sidebar" cookie is a samesite cookie which is used to remember
		whether the sidebar is being displayed as users browse the various pages
		on our site.
		</p>
	</article>
	<article>
		<q>uid</q>
		<p>The "uid" cookie is a samesite cookie which is used to autamotically
		log in associates to the website.
		</p>
	</article>
	<article>
		<q>hid</q>
		<p>The "hid" cookie is a used in amalgamation with the "uid" cookie to
		ensure that the security of a users login cannot be tampered with by a
		nefarious actor attempting to access someone elses account.
		</p>
	</article>
	<article>
		<q>PHPSESSID</q>
		<p>The "PHPSESSID" cookie is created by through the server softwarea used
		by auranos. It is used to store various temporary pieces of data about
		your browser and is erased at the end of your session with the website.
		</p>
	</article>
	</article>

<div class='anchor' id='3rdpc'></div>
	<article>
		<h1 class='article'>Third Party Cookies</h1>
		<p>With the possible exception of benign session cookies which are deleted at
		the end of each session and do not contain personally identifying information,
		this web application does not create any cookies which can be read by sites
		other than the site on which the instance of the web application is running.
		</p>
		<p>In saying this, in order to provide features that some websites employing
		an instance of the this web application may desire to use, the use of 
		<a href='#3rdpr'>Samesite Cookies by Third Parties</a> is unavoidable if
		the certain features of the instance are enabled such as facebook logins.
		</p>
		<p>The website owner should consult the list of site settings section of the
		setup or install page to switch these features on and off.
		</p>
<!--
	<article>
		<p>No third party cookies are permitted on this website at present. The
		website is still under construction in terms of its core functionality
		and it is unlikely to remain the case that no third party cookies will be
		used in future.
		</p>
		<p>In the likely event third party cookies will be used on this website,
		the details about them will be placed here.
		</p>
	</article>
-->
<!--
	<article>
		<h2>Facebook</h2>
		<p>Our website may be enabled to support logging in and signing up using
		Facebook as an Outside Authentication (OAuth) service provider. If you have
		logged in or signed up using the Facebook login then you will receive cookies
		which appear to be samesite cookies from our website but which were actually
		created by a script which is run through our site but hosted on Facebook.
		</p>
		<p>At the current time (January 2021), Facebook will create two cookies which
		appear to be same-site/any-subdomain cookies from our website for anyone who
		logs in or signs up using the facebook login or continue as button. Their names
		are as described here:
		</p>
		<p class='center'><code>fbm_###############</code> (where # is digit from 0 to 9)
		</p>
		<p class='center'><code>fbsr_###############</code> (where # is digit from 0 to 9)
		</p>
		<p>These cookies are only sent for "social members" who login to our site using
		the facebook login button and are not needed for members who have signed up for
		or upgraded from "social membership" to "Basic Membership".
		</p>
		<h3>Other Facebook Cookies</h3>
		<p>If Facebook analytics has been enabled for the website, a cookie for a
		Facebook Pixel will be set on your browser like so: &nbsp; <code>_fbp</code>
		</p>
	</article>
-->
	<article>
		<h2>Google</h2>
		<p>Our website may be enabled to support services provided by Google. This
		will most especially by cookies which are set for the purposes of outside
		authenitication (OAuth), which is when a user logs into this website using
		a third party which in this case is Google. Google also provides other
		services besides OAuth, so there may be cookies which are set for other
		purposes such as those which allow our users to send content to YouTube.
		All of the cookies which we may allow Google to set on our website are
		listed here.
		</p>
		<article>
		<q>g_state</q>
		<p>The "g_state" cookie is an external cookie set by Google when a social
		user authenticates through the google one tap service
		</p>
		</article>
<!--
		<p class='center'><code>_gat_gtag_UA_#########_#</code>
		</p>
		<p class='center'><code>_ga</code>
		</p>
		<p class='center'><code>_gid</code>
		</p>
-->
	</article>
	</article>
<div id='3rdpr'></div>
	<article>
		<h1 class='article'>Third Party Requests</h1>
		<p>Our website may be enabled to support various third parties who wish
		to make requests of third party sites for use on your experience of this
		website. It is hard to provide a comprehensive list of third party sites
		which this website may call due to the use of external scripts by third
		parties who may change which sites they make requests to without this site
		having much of any direct control over it rather than just switching off
		the features which cause the third party requests to be made.
		</p>
		<p>We highly recommend the use of Searxes Third Party Request Blocker
		browswer extension as a means to prevent all Third Party Requests on any
		website to be blocked unless you specifically enable the ones that Searxes
		indicates websites are wanting to make.
		</p>
		<p>This software was developed by Stephen Duffy for udhr.auranos.org which
		has a very special privacy policy which takes into account the Universal
		Declaration of Human Rights amongst other former high standing documents
		with the intent to provide users with maximum privacy and anonymity while
		at the same time providing features which will allow website owners who
		employ this software to reduce privacy to standard levels such as might be
		seen on most internet sites in operation today.
		</p>
	</article>
</section>
<?php
	$app->footer();
	$app->tails();
?>
