Privacy Policy

1. Who we are

BeefyGuard operates this Telegram group security product, focused on admin impersonation detection and related moderation. Official properties only:

• Website: https://beefyguard.com
• Docs: https://docs.beefyguard.com
• Bot: @beefyguard_bot

Telegram Inc. is a separate company. Their app is governed by Telegram's own privacy policy.

2. What this product does

Group admins add the bot to a Telegram group or channel and grant it moderation permissions. The bot then processes updates Telegram sends it (joins, profile changes, messages in chats it can see) so it can detect impersonators, spam, and related abuse, then delete, mute, or ban according to settings the admin chose.

If Group Privacy is disabled (required for detection), the bot can receive ordinary group messages: not only commands. It still cannot read secret chats or private DMs between members unless a person writes to @beefyguard_bot directly.

3. Data we process

Depending on how you use the service, we may process:

• Telegram identifiers: user id, chat/group/channel id, names, usernames, language code, and whether an account is a bot.
• Admin and member profile fields used for detection: display names, usernames, and perceptual hashes of profile photos (to compare lookalikes). We store hashes for matching, not a public gallery of member photos.
• Group configuration: feature toggles, thresholds, flagged names, whitelist entries, linked channels, log-channel ids, portal settings, and similar admin-chosen options.
• Activity counters: per-user message counts and join/flood timestamps used for anti-spam and raid detection. We do not keep a full searchable archive of every group message.
• Moderation events: detections, bans, mutes, deletes, and related reasons so admins can review logs and so the product can function.
• Dashboard login: Telegram Login Widget data you authorize (typically user id, name, username, photo URL) plus session cookies needed to stay signed in.
• Direct messages with the bot: commands, support messages, portal / verification replies, and payment flows you start with @beefyguard_bot.
• Portal / join verification: tokens, captcha or challenge status, and invite links the bot creates so a user can join a linked group after checks pass.
• Billing: plan, subscription status, Telegram Stars invoices, and payment-processor records if you buy a plan. Processors see the payment details we do not store ourselves (card numbers stay with the processor).
• Affiliate program: referral codes, earnings, and an optional payout wallet address you type in for commissions. That address is for paying affiliates. It is not used to log into the dashboard and is never a seed phrase.
• Combot import (optional): if an admin runs a Combot history import, we pull public Combot stats the admin is allowed to access so activity counts can be seeded.

4. What we do not collect

• Seed phrases, recovery phrases, or private keys
• WalletConnect / MetaMask sessions, or any wallet connection to use BeefyGuard
• Contents of private chats between two people that never include the bot
• Telegram account passwords or 2FA codes
• Payment card PAN / CVV (those stay with the payment provider)

5. Why we process it

• Provide the service: detection, moderation actions, dashboard, portals, and subscriptions (contract / requested service).
• Secure the service: abuse prevention, billing integrity, and investigating reports.
• Improve reliability: logs and error traces so we can fix outages (legitimate interest / operating the service).
• Legal obligations: tax, accounting, and lawful requests.

6. Sharing and processors

We do not sell personal data. We share data only as needed to run BeefyGuard:

• Telegram: the platform that delivers updates and carries bot actions. You already use Telegram under their terms.
• Hosting and database: cloud infrastructure that stores the application and Postgres data.
• Payment providers: e.g. Telegram Stars and any card/crypto processor shown at checkout.
• Combot Anti-Spam (CAS): only if a group admin enables CAS. We then query cas.chat with a Telegram user id to see if CAS lists that account. CAS is operated by Combot, not by us. See Combot's privacy policy.
• Discord forwarding: only if a group admin turns it on. Selected group messages may be copied to a Discord webhook the admin configured.
• Law: if we are legally required to disclose information.

Group admins are typically the "customer" of the bot. Members in a protected group are processed because an admin installed BeefyGuard there. If you do not want a moderation bot processing your group activity, leave groups that use it or ask that group's admins to remove it.

7. Cookies and the website

The dashboard uses essential cookies / local session storage for Telegram Login and to keep you signed in. We do not run advertising pixels on the product for third-party ad networks. The Telegram Login Widget may set its own cookies (Telegram's policy applies).

8. Retention

• Active groups: configuration, admin hashes, counters, and moderation logs while the bot is used in that chat.
• After the bot is removed: we aim to delete or de-identify group operational data within about 60 days, unless we must keep a subset for billing, dispute, security, or legal reasons (for example a paid invoice).
• Billing and affiliate records: kept as long as tax and accounting rules require.
• Global / safety lists: accounts recorded for confirmed abuse may be retained longer so other customer groups can stay protected.

9. Your choices

• Group admins: remove the bot, disable features, or adjust detection. Removing the bot stops new group updates from arriving.
• Members: you cannot fully "opt out" of a group bot while remaining in that group; leave the group or ask admins to uninstall BeefyGuard.
• Dashboard users: stop using the dashboard and request deletion of your login/account records via the contact below.
• Access / correction: names and usernames follow what Telegram sends; change them in Telegram and the next sync will pick up the new values.

To request a copy or deletion of personal data we hold about you (dashboard account, affiliate profile, or identifiable logs), contact us through @beefyguard_bot. We may need you to prove control of the Telegram account. We may refuse or limit a request where we must keep records (billing, abuse, legal hold) or where it would expose another customer's group.

10. Children

BeefyGuard is built for community operators, often crypto groups. We do not knowingly offer the product to children under 16. If you believe we have data about a child, contact us and we will delete it where we can.

11. International processing

Hosting and subprocessors may be in multiple countries (including Australia and the United States). If you access the service from the EU/UK, you understand that data is processed outside those regions to run the bot.

12. Security

We use access controls, encrypted transport (HTTPS / Telegram Bot API), and least-privilege hosting practices that are reasonable for a small SaaS. No method is perfect. Limit the bot's Telegram admin rights to what it needs (delete, ban / restrict, and invite users if you use portals). Do not grant "Add new admins" unless you have a specific reason.

13. Changes

We may update this page. The "Last updated" date will change. Continued use after an update means you accept the revised policy. Material changes may also be noted on the site or via the bot.

14. Contact

Privacy questions: @beefyguard_bot or the support flow in docs. Also: About, Trust, Terms.