Legal
Privacy Policy
Last updated: 26 October 2026
Block by Block ("we", "us") builds community analytics and engagement bots for Telegram and Discord. Block by Block is operated from the United Kingdom. This policy explains what our bots and dashboards collect, why, and what we do with it.
1. Who we are and our role
When a community adds our bot to their Telegram group or Discord server, that community (the "Customer") decides how the bot is used. Under UK and EU data protection law the Customer is the data controller and Block by Block acts as a data processor on their behalf. For our own website, dashboard accounts and billing, we act as a controller.
2. What we collect
From communities where the bot is installed:
- Platform user IDs and usernames (Telegram / Discord)
- Text of messages posted in the group or server where the bot is present. We do not store GIFs, stickers, or images.
- Message timestamps, channel or chat identifiers, and reply references
- Join and leave events, and administrator status
- Activity-derived data: message counts, points, leaderboard positions, response times
- Questions members ask, and the answers your team posts (for the FAQ features)
From dashboard users:
- Your Telegram or Discord account ID and username
- A login session cookie
- Your settings and access grants
We do not collect wallet addresses, member email addresses, or private messages between members. Our bots never send private messages to individual community members.
3. Why we process it
To provide community analytics (activity, growth, retention, sentiment), automated answering of members' questions from your FAQ, translation of announcements, AI-written summaries and recommendations for your team, gamification (points, badges, leaderboards), team performance reporting, and to operate, secure and support the service. We do not sell your data, and we never use community or dashboard data for advertising.
4. AI processing
To provide sentiment analysis, FAQ matching, summaries and translations, message text, together with the sender's platform username and any role label your team has assigned, is sent to Anthropic (Claude), our AI sub-processor, which processes it on our behalf and returns a result. Under Anthropic's commercial API terms this content is not used to train their models. Anthropic is based in the United States, so this involves an international transfer, made under appropriate safeguards.
5. Sub-processors
- Anthropic (United States) — AI processing of message text
- Hetzner Online GmbH (Germany, EU) — hosting and database
- Cloudflare, Inc. (United States) — content delivery, security filtering and TLS termination for our dashboards
- Telegram and Discord — the platforms our bots run on, governed by their own privacy policies
- Telegraph (operated by Telegram) — public hosting of translated announcements
6. Where your data is stored
On servers located in Germany (EU), in a PostgreSQL database. Traffic to our dashboards passes through Cloudflare's global network before reaching those servers, which involves an international transfer made under appropriate safeguards.
7. How long we keep it
We retain a community's data while the bot is installed and the subscription is active. If a subscription ends, the bot stops collecting new data and existing data is retained so the community can resume later without losing its history. A Customer can ask us to delete the community data we hold at any time and we will do so.
One exception: content that our bots publish to a third-party service at your team's request cannot be withdrawn by us. In particular, when your team pins an announcement for translation, each translation is published as a public page on Telegraph, and Telegraph provides no way to delete a page once published.
8. Your rights
If you are in the UK or EU you have the right to access, correct, delete, restrict or object to the processing of your personal data, and to data portability. Because we usually act as a processor, the quickest route is to contact the administrator of the community you are in. You can also contact us and we will help or pass your request on.
9. Security
Data is transmitted over HTTPS, and the data we store is encrypted at rest. Dashboard access requires platform-verified authentication and is granted only to administrators we have explicitly approved for that specific community.
10. Our website and Google Ads
Our website, blockbyblock.network, uses the Google tag to measure our Google Ads. When you arrive on the site from one of our ads, Google can tell us whether you then clicked "Add to Telegram" or "Add to Discord", so we can see which ads bring new trials. For this, Google may set or read cookies on your device (such as an ad click identifier, kept for up to 90 days) and receives technical information such as your IP address, browser type and the pages you visit. Google processes this information under its own Privacy Policy, and you can read how Google uses information from websites that use its services.
If you visit from the EEA, the UK or Switzerland, advertising and analytics cookies are switched off by default, so no advertising cookies are stored on your device. Google may still receive basic information without cookies, such as that a page was viewed or a button was clicked, which is not used to identify you.
You can manage how Google personalises ads for you in My Ad Center, and you can block or delete cookies in your browser settings at any time. We never combine this website information with data from the communities where our bots are installed.
Our website also uses Google reCAPTCHA to protect it from spam and abuse. Its use is subject to Google's Privacy Policy and Terms of Service.
11. Changes
We will update this page if this policy changes, and revise the date above.
12. Contact
team@blockbyblock.network · Telegram: @Andrei_Web3
