Version 3.21 · in force since 16 November 2026
This policy describes which personal data are processed when the website www.lukaswojcik.com is used, on what legal basis this happens, how long the data are kept and which rights the persons concerned have. It follows Regulation (EU) 2016/679 (GDPR) and the Polish Act on the Protection of Personal Data of 10 May 2018.
1. Controller
The controller within the meaning of Art. 4(7) GDPR is:
LW IT Solutions Company Lukas Wójcik
al. Tadeusza Kościuszki 80/82, lok. 301
90-437 Łódź, Poland
NIP: PL7252266190 · REGON: 369859995
E-mail: contact@lukaswojcik.com
A data protection officer has not been appointed, because none of the conditions of Art. 37(1) GDPR applies to an operation of this size. All matters concerning data protection are handled directly at the address above.
2. What shapes this website
Three decisions determine how little data this site actually needs, and they are worth stating before the individual processing operations are listed.
- The infrastructure is self-operated. The web server runs on hardware belonging to the controller, connected through a local access provider in Łódź, Poland. There is no external hosting provider, no content delivery network and no reverse proxy in front of it. Requests reach the controller’s own machine directly, which means no third party sees the traffic before it is answered.
- Nothing is loaded from third parties without need. Fonts, stylesheets and images are delivered from the site’s own domain, and the comments do without pictures from an external avatar service. Without consent, the only thing loaded from an external server is the spam protection reCAPTCHA described in section 8.1, together with our own form protection formconfirmed from formconfirmed.com (section 8.2). A Content Security Policy restricts, at browser level, which external origins may be contacted at all.
- Everything that is not strictly necessary is blocked until consent exists. Analytics scripts are held back by the consent management platform and are only released after an explicit decision. Refusing has no effect on the usability of the site.
3. Server log files
Every retrieval of a file from this website is recorded by the web server in a log file. This happens automatically and cannot be switched off, because without it a server cannot be operated securely. The following data are recorded:
- the IP address of the requesting device
- date and time of the request
- the path and name of the retrieved file
- the HTTP status code and the volume of data transferred
- the referring page, if the browser transmits one
- the browser identification string (user agent)
Purpose and legal basis: the logs serve to deliver the site, to detect and trace attacks, and to diagnose technical faults. The legal basis is Art. 6(1)(f) GDPR. The legitimate interest lies in the secure and stable operation of the server.
Storage period: log files are rotated daily and deleted automatically after 14 days. They are not merged with other data sources and are not used to build profiles.
4. Cookies and local storage
This site works without advertising cookies and without cross-site tracking. What this website stores locally is limited to the following; in addition there are the cookies which reCAPTCHA sets under the domain google.com (section 8.1):
| Name | Type | Purpose | Duration |
|---|---|---|---|
pll_language | Cookie | Retains the chosen blog language (English, German, Polish) | 1 year |
lw-theme | Local storage | Retains the choice between light view, dark view and system default | Until deleted in the browser |
lw-tools-v1 | Local storage | Keeps the tools saved with the star (their numbers only) for the saved list in the toolbox; created only when the star is clicked, an empty list is deleted | Until deleted in the browser |
| Consent record of the consent management platform | Cookie / local storage | Retains which categories were accepted or refused, so that the banner is not shown again on every page | Up to 12 months |
comment_author_* | Cookie | Set only if the box for saving them is ticked when a comment is submitted; on the next visit the name, e-mail address and website are then pre-filled, and the visitor’s own comment that is still awaiting approval is visible | 1 year |
wordpress_test_cookie | Cookie | Set only when the blog’s login page is opened, to check whether the browser accepts cookies; reading and commenting do not create it | Session |
_grecaptcha | Local Storage | Token of the spam protection reCAPTCHA, see section 8.1 – created on pages with a form when the page loads, on tool pages only when a check is started | Until deleted in the browser |
_ga, _ga_* | Cookie | Google Analytics 4 – only set after consent, see section 6 | Up to 2 years |
rc_conv, rc_seen, rc_tab, rc_theme, rc_locale_wahl, rc_dnd, rc_dnt and further entries beginning with rc_ | Local storage / session storage | Chat, see section 6.2: the current conversation, messages already received, the view and language of the window, the wish not to be addressed again – without consent none of this is created | Conversation 24 hours, settings up to 1 year |
rc_ai_k:… | Session storage | Smart Answer, see section 10.5: settings of the search, no search terms and no answers – not created without consent to the chat | 5 minutes, at the latest until the tab is closed |
mp_visitor_id | Local storage | MousePlayer: random identifier making repeat visits from the same browser distinguishable – only after consent, see section 7 | Until withdrawal or until browser data are cleared |
mp_session_data | Local storage | MousePlayer: identifier of the current visit together with its origin, so that paths across several pages are held together | 30 minutes without activity |
mp_pv_count_* | Local storage | MousePlayer: counter of page views within a visit | As the session |
mp_tab_id | Session storage | MousePlayer: tells apart several open tabs of the same session | Until the tab is closed |
Legal basis: for the language cookie, the display preference, the saved-tools list and the comment cookies, Art. 6(1)(f) GDPR together with the Polish Electronic Communications Law (Prawo komunikacji elektronicznej) – these entries are technically necessary for a function that was actively requested. For all analytics cookies, Art. 6(1)(a) GDPR, that is consent.
Stored cookies can be deleted at any time in the browser settings, and their storage can be prevented there in general. Blocking all cookies may cause the language selection and the display preference to be forgotten between visits.
5. Consent management
Consent for non-essential scripts is obtained and documented through the consent management platform Consented (consented.eu). That platform is another product of the controller named in section 1 and runs on the same self-operated infrastructure in Poland; loading it means the browser contacts the domain consented.eu, which is under the same operator and is not a third party. Its script runs before all other scripts and blocks the services listed in sections 6 and 7, as well as the Google sign-in of the tools in section 10.3, until a decision has been made.
When the banner is used, the decision is recorded on the controller’s own server so that the consent can be demonstrated later, as required by Art. 7(1) GDPR. The record contains:
- the decision itself, in the form
acceptedorrejected - the IP address at the moment of the decision
- the browser identification string, shortened to 255 characters
- the timestamp of the decision
Legal basis: Art. 6(1)(c) GDPR, since Art. 7(1) GDPR obliges the controller to be able to demonstrate consent. Storage period: for the duration of the consent and for a further three years afterwards, which corresponds to the general limitation period under Polish civil law.
A decision once made can be changed at any time through the cookie symbol at the lower edge of the page. Withdrawal takes effect for the future and does not affect the lawfulness of the processing carried out until then.
6. Services that load only after consent
Three services stay held back until the consent management platform described in section 5 releases them: audience measurement with Google Analytics 4, the chat, and the Stats4U visitor counter. The session recording in section 7 follows the same rule, as does Google’s sign-in script for the tools in section 10.3.
6.1 Web analytics with Google Tag Manager and Google Analytics 4
2026-11-16
GTM loads only after Analytics consent in the applicable consent manager. Google receives the IP address and technical request data. Its purpose is technical management of website tags; the legal basis is Article 6(1)(a) GDPR. A local pageView event is written to the dataLayer on page loads and URL changes within the application. GTM itself does not set analytics cookies. Google signals for analytics and advertising storage initially use denied.
Google Analytics 4 (GA4) is configured through GTM and, where enabled, analyses usage: pages and events, referral sources, browser/device information and pseudonymous identifiers. Analytics cookies (_ga and _ga_*) require consent (Article 6(1)(a) GDPR; Article 5(3) of Directive 2002/58/EC). Their default lifetime is two years; browsers or project settings may shorten it. Retention within GA4 depends on the project configuration. Choices and withdrawal are managed in the consent settings.
Recipients may also include Google LLC and subprocessors in the USA. International transfers are subject to Google’s data processing terms and the safeguards provided there, in particular standard contractual clauses. The Google information linked below explains processing, cookies and transfers.
Google Ireland Limited · Gordon House, Barrow Street, Dublin 4, Ireland.
6.2 Chat
A chat window is available on every page. Behind it stands Reactive Chat, another product of the controller named in section 1; it runs on the same self-operated infrastructure, and no external provider is involved. The window is loaded via the domain chat.lukaswojcik.com, which also carries the exchange over a WebSocket connection; this server of the controller passes both on to reactive.chat. Both domains are under the same operator.
Already when the page loads: where consent exists, the window opens the connection immediately, not only when it is opened. What is transmitted then: the address and title of the page, the referring page, the browser language, the time zone, window and screen dimensions, whether the device is a mobile one, and campaign identifiers from the address such as utm_source or gclid. The server sees the IP address of the connection and the browser identification string; the IP address is not stored.
A conversation: what is stored are the messages with their time and direction, a session and a visitor identifier, the browser identification string, and the page on which the conversation began. Name and e-mail address are not asked for. Recognised e-mail addresses, phone numbers and card, tax and bank account numbers are replaced before storage – in the browser, and once more on the server.
The text of the page: when the window is opened, it reports the visible text of the page to the server, so that a question about that page can be answered; there it is stored. Form fields are left out entirely, and the result containers of the tools described in section 10 are marked as private – their content does not go along.
Answers from a language model: part of the answers is produced by a language model. It runs on the controller’s own machines in the local network; nothing goes to a provider of AI services or to a third country. The model receives the cleaned question, the conversation so far, extracts from a knowledge base of the site’s own pages, and the title and path of the page.
In the browser the chat stores entries under names beginning with rc_; they are listed in section 4. Without consent, none of them is created.
Legal basis: Art. 6(1)(a) GDPR and, for the storage on the device, the Polish Electronic Communications Law in addition. Without consent the window is not loaded; withdrawal through the cookie icon takes effect for the future.
Storage period: no fixed period has been set for conversations so far; they remain stored until deletion is requested. The chat window has a button of its own for that, which removes conversation, messages and session immediately and completely; an informal message to the address in section 1 is equally sufficient. As soon as a period is set, it will be stated here.
6.3 Visitor counter (Stats4U)
This website uses the Stats4U visitor counter (stats4u.net, LW IT Solutions Company, Łódź, Poland). Only after your consent, when a page is opened, does your browser load a counter image from stats4u.net and, as a technical necessity, transmit its IP address, the browser identification and the address of the page being viewed.
The IP address is used to determine country and city approximately and to build a daily hash, which counts a visitor only once per day. It is not stored in the statistics. The daily hash is built with a secret salt that changes every day and is deleted after 2 days; after that it cannot be traced to anyone. The web server’s access log holds the IP address for up to 14 days.
The counter sets no cookies and reads nothing from your device. What is stored are daily totals: hits, visitors, country, browser, operating system, language, the pages of this website that were opened and the transitions between them, the domain of the referring page, events defined for this website, time on page, scroll depth, load time, and the entry and last page of a visit. They are kept for 400 days. Processing takes place in Poland; no data is transferred to third countries. For the duration of a visit there is additionally one row in the live list “who is on the site now”: country, city, the page currently open, browser, operating system, device type and language. It is deleted at the next nightly clean-up. While the page stays open the counter checks in about once a minute so that this row does not age prematurely; all it sends is the counter number, and nothing additional is stored.
The legal basis is your consent (Art. 6(1)(a) GDPR). Without consent the counter is not loaded and nothing is transmitted to stats4u.net. Consent can be withdrawn at any time with effect for the future through the cookie symbol at the lower edge of the page.
The statistics for this website are not publicly visible.
Stats4U privacy policy: https://www.stats4u.net/privacy
7. Session recording and heatmaps (MousePlayer)
This website uses MousePlayer, a tool for recording and analysing sessions, under the channel identifier 955a45df5ee842cb. It captures how visitors use the website and then presents the sequence as a replay and as a heatmap. This is reviewed in order to identify usability barriers, drop-offs and technical errors. A session may also be followed live while it is happening; no separate notice is given at the moment someone is watching.
Of everything described in this policy, this is the most far-reaching processing. It therefore gets the most detail.
7.1 Who operates it
MousePlayer is not a third-party service here. It is developed and operated by the controller named in section 1, on that controller’s own infrastructure. Provider and controller are the same legal person, which is why no processing agreement pursuant to Art. 28 GDPR exists for it and no recordings are handed to an external analytics provider. The one external element is the encrypted backup described in section 7.8.
7.2 Data processed
- Device and environment data: browser and version, operating system, device class, screen resolution and window size
- Behavioural data: mouse movement and pointer paths, clicks, scroll depth, timestamps of interactions
- Navigation and origin: pages and addresses opened, landing page, referring domain, campaign identifiers
- The structure of the pages displayed, used solely to replay the session
- A random identifier assigned in the browser to tell visits apart
- The country derived from the IP address
7.3 IP address
The full IP address exists only in memory, for as long as establishing the connection, determining the country and preventing abuse require it. It is truncated before anything is written to the database. A visitor’s full IP address is neither stored nor displayed in the analysis.
7.4 Form input
Every character of every form input is replaced in the browser before it is transmitted. A replay shows that someone typed and how long they took – not what. Fields identified as password or payment fields always stay fully obscured. This full masking is the setting in force for this website.
One limit deserves to be stated plainly: what the website itself displays – a confirmation page repeating an address that was entered, for instance – is part of the page and therefore part of the replay.
7.5 Legal basis
Consent pursuant to Art. 6(1)(a) GDPR; for storing information on the terminal device and accessing it, additionally the Polish Electronic Communications Law (Prawo komunikacji elektronicznej). Without consent the script assigns no identifier, stores nothing, opens no connection and records nothing. A Global Privacy Control signal sent by the browser is honoured and takes precedence over an approval.
7.6 Withdrawal
Consent can be withdrawn at any time with effect for the future, through the cookie symbol at the lower edge of the page. Withdrawal takes effect immediately: recording stops, the connection is closed, data not yet transmitted is discarded rather than sent, and the identifiers stored in the browser are deleted.
7.7 Retention
Recordings are deleted automatically after no more than 365 days. Records of the consent decision itself are kept longer; they contain no behavioural data, only the fact, time and source of the decision.
7.8 Place of processing and recipients
Processing takes place on the controller’s own servers in Łódź, Poland. The recording script transmits to that infrastructure only. For backup purposes, an encrypted copy of the database is stored daily with Google Drive (storage location USA/worldwide); encryption happens before the transfer and the keys do not leave the controller. Google therefore holds a container it cannot open.
7.9 Seeing and deleting what is stored
The browser identifier described above is the key to the recordings. MousePlayer keeps a self-service page on which that key can be used to see how many sessions are stored under it, what period they date from and on which websites they were created – and to request their deletion. The page deliberately does not display the recordings themselves: the identifier is a key without a password.
My stored data – the link carries the identifier of this browser with it, so nothing has to be typed in on arrival. Where no consent was given, no identifier exists and nothing was recorded; the link then simply leads to the general page.
(function () { // Der Aufruf haengt am Klick, nicht am Laden: mp.js wird asynchron und // erst hinter dem Einwilligungs-Riegel geladen, ist beim Ausfuehren // dieses Skripts also in aller Regel noch nicht da. Der feste Verweis // im href traegt jeden Fall, in dem nichts geladen wurde. var a = document.getElementById(‘mp-daten’); if (!a) { return; } a.addEventListener(‘click’, function () { var u = window.MousePlayer && MousePlayer.privacyUrl && MousePlayer.privacyUrl(); if (u) { this.href = u; } }); })();Independently of this, requests concerning recordings are answered at the address given in section 1, which is also the operator of MousePlayer. All rights set out in section 12 apply to them without restriction.
8. Contact form
The contact form on the start page and beneath the articles transmits the name entered, the e-mail address, the message text and the address of the page from which the form was sent. This last item makes it possible to see which article prompted the enquiry.
Purpose and legal basis: the data are processed solely in order to answer the enquiry. Where the enquiry concerns the initiation or performance of a separately concluded contract, the legal basis is Art. 6(1)(b) GDPR; in all other cases Art. 6(1)(f) GDPR, with the legitimate interest lying in answering the enquiries addressed to the controller.
Storage: submitted messages are stored in a database on the controller’s own server and are not passed on to anyone; for checking, the name, the e-mail address and the text go only to our own form protection formconfirmed (section 8.2), which does not store them in plain text. If formconfirmed has flagged a message, a note with the reasons precedes it.
So that a new enquiry is noticed promptly, a short push notification is sent through the messaging service Telegram. This notification deliberately carries no personal data. It contains the record number of the entry and the page from which the form was sent – and nothing else: neither the name, nor the e-mail address, nor a single word of the message. Reading an enquiry requires access to the database on the controller’s own server, so the content never leaves that machine.
Storage period: enquiries are deleted once the matter has been dealt with conclusively and no statutory retention obligation stands against deletion. Where an enquiry becomes part of business correspondence, the retention periods under Polish tax and accounting law apply, which normally amount to five years.
8.1 Protection against misuse with reCAPTCHA
The contact form, the comment form below the articles (section 9) and the Toolbox tools with a server component (section 10.2) are protected against automated use by reCAPTCHA v3, a service of Google Ireland Limited. The only exception is the Connection Mirror, which evaluates nothing but the incoming connection itself. reCAPTCHA analyses behaviour in the browser and returns a score between 0 and 1 which expresses how probable it is that a human is acting. Submissions and requests below a score of 0.5 are rejected. For the comment form, the server additionally checks that the token was issued for this form and for a page under lukaswojcik.com.
For this purpose reCAPTCHA processes the IP address, the duration of the stay on the page, mouse and keyboard movements, browser and device information, and it reads and sets cookies of the domain google.com. The check runs invisibly; no images have to be selected. On tool pages, reCAPTCHA is loaded only at the moment a check is started; merely opening a tool page does not include the service. For contact forms on the home page and below articles, reCAPTCHA loads only after interaction with an input field. For the comment form, the service loads only when someone starts writing in the comment field. Merely opening these pages does not load reCAPTCHA. On submission, a fresh token is requested for the corresponding form action. In doing so it creates the entry _grecaptcha in the browser’s local storage, which is listed in section 4. The server of this website has the score confirmed by Google and transmits only the token generated in the browser, not the IP address. The blog’s login page, which serves the controller alone, is protected by a reCAPTCHA checkbox from the same service; it loads only there, and here too the server sends Google nothing but the token.
Legal basis: Art. 6(1)(f) GDPR. The legitimate interest lies in protecting the forms and the tools from misuse: without such a check the contact route and the comments would become unusable within a short time, and the tools could be turned against third-party servers in automated fashion. Anyone who does not wish reCAPTCHA to run can reach the controller by e-mail without using a form, and can submit a comment the same way; the tools that run entirely in the browser work without reCAPTCHA.
8.2 Our own form protection (formconfirmed)
In addition to reCAPTCHA, formconfirmed checks the contact form, the comment form (section 9), the tools with a server component (section 10.2), the AI tools of the toolbox, the quiz and the form for feedback on the tools. formconfirmed is another product of the controller named in section 1 and runs on the controller’s own servers in Poland; no third parties are involved.
How it works: The script comes from formconfirmed.com. It is loaded only when such a form comes into view on the page or is clicked, and for the tools, the AI tools and the quiz only when a check is started; pages without such a form do not load it. It fetches a signed task, which the browser solves in the background (a proof of work), and passes the result to lukaswojcik.com with the request as a single-use token. In the process, the browser sends formconfirmed.com the address of the page, the IP address and the browser identifier; the token contains the task, its solution, points in time, whether a field invisible to humans was filled in, and two browser signals: whether the browser reports itself as automated (webdriver) and whether there were real inputs. The server of this website submits the token and the IP address to formconfirmed, and for the contact and comment forms also the name and e-mail address entered, the message or comment text and the content of the invisible field, and for all of these forms the value that reCAPTCHA (section 8.1) produced for the same request. formconfirmed uses them to check whether the submission comes from the same network range the task was issued for, whether the address belongs to a known data centre network and whether submissions from this range were recently rejected on other websites (reputation across several websites); for the name, whether it looks like a random string of characters; for the e-mail address only the domain, namely whether it belongs to a provider of disposable addresses and whether it accepts e-mail at all (a DNS query); and the text for typical spam patterns, for which a language model on the controller’s own computers may classify it. formconfirmed uses the reCAPTCHA value only to compare the two checks with each other; it does not change the result.
Storage: From the request for a task, formconfirmed stores the IP address only in truncated form (IPv4 without the last byte, IPv6 only the first 48 bits) and as a hash with a key that changes daily, in order to detect repeated requests, and deletes this value after about one hour. formconfirmed does not store the name, the e-mail address or the text in plain text: it checks the name and the text only in memory and, of the e-mail address, only the domain, whose result is cached for at most seven days. Campaign detection: From the message or comment text, the e-mail address and the domains of links it contains, formconfirmed creates fingerprints (encrypted hashes that cannot be turned back into the original; short texts under 40 characters or six words get none) and compares them for 30 days across all websites that use formconfirmed, in order to recognise the same spam message when it is sent to many websites. This includes reports from this and other websites that a message, a link or an address was spam. The name and the IP address are not part of this. The fingerprints are deleted after 30 days. Used tokens are deleted after about eleven minutes. Check results (action, score, reasons, domain of the website, the reCAPTCHA value sent along and, where applicable, the feedback “spam” or “not spam”, section 9) are kept for 30 days; the hash of the truncated address range (with a key that changes daily), which formconfirmed uses to recognise sources that stand out on several websites, is removed from them after at most one hour. As with every request, the web server log of formconfirmed.com records the full IP address and the browser identifier for 14 days. The form protection sets no cookies, stores nothing in the browser and creates no fingerprint of the device. The “Confirmed by formconfirmed” badge at the forms is an ordinary link and opens formconfirmed.com only when clicked.
Result: formconfirmed answers “allow”, “flag” or “block”. A flagged message from the contact form is delivered and marked as flagged, a flagged comment stays held back for review; a flagged request to an AI tool is accepted by the server only if reCAPTCHA (section 8.1) gives a score of at least 0.7. If the result is “block” or the token is missing although formconfirmed can be reached, the request is rejected; this also applies if only the browser cannot reach formconfirmed.com. If formconfirmed is down or cannot be reached by the server of this website, a message from the contact form is delivered and marked as flagged and a comment is held back for review; requests to the tools, the AI tools and the quiz as well as feedback are rejected during this time and can be sent again later. A rejected message can be sent by e-mail instead (section 14).
Legal basis: Art. 6(1)(f) GDPR; the legitimate interest is the same protection against misuse as in section 8.1 and, for campaign detection, also the joint defence against spam that is sent to many websites. You can object to this processing at any time under Art. 21 GDPR. In the browser, the form protection processes only what is technically necessary to send the form being used (Art. 5(3) of Directive 2002/58/EC and the Polish Electronic Communications Law, Prawo komunikacji elektronicznej); it is therefore not controlled through the consent management platform (section 5). No data are transferred to a third country.
9. Comments on blog articles
Articles in the blog can be commented on. When a comment is submitted, WordPress stores the name entered, the e-mail address entered, the comment text, the time of submission, the IP address and the browser identification string. The IP address and the e-mail address are not published; they serve to combat spam and to allow enquiries in case of legal objections to a comment.
Legal basis: Art. 6(1)(a) GDPR for publication of the comment together with the chosen name, and Art. 6(1)(f) GDPR for storing the IP address and for the spam checks, the legitimate interest lying in defence against abusive entries.
Storage period: comments and the associated data remain stored until the comment is deleted. Entries in the spam folder are moved to the trash after 30 days, and WordPress deletes them permanently from there after a further 30 days. Deletion can be requested informally at any time.
Spam protection: Before it is stored, a comment goes through four checks. A field invisible to humans catches form bots, reCAPTCHA and formconfirmed check as described in sections 8.1 and 8.2, and a keyword list on the site’s own server puts entries with typical spam content in the spam folder instead of the approval queue. Google receives only what reCAPTCHA records in the browser, and from the server only the token. The name, e-mail address, IP address and comment text go for checking only to our own form protection formconfirmed (section 8.2; it does not store the name, and stores the text and the e-mail address only as fingerprints for campaign detection); beyond that, the server passes the name, e-mail address, website, IP address and comment text to no one. A rejected entry is not stored. Every stored comment is held back and published only after review. With the comment, the website stores the identifier of the formconfirmed check result for as long as the comment exists; it contains no personal details. If the comment is approved or classified as spam, including by the keyword list, the server reports only “spam” or “not spam” to formconfirmed under this identifier within 30 days. This serves only to improve the check and does not change the decision about the comment.
So that a new comment is noticed promptly, a short notification goes out via the messaging service Telegram as soon as it is awaiting approval. It contains only the number of the comment and the address of the article, no personal data: neither the name nor the e-mail address nor the comment text.
10. The Toolbox
The Toolbox contains a collection of technical tools – calculators, generators, validators and analysers. Most of them run entirely in the browser (section 10.1). Some check things that cannot be checked in the browser and for that purpose send the input to the server of this website (section 10.2). These tools state on their page what the server does with the input.
The session recording described in section 7 captures the displayed page and would otherwise make readable a result that is meant only for the person in front of the screen. The containers in which the tools display their results are therefore marked in the markup as areas to be masked – regardless of whether the result was produced in the browser or on the server. Before anything is transmitted, the recording replaces their content character by character. The same marking applies to the chat in section 6.2: its reading of the page text skips these containers. A replay shows that a result appeared and how much room it took – not what it said. Characters typed into a field are masked in any case.
How the search works, and when a search term is sent to the server in the process, is described in sections 10.4 and 10.5.
10.1 Tools that run in the browser
With these tools, values entered are processed in the browser and transmitted to no server. Anyone wishing to verify this can disconnect the network connection after the page has loaded, and these tools continue to work.
10.2 Tools with a server component
Some checks need a server: DNS queries, TLS handshakes, fetching a third-party page together with its headers, looking up a code in a music database. Tools of this kind (31 at the time of this version) send the input to the server of this website only after a click; the server runs the check and returns the result. What is processed is the input – depending on the tool, a domain, an address, an IP address, a DKIM selector, an ISRC, ISWC or barcode, or a Measurement Protocol payload – and the IP address of the requesting device.
Storage: the input is not stored, and neither is the result or any response from third-party services; both exist only in the answer sent to the browser. For each request, the only thing stored is a counter entry consisting of the IP address, the tool, the time and the size of the request in bytes. That size cannot be turned back into the input; it shows whether someone is using the tools on a mass scale or with unusually large payloads. The entry limits each tool to a fixed number of requests per IP address and hour (between 4 and 30, depending on the tool), so that it cannot be used against third-party servers on a mass scale. Counter entries are deleted after seven days; the deletion job runs every hour, so no entry exists in the database for longer than seven days and one hour. On backups, see section 15. The input does not appear in the log described in section 3 either: the tools send it in the body of the request, and the log records only the path.
Requests to third parties: to carry out a check, the server itself sends requests, under its own identification and from its own address. Depending on the tool, the input is received by:
- the servers of the domain or address entered, and in the mail transport check also its mail servers
- the public DNS resolvers of Cloudflare (1.1.1.1) and Google (8.8.8.8), through which this server resolves names
- rdap.org and the responsible registry, or for registries without RDAP their whois service, for the holder data of a domain or of an IP network
- crt.sh (Sectigo Limited) for the certificate logs of a domain
- MusicBrainz (MetaBrainz Foundation) for the ISRC, ISWC and barcode lookup
- the Google Analytics validation server for the GA4 Measurement Protocol JSON Validator, unless this check is deselected; placeholders are sent instead of access credentials, but the payload itself goes out as entered – including any real identifiers such as
client_idoruser_id
None of these recipients receives the IP address of the requesting device – except in the case of the Connection Mirror, where that very address is what the check is about: there it goes to the DNS resolvers for the host name and, after a click on the button for the network holder, to rdap.org and the responsible registry.
Connection Mirror: the tool shows what a web server learns about a connection before a single line of JavaScript runs: the IP address the request comes from, its address family, the request headers and the parameters of the encrypted connection. Every web server knows this IP address anyway, because it could not otherwise reply; the Mirror merely makes it visible. The host name is looked up by reverse DNS through the DNS resolvers named above. For a private address, that is skipped as well.
The network holder is recorded in the database of a Regional Internet Registry. For European addresses that is the RIPE NCC in Amsterdam, hence within the European Union; for other address ranges it is ARIN in the United States, APNIC in Australia, LACNIC in Uruguay or AFRINIC in Mauritius. Depending on where the address comes from, the query therefore reaches a country without an adequacy decision, and for that reason it does not happen by itself: at this point the tool shows a button and, next to it, a note saying where the address goes. Only a click on it triggers the query – through rdap.org, which forwards to the responsible registry. The click is at the same time the explicit consent under Art. 49(1)(a) GDPR, in so far as the responsible registry sits outside the European Union; with the RIPE NCC there is no third-country transfer at all. Without that click, the address leaves the server for the reverse DNS lookup only. Cookie values and authorisation data are never returned. Here too, only the counter entry is stored. The Crawler IP Verifier looks up the same details for the address someone enters there – not for that of the requesting device; what leaves the server is the address typed in.
Legal basis: Art. 6(1)(f) GDPR. The legitimate interest lies in carrying out the check that was actively requested and, as regards the counter entry with its size figure, in protecting the tools and third-party servers from mass automated use. Where a transfer to a country without an adequacy decision is involved, the explicit consent under Art. 49(1)(a) GDPR is added, as with the network holder in the Connection Mirror. The recipients and the basis are set out in section 11.
10.3 Tools with Google sign-in
Seven tools are an exception, because their purpose is to read data out of a Google account:
- GTM Container History Deep Search Engine – scope
tagmanager.readonly - GA4 PII Checker – scope
analytics.readonly - GA4 Anomaly Detector – scope
analytics.readonly - GA4 Bot Detector – scope
analytics.readonly - GA4 Advisor & runReport Verifier – scopes
analytics.readonly,analytics.chatbot.read - Acquisition Audit in the GA4 Channel Debugger – scope
analytics.readonly - GA4 Property Configuration & Snapshot Comparator – scope
analytics.readonly
These tools request a temporary access token through Google’s sign-in dialogue. The requested permissions are read-only in every case; none of these tools can change, create or delete anything in a Google account.
Consent before loading. The Google Identity Services sign-in script (accounts.google.com/gsi/client) loads only once the service “Google Identity Services” in the “Functional” category has been allowed in the consent management platform (section 5). Without that consent, a click on sign-in only shows a notice with a button to the settings; nothing is sent to Google. As soon as the script loads, Google receives the IP address and technical information about the browser; cookies the browser already holds for Google domains may be sent along. Consent can be withdrawn at any time via the cookie icon at the bottom of the page; a script that has already loaded remains in the tab until the page is left or reloaded. For this reason the consent management platform from section 5 also loads on the tool pages where tracking, session replay and chat are disabled; it transmits neither the tools’ inputs nor their results.
Limited Use disclosure. The use and transfer of information received from Google APIs by these tools adheres to the Google API Services User Data Policy, including its Limited Use requirements. In concrete terms: the access token and the retrieved data remain in the browser. They are not sent to the server of this website. The website operator does not retain them, disclose them to other recipients, use them for advertising or use them to train models. The direct processing by Google needed for API requests, including the Advisor chat described below, remains separate from this commitment. The token expires by itself and is gone at the latest when the browser tab is closed.
GA4 Advisor & runReport Verifier. Login loads after an explicit click and only with consent (see above). The browser sends the selected property, periods, metric and dimension as a question to Google’s Analytics Advisor and retrieves comparison reports directly from Google. Follow-up questions are also sent to Google. Access tokens, session identifiers and results stay in the tab’s memory; the tool uses no backend proxy, token cookies or persistent browser storage. Disconnecting clears the local token and results but does not revoke the permission in the Google account. Tracking, session replay and reactive.chat are disabled on this tool page. Normal page-access logs remain. An own OAuth client can be entered instead of the prefilled public client; this does not eliminate processing by Google. According to Google’s documentation, chat activity may be used to improve the product. The AI response can be inaccurate. This tool does not request the cloud-platform scope.
Legal basis: for loading Google Identity Services, Art. 6(1)(a) GDPR, that is consent; for storing information on the terminal device and accessing it, additionally the Polish Electronic Communications Law (Prawo komunikacji elektronicznej). For the subsequent sign-in and the queries, Art. 6(1)(f) GDPR, as for the other tools: the legitimate interest lies in providing the function that was actively requested. No contract arises in doing so, as section 2 of the Terms of Service states. The permission granted can be withdrawn at any time in the Google account settings at myaccount.google.com/permissions. For the transfer to Google LLC in the USA, see section 11.
Acquisition Audit and configuration snapshots. These two functions also use direct browser requests to Google with read-only authorization. The acquisition audit retrieves session acquisition reports; the configuration comparator retrieves a defined set of property settings, retention settings, streams, custom definitions and key events. Neither uses an AI service. Configuration snapshots can be downloaded as JSON and later compared locally without login. API secrets are not requested. Tracking, session replay and chat are disabled on these tool pages.
Local file comparison. The Shop vs. GA4 Revenue Reconciliation tool reads CSV files only in the browser, without uploading their contents or requesting Google access. It compares order IDs, amounts and currencies. Snapshot and CSV inputs remain in tab memory until cleared or the page is left; explicitly downloaded files remain on the device until deleted there. Tracking, session replay and chat are disabled on the reconciliation page. Normal website access logs are unaffected.
Local Collect request analysis. The GA4 Parameter Analyser processes pasted request URLs and query/body strings only in the tab. Requests are not replayed or uploaded. Tracking, session replay and chat are disabled on this tool page. Inputs and results are cleared when the page is left or the clear button is used; downloads remain on the device. CSV exports contain decoded input values and are not anonymized. Normal website access logs remain unchanged.
GA4 Anomaly Detector. Google login is loaded only after a click and only with consent (see above). Daily aggregate report values are retrieved directly from Google using analytics.readonly and compared in the browser. Tokens and results remain in tab memory and are cleared on disconnect, client change or leaving the page. CSV downloads remain on the device. Tracking, session replay and chat are disabled on this tool page; normal website access logs remain. No AI service or background alert delivery is used.
E-Commerce Item Array Validator: pasted product arrays are checked locally in the browser tab without a Google login or upload. The tool does not store the input or results in cookies or browser storage. Clearing the form or leaving the page clears these values; downloaded JSON reports remain on the device. Tracking, session recording and chat are disabled on this tool page. Normal server access logs still record page requests.
GA4 Bot Detector / traffic review: Google login loads only on click and only with consent (see above). Read-only reports pass directly between the browser and Google. Tokens and reports remain in tab memory; disconnecting, changing the client ID or leaving the page clears them. CSV downloads remain on the device. No bot classification is sent to Google, and no Analytics data is changed. Tracking, session recording and chat are disabled on these tool pages; normal server access logs remain.
10.4 Search across articles and tools
The search in the header of every page works in two stages. The keyword search runs entirely in the browser: it loads a list of all articles, tools and legal texts from this server once and matches the search term against it itself. The term does not leave the device in the process.
From three characters on, the search also sends the term to the server of this website while it is being typed, each time after a short pause in typing, so that pages that fit by content but use different words are found as well (semantic search). The server passes the term on to another computer of the controller in the same local network. The controller’s own embedding model, self-hosted and operated there, converts it into a series of numbers and compares it with the series precomputed for the pages. Only titles and addresses of matching pages go back to the browser. No third party receives the term.
The AI tool search at the top of the toolbox uses the same semantic search. There, the description of the task (2 to 200 characters) is sent to the server only after it is submitted or a suggestion is clicked, first to find matching tools and, if none fits, a second time to find matching articles. Processing and storage are the same as for the search in the page header; both share one counter. If the chat has been allowed, Smart Answer additionally answers the description from the content of this website (section 10.5).
Storage: The search term is not stored. During processing it is held only in working memory and deleted as soon as the answer is ready, at the latest after 30 seconds. It does not appear in a database, nor in the log described in section 3, because it is sent in the body of the request. As with the tools in section 10.2, the only thing stored per request is a counter entry consisting of the IP address, the identifier of the search, the time and the size of the request. It limits the search to 240 requests per IP address and hour and is deleted after seven days.
Legal basis: Art. 6(1)(f) GDPR. The legitimate interest lies in carrying out the requested search and, for the counter entry, in protecting the search against mass automated use.
10.5 AI answers in search (Smart Answer)
If the chat described in section 6.2 has been allowed in the consent banner, search adds a brief answer written by a language model to the results. For this, the browser loads a script from cdn.reactive.chat and, once, the settings of the search from chat.lukaswojcik.com. From three characters on, it sends the search term in encrypted form to chat.lukaswojcik.com as soon as typing pauses briefly (currently 0.6 seconds) or the search is submitted, regardless of whether the term is phrased as a question. Transmitted are the term (at most 300 characters), the selected language, the address and path of the current page and the address of the referring page, each without parameters or anchor, and the visitor identifier of the chat described in section 6.2 if the chat window has already been loaded. If a follow-up question is asked in the answer box itself, up to three previous questions of this box are sent along with their answers. No cookies are sent.
The same answer also appears in the AI tool search at the top of the toolbox (section 10.4), likewise only if the chat has been allowed. There, the description of the task is not sent while typing but only after it is submitted or a suggestion is clicked, from three characters on, to chat.lukaswojcik.com. What is transmitted, processed and stored is the same as for the search in the page header.
The answer is produced by Answely, like Reactive Chat a product of the controller named in section 1, running on the same self-operated server. Answely passes the request on to the chat server of Reactive Chat, which also receives the IP address for the duration of the request and does not store it. From there it goes to computers of the controller in its own network: the controller’s own embedding model, likewise self-hosted, looks for matching passages in the content of this website; from them the controller’s own AI, self-hosted on its own hardware, writes the answer, which is returned to the browser step by step. If one computer is busy, another of the controller’s own computers takes over. All models run on own hardware; no provider of AI services and no other third party receives the term or the answer. The references “Answely” and “reactive.chat” in the answer box are ordinary links and load nothing until clicked.
Storage: The term and the answer are not stored. They exist only in an in-memory database while being processed, for at most 180 seconds, and are deleted afterwards. This database writes a snapshot to the server’s disk at intervals, which is replaced by the next one; a request in progress may be contained in it until then. No chat history is created, and neither the term nor the answer appears in a table or a log. What is stored:
- per request a counter entry without content: time, shortened IP address (for IPv4 without the last byte, for IPv6 only the first 48 bits), identifier of the website, length of the term, result and duration. It serves to detect abusive numbers of requests and to troubleshoot, and is deleted after seven days;
- against mass requests a check value formed from the IP address and a secret that changes daily; it expires after two minutes, the secret after two days;
- per request a job record without content and without reference to a person: time, processing computer, model and identifier of the website, plus a monthly total of answers;
- the access logs: cdn.reactive.chat (retrieval of the script) and chat.lukaswojcik.com record each request with time, IP address, requested path, referring page and browser identifier, without term or answer, and are deleted after at most 15 days. The log of Answely holds only the shortened IP address, time and path without parameters and is deleted after seven days.
In the browser, the search keeps only its settings in session storage (sessionStorage) (entry rc_ai_k, see section 4). It is valid for five minutes and disappears at the latest when the tab is closed. No cookies are set.
If a follow-up question is sent to the chat, the displayed search question, the answer and up to three sources are carried over into a normal chat under section 6.2; the retention period described there then applies. A notice beside the answer explains this before sending. Until that step, the search remains transient.
Note: The answer is machine-generated and may contain errors. The linked articles are authoritative.
Legal basis: Art. 6(1)(f) GDPR. The legitimate interest lies in answering the question asked on the basis of the content of this website and, for the counter entry and the access logs, in protecting the service against mass automated use.
10.6 Feedback on the tools
Below the tools of the toolbox and the AI tools, a short note – for example about an error – can be sent using the feedback button. Stored are the text entered, the address of the tool page, the language, a random identifier created in the browser that prevents duplicate storage when a request is repeated, and the time. Name, e-mail address and IP address are neither requested nor stored; anyone who writes personal details into the text transmits them with it.
Protection against misuse: A field invisible to humans catches form bots, and the form protection formconfirmed checks every submission (section 8.2). Five feedback messages per IP address and hour are possible. For this, the server keeps a hash of the hour and the IP address, formed with a secret key, and deletes it after at most two hours; the IP address itself is not stored.
A short notification via the messaging service Telegram points to new feedback. It contains only the number of the entry and the name of the tool, not the text.
Legal basis and storage period: Art. 6(1)(f) GDPR; the legitimate interest lies in finding errors in the tools and improving them. Feedback is kept in the database on the site’s own server, is not passed on to anyone and is deleted once it is no longer needed. Deletion can be requested informally at any time.
11. Recipients of the data
Data are only passed on where this is necessary for the purposes described above. The recipients are:
| Recipient | Purpose | Location | Basis for transfer |
|---|---|---|---|
| Google Ireland Limited / Google LLC | Analytics, Tag Manager, reCAPTCHA for the contact form, the comment form and the tools, Google sign-in (after consent) and API access for seven tools, including Analytics Advisor queries | Ireland / USA | EU–US Data Privacy Framework, standard contractual clauses |
| Google LLC (Google Drive) | Storage of the daily encrypted database backup that includes the MousePlayer recordings; the keys do not leave the controller | USA / worldwide | EU–US Data Privacy Framework, standard contractual clauses |
| Google LLC (Google Public DNS, Measurement Protocol validation server) | Name resolution for the tools with a server component, including reverse DNS of IP addresses (Connection Mirror, Crawler IP Verifier); validation of a payload entered | USA | EU–US Data Privacy Framework |
| Cloudflare, Inc. | Name resolution for the tools with a server component, including reverse DNS of IP addresses (Connection Mirror, Crawler IP Verifier); Cloudflare also sits in front of rdap.org | USA | EU–US Data Privacy Framework |
| rdap.org | Forwarding of an RDAP query to the responsible registry (Domain RDAP & CT Lookup, Crawler IP Verifier; Connection Mirror only after a click on the button for the network holder) | United Kingdom | Adequacy decision of the European Commission; for one’s own address in the Connection Mirror, the consent in addition |
| Registry of the domain or IP address looked up | Holder data of a domain (Domain RDAP & CT Lookup) or of an IP network (Crawler IP Verifier; Connection Mirror only after a click); what is transmitted is the entry looked up and nothing else | Depending on the domain ending or address range; for European IP addresses the RIPE NCC in the Netherlands, otherwise ARIN (USA), APNIC (Australia), LACNIC (Uruguay) or AFRINIC (Mauritius) | For a domain or address entered, no data of the requesting device leaves the server. In the Connection Mirror: within the EU (RIPE NCC) no third-country transfer, otherwise the explicit consent under Art. 49(1)(a) GDPR given by the click |
| Sectigo Limited (crt.sh) | Certificate logs of a domain entered | United Kingdom | Adequacy decision of the European Commission |
| MetaBrainz Foundation (MusicBrainz) | Lookup of an ISRC, ISWC or barcode entered | USA | No personal data: only the code is transmitted |
Beyond this, data are only disclosed where a legal obligation to do so exists. Personal data are never sold, and they are never made available to advertising networks or data brokers.
12. Rights of the persons concerned
Every person whose personal data are processed has the following rights under the GDPR:
- Access (Art. 15 GDPR) – confirmation of whether data are being processed, and a copy of them
- Rectification (Art. 16 GDPR) – correction of inaccurate data and completion of incomplete data
- Erasure (Art. 17 GDPR) – deletion, provided no retention obligation stands against it
- Restriction of processing (Art. 18 GDPR) – a stop on processing while a matter is being clarified
- Data portability (Art. 20 GDPR) – receipt of the data in a structured, machine-readable format
- Objection (Art. 21 GDPR) – objection to processing based on Art. 6(1)(f) GDPR, on grounds arising from the particular situation of the person concerned
- Withdrawal of consent (Art. 7(3) GDPR) – withdrawal at any time, with effect for the future
These rights can be exercised informally by e-mail to contact@lukaswojcik.com. A reply follows within one month; where a request is complex, this period may be extended by two further months, in which case notification is given.
13. Right to lodge a complaint
Independently of any other remedy, a complaint may be lodged with a supervisory authority. The authority responsible for the controller is:
Prezes Urzędu Ochrony Danych Osobowych (UODO)
ul. Stawki 2
00-193 Warszawa, Poland
uodo.gov.pl
A complaint may equally be lodged with the supervisory authority of the place of residence or of the place where the alleged infringement occurred. For persons in Germany this is the data protection authority of the respective federal state, for persons in Austria the Datenschutzbehörde in Vienna.
14. Obligation to provide data, automated decision-making
There is no legal or contractual obligation to provide personal data. The entries in the contact form and in the comment function are voluntary; without them, however, an enquiry cannot be answered and a comment cannot be published.
Automated decision-making within the meaning of Art. 22 GDPR does not take place. The reCAPTCHA score described in section 8.1 decides only whether a form submission or a tool request is accepted, not about any matter of legal effect; a rejected submission can be sent by e-mail at any time instead. The same applies to the result of formconfirmed (section 8.2).
15. Data security and backups
Backups: an encrypted copy of the database is created daily and stored with Google Drive; encryption happens before the transfer, and the keys never leave the controller (section 7.8). A copy covers every table, including those named in this policy. A deleted record can therefore persist there for a while: daily copies are deleted after 7 days, weekly copies after one year. A backup is restored only after a loss of data.
The entire site is delivered exclusively over TLS-encrypted connections; unencrypted requests are redirected. A Content Security Policy limits which origins the browser may contact, which considerably reduces the effect of injected scripts. Access data for the database and for external services are held outside the web directory and appear in no source file that is delivered. The administration area is protected by additional access checks.
16. Changes to this policy
This policy is amended whenever a change in the services used or in the legal position requires it. The version currently in force is always the one retrievable here. A substantial change raises the main version number. The start page may point it out for a limited period. The current version number and the date on which it took effect appear at the top of this page.
AI Tools privacy
The controller is LW IT Solutions, identified in the imprint. Submitted URLs, texts, images and technical findings are processed to provide this service (Article 6(1)(b) GDPR); abuse prevention relies on legitimate interests (Article 6(1)(f) GDPR). AI evaluation of submitted content takes place on my own EU servers. Inputs are not used to train models. Image metadata is removed on ingestion. Raw inputs are discarded after processing; results including image previews and queued inputs are retained for no more than 30 days. A secret daily hash of the IP address enforces limits and is deleted within three days. Google reCAPTCHA loads when each check is started to prevent spam and abuse. In particular, IP address, device and interaction data are transmitted to Google; the _grecaptcha cookie may be set. Processing outside the EU is possible. AI evaluation of submitted content remains on my own EU servers; the EU-hosting statement does not cover the reCAPTCHA security check. Further details are provided in the reCAPTCHA section of the main privacy policy. In addition, my own form protection formconfirmed checks every request with a proof of work in the browser; it runs on my own servers in Poland, sets no cookies and receives a token and the IP address from the server, no inputs. Without this token no check is started (section 8.2 of the main privacy policy). Target sites receive the server address and the LW-AIToolsBot user agent. General server logs and data subject rights are described in the main privacy policy. Do not submit confidential data or personal images without appropriate authorisation. Result links grant access to anyone who knows the link. Tool data is excluded from regular backups. For troubleshooting, normalized inputs and results are stored on the owner's server for up to seven days. reCAPTCHA tokens and credentials are not part of the debug log; older records may be deleted sooner when the storage limit is reached.
AI quiz lab on Explore
Starting a quiz round uses Google reCAPTCHA to prevent abuse; it loads only after the start click. Our own form protection formconfirmed also checks the request (section 8.2). Topic, difficulty, language and identifiers of recent questions are sent to our server. Answers, hints used and scores remain in the browser. AI servers receive prepared quiz models only, not visitor answers or IP addresses. AI creates fictional scenarios; fixed calculation models determine numbers, choices and solutions. A daily rotating HMAC identifier enforces the allowance of 20 rounds per calendar day (Europe/Warsaw) per IP. Allowance data is removed within three days. Quiz jobs and generated rounds are stored for at most 24 hours, with cleanup running every minute. Result cards are created locally in the browser. No quiz account is created.