Privacy, in plain English.

SiteBrain ("we", "our", "us") operates the AI chatbot platform at sitebrain.app and sitebrain.pl. It is run by Sebastian Czajkowski, a sole trader in Ireland, at Rathgar, Dublin 6, D06 X294, Ireland. Privacy contact: privacy@sitebrain.app.

We have two roles. For people with a SiteBrain account (you, the customer), we are the controller of your account, billing and usage data. For visitors who chat with a SiteBrain chatbot on a customer's website, or send its contact form, the business that owns that website is the controller. We process that data on the business's behalf, under our Data Processing Agreement.

If you are a visitor and want to see or delete your messages, contact the business whose website you used. You can also write to privacy@sitebrain.app. We pass your request on to the business and help it act on it.

We handle the data the product needs to work:

• Account data — your email address and a hashed password when you sign up. If you sign in with Google, Google sends us your Google account id, email address, name and profile picture; we keep only the id and the email address.
• Your website content — our crawler fetches the public pages of your site to build the chatbot's knowledge base.
• Chatbot conversations — we store the conversations your visitors have with the bot so you can review them in your dashboard and so we can count messages for billing.
• Contact-form messages — when a visitor sends a chatbot's contact form, we store the name, email address, optional phone number, message and the address of the page it was sent from. We show it to the owner of that website.
• Security data — we keep no web server request logs. When you sign up, sign in, reset your password or ask for a new verification email, we store the IP address and the email address used for up to 8 days, to block password guessing and sign-up abuse. For chat visitors and other anti-abuse counters we store only a one-way hash of the IP address, which cannot be turned back into the address. Chat-widget counters are deleted after 2 days, free-preview counters after up to 8 days, and hashed IP addresses in our internal event logs after 30 days.
• Free preview — when you try SiteBrain on /try without an account, we store the website address you enter, the public pages and business profile we build from it, a hashed IP address and how many chat messages you have used. We do not store the text of your messages. If you ask us to email you the preview link, we also store your email address and email you the link. If you also tick the reminder box, we send one more email before the preview is deleted, inviting you to start the trial. Your address is deleted from our database together with the preview, after 7 days at most, or sooner if you use the delete link in either email. To limit abuse we keep a one-way hash of the address in a counter for up to 8 days. Resend delivers these emails and keeps its own delivery logs.
• Game leaderboard — when you submit a score on the /game page, we store the nickname you type, your score, combo, the tournament month and a hashed IP address. Nicknames and scores are shown on a public leaderboard. The hashed IP address is blanked about 10 minutes later, the next time the leaderboard is opened or a score is submitted.
• Billing data — if you upgrade, our payment processor stores card details. We never see your full card number.

When you create an account, we also keep how you found us (campaign tags, the website that sent you and the first page you visited) to see which channels bring customers; the legal basis is our legitimate interest, and we store it with your account and delete it along with the account.

On our marketing pages we count visits with a counter that sets no cookies and stores nothing on your device. It does not keep your IP address. It records the page, the website or campaign that sent you, and your country, and it runs on Cloudflare.

We use your data to make the product work the way you expect:

• delivering, maintaining and improving SiteBrain,
• building and refreshing your website's business brain,
• answering your visitors' questions,
• handling billing and plan limits,
• detecting abuse and securing the service,
• communicating with you about product and support.

When you ask us to email you a free-preview link, we send it to do what you asked (Art. 6(1)(b) GDPR). The optional reminder email is based on your consent (Art. 6(1)(a) GDPR), which you can withdraw at any time with the link in each email.

We do not train foundation models on your content. Your data is not sold, not shared with other customers, and not used as training material.

SiteBrain runs on Cloudflare infrastructure (Workers, D1, R2). Since 10 October 2026 our database (Cloudflare D1) and the files you upload as the bot's knowledge (Cloudflare R2) are kept in Cloudflare's EU jurisdiction: Cloudflare runs and stores them only in data centres in the European Union. Conversations, contact-form messages and account data live there. Read replication is off, so the live database has no copies in other regions. Until 17 October 2026 we also keep the copy made before the move, in Cloudflare's data centres in the eastern United States, as a fallback; then we delete it. Our pages and the chat widget are served from Cloudflare's worldwide network, so a request passes through the Cloudflare data centre nearest to the person making it, and the code that answers it runs there.

Storage is in the EU, but data still leaves the EU/EEA for processing: a request is handled in the Cloudflare data centre nearest to the person making it, Workers AI (which builds the search index) can run outside the EU, and until 17 October 2026 the fallback copy sits in the United States. Cloudflare is certified under the EU-U.S. Data Privacy Framework (DPF), and its customer data processing addendum includes the EU Standard Contractual Clauses (SCCs). Google, Stripe and Resend are also DPF-certified. OpenRouter, a US company, is not on that list; its data processing agreement includes the SCCs. Firecrawl (US) only ever receives public pages of a website we crawl with it, never conversations, contact messages or account data. CallMeBot receives contact-form messages only if you connect WhatsApp alerts, and we have no data processing agreement with it (see below).

We also use sub-processors for specific capabilities:

• Cloudflare — hosting, database, file storage and Workers AI, which turns your content into the search index (embeddings). Cloudflare does not use customer content to train models,
• OpenRouter — LLM calls for knowledge extraction and answer generation. OpenRouter routes each request to a model provider; with our current settings that is Google (Gemini) for building your business profile, DeepSeek for chat answers, and OpenAI for reading text out of images you upload. Every request carries the OpenRouter setting data_collection = "deny", which means only hosts that do not store or train on the data may be used. The DeepSeek model runs on hosts OpenRouter picks under that rule, not on DeepSeek's own service,
• Stripe — payment processing (when you start a paid plan),
• Resend — transactional email,
• Google — sign-in if you use “Continue with Google”, and Google Tag Manager for analytics, only after you accept analytics cookies,
• Telegram — only if you connect it: visitor messages and contact-form messages are forwarded to your own Telegram chat so you can take over a conversation. Telegram's own terms apply to that chat,
• CallMeBot (WhatsApp) — only if you enter a WhatsApp number and a CallMeBot key in your widget settings: each contact-form message (the visitor's name and email address, their phone number if given, the page address and the message) is sent to CallMeBot, which delivers it to your WhatsApp number. The message travels in the request address (URL), so CallMeBot sees it in full. We have no data processing agreement or Standard Contractual Clauses with CallMeBot; by switching this on, you choose to make that transfer. WhatsApp's own terms apply to that chat,
• Firecrawl — only if we enable its crawler for a site: that site's public pages are sent to it to be fetched.

We serve our typefaces from SiteBrain's own servers. The one exception is the /game promo page, which loads the Nunito typeface from Google Fonts. In the dashboard, scripts and icons load from jsDelivr. Those services see your IP address.

If you agree to marketing cookies, we use the Meta Pixel and Meta's Conversions API to measure how well our ads work. We send Meta a page-view event for each page you open on our marketing site and on the sign-in and sign-up pages (never in the dashboard), and four more events: your bot preview is ready, you create an account, you start a trial, and you make your first payment. Meta then receives your IP address, browser details, the address of the page you are on, and Meta's cookies _fbp and _fbc. For an account, a trial or a payment it also receives a hashed copy of your email address, and for a trial or a payment a hashed copy of your SiteBrain account id and the plan price or the amount paid, with its currency. The recipient is Meta Platforms Ireland Ltd. Without your consent none of this is sent. You can withdraw consent at any time through "Cookie preferences".

If you're in the EU you have the full set of GDPR rights — access, rectification, erasure, restriction, portability, and objection. If you're in another jurisdiction, we honour equivalent local rights.

To exercise any of these, write to privacy@sitebrain.app. We respond within 30 days.

Most things you can do yourself from the dashboard: view and export conversations, delete a single conversation, delete a single contact-form message, delete a bot, delete your account.

We keep your account data for as long as the account exists.

• Chat conversations are deleted automatically 12 months after the last message in them. The owner can delete one sooner from the dashboard.
• Contact-form messages are deleted automatically 12 months after they arrive. The owner can delete one sooner from the dashboard.
• Sign-up and sign-in attempts (IP address and email address) are kept for up to 8 days.
• Anti-abuse counters (hashed IP address only) are deleted after 2 days for the chat widget and after up to 8 days for the free preview.
• Free previews (/try), including their hashed IP address and any email address you gave, are deleted 7 days after they are created.
• Internal event logs (errors, deliveries, jobs), including hashed IP addresses, are deleted after 30 days.
• Daily usage counters are deleted after 90 days. Monthly usage totals for an account (conversations, messages, AI cost) are kept while the account exists, because we settle billing questions with them, and are deleted with the account.
• Game leaderboard entries (nickname and score) have no set deletion date. To have yours removed, write to privacy@sitebrain.app.

When you delete your account, we remove it from the live database at once: all bots, conversations, contact messages and documents. The database's restore history (Cloudflare D1 Time Travel) can hold the data for up to 30 days, then it is gone. Stripe keeps invoices for as long as tax law requires.

If anything material changes, we'll email the address on your account at least 14 days before the change takes effect. The "last updated" date at the top of this page is always the source of truth.