Privacy Notice
bktus.com and its subdomains
1. About this notice
bktus.com is the personal, non-commercial domain of the person named in Section 2. This notice explains what personal data is processed when you visit its websites or use its Matrix homeserver, and gives the information required by Art. 13 of the EU General Data Protection Regulation (GDPR). It covers:
- bktus.com, this site, and www.bktus.com, which only redirects here;
- blog.bktus.com, the blog;
- git.bktus.com, a read-only web view of Git repositories, which can also be cloned from there;
- ftp.bktus.com, a file archive for downloads;
- img.bktus.com, an image host;
- microbin.bktus.com, which serves texts and files that the operator shares by link;
- the Matrix homeserver for bktus.com.
The GpgFrontend website (gpgfrontend.bktus.com) and the GpgFrontend update servers have their own privacy policy.
2. Controller
The controller for the processing described in this notice is:
- Name
- Yu Hu ("saturneric")
- privacy@bktus.com
- Address
- see https://bktus.com/impressum/
This notice calls this person "the operator".
3. Summary
- None of these sites uses analytics, tracking, advertising, or social media plugins, and none loads content from other hosts.
- There are no user accounts, apart from accounts on the Matrix homeserver, which exist only for the operator and people the operator invited.
- The blog, git.bktus.com, and microbin.bktus.com set one cookie from Cloudflare's bot detection. git.bktus.com sets its own check cookies as well (Section 5). bktus.com and ftp.bktus.com set no cookies.
- On the operator's own server, request logs are kept for at most 7 days.
- You have the rights listed in Section 9.
4. Sites served by Cloudflare
- Sites: blog.bktus.com, a static blog; img.bktus.com, an image host; and www.bktus.com, which only redirects to bktus.com. They are hosted with Cloudflare, Inc. Requests to git.bktus.com and microbin.bktus.com also pass through Cloudflare on their way to the operator's own server (Section 5).
- Data processed: your IP address; the time of the request; the page or file requested; and the headers your browser sends, such as User-Agent, language, and referrer.
- Cookie: Cloudflare's bot detection adds a small script to a page when your browser does not yet hold its cookie, and then sets one cookie, cf_clearance. According to Cloudflare, the script checks signals in your browser; it sends the result to Cloudflare in a request to the site, under /cdn-cgi/challenge-platform/. The cookie serves to tell browsers from automated traffic, to protect the sites against abuse. It is valid for all of .bktus.com, so your browser also sends it to the hosts on the operator's own server (Section 5), which do not read it. It expires one year after it is set. Cloudflare sets and reads it; the operator does not read it and does not use it to identify or track visitors. You can delete or block the cookie in your browser; the sites still work, and while the cookie is blocked the check runs again on each page. The same cookie is set when Cloudflare's attack protection challenges a request. See Cloudflare's cookie list.
- What the blog does not do: no comments, no analytics or tracking, no advertising, no forms that send data (the search runs in your browser, on an index loaded from the blog), no other cookies, and no content loaded from third-party hosts. If you use its theme switch, your choice is saved in your browser's local storage and is not sent anywhere.
- Purpose: to deliver the pages and files, to keep the sites available and secure, and to protect them against automated abuse.
- Legal basis: Art. 6(1)(f) GDPR. The legitimate interest is publishing these sites and operating them securely. The script and the cookie are stored on and read from your device because this is strictly necessary to provide the sites securely, and the theme setting because you asked for it (§ 25(2) no. 2 TDDDG).
- Recipient: Cloudflare, Inc., as hosting provider (see Section 8).
- Retention: the operator stores no request logs for these sites. Cloudflare shows the operator aggregated statistics, such as request counts, and, for up to 31 days, a sample of individual requests that includes IP addresses (Cloudflare security analytics). The operator does not use this data to identify visitors. For how long Cloudflare itself keeps request data, see Section 8.
5. Sites on the operator’s server
- Sites: bktus.com, ftp.bktus.com, git.bktus.com, and microbin.bktus.com. They run on the operator's own server, hosted by Hetzner Online GmbH in Germany (see Section 8). bktus.com and ftp.bktus.com are reached directly. Requests to git.bktus.com and microbin.bktus.com first pass through Cloudflare (Section 4), which passes your IP address on to the server.
- Data processed: your IP address; the time of the request; the address requested; and the headers your browser or Git client sends, such as User-Agent, language, and referrer.
- Logs: the server records requests in logs, with the IP address, the time, the request, the response, and for some services the User-Agent, language, and referrer. These logs are deleted after at most 7 days.
- Cookies on bktus.com and ftp.bktus.com: none. If you use the theme switch on bktus.com, your choice is saved in your browser's local storage and is not sent anywhere.
- microbin.bktus.com: visitors can only read what the operator shares there. Its forms for uploading and for the admin area are for the operator and need the operator's password. It sets no cookies of its own; the cf_clearance cookie from Section 4 applies.
- Cookies on git.bktus.com: before showing a page, git.bktus.com runs a bot check called Anubis in front of the Git pages, which protects the server from automated mass downloads. Your browser receives a script that solves a small computing task. The check sets two cookies, which are valid for git.bktus.com only and are needed to pass it. The first, whose name begins with techaro.lol-anubis-cookie-verification-, is set while the check runs and expires after 30 minutes. The second, whose name begins with techaro.lol-anubis-auth-, is set after a successful check and expires after 7 days; it records that you passed, so that the check does not repeat on every page. To recognise search engine crawlers, Anubis may look up the requesting IP address in DNS. When you clone a repository over HTTPS, the server also sets a session cookie, i_like_gitea, which is not used to identify you. The cf_clearance cookie from Section 4 applies as well.
- Purpose: to deliver the pages and files, to keep the server available and secure, to protect it against automated abuse, and to find errors.
- Legal basis: Art. 6(1)(f) GDPR. The legitimate interest is publishing these sites and operating them securely. The Anubis script and cookies, the session cookie, and the theme setting are stored on and read from your device because this is strictly necessary to provide the sites securely or for a function you asked for (§ 25(2) no. 2 TDDDG).
- Recipients: Hetzner Online GmbH, as hosting provider (see Section 8). For git.bktus.com and microbin.bktus.com, also Cloudflare, Inc. (see Sections 4 and 8).
- Retention: at most 7 days, as stated above. These logs are not included in backups.
6. Matrix homeserver
The operator runs a Matrix homeserver for instant messaging, for the domain bktus.com. Accounts exist only for the operator and people the operator invited: a new account needs an invitation token. This section applies to those users.
- Data processed: your Matrix user ID; your display name and avatar, if set; your password in hashed form; your devices and sessions, with the IP addresses and User-Agents your apps connect from; the rooms you join; and the messages, files, and images you send. Messages in encrypted rooms are stored in encrypted form. Media from other servers that you view is kept in a cache.
- Federation: Matrix is federated. When you take part in a room that has members on other servers, your messages, files, user ID, display name, avatar, and room membership are sent to those servers, which store them under the control of their own operators. The operator cannot delete data from other servers.
- Push notifications: if your app has turned on push notifications, the server sends notification data to the push service of that app. For the Element apps, this is the push gateway at matrix.org. In rooms without encryption, this data can include the sender and the text of a message.
- Purpose: to provide your account and to deliver your messages. Connection data also serves to keep the service secure.
- Legal basis: Art. 6(1)(b) GDPR, providing the service you asked for. For connection data kept for security, Art. 6(1)(f) GDPR.
- Recipients: Hetzner Online GmbH, as hosting provider (see Section 8); the servers of other people in your federated rooms, and the push service of your app, as independent controllers.
- Retention: account data is kept until your account is deleted. The list of recent IP addresses and User-Agents is kept for 28 days. The last IP address and User-Agent of each device are kept until you sign that device out. Messages, files, and images have no fixed deletion period; they are kept until they are deleted.
- Backups: the homeserver's database is included in daily backups, stored with Hetzner Online GmbH in Germany. Backups are thinned out over time; the oldest is kept for about three months.
7. Contacting the operator
If you contact the operator by e-mail or post, the operator processes your e-mail address, your name and postal address if given, and the content of your message.
- Purpose: to answer your request.
- Legal basis: Art. 6(1)(f) GDPR (legitimate interest in answering inquiries), or Art. 6(1)(c) GDPR where your request concerns your data protection rights.
- Recipient: the operator's e-mail provider, mailbox.org (Heinlein Hosting GmbH, Berlin, Germany), which stores the mail on servers in Germany as a processor under Art. 28 GDPR. Postal mail is received, opened, and scanned on the operator's behalf by Postflex GmbH (Greven, Germany) under a data processing agreement pursuant to Art. 28 GDPR.
- Retention: deleted once your request is fully settled, unless a legal obligation requires longer storage. Correspondence about data protection rights is kept for up to three years after it is settled, so that the operator can show the request was handled properly (Art. 5(2) and Art. 6(1)(f) GDPR).
8. Hosting and international transfers
blog.bktus.com, img.bktus.com, and www.bktus.com are hosted with Cloudflare, Inc. (101 Townsend St., San Francisco, CA 94107, USA), and requests to git.bktus.com and microbin.bktus.com pass through Cloudflare's network. Cloudflare processes request data, such as IP addresses, on behalf of the operator to deliver the sites and to protect them against abuse, under a data processing agreement pursuant to Art. 28 GDPR. Cloudflare states no fixed period for this data: it keeps personal data for as long as the purposes named in its privacy policy, or legal obligations, require (Section 11 of the policy linked below). The sampled request records it shows the operator are kept for up to 31 days.
Because Cloudflare is a US company and operates a global network, this data may be processed outside the European Economic Area. Such transfers are based on the EU-US Data Privacy Framework, under which Cloudflare is certified (adequacy decision, Art. 45 GDPR), and on the standard contractual clauses in that agreement (Art. 46(2)(c) GDPR). See Cloudflare's privacy policy. The data processing agreement, including the standard contractual clauses, is available at cloudflare.com/dpa.
The operator's own server (Sections 5 and 6) and its backups are hosted by Hetzner Online GmbH (Gunzenhausen, Germany) in Germany, under a data processing agreement pursuant to Art. 28 GDPR. Data on that server is not transferred outside the European Economic Area, except as described for Cloudflare above and for Matrix federation and push notifications in Section 6.
9. Your rights
Under the GDPR, you have the right to:
- access the personal data concerning you (Art. 15);
- have inaccurate data corrected (Art. 16);
- have your data deleted (Art. 17);
- restrict its processing (Art. 18);
- receive your data in a portable format, where this right applies (Art. 20);
- lodge a complaint with a supervisory authority (Art. 77), in particular in the EU member state of your habitual residence, your place of work, or the place of the alleged infringement.
Right to object (Art. 21 GDPR): where processing is based on Art. 6(1)(f) GDPR, you have the right to object to it at any time on grounds relating to your particular situation.
To exercise these rights, contact the operator (Section 2). For visitors of the websites, the operator keeps nothing beyond the short-lived logs described above, so in most cases there is no stored data to provide or delete. Matrix users can ask for a copy of their account data or for their account to be deleted.
You are not required by law or by contract to provide any personal data. Without the connection data described above, the sites cannot be delivered to you.
No automated decision-making, including profiling (Art. 22 GDPR), takes place.
10. Changes to this notice
If the processing described here changes, this notice will be updated, and the effective date at the top will change.