Privacy rules

This website aims for data frugality. We only collect data which is necessary to operate this website or which is explicitly submitted voluntarily by the user. We use cookies to enable an internal area which serves to store settings and manage access-rights for content.

In particular we collect and process the following data:

• Content (if voluntarily submitted)
• Account data: a user name, and – voluntarily – a contact email address. A pseudonym is fine for the name, and neither is verified against a legal identity. The address may be left empty. If it is given, it is meant for questions from the operator, for resetting your password at a later time, and for notifications about answers in debates you take part in, which will be switchable. Today no email is sent at all: this site has no mail dispatch set up, so an address that is given is stored and otherwise unused. Nothing else is asked for.
• Alongside the account, the web framework this site is built on (django) keeps four fields of its own: last_login and date_joined are written automatically, first_name and last_name are never asked for and stay empty.
• One session row per login (table django_session: a session key, its expiry date, and which account it belongs to), removed when it expires. This is what the cookie mentioned above points to; the cookie itself carries the key, not the data.
• Messages sent through the feedback form (the f symbol at the top of every page, or the report symbol next to a contribution): the text, and what the form records about the page it was sent from – its address, the debate and the contributions on screen, the language, whether you were logged in, the size of the browser window and the browser's user agent string. A way back to you is stored only if you give one: a contact detail you type in (without an account), or your user name if you tick the box for it (with an account). That way back is deleted as soon as the message has been handled, after 6 months at the latest; the rest of the message is kept.
• Webserver logs (contains ip-addresses, browser version and url of origin("referrer"); Duration of storage of this data: 14 day; This data is collected to prevent abuse and facilitate secure operation of this website; See also Reason 49)

Your user name is shown next to every contribution you publish, to anyone signed in to this site – and since a published contribution cannot be withdrawn, that link between the name and the text is permanent. Visitors who are not signed in see only the role-token (a, b, ...). This is the reason the choice of a pseudonym above matters: it is made once, at registration, and it is what everybody else will see.

Published contributions live in the git repository of their debate. Those commits carry no account data: the author of a commit is a placeholder built from the debate key and the role-token inside that debate, and the committer is the platform itself. What an author writes into the text of a contribution is published with it, personal data included – no publishing platform can prevent that, and a published contribution cannot be withdrawn (see the terms of use and the FAQ).

If you have questions or requests (e.g. Correction or Deletion of data) please contact the maintainer of this website, see contact.