Privacy Policy, dyniq.ai
Last updated: 14 November 2026
Lees dit beleid in het Nederlands
1. Who is responsible
Dyniq®, KvK 77272471, VAT NL860955357B01, Ceresstraat 13, 4811 CA Breda, the Netherlands. Dyniq is the controller for the data in this notice, except store customer data, where we act as the processor of the store (see section 5). Email: support@dyniq.ai. We have no data protection officer. Contact us at the email above for any privacy question.
2. This website
This site sets no tracking cookie and runs no advertising or analytics script, with two exceptions: the Dutch waitlist page at /telefoon, and the pages of the free trial funnel (the home page, /pilot, /demo-store, /pricing, /managed-ai-support, the pages under /answers/ and /vs/, and this page), and only after you click "Accepteren" in the cookie banner of /telefoon, or click "Accept all" (or "Save choices" with the Marketing switch on) in the cookie bar of the funnel pages. It loads its fonts from this website, not from a font service. The demo chat on the home page sends your messages to our chat service, and when you send your first chat message, the trial request form, the SMS alerts form or the Telefoon waitlist form your browser loads the Cloudflare bot check (Turnstile) from challenges.cloudflare.com. See sections 3 and 4. Our hosting provider, Cloudflare, receives your IP address and technical request data when you load a page, because that is how a website is delivered and kept secure. Legal basis: our legitimate interest in running a secure website (Art. 6(1)(f) GDPR). Cloudflare keeps these technical logs for a short period under its own terms. The Dutch waitlist page at /telefoon is the exception: when it opens, and when you click a button, play a demo call or start the form, it sends a short event to our waitlist service at agent.dyniq.ai. The event holds a random id that lives only in the open page, the page address without its query, the address of the site that sent you (its domain only), and the utm and lead_token values of the link you followed. With each event and with a waitlist signup, our service also stores the labels of the page (its niche, language, version and variant), the country and region that Cloudflare derives from your connection, and the device class (mobile, tablet or desktop), which it reads from your browser's user agent. It stores neither your IP address nor the user agent itself. Before you choose in its cookie banner, the page sets no cookie and stores nothing in your browser.
Links of ours. A link in one of our emails or text messages, and a trial button on a private demo page, can carry a short code of our record of your store (?r= or ?k= in the page address). When you open such a link from outside this website, the page sends that code, the kind of link and the channel of the message (email, SMS or WhatsApp) to our service at agent.dyniq.ai. Our service stores one click event on our record of your store, at most once per code, link and channel in 30 minutes, and nothing for a code it does not know. A reload, a back or forward move and a move within this website send nothing. The note holds no cookie, and the page stores nothing in your browser for it. Our service stores neither your IP address nor the user agent; to stop abuse, a rate limit counts the notes per salted hash of your IP address for one hour. We use the click to see which of our messages are opened. Legal basis: our legitimate interest in following up on our own messages (Art. 6(1)(f) GDPR). We keep the click event as long as our record of your store.
The Telefoon waitlist form on /telefoon asks for your email address and, if you want, one phone number for WhatsApp or for a call. It has no box for the update emails. A line in the form, and at each button lower on the page that starts a signup, asks for your consent to the update emails, and you give that consent when you press such a button. The button in the page header has no line of its own: it brings you to the form with its line and starts the sign-in there. It has two boxes, which start unticked and are optional: one for update WhatsApp messages and one for calls (the paragraph on the call number below says more). Before the form is sent, your browser loads Cloudflare Turnstile from challenges.cloudflare.com to check that you are not a bot. Cloudflare receives your IP address and browser data for that check. We store your email address, your WhatsApp number only when its box is ticked, and, for the email consent and for the WhatsApp box when it is ticked, the time of your consent, the version and the exact text of the line or the box, the page address and a salted hash of your IP address. After you join, the page also asks for your postcode, which is optional. We use it to see in which regions the interest is high, and, only with your consent, we send it hashed to Meta to match our ads. Our event log keeps only its first digit. We keep the postcode as long as your email address: until you ask us to delete your signup. The page can ask for your business address in place of the postcode. It is optional too. While you type it, our agent service sends the text you type to the Google Places API (Google LLC, USA) to get address suggestions, with a random session ID and the country of your connection; Google does not get your IP address from this. When you pick a suggestion, we store the street and number, the postcode, the town and the country of that address, and the ID Google gives the place. We store it at once, also when your email address is not confirmed yet. We use the address to see in which regions the interest is high, and to know where your business is when the service starts in your region. Of the address, only a Belgian postcode goes hashed to Meta, as said above, and our event log holds none of it. We keep the address as long as your email address, and you can remove it on the page. To stop abuse, rate limits count requests per hashed IP address and per hashed email address, as for the trial form in section 4. We then send you one email with a confirm button. Resend (USA) sends it and processes your email address, the content of that email and its email events (for example delivered, bounced or a complaint). The form also has the button Doorgaan met Google. If you click it, your browser opens the sign-in page of Google, and Google LLC (USA) receives your IP address and browser data. Google sends you back to our site with a signed token with your email address and your name. Your browser keeps that token and what you had filled in on the form in session storage, for this tab only, until the form reads it and removes it. Our service checks the token, stores the email address as your waitlist address and stores neither the token nor your name. Google has already checked that address, so we send no email with a confirm button: your place is confirmed at once and you get one welcome email. When you press that button you also give the consent to the update emails that the line at the button asks for. No WhatsApp message is sent until Dyniq switches these messages on. Legal basis: your consent (Art. 6(1)(a) GDPR). You can withdraw it at any time with the unsubscribe link in an update email, by replying STOP on WhatsApp, or by emailing support@dyniq.ai. We keep the signup and its consent record until you ask us to delete it, and then only as long as the law needs us to keep proof of consent. The call number is the exception: see the next paragraphs.
The report page /telefoon/rapport asks the same questions and shows an estimate. To get the full report, you give your email address and your mobile phone number (required, see the paragraph on the call number below). The form has two boxes, which start unticked and are optional: one for the update emails, and one for sharing your request with our advertising partners (see "The report and Meta" below). Before the request is sent, your browser loads Cloudflare Turnstile, as for the waitlist form. We store your email address as a waitlist signup, and with it your request: your answers to the questions the report uses, the state of the box, the time of the request and, when you click the button in our email, the time of that click. For a new signup, the page then also sends the answers it kept, as the questions on /telefoon do after a signup: for each of the five questions your answer or that you skipped it, the estimate it showed with the share you chose, and the price band you picked. We store them with your signup. When the box is ticked, we also store the time of your consent, the version and the exact text of the box, the page address and a salted hash of your IP address. We then send you one email with a button to a short web version of your report, which has a button to download it as a PDF file. Resend (USA) sends it, as above. We also count the steps of the report (requested, email sent, web version opened, PDF downloaded, link to the waitlist clicked) as anonymous numbers, with only the utm_source of your link: no email address, no id of you and no IP address. If you clicked "Accepteren", our server also sends Meta the event of your request, as for joining the waitlist (see Meta on /telefoon below). Without the box we send you no other email. With the box, your click on that button also confirms your waitlist signup, and the update emails follow. The rate limits and the rules for keeping and deleting your data are those of the waitlist signup above. Legal basis: your request for the report (Art. 6(1)(b) GDPR), and your consent for the update emails (Art. 6(1)(a) GDPR).
The call number. On /telefoon you can type one phone number for WhatsApp or for a call, and tick a separate box for each. The box for calls starts unticked and says: "Ja, Dyniq mag mij op het nummer hierboven bellen over mijn inschrijving voor de AI-telefonist, tot ik dat stop. Stoppen kan met de uitschrijflink in een mail of door het aan de telefoon te zeggen." On /telefoon/rapport the number is required to get the report and has no box. The form says beside the field: "Uw nummer gebruiken we alleen om u hoogstens één keer te bellen over uw rapport." We call only numbers in Belgium (+32) and the Netherlands (+31). We store the number with your signup, and for the consent we store the time, the version, the exact text, the page address and a salted hash of your IP address, as above. We use the number only so that the founder of Dyniq can call you: about your signup (the box on /telefoon) or once about your report (the number on /telefoon/rapport). We do not send it to Meta, and we do not use it to send you texts or WhatsApp messages. Once you have confirmed your email address, our service also posts a short alert with that number, and no email address and no name, in a private Slack channel of Dyniq, so that the call can start soon after. You confirm your address with the button in the confirmation email, with the button "Bekijk uw rapport" in the report email, or by signing in with Google. Until then we post nothing. On /telefoon/rapport the alert also holds the answers you gave for the report (such as your trade and the number of calls a week), so that the call can start from your report. The alert also says how many people we called that day, and whether we already called this number before. Slack (USA) processes that alert. Legal basis: your consent (Art. 6(1)(a) GDPR). You can withdraw it at any time: with the unsubscribe link in an update email, by saying so on the phone, or by emailing support@dyniq.ai. When you withdraw, your signup loses the number at once, and so does a signup that nobody confirms and that we erase after 30 days. In every case we remove the number 90 days after you gave it: from your signup and from the consent record. The consent record then stays without the number, with the time, the version, the text, the page address and the hashed IP address, as proof of your consent.
Meta on /telefoon. The page asks first, with two equal buttons. If you click "Weigeren", we set one cookie, dyniq_consent, that remembers your choice for 6 months, and nothing from Meta loads. If you click "Accepteren", we set dyniq_consent, the page sets the Meta cookies _fbp and, when you came through a Meta ad, _fbc, both for 90 days, and your browser loads the Meta pixel from Meta Platforms Ireland Limited. The pixel sends Meta data about your visit, such as the page address with its query and your signup, with your IP address and browser data. When you then join the waitlist, request the report on /telefoon/rapport, confirm your email address or finish the questions, our server also sends that event to Meta: your email address, your WhatsApp number if you gave one, your postcode if you gave one, our random id of your signup and the country, all hashed with SHA-256, plus your IP address, your browser's user agent, the page address, the Meta cookies and the Meta ad click id of the link you followed. For the finished questions it also sends two of your answers: your trade and your price band. We store the time of your consent with your signup. After you click "Accepteren", the page also sends our waitlist service a short note of the Meta page view: the same random event id the pixel got, the page address without its query and the utm values of your link. For each event our server sends to Meta, we store one status row: whether Meta took it and which kinds of data it carried, never the values. These notes and rows hold no IP address and no user agent. A status row of a waitlist event carries our random id of your signup. Our server never sends the utm values of your link to Meta, but the page address that the pixel sends can hold them. We use this data to measure and improve our ads on Facebook and Instagram. The legal basis is your consent (Art. 6(1)(a) GDPR and the cookie rules of the ePrivacy Directive). Meta acts as a joint controller for the collection and as controller for its own further use, and can transfer data to the USA under the EU-US Data Privacy Framework. You can withdraw your consent at any time: click "Cookie-instellingen" at the bottom of /telefoon and choose "Weigeren". The page then reloads without the pixel and removes the Meta cookies, and our server sends no more events for requests from that browser. To stop all events about your signup, also from another device, email us. The events for joining and for the confirmed address also say which way you joined. If you joined with Sign in with Google, these two events also hold your first and last name, hashed with SHA-256.
The report and Meta. On /telefoon/rapport the form has a second box, which starts unticked and is optional. It is shown only while your cookie choice is not "Accepteren", because with "Accepteren" you have already agreed to our advertising partners. It says: "Ja, Dyniq mag mijn aanvraag delen met zijn advertentiepartners, zodat onze advertenties beter de juiste vakmensen bereiken." The word "advertentiepartners" links to the partner list in the cookie settings, which names Meta. Meta here is Meta Platforms Ireland Limited. The box takes effect only when we have switched this feature on, and a tick before that is not stored. The report never depends on this box, and the box sets no cookie and loads no pixel script. When you tick it, we store the time, the version and the exact text of the box with your request. Our server may then send Meta events about that one request, through the Meta Conversions API, and only while the box is ticked and not withdrawn: it checks this again just before each event. The events are your request (Lead), the first time you open the web version of your report (ViewContent), your PDF download (ReportDownload, once for each request), your confirmation with the button in the report email when you ticked the update box (CompleteRegistration), and the payment of a deposit for Dyniq Telefoon, if you pay one (Purchase). Each event carries the hashed email address, our random id of your signup, the country, your IP address and your browser's user agent, as above, plus the word "rapport" as the funnel (the Purchase comes from our payment service and carries no country, no IP address and no user agent). Without "Accepteren" it carries no Meta cookie value. Some events carry a number in euro: the Lead a value in four steps from 5 to 100, set from the estimate that your answers give; the confirmation with the button in the report email a fixed value of 22.41; the deposit the amount paid. The number only says how large a lead looks. These events carry no trade and no single answer, and the utm values of your link go to none of them. Your click on the button of the web version to join the waitlist is stored in our database only, and we send Meta no event about opening an email. If you clicked "Accepteren" and did not tick the box, the same events can go on the basis of "Accepteren" instead. "Weigeren" stops the events that come from your browser. A deposit event uses the consent that we stored with your signup. It stops only after you withdraw that consent by email, or after you confirm with "Weigeren". Meta acts as a joint controller for the collection of this data and as controller for its own further use, as above. The legal basis is your consent (Art. 6(1)(a) GDPR). You can withdraw it at any time, and you have the right to object: email support@dyniq.ai, and our server sends no more events about your request. Events that Meta already has stay with Meta. We keep the consent record and the status rows of these events as for the other Meta events above, and the request and its consent go when your signup is erased, under the rules above. Resend (USA) sends the report email as a processor.
Meta's lead form for Telefoon. If you join through our ad on Facebook or Instagram, Meta's form asks for your email address and your trade, and Meta can fill in your email address from your profile. The form has one box, which starts unticked, for the update emails. When you send the form, Meta notifies our waitlist service at agent.dyniq.ai, which then reads your entry from Meta into our database. Once a night we also read the new entries from Meta, so an entry whose notice did not arrive is stored too. We store your email address, your answer, the ids of the ad and the form, the time, and the text of the box you ticked. We use this to put you on the waitlist and to send the update emails. Legal basis: your consent (Art. 6(1)(a) GDPR). We send you one email with a confirm button, and update emails start only after you confirm. Resend (USA) sends these emails and processes your email address, the content of each email and its email events (for example delivered, bounced or a complaint). If you do not confirm, we delete your email address and your answer after 30 days. You can ask us to delete your data at any time. Meta runs the form and also processes your data for its own purposes, under its own privacy policy.
Meta on the free trial pages. These pages ask first, in a bar at the bottom of the page with two equal buttons. You can use the page without answering, and until you choose, nothing from Meta loads. A "Customize" screen shows the two categories, "Strictly necessary" (always active: it holds only your cookie choice) and "Marketing" (the cookies of our advertising partner Meta Platforms Ireland Limited, off until you switch it on), and three equal buttons, "Reject all", "Save choices" and "Accept all". "Save choices" counts as "Accept all" when the Marketing switch is on and as "Reject all" when it is off. If you click "Reject all", we set one cookie, dyniq_consent_pilot, that remembers your choice for 12 months, and nothing from Meta loads. If your browser sends a Global Privacy Control (GPC) signal and you have not chosen on these pages, we treat it as "Reject all": no cookie bar appears and nothing from Meta loads. If you then click "Accept all" in Cookie settings, we treat that click as your choice. If you click "Accept all", we set dyniq_consent_pilot, the page sets the Meta cookies _fbp and, when you came through a Meta ad, _fbc, both for 90 days, and your browser loads the Meta pixel from Meta Platforms Ireland Limited. The pixel sends Meta data about your visit, such as the page address with its query, with your IP address and browser data. After you accept, our own server also keeps a note of each event on these pages: a page view, a section you viewed, a click on a button, how far you scrolled (half way and 90 percent), the opening of the chat, a message count of the chat (never the text you type) and the steps of the free trial form. A note holds the page path without its query, the name of the button or section, a random event id, a random id kept for the open browser tab, the utm values and the referring site of your link, the country that Cloudflare derives from your connection, the device class (mobile, tablet or desktop) that our server reads from the user agent of your browser, whether your link carried a Meta click id, your cookie choice, whether you accepted while your browser sent a Global Privacy Control signal, and the time, with no IP address, no user agent and no email address. If you click "Accept all" (or "Save choices" with the Marketing switch on), the page also sets one first-party cookie, dyniq_visitor, a random id for 180 days, and the notes then carry that id, so we can tell that several visits come from the same browser. We remove that id from the notes after 180 days, and sooner if you email us to delete your data and you sent a free trial request from that browser after you accepted; the notes without it stay, as counts. Also then, for a page view, a section viewed, a button click, the opening of the chat and a chat message, our server sends the same event to Meta with the same event id as the pixel, so Meta counts it once: the visitor id hashed with SHA-256 and the country hashed, plus your IP address, your browser's user agent, the page address without its query, the Meta cookies and the Meta ad click id of the link you followed. After "Reject all", or with no choice, the page sends no notes and nothing goes to Meta. Only a free trial request, if you send one, leaves one note, with the id of that request. When you send the free trial request, your browser tells Meta, and our server also sends a Lead event to Meta: your work email address, your mobile or WhatsApp number if you gave one, your first name, your last name if you signed in with Google, our random id of the request and the country your connection comes from, all hashed with SHA-256, plus your IP address, your browser's user agent, the page address, the Meta cookies, the Meta ad click id of the link you followed and whether you signed in with Google or with your email. If you accepted, we keep your IP address, your user agent, the Meta cookies and the Meta ad click id with the request for 90 days, the life of the Meta cookies, so that a later event about your request can be sent to Meta, and then delete them. The page also keeps the id of that request in your browser's local storage, under the name dyniq.pilot_requests, for 90 days, so that you can withdraw your consent for the request (see below). If you accepted and then book the kick-off call of your free trial within those 90 days, our server sends Meta a Schedule event about your request: your email address hashed with SHA-256, plus the IP address, user agent, Meta cookies and Meta ad click id we kept with the request. If you accepted and then book the results call of your free trial within those 90 days, our server also sends Meta one ResultsCallBooked event about your request, with the same data. It sends nothing you typed in the booking. If you accepted, the request also keeps the dyniq_visitor id and the utm values and referring sites of your first and last visit, and we delete them with the request. Our server never sends the utm values of your link to Meta, but the page address that the pixel sends can hold them. We use this data to measure and improve our ads on Facebook and Instagram. The legal basis is your consent (Art. 6(1)(a) GDPR and the cookie rules of the ePrivacy Directive). Meta acts as a joint controller for the collection and as controller for its own further use, and can transfer data to the USA under the EU-US Data Privacy Framework. A visit through a private demo link gets no banner and sends nothing to Meta. For every free trial request, whatever you chose, we also store a record of the event: its id, the time, whether you accepted, declined or made no choice, whether you accepted while your browser sent a Global Privacy Control signal, the utm values of your link and, for each key we sent to Meta, only yes or no, never the value. Legal basis for that record: our legitimate interest in knowing how many requests come with and without consent (Art. 6(1)(f) GDPR). We delete it with the request, under the retention rule below. You can withdraw your consent at any time: click "Cookie settings" at the bottom of any of these pages and choose "Reject all". The page then reloads without the pixel and removes the Meta cookies and dyniq_visitor. Just before it reloads, it tells our server the ids of the free trial requests you sent from this browser while you had accepted. It keeps those ids in your browser until our server has confirmed, and repeats the call on each later visit to these pages until it has. For each of those requests we then delete the IP address, user agent, Meta cookies and Meta ad click id that we kept with it, and our server sends no more events about it to Meta, a Schedule or ResultsCallBooked event included. To stop all events about your request, also from another device, or if your browser does not allow local storage, email us.
3. The chat on this site
The chat on the home page is a demo with a fictional store and dummy data. It is for business users aged 16 and over. Do not type real personal data.
A private demo for one store, at dyniq.ai/demo/ followed by a long code, uses the same chat service. It answers only from that store's public Refund policy, Shipping policy and Terms of service pages. It has no order data. When the page opens, we store the time, the channel and the short code of the link, and the store the demo is for. If the page address had utm_source, utm_medium, utm_campaign or utm_content values, we store those four values with it to see which link brought you.
Before your message is stored or sent to anyone, email addresses and card numbers in it are masked, and so are phone numbers that start with +, 0 or a bracket. An email address you type is used only to look up the demo order, during that one request. The masked message, the earlier messages of the chat and the demo store data go to Anthropic (a US company, with standard contractual clauses) to write the reply. TypeSafe (Jev, a US company, with standard contractual clauses) gets two things. To route the question, it gets your masked message and up to 3 earlier masked messages. To check the reply before you see it, it gets all the masked messages you sent in the chat, the draft reply, and the store and order data that the reply relies on.
Conversations are stored in the EU with Supabase (Ireland). Cloudflare runs the chat service and the bot check, and can process the text in its network outside the EU. When you send your first message, your browser loads Cloudflare Turnstile from challenges.cloudflare.com to check that a person, not a bot, is chatting. Cloudflare receives your IP address and browser data for that check.
To monitor quality, each reply writes one trace to our own Langfuse server (langfuse.dyniq.ai). A trace holds no message text. It holds a salted hash prefix of the chat and of the visitor, which are pseudonymous IDs, the message length, the cost, the outcome and the number of tools used. A nightly job deletes traces older than 30 days. That server runs on a rented server (VPS) from Contabo in Germany.
After an answer the chat asks "Did that answer your question?". Your Yes or No is stored with that answer, holds no text, and goes when the chat goes. When you ask for a person, the chat first sums up your question and asks you to confirm it. After you confirm, a hand-off is made. On a real store, the store's team then gets an email with the last 6 messages of the chat and replies by email. An urgent matter, such as a chargeback, a legal threat, an injury, an allergy, a request about your personal data or a change of payment or address, is handed off at once. In this demo, nothing goes to a store and nobody replies, and a hand-off here sends no message text anywhere. On a real store a hand-off needs your email address, because the team can only reply by email, and for a question about one order also your order number. The chat asks for them only when it has none for this chat, and it passes nothing on without them. An address you type in a message can be kept in the memory of that chat on our server, so that a hand-off or an order lookup a few messages later can use it. The chat keeps an address from a message only when it is the one valid address in that message that is not on a header line of a pasted email and is not the store's hand-off address. It becomes the contact address of the chat only when a hand-off is made. The address you type in the form is stored with the chat at once. The address you type in the form is used only so the store team can reply. The address you type in a message is used only for that reply and for an order lookup in the same chat. Neither address is put in our logs. The memory of the chat goes when the chat goes. The demo chat has no address form and keeps no address.
Retention: chats are deleted 30 days after the last message, with their feedback answers and the email address you typed for a reply. The "Delete my chat" button deletes the conversation, its feedback, that email address and its memory on our server at once.
By default the chat stays in your browser tab only (session storage). Only after you press "Remember this chat on this device for 30 days" does our chat service set a cookie, dyniq_vid, with a random visitor ID (30 days, not used for tracking), and your browser keeps a copy of the chat in local storage for 30 days, so that you and the assistant can continue it.
Security: to stop abuse, rate limits count requests per hashed IP address. These counters are deleted after 2 days.
The chat opens from a button at the bottom right. A small greeting bubble above the button shows once. When it shows, or when you open the chat, two flags, dyniq-assistant-greeted and dyniq-assistant-greeting-read, are stored in your browser local storage, so the bubble does not show again and its unread badge goes once you open the chat. They hold no personal data: each holds only a 0 or a 1.
Dyniq does not use demo chats to train or tune models.
Legal basis: our legitimate interest in showing the product to businesses and keeping the service secure (Art. 6(1)(f)). The remember feature only runs when you ask for it.
4. The trial request form
The form has five screens and saves your request in steps. Screen 1 is the sign-in, and nothing you type there is stored. When you first click or type in the form, the page asks our agent service (run by Cloudflare) which country your connection comes from, so it can fill in the country on screen 2. That call sends nothing you typed. If you sign in with Google, the page sends the Google token to the same service, as the paragraph on Sign in with Google below says. When you press Continue on screen 2, your email address and store web address go to our agent service and are stored in our database (Supabase, Ireland, EU). When you press Continue on screens 3 and 4 and the button of screen 5, the answers you gave (what you do, the country of your store, support questions a month, how you answer them today, the tool you use, whether you decide, your first name, and the optional numbers of screen 5) are added to the same request. The first name, the tool and the numbers are optional; the other answers are needed to go on. Before screen 2 is sent, your browser loads Cloudflare Turnstile from challenges.cloudflare.com to check that you are not a bot. Cloudflare receives your IP address and browser data for that check. To stop abuse, rate limits count requests per hashed IP address and per hashed email address. These counters are deleted after 2 days. If the page address had utm_source, utm_medium, utm_campaign or utm_content values, the form also sends those four values, and we store them with the request to see which link brought you.
The form is on the page dyniq.ai/pilot. Nothing you type is stored before you press Continue on screen 2. If you leave after screen 2, we keep what screen 2 sent, and the trial emails start from screen 2, under the retention rule below. If you type your work email in the dark band at the bottom of the home page and press its button, your browser keeps that email in session storage, for this tab only, until the trial page reads it and removes it. The email is not put in the page address and is not sent anywhere at that point. The country list of the phone fields loads one flag image file from this website when you open the list.
We send you a confirmation email when screen 2 is saved. We send ourselves a copy of the request through Resend, with the form fields the request holds at that moment, and a second copy with all of them if you send the last screen. These are service emails about the request you made.
You can sign in with Google on screen 1. When you click "Continue with Google", your browser opens the sign-in page of Google, and Google receives your IP address and browser data. Google then sends you back to our site with a signed token with your name, email address and Google account id, and it may hold other profile details, such as a link to your profile picture, which we ignore. Your browser keeps that token and what you had typed on the form in session storage, for this tab only, until the form reads it and removes it. Our agent service checks the token and reads your email address, first name and last name from it. The email address becomes the address of your request and the first name its first name, and we store both with the request. We do not store your last name or your Google account id, and we ask Google for nothing else, such as your contacts or your calendar. Google handles its part under its own terms. If you accepted marketing cookies, the Meta paragraph of this notice says what the Lead event holds.
The form also has an optional mobile number and an optional WhatsApp number. We use them only to contact you about your trial. We store them with the trial request, and they are also in the copy of the request we send ourselves. We delete them with the request, under the retention rule below. They are not consent to any message. Section 12 covers the two optional marketing boxes.
The trial emails are part of the trial you ask for: 7 emails over 14 days, during the 7-day trial and the week after it, about the setup, the first answers and the results. The form tells you this before you send it, and we store the form version and the exact text of that notice. Each trial email has an unsubscribe link. You can also stop them by email to support@dyniq.ai.
Before 29 October 2026 the form had a box for the trial emails. For a request sent with the box ticked, the trial emails started only after you pressed the confirm button on the page that the confirmation email linked to. As the record of that consent we keep the time, the form version, the exact text of the box and the time you pressed the button. For the confirm link we stored only a hash of its token.
Resend processes your email address, your first name and the email events (for example delivered, bounced or a complaint), and the content of the emails it sends: the confirmation email and our copies of the request, which hold the form fields the request has, your first name among them when you gave it. When the trial emails start, which is when screen 2 is saved, Resend also receives your store web address as the start signal. The start signal holds no first name, so the trial emails greet you with "Hi there". It sends from the EU (Ireland) and stores account and contact data in the USA. Each trial email has an unsubscribe link.
When you book a call through our booking page, our server receives the booking and keeps one note of it, with the id of your free trial request if the booking belongs to one. The note holds no name, email address or message.
Purpose: to answer your request and run the trial you ask for. Legal basis: steps you ask for before a contract (Art. 6(1)(b)) for the request, the service emails and the trial emails, and our legitimate interest in replying to business enquiries (Art. 6(1)(f)). For a request sent with the old box ticked: your consent (Art. 6(1)(a)), which you can withdraw at any time.
If you start a trial, we ask for access to store data that you choose to share (for example past customer questions and your policies). Those questions may contain personal data of your customers. For that data you are the controller and we act as your processor. We will agree a data processing agreement with you before we handle it. We do not need or want customer payment card data.
Retention: we delete the request and the Resend contact 6 months after your last request (the nightly job may take a few days more). If a store installs the Dyniq app from Shopify, its data follows the retention rules in section 5: chats are deleted 30 days after the last message and orders 12 months after the order date. If a chat that shows the order is still running then, we keep the order until that chat is deleted, 30 days after its last message. Shopify sends an erase request for a store about 48 hours after the uninstall. When it arrives we delete the data of the store, unless the store installed the app again. Customer account and invoice records are kept as long as Dutch tax law requires (currently 7 years).
5. Store customer data (Shopify stores)
When a store installs the Dyniq app from Shopify, the store is the controller of the data of its customers, and Dyniq is its processor. We use this data only for the purposes below. The data processing agreement is published at dyniq.ai/legal/merchant-dpa. The store owner accepts it in the Dyniq app before the chat can go live. Questions about it: support@dyniq.ai.
The data comes from two places: Shopify, through the access the store grants, and the customer in the chat. From Shopify we receive order data (order number, date, status, country, lines, amounts, refunds, payment method name and tracking), the customer's email address and first name, and the store's policies and pages. We store the email address of an order only as a keyed hash (HMAC-SHA256), never in plain form, and use it only to match the order lookup. We store the first name with the order. We do not read the last name, phone number, street address, payment card data, gift message, discount code or order note of a customer. From the customer we receive the chat messages. Before a message is stored or sent to our model provider, email addresses and card numbers in it are masked. So are phone numbers that start with +, 0 or a bracket. The one exception is an address typed in the chat, kept for a hand-off (see below).
We use this data only to answer the customer in the store chat, to look up the customer's own order after the customer gives the order number and the matching email address, to hand the customer to a person at the store, and to keep the service safe. We do not sell it.
Retention: orders from Shopify are deleted by a nightly job 12 months after the order date, with their lines and the first name, or earlier when Shopify sends an erase request. If a chat that shows the order is still running then, we keep the order until that chat is deleted, 30 days after its last message. Each read of a customer's order data by the chat, and each export for a data request, writes a row to an access log. The row holds the time, the store, who read it, the database role and the order id. It holds no email address and no name. We keep the log for 12 months.
After a verified order lookup, the customer's first name goes to our model provider, Anthropic, so the reply can use it. It does not go to the reply check service (TypeSafe) or to our quality traces. The email address is never sent to Anthropic. The services that process store customer data are listed at dyniq.ai/sub-processors.
In short, this is what the chat that Dyniq® runs in a Shopify store processes. The store is the controller and Dyniq® is its processor, as said above.
- What we read from orders. The app copies the orders of the last 60 days from Shopify. When a customer gives an order number and an email address that match no copied order, the app can ask Shopify for that order, if the store has approved access to older orders. It keeps the order only when the email address matches and the order is less than about 11 months old. It reads the same fields as for a copied order. From these orders we read the order email address, the first name and the country code of the shipping or billing address, with the order data listed above. We read no customer record: the app has no access to customers in Shopify. We read no last name, street address, phone number or order note.
- What we store. The order email address is stored only as a keyed hash (HMAC-SHA256), never in plain form, and the key is kept outside the database. The first name is stored with the order, at most 40 characters. The country code is used for the store's return rules.
- Why. A customer gets the status of an order in the store chat only when the order number and the email address typed in the chat match the same order.
- The chat text. Email addresses and card numbers are masked before the model sees the text, and so are phone numbers that start with +, 0 or a bracket.
- An email address typed in the chat. It is used for an order lookup in the message that holds it. When a later message in the same chat asks about an order and holds no email address, the newest address that the chat kept from an earlier message of the customer is used for the lookup. The chat keeps an address from a message only when it is the one valid address in that message that is not on a header line of a pasted email and is not the store's hand-off address. An address from another chat or another store is never used. The address can stay in the stored memory of that chat in our database, so that a hand-off to the store team or a later order lookup can use it. When a hand-off is made, the address is saved with the chat as its contact address if the chat has none, kept with the hand-off, and shown to the store team in the hand-off email. All of it is deleted with the chat, except the copy in the email the store team received.
- Our model provider. Anthropic gets the masked chat text. After a verified order lookup it also gets the result of that lookup. That holds order fields such as the order number, status, dates, country, carrier and tracking, payment status, shipping cost and the cancel reason. It also holds refunds and returns with the name of the payment method, the order lines with titles, SKUs, quantities, prices and return eligibility, and the first name. Anthropic sees a placeholder, not an email address.
- Retention. A nightly job deletes Shopify order data 12 months after the order date and chat data 30 days after the last message. If a chat that shows the order is still running then, we keep the order until that chat is deleted, 30 days after its last message. The app handles the three Shopify privacy requests: customer data request, customer redact and shop redact. Shopify sends the shop redact request about 48 hours after an uninstall.
A customer who wants access to, correction of or deletion of their data should ask the store first. We help the store answer. You can also email support@dyniq.ai, and we pass the request to the store.
6. Data protection summary for Shopify review
This is a short answer to each data protection question for protected customer data in a Shopify store.
- Purpose and minimum data. The chat answers customer questions and looks up one order for the customer who gives its number and the matching email address. It reads order data, the first name, the email address (stored only as a keyed hash) and chat messages. It does not read the last name, phone number, street address or payment card data.
- Limiting use to that purpose. Dyniq uses customer data only for the chat and for security. Section 5 says what we use it for, and dyniq.ai/sub-processors says what each provider receives.
- Agreement with the store. The data processing agreement is published at dyniq.ai/legal/merchant-dpa. The store owner accepts it in the Dyniq app before the chat can go live.
- No sale. Dyniq does not sell customer data.
- Automated decisions. The chat cannot issue refunds, cancel or change orders, or create discount codes. A customer can ask for a person at any time, and the store team replies by email.
- Retention. Chats are deleted 30 days after the last message. Orders from Shopify are deleted 12 months after the order date. If a chat that shows the order is still running then, we keep the order until that chat is deleted, 30 days after its last message. The access log of reads of order data is kept 12 months. Quality traces are deleted after 30 days. Shopify access tokens are deleted when the store uninstalls the app and Shopify confirms the access has ended. A data export link expires after 7 days.
- Shopify privacy webhooks.
customers/redactdeletes the orders of that customer and the chats linked to the customer.shop/redactdeletes the data of the store.customers/data_requestemails the store's hand-off address a link to a copy of the customer's data, valid for 7 days. We check each request with the Shopify signature. - Encryption. Dyniq's services and the Shopify webhooks use HTTPS. Shopify access tokens are encrypted with AES-256-GCM.
- Test and production data. The demo store and the automated tests use fictional data. Real stores and the demo store share one database, separated by store id and row level security.
- Data loss prevention. Row level security per store, separate database roles, redaction of tokens and secrets in logs, secret scanning on each change, masking of emails, card numbers and phone numbers in messages, an access log of each read of order data, rate limits, a daily spend cap and a kill switch.
- Staff access. One person runs Dyniq and is the only person with access to production systems.
7. SMS alerts for store owners
A store owner can ask for hand-off alerts by SMS at dyniq.ai/sms-alerts. Dyniq®, KvK 77272471, is responsible for this data. We keep four things: the mobile number you enter, the time of your consent, the version of the consent text you saw, and the time you confirmed. The form also takes your store's hand-off email address. We use it only to find your store and to send the confirm link. We use the number only to send you hand-off alerts. If the page address had utm_source, utm_medium, utm_campaign or utm_content values, the form also sends those four values, and we store them with the request to see which link brought you.
Nothing is sent until you confirm. When you send the form, the number is held as an unconfirmed request, and we send a confirm link to the store's hand-off email address. The link works once and for 7 days. It opens a page with a button, and the number counts as confirmed only after you press that button. A request for a new number does not replace a confirmed one until its own link is used.
An alert is one SMS when a shopper is handed to a person at your store. It names the store, the reason, the priority and the reply time, and holds no shopper email, name or order number. We send up to 10 a day for a store. Message and data rates may apply. Reply STOP to opt out and HELP for help. Alerts begin once Dyniq has switched SMS alerts on.
We do not share SMS opt-in data or personal information with third parties for marketing purposes. Twilio (USA) delivers the SMS and so receives the number and the text of each alert. When you get alerts on WhatsApp and tap "Reply here", Twilio also carries the case summary, the last 3 shopper messages and the answer you type, which we email to the shopper. The shopper messages are masked as listed at dyniq.ai/sub-processors. Resend (USA) sends the confirm email. Cloudflare checks the form with Turnstile and counts requests per hashed IP address and per hashed email address, as in section 4.
Retention: we keep the number, the consent time, the consent text version and the campaign source values as long as the store is a Dyniq store, and they are deleted with the store data. Email support@dyniq.ai to have them deleted earlier. Legal basis: your consent (Art. 6(1)(a) GDPR), which you can withdraw at any time by replying STOP or by email.
8. Where our business contact details come from (outreach)
We sometimes email store owners and businesses we think may benefit from Dyniq. We take business contact details only from public sources, such as the store's own website, its contact page, or the owner's public business profile. We do not buy lists. We send only to business addresses, we send a small number of messages, and every message says who we are and how to stop.
What we keep about a business we contact: the business email address, the store name and web address, one public fact from its policy pages that the email mentions, where and when we found the address, and the emails we sent and received. We send these emails from mailboxes on askdyniq.com, dyniqpro.com and hellodyniq.com.
Retention: if you do not reply or do not start a conversation with us, we delete your details 6 months after our last email. If you reply, we keep the conversation as long as we are in contact, and at most 6 months after the last message.
Purpose: to tell a business about a relevant service. Legal basis: our legitimate interest in business to business promotion (Art. 6(1)(f)). We do not claim your consent, and we do not rely on consent for outreach. We balanced this interest against yours: you are contacted in your business role, about a service related to your business, and you can object at any time with a single reply.
Before we email a business, we check the rules of its country. We do not send cold email where the law needs prior consent.
We keep a suppression list with the addresses of people who asked us to stop, so that we do not contact them again. It holds a keyed hash of your email address, the date, the reason and, for an opt-out of a whole domain, the domain. It does not hold the address itself. We keep it for as long as we send outreach emails. After an opt-out, the suppression record is the only thing we keep about you as a contact. Your other details and our emails are deleted after the retention period above.
Opt out: reply "stop" to the email, or use the unsubscribe link in the email when it has one. We then stop emailing you and do not ask for a reason. You can also email support@dyniq.ai; we stop when we read your message. We tell you the source of your address if you ask.
9. Who receives data
Zoho Mail (email to support@dyniq.ai, EU data centre), Google (Google Workspace, the mailboxes we send outreach emails from; Ireland, with processing also in the USA; Google LLC, USA, also runs Sign in with Google, which opens only if you click Continue with Google on the trial request form or Doorgaan met Google on the Telefoon waitlist form), Instantly (Foo Monk, LLC, USA, to schedule outreach emails and stop them when you reply; it stores data in the USA), Cloudflare (hosting, the chat, trial request, SMS sign-up and waitlist service and the bot check), Contabo (Contabo GmbH, Germany, hosting of our own Langfuse server for quality traces, which hold no message text), Slack (USA, our internal alerts, which hold reason codes and store ids, the alerts for a call, which hold the phone number to call, the answers given for the report and no email address, and the approval of replies to outreach emails and texts, which holds the text of the reply of the business contact), Apify (Czech Republic, EU, to find public business contact pages for outreach), Anthropic (USA, to draft answers during a trial and to write the demo chat replies), TypeSafe (USA, to route questions and check replies in the demo chat), Twilio (USA, to send the SMS alerts), Meta Platforms Ireland (advertising measurement, only after consent on /telefoon or on the free trial pages), Supabase (Ireland, EU, to store demo chats, trial requests, SMS alert sign-ups and waitlist signups) and Resend (USA, to send the trial request emails, the SMS confirm email and the waitlist emails; it stores account and contact data in the USA). For store customer data, the full list of services is at dyniq.ai/sub-processors. We do not sell personal data for money. Section 11 says more for US residents. If a provider is outside the EU/EEA, we rely on a transfer mechanism such as the EU-US Data Privacy Framework or standard contractual clauses. Email us for a copy of the safeguards.
10. Your rights
You can ask for access, correction, deletion, restriction or a copy of your data, and you can object to processing based on legitimate interest, including all outreach. Email support@dyniq.ai. We answer within one month. You can complain to the Dutch Data Protection Authority, Autoriteit Persoonsgegevens (www.autoriteitpersoonsgegevens.nl) or to the authority in your own country.
11. US residents
In the last 12 months we collected these categories of personal information: identifiers (email address, name, phone number, IP address, cookie ids and our request ids); professional information (your store web address, your role, your say in the purchase, your support volume and your support tool); internet activity on the free trial pages (the events listed in section 2); the messages you send in the demo chat, when it is on; and the approximate location (country) that our host derives from your connection. Sections 2 to 9 say where each comes from, why we use it and how long we keep it.
We do not sell personal information for money. Only after you click "Accept all" (on the Dutch page /telefoon, "Accepteren"), we give Meta data about your visit and your free trial request (on /telefoon, your waitlist signup) to measure our ads. Some US state laws call this "selling" or "sharing". You can stop it at any time with Your Privacy Choices at the bottom of the free trial pages listed in section 2 (on /telefoon, with "Cookie-instellingen"). On the free trial pages, if your browser sends a Global Privacy Control signal and you have not chosen, we treat it as a request to opt out.
You can ask to know, delete or correct your personal information and to opt out of its sale or sharing. We will not treat you differently because you used these rights. Email support@dyniq.ai. An authorized agent can ask for you. We may ask you to confirm the email address the data is about. We answer within 45 days. If we refuse, reply to our answer to appeal.
12. Marketing texts and WhatsApp messages (optional)
This section is about marketing text messages and marketing WhatsApp messages. It is separate from the SMS alerts for store owners in section 7, which it does not change. On the trial request form and on a private demo page you can give a phone number and tick one or two separate boxes: one for marketing text messages and one for marketing WhatsApp messages. Both boxes start unticked and both are optional. The mobile number on the trial form is for your trial contact only. It is not consent to text you, and consent to our emails is never consent to texts or WhatsApp messages.
When you tick a box, Dyniq®, KvK 77272471, keeps for that channel: the number, the time of your consent, the version and the exact text of the box you saw, the form it came from, and a salted hash of your IP address. Each channel has its own record. We send no marketing text or WhatsApp message to a number without a ticked box for that channel, and none is sent until Dyniq switches these messages on.
If you consent, the messages are recurring and automated: up to 3 in the first 3 days. Message and data rates may apply to text messages. Reply STOP to cancel and HELP for help. Consent is not a condition of the trial or of any purchase.
We do not share SMS or WhatsApp opt-in data or personal information with third parties for marketing purposes. When these messages are on, Twilio (USA) delivers them and so receives the number and the text of each message. Cloudflare checks the forms with Turnstile and counts requests per hashed IP address, as in section 4.
Legal basis: your consent (Art. 6(1)(a) GDPR). You can withdraw it at any time by replying STOP or by emailing support@dyniq.ai, and withdrawing does not affect your trial. We keep the consent record as proof until you ask us to delete it, and then only as long as the law needs us to keep proof of consent.
13. Changes
We update this notice when something changes. The date at the top shows the latest version.