It is your right as a visitor to “Benung. The Ayeri Language Resource” (“this website”) to object to any of the below points, as well as to demand comprehensive information about any data which is stored on your using this website, and to demand its prompt deletion without giving any reasons. To do so, please provide a written notice to the below address.
Ba chw eg 5
3 503 7 Mar bu rg
Ger ma ny
info@ ayeri. de
Hosting of this website is obtained from NFSN, Inc., an American company. Server-side data incurred by your using this website is thus processed outside of the European Union.
Logging, Tracking, etc.
This website logs traffic in order to recognize attacks against it and to be able to react to attacks so as to prevent them in the future. The data saved by a visitor’s access includes their IP address, files accessed on this website, referring link, time of access, and the visitor’s browser/operating system. The logs are kept in a directory which is not publicly accessible and purged weekly. Retention of information about a visit is thus limited to a maximum of 7 days. Logged information is not used to generate user profiles; there is no way for users to register an account on this website either. Hourly anonymization of IP addresses in the log file additionally ensures that only the first 24 bits (out of 32) of an IPv4 or the first 48 bits (out of 128) of an IPv6 are kept. This allows to trace back a website access to an IP network, but not to an individual visitor. Access to this website is secured by an SSL certificate obtained from Let’s Encrypt.
Moreover, as a way to basically crowdsource finding gaps in the dictionary and thus to get inspiration on what to make up words for next, dictionary queries which fail to return any results are logged seperately from the server’s access log. Only the failed query itself is saved in this case, but no traits which could identify an individual visitor. In querying the dictionary database, only the data which a visitor provided in the search form is processed, nothing more. The independent site search by which blog articles and pages within this website can be searched is not logged, and no data besides what was entered is processed there either.
Additionally, as a means to prevent spam, every visitor’s IP address is screened for recent cases of malevolent behavior by Cleantalk. Your IP address is matched with a locally stored list of IP addresses recently associated with notorious comment spammers and those which have engaged in brute force attacks. If the result is positive, comment fields or site access may be blocked. Cleantalk makes information on blocked access attempts available to the website owner for a period of 8 days, including the full IP address of a blocked visit.
By commenting on an article, a visitor’s IP address is saved automatically, however, it is set to be anonymized to 127.0.0.1 for permanent keeping. This way, effectively, only the information which a visitor provided in the comment form is saved. A commenter’s e-mail address is regarded as confidential and may be provided by a commenter optionally; it is not publicly visible. Any factual private information visitors choose to include in the publicly readable part of comments—that is, “Name”, “Website”, “Comment”—they publish at their own risk. The website owner reserves the right to moderate or delete comments if they are abusive, for instance, if they contain harassment or spam. Also see NFSN.net’s hosting policies.
|comment_author_*||persistent||1 year||Saves the input of the 'author' field in comment forms.|
|comment_author_email_*||persistent||1 year||Saves the input of the 'email' field in comment forms.|
|comment_author_url_*||persistent||1 year||Saves the input of the 'website' field in comment forms.|
|viewed_cookie_policy||persistent||1 year||The plugin 'Cookie Law Info' saves whether you clicked to agree that you're aware of this website possibly setting cookies in your browser.|
- 2014-02-11: Added link to NFSN.net’s hosting policies
- 2014-03-11: The WP SlimStat traffic analysis plugin has been removed completely and all its accumulated data has been deleted in accordance with German jurisdiction. A passage about which data is gathered in server logs and by Bad Behavior has been added for clarification.
- 2014-03-24: Currently trying out AVH First Defense Against Spam as a replacement for Bad Behavior. Text changed accordingly.
- 2014-03-31: AVH FDAS queries the ZEN list of Spamhaus, not just SBL/XBL. Text changed accordingly.
- 2014-06-05: AVH FDAS removed, back to Bad Behavior. Text changed accordingly.
- 2014-12-04: Server log retention shortened to 1 week. Comments save IPs generally as 127.0.0.1.
- 2015-04-05: Additional information on cookies. Youtube and Twitter embeds set third-party cookies on this website.
- 2015-04-17: Bad Behavior makes it basically impossible to use caching plugins, so going back to AVH FDAS.
- 2015-05-08: Caching creates more problems than it solves for now; AVH FDAS in addition proved rather toothless in keeping bad bots out, so yet again back to Bad Behavior. Improved wording in places.
- 2015-12-06: Removed third-party cookies from cookie list and replaced it with a general disclaimer that embedded content may set cookies in a user’s browser.
- 2016-01-31: Added statement on the dictionary logging queries with zero results.
- 2016-03-09: Added warning about embedded content from third-party websites potentially gathering user data.
- 2017-03-02: Exchanged Project Honeypot DNSBL for cloud-based solution from Cleantalk.
- 2017-11-09: No Bad Behavior plugin anymore because it put users’ IPs in pages which were then cached, so others could see those IPs. Also, the server logs can’t be fitted to German privacy requirements, which means no logging.
- 2018-01-08: Logging reactivated (with anonymization routine in place) due to bad bots. Updated Logging and Cookies sections.
- 2018-05-07: Notice on right to information and deletion regarding privacy. Clarification that this website runs on American servers.
- 2018-09-12: No statistics on page views anymore.
- 2019-07-29: Cleantalk DB is mirrored locally. No third-party content is loaded dynamically anymore for front-end users.