Privacy at DataWise
What you send us, we use only to answer you. If you accept cookies, we also record your visits here to improve the site. We never sell any of it, pool it, or add you to a mailing list.
The short answer
What you send us, we use only to answer you, and we never sell it, pool it, or add you to a mailing list. If you press Accept on our cookie banner, we also record your visits and journey on this site with two first-party cookies, to understand what helps visitors and improve the site. This page explains exactly what that means for the places on this site where anything is collected from you: the contact form, AI Mode and, if you accept, analytics. There is one further thing we record, and it never identifies you: anonymous counts of page views, and of how often search-engine and AI crawlers fetch our pages. It is described in full below. The analytics are described under Cookies and storage.
Who we are
DataWise Data Science (Dan Malka) is a boutique data-science consultancy based in Israel. For any question about your data, or to exercise the rights below, write to hello@datawiseds.com. The founder reads it personally.
The contact form
When you write to us through the form, you send your name, your email, an optional company name, and a description of your problem. We use it for one thing: to reply and, if it makes sense, to scope your project. The message reaches us two ways, both only so we can follow up: it is delivered to our inbox through EmailJS, our email-delivery provider, and the same details also open a record in our own internal scheduling and follow-up system (run by DataWise, not a third party). We do not build a marketing list from them, and we never sell them or hand them to any outside party. This is the same commitment as the confidentiality note on our contact page: no mailing lists, no third-party sharing, and no naming you anywhere without your written permission.
AI Mode
AI Mode answers your questions using only the content published on this site. When you ask something, your question is sent to our answering service and to Google’s Gemini, the AI provider that generates the answer (with Cerebras as a fallback provider if Gemini is unavailable); the relevant passages are matched on our own edge, not by a third party. We designed it to keep as little as possible: your questions and your IP address are never stored on our servers, and conversations are ephemeral, so nothing is kept after the session. Gemini runs for us on Google Cloud (Vertex AI): Google does not use your questions to train its models, but it may keep them, with the answers, in a short-lived cache for up to 24 hours, and may log requests to detect abuse. For operations we log only technical events (which passages were retrieved, response times, and token usage), never the content of what you asked, and the conversation itself lives only in your browser’s session storage. An invisible bot check (Cloudflare Turnstile) runs on your first message to keep the service available. AI answers can be imperfect; verify anything critical with us directly.
Voice conversation
In a voice conversation you speak and the assistant answers out loud. This is how it travels:
- Your browser turns what you say into text, with its own built-in speech recognition. Depending on the browser, that happens on your device or with the browser’s maker (for example Google for Chrome and Apple for Safari), under their terms. No recording of your voice reaches us.
- That text passes through our relay on Cloudflare to Gemini on Google Cloud (Vertex AI), which generates the spoken answer. The answer, as audio and as text, comes back to you the same way.
- Our relay stores nothing: no audio, no transcript, no messages. For operations it logs only technical events, such as when a session opened and closed, how long it ran and how much data passed, never the content.
- Google does not use the conversation to train its models. It may hold it in a short-lived cache, deleted within 24 hours, to answer faster, and may log requests to detect abuse.
- You can end the conversation at any moment with the end button. When it ends, the microphone turns off.
Booking hand-off in AI Mode
To book a scoping call, you enter your name and email, and we receive those so we can confirm the call. The booking itself is handled by our own scheduling system (at meet.datawiseds.com, run by DataWise, not a third party). Booking requests reach it through Cloudflare, but our server does not receive, use, or store your IP address: abuse protection is aggregate rate-limiting, not per-visitor. At the network edge, IP handling is governed by Cloudflare’s own policy, outside our systems.
Sharing anything from the conversation is a separate, optional step, and it is off unless you turn it on. When you book from inside AI Mode you see a checkbox that is unchecked by default. Only if you tick it do we add a short snapshot to help us prepare: the questions you typed in that session, the page you were on, and your language, and nothing else. The checkbox shows you the exact list before you continue. We never include the answers you were given, or anything you typed into any other form, and we never attach your IP address to it. If you leave the box unchecked and simply book the call, nothing from the conversation is shared.
Visit counts
Search engines and AI assistants send automated crawlers (Googlebot, Bingbot, GPTBot, ClaudeBot, PerplexityBot and others) to read our pages. We record when they do, because whether these crawlers reach a page decides whether that page can ever appear in a search result or an AI answer, and until now we had no way to see it.
For every request the site serves, we add one to an hourly tally. That tally is a number and nothing else: no address, no identifier, nothing that could be traced to a person or a device.
When a request identifies itself as a known crawler, we additionally record which crawler it claims to be, which page it asked for, what our server answered, and whether we could confirm the claim. A user-agent string is trivially faked, so we check it: either the visiting address falls inside a range the crawler’s owner publishes, or a reverse-then-forward DNS lookup confirms it. That address is used for the check and is discarded immediately. It is never written down. The record we keep has no field for it, by design.
Nothing here identifies a person. For every page view in a browser, we add one to that page’s daily count. We also add one to each of a few broad tallies, kept apart from each other: your region (Israel, the US, the EU, the UK or elsewhere), device type, language, where you came from, and the time of day. All of this without an IP address, without a cookie, and without keeping anything about you as one visitor.
What we never do
Your data stays for your purpose only. Nothing is sold, nothing is pooled, and nothing you send is used to train or improve anyone’s models.
Cookies and storage
We keep strictly necessary storage that makes the site work (your cookie choice, AI Mode’s session, and a guard against sending a message twice). Only if you press Accept, we also set two first-party cookies for analytics: dw_consent (your answer) and dw_vid (a random identifier for your browser), both for 12 months. With them we record your visits and journey on this site: the pages you open, the site that referred you and the campaign tags of the link you arrived through, which buttons and links you click and which demos you play, whether you open AI Mode and how many questions you ask (never the text), the steps of a booking, and that you sent a form (never its content), with your language, device type and the time. With them we also record how long each page is open and in use, which sections of it are on your screen and for how long, and how far down you scroll. We never record the screen itself or anything you type. We use it only to understand which pages and content help visitors and to improve the site. It is never sold or shared, there is no advertising and no third-party analytics or tracking, and we store no IP address. We keep it for 13 months. If you press No thanks, only your answer is stored. You can change your choice at any time with Cookie settings in the footer. The full list is on our cookie policy.
Sub-processors
A short list of the services that may handle your data on our behalf: EmailJS (delivers contact-form messages), Google Gemini on Google Cloud (Vertex AI) (generates AI Mode answers in text and voice, with Cerebras as a fallback provider for text), Cloudflare (invisible bot protection for AI Mode, and the relay that carries voice conversations, storing nothing), and our hosting provider. Some are outside Israel and the EU; where your data crosses borders it does so only to provide these functions, under those providers’ own safeguards.
Who controls your data
The controller of any personal data described here is DataWise Data Science (Dan Malka), based in Israel. That means we decide what is collected and why, and we are the people you deal with about it. Write to hello@datawiseds.com.
Why we are allowed to use it (legal bases)
For visitors in the EU and UK, the law asks us to name a lawful basis for each use. There are two, and they are simple:
- Your consent, for the contact form and for analytics cookies. You choose to write to us, and you choose Accept or No thanks on the cookie banner. You can withdraw at any time: with Cookie settings in the footer for the cookies, or by asking us to delete a message.
- Our legitimate interest, for keeping the site and AI Mode secure and available, which is why the invisible bot check (Cloudflare Turnstile) runs. This is a narrow, expected use, and it does not involve profiling you.
- Our legitimate interest, to know how many people reach the site, which pages they open and where they came from, so we can improve it. For that we count page views as aggregate tallies only, as described under Visit counts. Nothing that identifies you is kept, and no profile of you is built.
How long we keep things
We keep personal data only as long as we need it. Contact-form details stay with us for as long as the conversation is useful, so we can reply and, if it makes sense, scope your project; you can ask us to delete them at any time. They are never on a marketing list and never shared. AI Mode keeps nothing after the session. If you pressed Accept, the record of your visits is kept for 13 months and then deleted; the cookies themselves expire 12 months after your answer.
International transfers
We are based in Israel, and some of the providers that help run the site are located outside Israel and the EU. Where your data crosses a border it does so only to provide the functions described on this page, and only through the providers listed under sub-processors, under those providers’ own safeguards. We do not move your data across borders for any other reason.
Your rights
Because we keep so little, exercising any of these is usually a one-email matter. Write to hello@datawiseds.com and tell us what you want to do; we will handle it, and we will not treat you differently for asking.
- If you are in the EU or UK (GDPR). You have the right to access the data we hold about you, to have it corrected, to have it erased, to restrict or object to how we use it, to receive it in a portable form, and to withdraw any consent you gave. You also have the right to complain to your local data-protection supervisory authority.
- If you are in the US, including California (CCPA and CPRA). You have the right to know what personal information we hold and to have it deleted or corrected, and the right to opt out of the sale or sharing of personal information. To be clear, DataWise does not sell or share your personal information, so there is nothing to opt out of, and we will never discriminate against you for exercising any of these rights.
- If you are in Israel (Privacy Protection Law). You have the right to access the information we hold about you and to ask us to correct it.
These are the standard rights the main privacy laws provide; we honor them regardless of where you are, and this is not a claim of formal certification under any of them.
Changes
If this policy changes, the date at the top of this page changes with it. Last updated: 1 November 2026.