Privacy policy

1. Who is responsible for your data

The data controller is Daniil Puiatrouski, address: ul. Cynamonowa 19, 02-777 Warszawa, Poland, email: hello@delkind.eu. The services are provided under the trade name DELKIND STUDIO; the company is not yet registered, so the controller is an individual.

We do not have a data protection officer. For any questions about data, write to hello@delkind.eu.

2. What data we receive

When you submit a request

• your name or how we should address you;
• the contact you give: Telegram, WhatsApp, phone or email;
• the service, package or topic you chose, and your message if you write one;
• the page the request was sent from, the previous page of our site (only its path, for example an article after which you opened a service page) and the address of the page you were referred from; the name of the site you came from is recorded in the request on a separate line;
• ad campaign tags from the page address, if there are any (utm_source, utm_medium, utm_campaign, utm_content, utm_term), and click identifiers of advertising systems (fbclid, gclid, gbraid, wbraid, ttclid, msclkid and similar): they show which ad brought the request;
• device type (phone or computer), browser details, page language and the time zone of your browser;
• technical data: the request number and time, how long the form took to fill in, which cookies you allowed, which version of this policy applied and which data notice you saw next to the form;
• the hash of your IP address — an irreversible fingerprint of the address, calculated with a secret key. We use it to limit the number of requests from one address. We do not store the IP address itself in the request database;
• only if you agreed to marketing cookies: the first page and the first ad tag of the visit, and the identifiers of Meta cookies (_fbp, _fbc).

When you write to us by email or in a chat app

Your address, name or username, phone number and the text of the correspondence.

If you write to our Facebook or Instagram page, Meta tells our server about the new message: its text (or the type of attachment — photo, video, voice message), the message’s service number and the sender number that Meta assigns for our page. Using this number, the server asks Meta for your name (on Instagram, your username as well), so that the notification shows who wrote.

When you simply open the site

The site runs on our server at Hetzner Online GmbH. When you open a page, the server records in its log your IP address, the time of the request, the address of the page opened (together with ad tags, if they are in the address), the address you came from and browser details. The log is needed to show you the page, protect the site from attacks and investigate faults; it is kept for up to 14 days.

Separately from this log, the server counts visits: how many times pages are opened, where visitors come from and which pages lead to a request. For this it writes only the following to a separate visit statistics log:

• the hour at which the page was opened (minutes and seconds are not recorded);
• the path of the page opened, for example /en/crm/: the rest of the address is not saved, so click identifiers of advertising systems (fbclid, gclid and similar) and other parameters do not enter this log;
• the site you came from: if it is another site, only its name, for example google.com, without the page address and search words; if you came from another page of our site, the path of that previous page;
• the ad tags utm_source, utm_medium and utm_campaign, if they are in the address.

This data does not show who you are: the statistics log has no IP address, cookies, or browser and device details. The server filters out search engine and other robots by the name of the program that opened the page, but only at the moment of the request: the name itself is not written to the statistics log, and robot requests do not enter it. For these statistics the site writes nothing to your browser and runs no scripts on the pages.

Once an hour the server adds the records up into totals by day (which page, where visitors came from, how many views) and deletes the log records themselves after no more than 7 days; the totals are kept longer, but without data about you. The periods are in the section “How long we keep data”. So with this counter we cannot tell one visitor from another and do not know how long you spent on the site: it counts page views, not people. Google Analytics and Microsoft Clarity work only with your consent and are described below.

The demos on service pages (chats, dashboards, builders) run right in your browser: what you enter in them never leaves your browser. The exception is the “Ask AI” window: its messages go to our server and from there to Google (Gemini API) to prepare a reply, and are handled as described in the section “AI assistant on the site and in chat apps”.

When you write to the AI assistant

Messages (on Telegram, voice messages and images too), the contact you left yourself, details of the task and the hash of your IP address. Details are in the section “AI assistant on the site and in chat apps”.

Only with your consent — the Meta pixel

If you allow marketing cookies, your browser will tell Meta about page views, clicks on the Telegram and WhatsApp buttons and the submission of a request (without name and contact), and will also pass your IP address, browser details and Meta cookie identifiers. More in the section “Cookies”.

Some of these events — submitting a request (in the form and in the chat window with the AI assistant on the site) and clicking the Telegram or WhatsApp button — are also duplicated to Meta by our server (Conversions API). The purpose is the same as for the pixel: to see which ads bring requests and to help Meta show ads more accurately. The data set is the same: the event name and time, the page address, the service or channel, the Meta cookie identifiers (_fbp, _fbc); plus the IP address and browser details at the time of the event. We do not pass Meta your name, contact, the text of your request or chat messages, or your email and phone number in encrypted (hashed) form. Our server sends this only if you allowed the Meta pixel; without your consent it sends Meta nothing.

Only with your consent — statistics (Google Analytics and Microsoft Clarity)

If you allow the “Statistics” category in the cookie banner, the site will load two services, which can be switched on separately. We use them to understand how visitors use the site and to improve the pages. Without your consent they are not loaded. Our own visit counter without cookies, described above, works separately and does not depend on this choice.

• Google Analytics 4 (Google) counts visits: which pages are opened, where you came from, how long the page stayed open, from which country and city, and from which browser and device. It sets the cookies _ga and _ga_XXXXXXXXXX (the name contains the identifier of our site’s data stream). When you submit a request, it receives the “request submitted” event (generate_lead) with only the service name and form type: without name, contact, text or request number. According to Google, Analytics does not record or store the IP address: for visitors from the EU the address is discarded before recording, after being used briefly to determine the city, region and country. We have switched off Google signals and ad personalisation, and we do not link this property to Google’s advertising services.
• Microsoft Clarity (Microsoft) records how you use the pages: clicks, scrolling, mouse movements, text selection, window resizing, script errors and load times. From this data it replays your visit (session recording) and builds heatmaps. A Clarity user identifier (the cookie _clck) is attached to the recording: it shows that the same browser opened the pages. Clarity always hides the content of input fields; we have additionally hidden the request forms and the AI assistant window from recording entirely. Microsoft’s servers can see the IP address, as any site you open can; Clarity uses it to determine the region and to operate. We do not allow Clarity’s advertising storage.

We do not pass your name, contact, or the text of your request or chat messages to these services.

3. Why and on what legal basis

Providing data is voluntary. Without a name and a contact we cannot reply to your request.

4. Who we share data with

• Hetzner Online GmbH (Germany) — hosting: the site, the request database, its daily backups and the server logs are on our server in a Hetzner data centre in Helsinki (Finland, EU). Hetzner processes the data on our behalf, under its own data processing terms.
• Telegram — a notification about a new request arrives in a private working group on Telegram: the request number, the service, package or topic, the page, the source, your contact for the reply, the beginning of your task description (up to 500 characters) if you filled in the field “Briefly about your project”, and a link to the request in our private CRM. Your name and the other data of the request do not go to Telegram. When you write to us on Facebook or Instagram, a notification arrives in the group: the channel, your name or username, the beginning of the message (up to 200 characters), the time and a link to the conversation on Facebook or Instagram. The exception is a failure: if the request database on the server is temporarily unavailable, the message also includes your name and the text of your message, and the full request record is added to a private file on our server so that the request is not lost (the retention period is in the section “How long we keep data”).
• Email — the emails you write to hello@delkind.eu are received and stored by the mail service Zoho Mail (Zoho Corporation B.V., the Netherlands; server in a Zoho data centre in the EU). The service processes the emails on our behalf. Requests from the form are not sent by email.
• Meta Platforms Ireland Limited — only if you agreed to marketing cookies: the pixel data and the same events that our server sends (sections “What data we receive” and “Cookies”). We and Meta are jointly responsible for collecting and passing on this data (Art. 26); after that Meta processes it as an independent controller under its own policy: facebook.com/privacy/policy.
• Google (Google Analytics 4) — only if you allowed “Statistics” and switched on Google Analytics. Google processes this data on our behalf (as a processor) under Google’s data processing terms (Google data processing terms); we have switched off the sharing of Analytics data with Google for its own purposes. The terms of use of Google Analytics for Poland are concluded with Google Ireland Limited (Ireland); the data may also be processed by Google LLC (USA). Which Google company is named in the terms depends on the country chosen when the Analytics account is created; if it turns out to be a different one, we will update this policy. How Google uses data from sites that work with its services: policies.google.com/technologies/partner-sites.
• Microsoft (Microsoft Clarity) — only if you allowed “Statistics” and switched on Microsoft Clarity. For visitors from the EEA, the United Kingdom and Switzerland, Microsoft’s policy names Microsoft Corporation (USA) and Microsoft Ireland Operations Limited (One Microsoft Place, South County Business Park, Leopardstown, Dublin 18, Ireland) as the data controllers; the contract with Clarity customers from the EU is concluded by Microsoft Ireland Operations Limited. Microsoft and we are independent controllers of this data: Microsoft does not process it on our behalf but acts under its own policy (privacy.microsoft.com/privacystatement). Under the Clarity terms, Microsoft may use the collected data to provide the service, to improve its products and services and to create user profiles, including for advertising; the fact that we do not allow advertising storage does not cancel these rights. If this does not suit you, do not switch on Clarity: you can leave Google Analytics on, and the choice does not affect how the site works. Clarity stores its data in the Microsoft Azure cloud.
• WhatsApp, Telegram, Facebook and Instagram — if you write to us there yourself, these services process the correspondence under their own rules as independent controllers. WhatsApp in the EU is WhatsApp Ireland Limited; Facebook and Instagram are Meta Platforms Ireland Limited.
• Google LLC (Gemini API, USA) — only if you write to the AI assistant: it receives your messages, images and voice messages (on Telegram) to prepare a reply or transcribe the voice, and processes them on our behalf: section “AI assistant on the site and in chat apps”.
• Public authorities — only when the law requires it.

We do not sell your data.

5. Transfers outside the EU and the EEA

• The server and the request database are in Helsinki (Finland, EU): there is no transfer outside the EEA here.
• Meta — only if you agreed to marketing cookies: the pixel data and the events that our server sends may be transferred to the USA. Meta participates in the EU-US Data Privacy Framework (European Commission adequacy decision of 10 July 2023, Art. 45). The fallback mechanism is the EU standard contractual clauses in its data processing terms (Art. 46(2)(c)).
• Google Analytics — only if you allowed Google Analytics. For visitors from the EU, data is collected through Google servers in the EU, where the IP address is discarded before the data is forwarded; Google LLC in the USA may also process the data. Google LLC participates in the EU-US Data Privacy Framework (European Commission adequacy decision of 10 July 2023, Art. 45); for Google’s analytics services it relies on the framework, and where the framework does not apply it uses the EU standard contractual clauses (Art. 46(2)(c)) under its data processing terms (data transfers in Google services).
• Microsoft Clarity — only if you allowed Microsoft Clarity. The data is stored in the Microsoft Azure cloud and may be stored and processed in your region, in the USA and in other countries where Microsoft and its companies operate. Microsoft Corporation participates in the EU-US Data Privacy Framework (Art. 45); in addition, Microsoft Ireland Operations Limited and Microsoft Corporation have a contract based on the EU standard contractual clauses (Art. 46(2)(c)).
• Email (Zoho Mail) — the emails are stored on Zoho servers in the EU. Zoho is an international group of companies, and under its own policy data may also be processed outside the EEA; Zoho puts transfers within the Zoho group on the EU standard contractual clauses (Art. 46(2)(c)).
• Google (USA) — only when you talk to the AI assistant; the transfer mechanisms are in the section “AI assistant on the site and in chat apps”.
• Telegram — the operating company is outside the EEA. There is no European Commission adequacy decision for its country, and we have no standard contractual clauses with Telegram either. So only what is needed to reply to your request quickly goes there (including the beginning of the task description, if you wrote one), on the basis of Art. 49(1)(b): the transfer is necessary for the implementation of pre-contractual measures taken at your request. The notification goes to the group right after you submit the form. If you do not want your contact to reach Telegram, do not submit the form; write to us at hello@delkind.eu instead: emails do not reach the Telegram group. If a notification has already gone and you want it removed, write to us: we will erase the data and delete the message (section “Your rights”).

6. How long we keep data

The periods below are maximums (except for correspondence by email and in chat apps: it has no period in days, see below). When a period expires, the data is deleted or anonymised (we remove the name, contact and message text). Expired requests, spam, tests, technical traces and records made during a failure are removed by an automatic clean-up on our server (it runs several times a day). Exceptions: it does not touch client data at all, and it removes messages in the Telegram group only while they are fresh; we do the rest by hand (details below).

• Requests that did not lead to a contract — 12 months from the last contact. Then we delete or anonymise them. In an anonymised record the name, contact, message and technical traces are erased; what remains is the number, time, service, package, page, the previous page of our site, the source site, the campaign tags, the device type and the status: they cannot be used to identify you.
• Client data — while the contract is in force and for 3 more years after it ends (the limitation period). Documents for tax and accounting — as long as the law requires. The automatic clean-up does not touch this data (it skips requests with the status “Won”): we check the period by hand at least once a year and delete what is past its period.
• Spam and test requests — up to 30 days.
• Correspondence by email and in chat apps — there is no fixed period: we keep it while it is needed for working with you. At your request we will delete it on our side, except for what the law requires us to keep (for example documents for tax and accounting). There is no automatic clean-up for it. Copies inside WhatsApp, Telegram, Facebook and Instagram themselves are kept by those services under their own rules.
• Conversations with the AI assistant (messages, the request questionnaire, the hash of the IP address) — up to 90 days from the last message, after which the server deletes them. A request created from a conversation is kept like other requests (the first item of this list). Google’s request log is kept separately. More about it and about our period is in the section “AI assistant on the site and in chat apps”.
• The hash of the IP address — one day in the request counter, up to 90 days in the request itself.
• Browser details and Meta cookie identifiers in the request — up to 90 days.
• Data for sending events to Meta (our server) — the IP address, browser details and Meta cookie identifiers (_fbp, _fbc) sit in the sending queue only until sending: usually seconds, and if Meta does not respond, the server retries for no more than 6 days; after sending or after a refusal by Meta they are erased. For a request from the chat window, this data sits in the chat session until the request is submitted, and if the conversation breaks off, no more than 48 hours after the last message (a request that did not reach the CRM loses it after 7 days). If the nightly database backup is made while the event is waiting to be sent, this data stays in the backup for up to 14 days. The sending log (the number and name of the event, the time, the result) contains no personal data. After that Meta keeps this data under its own policy.
• Record of a request during a database failure — if the database was unavailable, the full record of the request sits in a private file on the server. The record is deleted from the file automatically after 30 days.
• Database backups — made every night on the same server and kept for 14 days. A request we have deleted also disappears from the backups within these 14 days.
• Notifications in the Telegram group — when we delete or anonymise a request, the server also tries to delete its message in the group. Telegram does not allow a bot to delete messages older than two days, so after the retention period the message usually stays in the group. Our CRM shows the list of such requests, and we delete these messages by hand at least once a month, and immediately when you ask us to erase your data.
• Messages from Facebook and Instagram on our server — the beginning of the message is kept only until the notification is sent to the Telegram group (usually seconds; if Telegram does not respond, no longer than a day) and is then erased. The message’s service number, the sender’s number at Meta, the name and the username are kept for up to 30 days, after which the server deletes them itself. Notifications about such messages are deleted from the Telegram group after a month (auto-delete in the group settings).
• Proof of your cookie choice — together with the request, for as long as the request is kept; in your browser — 6 months.
• Cookies — the periods are in the section “Cookies”.
• Google Analytics — 14 months. This is how long the data of users and events is kept (what is tied to the cookie _ga): we set the period in the service settings, and a visitor’s new activity does not extend it. Then Google deletes the data at its next clean-up; summary reports without data about specific visitors remain.
• Microsoft Clarity — up to 30 days and up to 9 months. Visit recordings are available to us for 30 days from the moment of recording; favourite recordings and a random sample — up to 9 months; heatmaps and tags — up to 9 months. Clarity does not delete the data of a single visitor separately (section “Your rights”).
• Server logs (nginx) — IP address, time, page address and browser details: up to 14 days.
• Visit statistics log — up to 7 days: the hour, the page path, the source site, the ad tags and the previous page of our site; without the IP address and browser details. The server deletes old log files itself.
• Totals of visits by day — up to 24 months, without data about you: after the log is processed, only numbers remain (the day, the page, the source site, the tags, the previous page and how many views there were). The server deletes records older than 24 months itself.

7. Your rights

• to find out what data about you we hold, and to get a copy of it (Art. 15);
• to have inaccurate data corrected (Art. 16);
• to have data deleted (Art. 17);
• to restrict processing (Art. 18);
• to receive the data you gave us in a machine-readable form, if we process it under a contract or with your consent (Art. 20);
• to object to processing based on our legitimate interest (Art. 21);
• to withdraw consent at any time with the “Cookie settings” button at the bottom of every page. Withdrawal does not make the processing before it unlawful (Art. 7(3)).

If you withdraw consent to the Meta pixel, the pixel and our server stop sending Meta new events. An event that has already been sent is kept by Meta under its own policy, and we cannot take it back. If the event of your request has not gone yet (for example, because Meta did not respond), write to us: we will delete or anonymise the request, and its events in the sending queue will be cancelled.

If you withdraw consent to “Statistics”, Google Analytics and Microsoft Clarity no longer receive anything from your browser, and the site deletes the cookies _ga, _ga_XXXXXXXXXX, _clck and _clsk. If Clarity was already running on the open page, the page will refresh itself: otherwise Clarity would keep collecting data without cookies for some time. Data that has already been collected stays in the services until the end of the periods (section “How long we keep data”). We do not pass your name, contact or request number to these services, so your data can be found in them only by the identifier from your browser (the cookie _ga or _clck). Clarity cannot delete the data of a single visitor: the only way is to delete the whole project. If you ask us to erase your recordings in Clarity, we can do it only this way; the recordings themselves are kept for a short time.

To use a right, write to hello@delkind.eu. We will reply within a month (Art. 12(3)). We may ask you to confirm that the request was sent by you.

If you believe that we are infringing your rights, you can lodge a complaint with the supervisory authority of Poland — the President of the Personal Data Protection Office (Prezes Urzędu Ochrony Danych Osobowych, UODO), ul. Stawki 2, 00-193 Warszawa, uodo.gov.pl. You can also contact the supervisory authority of the country where you live or work (Art. 77).

8. Automated decisions

We do not make decisions based solely on automated processing that produce legal or similarly significant effects for you (Art. 22). The AI assistant that replies to you in the chat does not make such decisions either: it does not accept payment, does not promise discounts and does not sign a contract. If you allowed the Meta pixel, Meta may use this data (including the events that our server sends) to select ads under its own policy. Google Analytics and Microsoft Clarity are used for statistics and do not make decisions about you; however, Microsoft may use Clarity data to create user profiles under its own policy (section “Who we share data with”).

9. Cookies

Cookies are small files that the site saves in your browser. Browser storage (localStorage and sessionStorage) works in a similar way, so it is described together with cookies below. We may store anything in your browser beyond what is technically necessary only with your consent.

On your first visit the site shows a choice banner, but not at once, so as not to cover the first screen:

• on a computer — when you start scrolling the page or after 15 seconds, as a bar at the bottom;
• on a phone and tablet — when you scroll the page past the buttons of the first screen (for a page that cannot be scrolled, after 30 seconds); if you then go back up to those buttons, the banner moves down and returns when you scroll again;
• while the menu is open on a phone, the banner is hidden;
• the banner does not cover the form button: if you came to the request form and the banner would cover “Send request”, it does not appear until you scroll so that the button is above the banner or off the screen, or until you submit the request; a banner that is already open moves down for that time and then returns. “Cookie settings” in the footer is available at any time.

The buttons “Accept” and “Reject” carry equal weight. Until you press “Accept”, the Meta pixel is not loaded and Meta receives nothing from our site and server. If you allow the pixel, our server duplicates the same events, as described in the section “What data we receive”. If you decline, the site and the request form work exactly the same. Until you allow “Statistics”, Google Analytics and Microsoft Clarity are not loaded, and Google and Microsoft receive nothing from our site.

When you move between pages of the site, the ad tags utm_source, utm_medium, utm_campaign, utm_content and utm_term are passed in the address of the link and are not written to your browser.

Visit statistics (section “What data we receive”) are kept on the server and do not use cookies: they write nothing to your browser and run no scripts on the pages. So they are not in the tables below, and the “Reject” button and the choice for the “Statistics” category do not switch them off: “Statistics” in the banner refers only to Google Analytics and Microsoft Clarity.

Necessary — no consent needed

Marketing — only with consent

Statistics — only with consent

Google Analytics and Clarity can be switched on separately. Microsoft’s cookies on its own domains (CLID, MUID and others) cannot be deleted from our site: delete them in your browser settings.

How to change your choice

Cookie settings

The same button is at the bottom of every page. If you withdraw consent, the pixel will stop loading, our server will stop sending Meta new events, and the site will delete the cookies _fbp and _fbc. If you withdraw consent to “Statistics”, Google Analytics and Clarity will stop loading, and the site will delete the cookies _ga, _ga_XXXXXXXXXX, _clck and _clsk; if needed, the open page will refresh itself. Meta’s own cookies on its domains are deleted in your browser settings or in the Facebook and Instagram settings. You can also delete any cookies in your browser settings.

10. AI assistant on the site and in chat apps

On the site (the “Ask AI” button) and on Telegram (if you write in private messages to @delkind_studio) you are answered by the studio’s AI assistant. It is a program based on a language model, not a person. This is stated in the first message of the conversation and in the header of the chat window (Art. 50 of EU Regulation 2024/1689 on artificial intelligence, the AI Act). The assistant can make mistakes: we confirm an exact quote, timeline and terms in writing. It does not accept payment, does not promise discounts and does not sign a contract: we agree those steps with you separately.

What data

• your messages (on Telegram, including voice messages and images) and the assistant’s replies;
• your name and contact (Telegram, WhatsApp, phone or email), if you write them yourself or leave them at the assistant’s request;
• what you told us about the task, and what the assistant recorded in the request questionnaire: the service, the field of business, the timing, the budget;
• the page you opened the chat from, its language and a random conversation number;
• the hash of your IP address — an irreversible fingerprint of the address, calculated with a secret key. We use it to limit the number of messages and to protect the chat from abuse. The IP address itself is not stored in the conversation database;
• on Telegram — the number and username of your account, which Telegram passes on.

Do not write passport or payment details, passwords or other information that is not needed for your question in the chat.

The chat window remembers a random conversation number in the storage of the browser tab (sessionStorage) until the tab is closed, so that the conversation continues when you move between pages. This is a necessary record for a chat that you opened yourself (it is in the table of the section “Cookies”).

Why and on what legal basis

• To answer your question, suggest a service, give a price guide and prepare a request — Art. 6(1)(b): steps taken at your request before entering into a contract. If you write on behalf of a company — Art. 6(1)(f): our legitimate interest in replying to the company and concluding a contract with it.
• To protect the chat from spam and abuse — Art. 6(1)(f): our legitimate interest in the security of the site.

If you leave a contact or ask us to get in touch, the request goes to our CRM, and a notification about it goes to the Telegram group, in the same way as a request from the form (sections 4 and 5). If you write in the chat window on the site and allowed the Meta pixel, our server will tell Meta that a request has arrived — without your name, contact or the text of the conversation (section “What data we receive”). We do not pass requests from Telegram to Meta.

Who processes it

• Hetzner Online GmbH — conversations are stored on our server in Helsinki (EU), like requests.
• Google LLC (Gemini API, USA) — the only recipient of the assistant’s language model; the assistant uses no other language model providers. Google receives your messages in the chat, the course of the conversation, images if you sent them, and voice messages (on Telegram), and processes them on our behalf to prepare a reply or transcribe the voice: the sound goes to Google, the text comes back into the conversation, and we do not save the recording. Under the terms of the paid Gemini API plan, Google does not use requests and replies to improve its products and processes them under a data processing agreement in which Google acts as a processor (Gemini API terms). At the same time, Google keeps a log of requests and replies for a limited time, only to detect and prevent violations of its prohibited use policies, to ensure the security of the service and to make disclosures required by law or by regulators; the period is 55 days (Gemini API policies on abuse monitoring). Records that automatic filters have flagged as a possible violation may be reviewed by authorised Google staff; such data is not used to train models, except for the models needed to enforce the rules (same place).
• Telegram — it processes correspondence on Telegram under its own rules (section “Who we share data with”). In addition, a draft of the assistant’s reply together with your last message (up to 300 characters) may arrive in our private Telegram group: we read the reply before it is sent.

Transfers outside the EU and the EEA

• Google — Google LLC is in the USA and participates in the EU-US Data Privacy Framework (European Commission adequacy decision of 10 July 2023, Art. 45; Google’s page on the Data Privacy Framework). The fallback mechanism is the EU standard contractual clauses in Google’s data processing terms (Art. 46(2)(c); Google data processing terms). Google may process and temporarily store this data in any country where it, its subcontractors or its agents have facilities (Gemini API terms).
• Telegram — as in the section “Transfers outside the EU and the EEA”: only what is needed to reply to you.

How long we keep it

A conversation (messages, the request questionnaire, the hash of the IP address) is kept for up to 90 days from the last message, after which the server deletes it. A request created from a conversation is kept like other requests: 12 months, then we delete or anonymise it (section “How long we keep data”). We do not save voice messages. Google’s request log is separate; its period is given above, in the list of recipients.

Your rights

The same as in the section “Your rights”. For us to delete your conversation, write to hello@delkind.eu: give your Telegram username or the page of the site and the approximate time you wrote in the chat. You may object to processing based on our legitimate interest (Art. 21) and, if you wish, communicate with us without the assistant — through the request form or by email.

11. Changes to this policy

When the purposes, recipients or periods change, we issue a new version with a new date. The version that applied when a request was sent is kept with the request; we will send earlier versions on request. When we register a company, it will become the data controller, and there will be a new version of the policy.

Version 2.1 dated 22 October 2026.