Runko Works

Legal

Privacy policy

Last updated 4 October 2026.

This site is built to collect as little as possible. It sets no cookies, runs no analytics or tracking, loads nothing from third parties and keeps no access logs. The one thing on it that processes more is the chat assistants: one you can open on every page, and the ones in the live demos on the Demos page. They have their own section below, and so do the comments under blog articles.

Controller

Andrei Dmitrov. Email: andrei@runkoworks.com.

Hosting

The site is a set of static files served from a server of Amazon Web Services EMEA SARL in the Frankfurt region (Germany). To deliver a page, your browser necessarily sends the server your IP address and the usual request data (requested address, browser type, time). This data is used only to deliver the page and is not stored in access logs. Amazon Web Services acts as a processor under a data processing agreement. Legal basis: Art. 6(1)(f) GDPR, the legitimate interest in operating a website.

Fonts and other resources

Fonts, images and scripts are delivered from this server. The assistants' script comes from chat.runkoworks.com, which is the same server under another name. No requests are made to Google Fonts, content delivery networks or other third parties when you view the site.

Cookies, analytics and tracking

None. The site sets no cookies and uses no analytics, tracking pixels or advertising tools. The assistants use your browser's local storage, but only once you click one of them (see below).

Chat assistants: “Ask about my work” and the live demos

The button in the corner of every page opens an AI assistant that answers questions about my work, experience and projects from what is published on this site. It is an AI, not me, and the chat says so. It runs on an AI assistant platform that I built and operate myself, on the same server in Frankfurt as this site.

The live demos on the Demos page are further AI assistants on the same platform. One plays the service agent of a made-up machine maker and works through a fault you describe; another answers questions about the internal documents of a made-up company; a third advises on a made-up product catalogue; a fourth qualifies enquiries for a made-up estate agency; a fifth compares made-up CVs with a made-up vacancy; a sixth checks the offers of made-up contractors against the requirements of a made-up project. Everything below applies to them as well. If you go as far as a service case in the service demo, it stores what you told it as a ticket, and a remote appointment as a booking. The estate-agency demo books a viewing the same way and saves the name and the email address or phone number you give it, but only after you agree to be contacted. The product advisor keeps its rough price calculation with the conversation. All of this is on the platform. The companies, the machines, the properties and the documents are invented, so made-up contact details are fine; please do not enter real personal data you do not want me to see.

The CV demo lets you paste or attach a CV and a vacancy of your own. A file you attach (a PDF, a Word document or a text file) is stored with the conversation on the platform, and its text is sent to the AI model like any other message. Use only a CV you are allowed to share: your own, a sample, or one with the name and contact details removed, and never the CV of a real applicant without their knowledge. The demo only compares the text with the vacancy; it makes no decision about anyone, and it does not use age, gender, nationality, family status or a photo. A file is deleted together with its conversation.

The offer demo lets you paste requirements and an offer of your own: paste only made-up or anonymised text, nothing confidential and nothing covered by a non-disclosure agreement, because that text, too, is sent to the AI model. The demo only compares the two texts; it makes no decision about any bidder.

When the page loads

Your browser loads the assistant's script and its settings (button text, colours) from chat.runkoworks.com. This sends the server the same connection data as any page request. Nothing is stored in your browser and no conversation is started until you open the chat.

A few seconds later a short greeting appears next to the button. If you close it or open the chat, your browser remembers only that (an entry that holds no identifier), so the greeting does not come back on every page.

When you chat

The platform processes your messages, the page on which you opened the chat, the page you came from and campaign parameters in the address (utm_…), if there are any, and whatever you choose to tell the assistant, such as your name, company, the role you are hiring for or your email address. The assistant asks for contact details only if you want me to get back to you, and passes them to me only with your consent.

To keep the conversation across pages and visits, the chat stores a visitor ID, the conversation ID and a session token in your browser's local storage, in entries whose names begin withcw_, kept separately for each assistant. This is strictly necessary for the service you asked for (§ 25(2) no. 2 TDDDG). No cookies are set. If you delete these entries in your browser, the next chat starts afresh.

Where conversations are stored

In the platform's database on the same server of Amazon Web Services in the Frankfurt region; in the demos, tickets, bookings, contact details and price calculations are kept there too. Connections are encrypted (TLS). The database is backed up daily, and backups are kept for 30 days. Technical records of how each answer was produced (searches, tool calls) are deleted after 30 days. Your IP address is not stored with the conversation or in access logs; it is used for about a minute to limit the rate of requests.

The AI model

To write each answer, the conversation is sent to the Claude language model of Anthropic PBC (USA). To search the site's content (and the demos' documents), the assistant's search query, a short text derived from your question, is converted into a vector by OpenAI, L.L.C. (USA). Both receive the data only to produce the answer. Under the API terms that apply to me, content sent through their APIs is not used to train their models.

These are transfers to a country outside the EU. They are based on the European Commission's standard contractual clauses (Art. 46(2)(c) GDPR) and, where the provider is certified, on the EU–US Data Privacy Framework (Art. 45 GDPR).

The assistant makes no decisions about you (Art. 22 GDPR). It answers questions and passes conversations to me; anything beyond that I decide myself.

When a conversation is passed to me

If you ask to talk to me, or leave your contact and agree to be contacted, the assistant passes the conversation on. I then get a notification in Telegram with the reason and a short summary of the conversation, including any contact details you left, so that I see it quickly. The provider is Telegram FZ-LLC, Dubai (United Arab Emirates). I read the conversation and answer personally: in the chat if I am online, otherwise at the contact you left. In the service and the estate-agency demos, a handover reaches me the same way.

Service providers

All of them act as processors under data processing agreements.

Legal basis and how long conversations are kept

Art. 6(1)(b) GDPR where the conversation concerns a role, a project or another contract you are considering; otherwise Art. 6(1)(f) GDPR, the legitimate interest in answering questions about my work and in showing how the demos work. Passing your contact details to me: your consent, Art. 6(1)(a) GDPR, which you can withdraw at any time.

I keep a conversation for as long as I need it to answer you and follow up, and delete it after that or at any time on request. Deleting irreversibly anonymizes the messages and contact details and removes the conversation from the assistant's context. Deleted data remains in the encrypted backups for at most 30 days.

Comments and reactions under articles

Under each blog article you can react to it and leave a comment. Both run on this site's own small service; no third-party comment system is loaded.

Reactions. When you press a reaction for the first time, the browser creates a random identifier and keeps it in its local storage (not a cookie; it leaves your device only together with your reactions). It exists so that pressing the same reaction again removes it. The service stores only a keyed hash of that identifier together with the article and the reaction. Clearing the site's data in your browser removes the identifier; the reaction then stays as an anonymous count. Nothing is created for someone who only reads.

Comments. You are asked for a name and the comment; no email address, no account. A new comment is not public at once: I read it first and either publish it or not. For that I get a notification in Telegram with your name and the text; the provider is Telegram FZ-LLC, Dubai (United Arab Emirates). A published comment shows your name, the text and the date. To limit abuse, a keyed hash of the sending address is kept for 7 days; the address itself is not stored.

Where it is kept. In the site's own database on the same server of Amazon Web Services in the Frankfurt region, separate from the assistant platform. Connections are encrypted (TLS). The database is backed up daily; backups are encrypted and kept for 30 days.

Legal basis and retention. Art. 6(1)(f) GDPR, the legitimate interest in a discussion under my articles that you choose to take part in. A published comment stays until you ask me to remove it or I remove it; a reaction until you take it back; the address hash for 7 days. To have a comment removed, write to the email address above and name the article and the name you commented under.

Contact by email

If you write to me, I process your email address, your name and the content of your message to answer it and, where relevant, to prepare or carry out a project together. Legal basis: Art. 6(1)(b) GDPR where the message concerns a contract, otherwise Art. 6(1)(f) GDPR. Messages are deleted when they are no longer needed for that purpose, unless statutory retention periods apply.

Email to this address is received through Amazon Simple Email Service (Amazon SES), operated by Amazon Web Services EMEA SARL in the Frankfurt region (Germany), and forwarded to the mailbox in which I read and answer it, a Gmail account of Google Ireland Limited. Google may also process the data in the USA.

Links to other sites

Links to LinkedIn and other sites are plain links. Nothing is sent to those sites until you click one; from then on, their own privacy policies apply.

Your rights

You have the right to access your personal data, to have it corrected or deleted, to restrict its processing, to data portability, and to object to processing based on Art. 6(1)(f) GDPR. To use any of these rights, write to the email address above. To have a chat deleted, tell me roughly when it took place and what it was about, so I can find it.

You also have the right to lodge a complaint with a supervisory authority, for example the Bavarian State Office for Data Protection Supervision (Bayerisches Landesamt für Datenschutzaufsicht, BayLDA).