Legal

Privacy Policy

Last updated: 13 November 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, billing and customer feedback, 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
  • If the community turns on Referrals: which of the community's tracked invite links a person joined through, and whether they were still in the community, had posted at least one message, and had completed one of the community's product missions 7, 14 and 30 days after joining. On Discord, the community can also choose to count time spent in its Stage events and whether the person has the community's verification role. If the community turns this on, the Discord bot may give a new member a temporary label role so it can tell links apart, and removes it once the join is counted.
  • Activity-derived data: message counts, points, leaderboard positions, response times
  • Questions members ask, and the answers your team posts (for the FAQ features)
  • On Discord, an invite link to the server: when the bot is added to a server, it creates one invite link to that server and keeps one working while the bot is there (if the link is deleted, the bot creates a new one). Only the Block by Block team uses it, to open the server when we support the community, review a new community or check its subscription, and it is kept in our internal records. We never post it or share it with anyone else. If the bot is removed, it stops creating links, and the server's admins can delete the last one in Server Settings → Invites.

From dashboard users:

  • Your Telegram or Discord account ID and username
  • A login session cookie
  • Your settings and access grants
  • If you choose to fill in our feedback form: your answers, your name and role, your project's website or social page, and whether we may quote you

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, measuring which invite links and campaigns (for example, partners or influencers a community works with) bring in members who stay and stay active, and to operate, secure and support the service. We do not sell your data, and we never use community or dashboard data for advertising.

Near the end of a free trial or a paid period, we may ask the people who manage a community to fill in a short, optional feedback form. We use the answers to improve the product. We only quote someone publicly if they said we may in the form, and only in the way they chose (with their name and project, or with their project only). Each person's form link includes a reference code that links their answers to their Telegram or Discord account and community, so we know who has already answered and don't ask them again. You can ask us to remove your answers or your quote at any time.

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
  • Google (United States) — Google Forms and Google Sheets, where answers to our optional customer feedback form are collected and stored, and where we keep our own internal record of customer subscriptions (community name and link, plan and dates, and the contact person)

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. For communities using Referrals, the time a member left and their Stage event attendance are deleted after 90 days; the rest is kept like the community's other data. Answers to our feedback form are kept for as long as they help us improve the product, and removed sooner if you ask.

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 UK, the EEA or Switzerland, we ask you first with a cookie banner, and Google Ads cookies are only set if you click Accept. If you click Reject, or haven't chosen yet, 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. Visitors elsewhere get these cookies by default. Everyone can change their choice at any time with "Cookie settings" at the bottom of this page or the home page. Your choice is stored in your browser for 6 months, after which we ask again.

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.

11. Changes

We will update this page if this policy changes, and revise the date above.

12. Contact

team@blockbyblock.network · Telegram: @Andrei_Web3