Text block for your privacy policy

How to use this text block

When you embed reactive.chat on your website, you are the controller for your visitors' data under the GDPR, and we process it on your behalf under the data processing agreement. Art. 13 GDPR requires you to inform your visitors about this processing in your own privacy policy. Below you find a short version and a detailed version that you can copy and adapt, additional blocks for optional functions, a list of what you have to fill in, the places where the text stops being true once you change a setting, and the entries for your cookie and storage table.

This text is a template, not legal advice. It describes what reactive.chat actually does – not what is legally sufficient in your case. For your website you are the controller; the completeness and accuracy of your privacy policy are yours to answer for. Have the text reviewed before you publish it.

Three things the text assumes:

• You have accepted the data processing agreement. It is concluded on registration.
• Your consent banner and the chat are configured consistently. The widget writes to localStorage only after your consent management platform signals consent (an IAB TCF signal stating that the GDPR does not apply counts as consent) – with one exception: after a visitor has deleted the chat data, a single bit without any identifier (rc_dnt). Without that signal it uses sessionStorage only (see the storage table below).
• Your settings match the text. Several passages depend on your project settings; they are marked in square brackets, and the section "Places where the text stops being true" explains which.

How to proceed:

• Replace every bracketed placeholder such as [Company name], [retention period] and [e-mail address] with your own values, and delete the variants that do not match your settings.
• Choose the legal bases that match your situation. The block suggests Art. 6(1)(b) GDPR for answering requests, Art. 6(1)(f) GDPR for offering the chat and protecting it against abuse, and consent for persistent browser storage. Check the choice with your legal adviser.
• In the reactive.chat dashboard you decide whether the chat asks your visitors for consent before they can write, whether they can withdraw that consent and delete their chat data in the chat window, whether a deletion request written in the chat is recognised at all and whether it is then carried out after a confirmation or straight away, whether a deletion erases a conversation or only strips its personal reference, and after how many days conversations are deleted automatically. The withdrawal and delete buttons and the recognition of written deletion requests are switched on unless you turn them off, and the recognition asks for a confirmation unless you set it to delete straight away. No retention period is set unless you set one – see "Places where the text stops being true", point 1.
• The detailed block contains a paragraph on translation and writing aids for your team. Your agents can use these tools in the dashboard in every project, whether or not you use the AI assistant – automatic translation (of all incoming messages and every reply) only on a paid plan; if the chat asks your visitors for consent before they can write, automatic translation and the writing aids work only while a visitor's consent is known to the chat. Delete the paragraph only if your team does not use them. If you have connected an AI server of your own to reactive.chat, choose the wording in that paragraph that matches its mode.
• Add the additional blocks for the functions you use: the AI assistant, Smart Answer, messaging channels and campaigns, call-back and calls, order data from your shop.
• If you connect integrations (Slack, HubSpot, Zendesk and others) or MousePlayer session replay, add your own paragraphs for them. Those providers act for you, not for us, and are not covered by this block.
• Keep the block up to date when you change settings, for example when you enable visitor identification, change the privacy settings of the chat, switch the assistant on or off, or start using a new function.
• Alternatively, have the block inserted automatically: place <div data-rc-privacy></div> in your privacy policy, and it appears there filled in from your project settings and kept up to date – see Insert the privacy text automatically. The automatically inserted text covers the chat, the AI assistant and Smart Answer; for channels, campaigns, calls and order data add the additional blocks below yourself.

The short version

For privacy policies that give each service one paragraph.

Live chat (reactive.chat)

On this website we use reactive.chat, a live-chat service of LW IT Solutions Company Lukas Wójcik, al. Tadeusza Kościuszki 80/82, lok. 301, 90-437 Łódź, Poland. When you use the chat, your messages, any files and details you send, technical session data (random session id, the page you are on, referring page, browser language and type) and your IP address are processed; the chat also transmits the visible text of the page you are on, which is stored per page, not with your person; the IP address serves to establish the connection and to protect the chat against abuse, and the country is derived from it. [If you use the AI assistant: Some answers are written by an AI assistant, which is labelled as such; it runs on reactive.chat's own servers in Poland, and no third-party AI service receives your messages.] The legal basis is Art. 6(1)(b) GDPR where your request concerns a contract, otherwise our legitimate interest in offering direct communication (Art. 6(1)(f) GDPR) [or, if the chat asks for your consent first: your consent under Art. 6(1)(a) GDPR]. The widget sets no cookies; only with your consent does it store identifiers in your browser's local storage, otherwise only for the duration of the tab. reactive.chat processes the data on our behalf under Art. 28 GDPR on its own server in Łódź, Poland; an encrypted backup copy is stored with Google Cloud Storage in Warsaw, which only reactive.chat can decrypt. We delete conversations after [retention period]. You can [delete your chat data yourself under "Your data" in the chat window, or] contact us at [e-mail address] to exercise your rights.

Text block: live chat with reactive.chat

The detailed version, for privacy policies that list data categories, purposes and recipients separately.

Live chat (reactive.chat)

On this website we use reactive.chat, a live-chat service of LW IT Solutions Company Lukas Wójcik, al. Tadeusza Kościuszki 80/82, lok. 301, 90-437 Łódź, Poland ("reactive.chat"). The chat widget lets you send us questions directly on this website and receive answers from our team.

Data processed. When you open the chat, the following data is processed: the messages and files you send, time stamps, your answers to quick replies and forms, any details you enter in a form before or outside the chat (for example name, e-mail address or telephone number) and any rating or comment you give; and technical session data, namely a random session id and – only with your consent to storage in your browser – a random visitor id, the address and title of the page you are on and the last pages visited during your visit, the referring page and campaign parameters, your browser language, your browser type (user agent) and the screen size class. So that answers can take into account the page you are on, the chat also transmits the visible text of that page; it is stored per page, not together with your person. [If applicable: If you are logged in on our website, we pass your [name / e-mail address / customer number] to the chat so that our team can help you faster and you can see your earlier conversations.]

Your IP address. Your IP address is used to establish the connection, to protect the chat against abuse and to limit the number of requests; reactive.chat derives the country from it using a database on its own server. The conversation itself stores the country, not the IP address. The IP address is stored in the access log of reactive.chat's web server, which is deleted after the current day and 14 further days, in reactive.chat's system log, which is limited by size, in a list of the latest 500 security events, and, where the chat protects itself against an attack or our team blocks a visitor, in a block list for the duration of the block (24 hours unless set otherwise, at most 365 days). [If the chat asks for your consent before you can write: It is also stored in the record of your consent (see below).]

Storage in your browser. The chat sets no cookies. Without your consent in our consent banner, it keeps its data only in the sessionStorage of your browser, which is cleared when you close the tab, and creates no visitor id. Only if you have given your consent does it store its data in localStorage, so that your conversation can be continued on a later visit: the current conversation for one day; your language and theme choice, the details you entered in the form before the chat, your answer to the chat's consent question and the time of your first visit for one year; messages not yet sent for 24 hours; and, without expiry, a random visitor id with the visitor proof and a "do not disturb" choice. If you have deleted your chat data, a single bit without any identifier is kept in localStorage so that the chat does not identify you again. If you withdraw your consent, the chat removes its rc_ entries from localStorage; the visitor id stored under mp_visitor_id remains until you delete your chat data.

Purposes and legal bases. [Two variants. Keep the one that matches your setting and delete the other.]

Variant A – the chat starts without asking for consent: We process this data to answer your requests (Art. 6(1)(b) GDPR, where your request concerns a contract with us or its preparation) and on the basis of our legitimate interest in offering fast, direct communication and in protecting the chat against abuse (Art. 6(1)(f) GDPR).

Variant B – the chat asks for your consent before you can write: We process the content of your messages on the basis of your consent (Art. 6(1)(a) GDPR). Before you can write, the chat shows you the sentence you are agreeing to, and we record that you agreed together with the wording that was shown, the time, your IP address and your browser type, so that we can prove your consent (Art. 7(1) GDPR). Until you agree, the chat does not transmit the content of the page you are on. The technical session data needed to display the chat and to protect it against abuse is processed on the basis of our legitimate interest (Art. 6(1)(f) GDPR). You can withdraw your consent at any time with effect for the future [if you have left the withdrawal button switched on: in the chat window, under "Your data" – "Withdraw consent"] or by writing to [e-mail address]. Withdrawing ends the conversation and deletes the chat data of that visit; the processing carried out until then remains lawful.

In both variants: persistent storage in your browser is based on your consent (Art. 6(1)(a) GDPR and Art. 5(3) ePrivacy Directive [and the applicable national provision]). This is a separate consent from the one described in variant B: it covers only the storage on your device, not the processing of your messages. You can withdraw it at any time [in the consent settings: link].

Processor and place of processing. reactive.chat processes the data on our behalf under a data processing agreement pursuant to Art. 28 GDPR. The data is processed on a server owned and operated by reactive.chat in Łódź, Poland. For backup purposes, an encrypted copy of the data is stored daily with Google Cloud Storage (Google Cloud EMEA Limited; storage location Warsaw, Poland); it is encrypted before transfer, and the keys remain with reactive.chat. Backup copies are kept for up to 364 days. The full list of reactive.chat's sub-processors is available at https://reactive.chat/p/sub-processors.

Translation and writing aids for our team. Our team can have messages in the chat translated by a language model and can have it prepare drafts of replies and summaries of the conversation or reword its own replies. For this, the messages concerned are processed by a language model on reactive.chat's own servers in Poland [if you have connected an AI server of your own to reactive.chat, write instead, depending on its mode: with "Own node preferred": mainly on our own server and otherwise on reactive.chat's own servers in Poland / with "Own node only": only on our own server]; no third-party AI service receives your messages. Before a draft or a summary is prepared, e-mail addresses, telephone numbers and digit sequences of six or more digits are replaced. Nothing is sent to you automatically: a member of our team sees every draft and every translated reply before it is sent and decides what is sent. If our team uses translation, you receive our replies in your language, and the stored conversation also contains the original wording of our replies and the translations of your messages. This processing serves to answer your requests and is based on the same legal bases as the chat.

Retention. We delete chat conversations after [retention period]. The period runs from the last activity in the conversation; we set it in the settings of our chat project, and it is applied automatically in a daily run. [If you have set deletion to anonymisation: Instead of removing the conversation record itself, we strip its personal reference: the message texts are replaced by a placeholder, translations and form answers are removed, and the data describing you – the visitor id of the conversation, a rating comment you left, the browser identification, the country and the referral data – is cleared, so that the conversation remains only as an anonymous entry (time, channel, status, rating) for our statistics; the records of its AI processing are emptied as well. A question we have adopted into our knowledge base stays there as our content.] Files you send in the chat are deleted [7 / 90] days after upload. [If the chat asks for your consent: The record of your consent is kept so that we can prove it; when you delete your chat data, it is stripped of your identifiers, IP address and browser type.] Deleted data remains in the encrypted backup copies until they expire, at most 364 days. Card numbers, IBANs, e-mail addresses, telephone numbers and similar data are automatically redacted before a message is stored; please do not enter payment data in the chat.

Your rights. You may request access to your data, its rectification or erasure, restriction of processing and data portability, and you may object to processing based on legitimate interest. You also have the right to lodge a complaint with a supervisory authority. Please contact us at [e-mail address]. [If you have left the delete button switched on: You can also delete your chat data yourself, without contacting us: open "Your data" in the chat window and choose "Delete everything". That deletes the conversation, its history and the identifiers of your current visit, and it cannot be undone. It does not cover anything we hold about you outside the chat – a customer account, orders, a newsletter subscription or web analytics, for example; for those please use the contact address above.] [If you have left the recognition of written deletion requests switched on: You can also simply write your request in the chat – "please delete all my data" or "please forget me", for example. The chat recognises such wordings against a fixed list of phrases, without using an AI assistant, and answers you. Keep the variant that matches your setting: with a confirmation – the chat then asks you to confirm, and nothing is deleted until you do; straight away – the chat tells you what is being deleted and then deletes it without asking again. Either way this deletes the conversation, its history and the identifiers of your current visit and cannot be undone, and it does not cover anything we hold about you outside the chat.] Information on how reactive.chat processes data is available at https://reactive.chat/p/privacy-policy.

Additional block: if you also use the AI assistant

Insert this paragraph after "Data processed" or after "Processor and place of processing".

AI assistant. Part of the chat is answered by an AI assistant named [assistant name, e.g. Ada]. The chat tells you before the first answer that you are talking to an AI assistant and labels each of its answers with "AI". You can ask for a human colleague at any time [if your team is not always available: during our opening hours]; as soon as a member of our team takes over, the assistant stops answering. The assistant answers from our own knowledge base, which we maintain (content of our website, documents and product information) and, where it contains nothing suitable, from the general knowledge of the language model. The language models used are openly licensed and run on reactive.chat's own servers in Poland [if you have connected an AI server of your own to reactive.chat: see "Places where the text stops being true", point 4]; no third-party AI service (such as OpenAI, Google or Anthropic) receives your messages, and your messages are not used to train any model. The assistant makes no decisions with legal effect on you. [If you have configured actions: If the assistant offers to do something for you – for example to book an appointment – it does so only after you have confirmed with "Yes".] Answers are generated automatically and may be inaccurate; if in doubt, please ask our team at [contact].

Additional block: if you also use Smart Answer

Insert this paragraph after the AI assistant block. Of the passages in square brackets, keep those that match your Smart Answer settings ("Which input", "Store search queries", "Follow-up question") and delete the others. Smart Answer only answers if your AI assistant is switched on, and not while the chat asks for consent before the first message (variant B above).

AI answers in search (Smart Answer). [With "Questions only": If your input in our search field is phrased as a question,] [With "Every search": If your input in our search field has at least [minimum number] characters,] our search also answers it with a brief answer written by a language model, shown [above / below] the results. For this, your browser sends the question (at most 300 characters), the language, the address of the current page and the referring page, both without parameters and anchors (such as a search term in the address of our search page), [if the chat is embedded on the same page: as well as the chat's visitor ID] in encrypted form to reactive.chat [if you have set up your own domain: via [your chat address]]. As with the AI assistant, the answer is produced from our knowledge base on reactive.chat's own servers in Poland; no third-party AI service receives the question or the answer. The answer is machine-generated and may contain errors; the linked pages are authoritative.

[If "Store search queries" is off:] Question and answer are not stored. They exist only in working memory while being processed, at most 180 seconds on the way between reactive.chat's servers, and are deleted afterwards; no chat history is created. [With "Continue in the chat": A follow-up question opens a normal chat with only the text you then enter; the original search question is not carried over.]

[If "Store search queries" is on (default):] Question and answer are stored like a chat conversation; our team sees them in the chat dashboard, and the retention period for chat conversations stated above applies. [With "Continue in the chat": A follow-up question continues this conversation in the chat.] So that a repeated question is not computed again, the search keeps the answer together with your question in your browser's sessionStorage and uses it for at most ten minutes. On its server, reactive.chat also keeps a generated answer with its sources for 24 hours for the same purpose; the question is kept only as a one-way hash, and nothing about you.

[With "Answer in the box" or on pages without the chat: Follow-up questions are answered in the same field; with each follow-up question, the up to three previous questions and answers are sent along as context, of which only the questions go to the language model. If "Store search queries" is on, each follow-up question is stored together with these previous questions as a separate conversation.]

In both cases: For each request, reactive.chat stores a counter entry without content: time, shortened IP address (an IPv4 address without its last block, an IPv6 address shortened to its first 48 bits), identifier of our website, length of the question, result and duration. It serves to detect abusive numbers of requests and to troubleshoot, and is deleted after seven days; we only see daily figures from it, without IP addresses. In the browser, the search keeps its settings in sessionStorage and uses them for five minutes. The search deletes expired entries as soon as it reads them or starts again on a page; if a tab stays open without a new page load, an expired entry remains until the next page load or until you close the tab. No cookies are set. Each request also appears in the access log of reactive.chat's web server (time, IP address, requested address, browser type; without question or answer), which is deleted after the current day and 14 further days.

The legal basis is Art. 6(1)(f) GDPR: our legitimate interest in answering your question quickly on the basis of the content of our website and in protecting the service against mass automated use.

Additional block: if you use messaging channels or campaigns

Keep the channels you have connected and delete the others.

Messaging channels. You can also reach us via [WhatsApp / Facebook Messenger / Instagram / Telegram / SMS / e-mail]. Messages you send us there are shown to our team in the reactive.chat dashboard and answered from there, under the same conditions as the chat on this website. [WhatsApp, Messenger, Instagram: The messages are transmitted through Meta Platforms Ireland Ltd.; Meta processes them under its own terms.] [Telegram: The messages are transmitted through our own Telegram bot; Telegram FZ-LLC is located in Dubai, outside the EU/EEA. Messages in Telegram groups are not processed.] [SMS: The messages are transmitted through our account with Twilio.] [E-mail: The messages are collected from our mailbox and sent through our mail server.] [E-mail without an outgoing server of your own: Replies are sent through the e-mail service of reactive.chat from a reactive.chat sender address in our name, with our address as reply address; reactive.chat's e-mail provider processes your e-mail address, name, subject and the text of the reply.] For this, your [telephone number / profile id / e-mail address], your display name and your messages are processed, and reactive.chat stores the link between your channel identity and the conversation. These data are deleted together with the conversation according to our retention period.

Campaigns. [If you send WhatsApp campaigns: If you have agreed to receive messages from us via WhatsApp, we store your WhatsApp number, your name, the proof of your agreement, labels we assign and the delivery and read times of our messages; the delivery records are deleted after 90 days. You can unsubscribe at any time by replying [opt-out word]; we then keep your unsubscription so that it remains respected. If you ask us to delete your data, we delete your contact and the delivery records; if you had unsubscribed, only a blocking note (a keyed hash of your number) remains, so that you are not signed up again. The legal basis is your consent (Art. 6(1)(a) GDPR).] [If you show campaigns in the chat: If you are in the EU, the EEA, the United Kingdom or Switzerland, or your country cannot be determined, campaigns in the chat are shown to you only with your consent. So that a campaign in the chat is not shown to you too often and its effect can be counted, reactive.chat keeps, under a one-way hash of your visitor or session identifier, a counter until one day after the campaign ends (at most 400 days) or at most 90 days after you were last addressed, a repetition lock for the minimum interval we set between two messages (at most 90 days) and a marker of whether you have visited before (90 days after your last visit); reach is counted in counters that cannot be read back individually, kept for up to 400 days.]

Additional block: if you offer call-back or calls

Call-back and calls. In the chat you can ask us to call you back. For this we process your telephone number, your country, your request and the time window you choose; completed requests are deleted after 30 days, open ones after 90 days. [If you offer voice or video calls: You can also talk to us by voice or video directly in the browser. The connection is encrypted and established directly between your browser and the browser of our team member, who therefore receive each other's IP address. Calls are not recorded; reactive.chat keeps a log of the time, duration and type of each call for 365 days.] [If you use co-browsing: With co-browsing, after you have agreed, our team member sees the labels of the buttons, links and headings of the page you are on – no form fields and nothing you type – and can highlight elements for you. They cannot click or type on your page, and you can end co-browsing at any time. It is not recorded.] A call takes place only at your request. The legal basis is Art. 6(1)(b) GDPR where your request concerns a contract, otherwise our legitimate interest in answering your request in the way you chose (Art. 6(1)(f) GDPR).

Additional block: if the assistant answers questions about orders

Questions about your orders. If you are logged in to our shop, the AI assistant in the chat can answer questions about your own orders. For this, our shop confirms your customer number to reactive.chat with a time-limited signature, and the assistant receives only the following data of your orders: [list the fields you have enabled, e.g. order number, order date, status, total, items, carrier, tracking number, invoice number, payment status]. Names, e-mail address, telephone number, street address and payment data are never passed on. [If you use "fetch": The data is retrieved for your question and not stored.] [If you use "import": We transmit the data to reactive.chat in advance, where it is stored encrypted and deleted at the latest 90 days after our last transmission.] The data is processed only on reactive.chat's own servers in Poland and does not go to any third-party AI service. The legal basis is Art. 6(1)(b) GDPR.

What you have to fill in

• [Company name], [e-mail address], [contact]: your own name and address for privacy matters – not ours. For your visitors' data you are the controller and the first point of contact.
• [retention period]: the number of days you have set in your project under the privacy settings of the chat. Do not state a period that you have not set (see point 1 below).
• [7 / 90]: 7 days on the free plan, 90 days on paid plans, or the period of your individual contract.
• [assistant name]: the name you have given the AI assistant.
• [name / e-mail address / customer number]: only the details you actually pass to the chat when a visitor is logged in.
• Links: the place where your visitors can change their consent (for example "via the Cookie settings link in the footer").
• The heading: adapt it to the structure of your privacy policy. The name of the service should appear in it so that a visitor can find it again.

Places where the text stops being true

The text describes the actual behaviour of reactive.chat. Change one of the following, and a correct sentence can become a false promise that is then published on your website.

1. If you have not set a retention period. Unless you set one, reactive.chat deletes conversations at no fixed time: they are kept until the visitor deletes them, or until your project or workspace is deleted. Ending a paid subscription does not delete them either. There is currently no function in the dashboard to delete individual conversations. The sentence "We delete chat conversations after [retention period]" is therefore only true if you have set that period. Set it in the project settings (between 1 and 3,650 days) before you publish the sentence.
2. If you switch off the delete button, the withdrawal button or the recognition of written deletion requests. Then delete the corresponding bracketed passages; otherwise you promise a self-service that does not exist.
3. If you change the consent setting of the chat. Variant A and variant B are mutually exclusive. With variant B, your IP address is stored in the consent record; the sentence on the IP address must then contain that addition.
4. If you connect an AI server of your own. Then messages for AI functions are processed on your server and with the model you have chosen there, possibly by a provider you have engaged. The sentences "on reactive.chat's own servers in Poland" and "no third-party AI service" are then no longer true for those functions; name your server and, where applicable, your provider.
5. If you identify logged-in visitors, use order data or connect integrations. Each of these passes more data to the chat or from the chat to others than the basic text describes. Add the corresponding block or your own paragraph. Integrations such as ticket, CRM or team-chat tools receive names, e-mail addresses and conversation content from the chat on your instruction; they are your recipients, and they belong in your privacy policy.

Two things do not make the text wrong but are worth adding: if you exclude pages from the page text transmitted by the chat, saying so reassures your visitors; and if you use MousePlayer session replay, the chat and MousePlayer use the same identifiers (see the storage table).

For your cookie and storage table

The chat sets no cookies. If you maintain a cookie table, the entries below belong under "local storage" or "session storage". Without consent, everything is kept in sessionStorage until the tab is closed; with consent, the entries marked "local" move to localStorage with the duration stated, and the rc_ entries are removed on withdrawal.

• rc_id – sessionStorage, only without consent – session id and tab id – until the tab is closed.
• rc_conv, rc_thr – local with consent – current conversation and list of conversations – one day.
• rc_tab, rc_marke:<site key> – local with consent – last tab opened in the chat window, display marker of the website – one day.
• rc_locale_wahl, rc_thema_wahl – local with consent – language and theme chosen in the chat – one year.
• rc_prechat – local with consent – details entered in the form before the chat (for example name, e-mail address) – one year.
• rc_ds, rc_dsst – local with consent – the visitor's answer to the chat's consent question, consent level of the site – one year.
• rc_erst – localStorage, only with consent – time of the first visit – one year.
• rc_vtok – local with consent – visitor or session id with the visitor proof that protects the conversations against access by others – no expiry in the browser (400 days after last use on the server).
• rc_outbox_* – local with consent – messages written but not yet sent, including their text – 24 hours.
• rc_sig – local with consent – throttle for behaviour signals and error reports (page path, time, counter) – 30 minutes.
• rc_seen, rc_http – sessionStorage – technical state of the connection – until the tab is closed; rc_http 30 minutes. rc_leader – local with consent, only in browsers without Web Locks – which tab holds the connection – until that tab ends the connection.
• rc_offen, rc_seiten, rc_draft_* – always sessionStorage – chat window open, page counter, unsent draft of a message – until the tab is closed. rc_nav, rc_ruht, rc_cb – sessionStorage – last addresses within the page, quiet period, call-back form in progress – until the tab is closed; if consent is given while they exist, they move to localStorage with the other entries and stay there without expiry until withdrawal or deletion.
• rc_dnd – local with consent – "do not disturb" for proactive messages – no expiry.
• rc_dnt – always localStorage, also without consent – a single bit after the visitor has deleted the chat data, without any identifier, so that the deletion is respected – no expiry. It stores the visitor's own decision and is strictly necessary for it.
• mp_session_data, mp_visitor_id – localStorage, only with consent, also if you do not use MousePlayer – session id (used for 30 minutes) and visitor id of the chat, stored in MousePlayer's format – mp_visitor_id without expiry; not removed on withdrawal of consent, removed when the visitor deletes the chat data. mp_tab_id – sessionStorage, only with consent – tab id – until the tab is closed. If MousePlayer identifiers already exist in the browser, the chat uses them, also without consent.

Smart Answer keeps its settings (five minutes) and, if storing is on, recent answers (ten minutes) in sessionStorage; it sets no cookies either.

Where to find more

Every sentence in the text can be checked against a document. If you want to delete or reword one of them, look there first to see what actually happens:

• Privacy Policy of reactive.chat – the same operations from our side, with all periods
• Data processing agreement – your obligations and ours
• Sub-processors – who else is involved, where, and on what basis
• Technical and organisational measures – how the data is protected
• Our records of processing activities and our data protection impact assessment – not published; available to you on request (contact@lukaswojcik.com)
• AI Act information – labelling and limits of the AI functions

This document is drawn up in English. Translations into German (/de/p/textbaustein-datenschutzerklaerung) and Polish (/pl/p/fragment-polityki-prywatnosci) are provided for convenience; the English version prevails.

Version 2.4 replaces version 2.3 of 16 October 2026. Changed: our records of processing activities and our data protection impact assessment are available on request instead of being linked ("Where to find more"). The text block itself is unchanged.

Version 2.3 replaces version 2.2 of 12 October 2026. Corrected: language models in the block on the AI assistant; shortened IP address in the Smart Answer counter; retention period counted from the last activity; the automatically inserted text now says the same as this text block (takeover by the team, access log, daily run).

Version 2.2 replaces version 2.1 of 11 October 2026. Corrected: storage in the browser and storage table (rc_id, mp_ keys, rc_sig, rc_vtok, entries moved on consent, withdrawal); page text in the short version; places where the IP address is stored; campaign periods; answer cache of Smart Answer; the automatically inserted text now reflects this version.

Version 2.1 replaces version 2.0 of 11 October 2026. Changed: additional block for channels (Telegram bot, e-mail without own outgoing server) and campaigns (consent for visitors from the GDPR area, new periods, blocking note), co-browsing described.

Version 2.4 – effective 19 October 2026.