This Privacy Policy explains how The Bouncr LLC ("Bouncr", "we", "us") collects, uses, and shares information when you use Bouncr: our bots, Mini App / embedded app, dashboards, and website (the "Service"). We aim to collect only what the Service needs to work.
| Category | Examples |
|---|---|
| Platform identifiers | Telegram user ID, username, display name; Discord user ID, username; the group/server and channel IDs you interact with. Provided by Telegram/Discord when you use the Service. |
| Wallet data | Public wallet addresses you link, and the public on-chain balances/holdings we read to determine eligibility. We never collect private keys or seed phrases. |
| Membership & access state | Which communities and clubs you belong to, your eligibility status, roles, and grants. |
| Subscription & payment metadata | Plan, status, billing cycle, and payment references. Card details are handled by our payment processor (e.g. Stripe); we do not store full card numbers. Crypto payments are identified by public transaction references. |
| Community content (for moderation) | Where an operator enables moderation, the Service processes messages in the relevant groups/channels to apply the operator's configured rules (filters, blocklists, flood/anti-raid, and, where enabled, cross-platform bridging). Processing is per the operator's configuration. |
| Support & messages | Support tickets and direct messages you exchange with community admins through the Service. |
| Security data | Two-factor (TOTP) enrolment status, an optional recovery email you choose to add, and device/session information used to protect your account. |
| Connected social accounts | If you choose to connect a social account (see below), the account identifier, display name/handle, and public follower or subscriber count for that account, plus the access and refresh tokens issued to us by that platform. |
| Early-access list | If you join the early-access list on thebouncr.io: the email address you give us, when you joined and confirmed it, when we last emailed you, and which version of the sign-up wording you agreed to. See section 1b. |
| Usage & technical data | Basic logs, analytics, and diagnostics needed to operate and secure the Service. |
Some communities require a connected social account before they will grant access to a club, for example "has a connected X account" or "has at least 10,000 followers". Connecting an account is always started by you, from your own profile in the Service, and you may connect none, one, or several.
When you connect an account we ask that platform only for the fields listed below, and only on your behalf, using the authorisation you granted:
| Platform | What we receive and store |
|---|---|
| X (Twitter) | Your user ID, username, and public follower count. Where a community asks you to repost or like a specific post as part of an application, whether your own account has done so. |
| YouTube (Google) | Your channel ID, channel title, and public subscriber count. Where a community asks it, whether you are subscribed to a specific channel or have liked a specific video. |
| TikTok | Your open_id, display name, and public follower count. |
We request read-only permissions. We do not post, like, follow, comment, or send messages on your behalf, and we do not read your posts, videos, direct messages, or private content. We store the tokens the platform issues so that a community's requirement can be re-checked periodically without asking you to authorise again; disconnecting the account in your profile deletes those tokens and the stored profile figures.
These figures are visible to you, and to the administrators of communities you have applied to or are gated by. They are not sold, shared with other communities, or combined into any cross-service profile.
The early-access list on thebouncr.io is for community owners who want to hear when Bouncr opens to them.
We process personal data to perform our contract with you (providing the Service), on the basis of our legitimate interests (security, abuse prevention, product operation), with your consent where required (e.g. optional features, and the early-access list, where you can withdraw consent at any time by unsubscribing), and to comply with legal obligations.
We do not sell your personal information.
We keep information for as long as needed to provide the Service and for legitimate business or legal purposes, then delete or anonymise it. Moderation processing of message content is transient or as configured by the operator; support and account records are retained as reasonably necessary. The early-access list has its own limits, set out in section 1b.
Depending on your location, you may have rights to access, correct, delete, port, or restrict processing of your personal data, and to object to certain processing or withdraw consent. You can exercise these by contacting us at [email protected]. You can also remove linked wallets, disconnect social accounts, unlink platforms, or stop using the Service at any time.
We use technical and organisational measures to protect information, including encryption of sensitive secrets at rest, row-level tenant isolation between communities, and access controls. No method of transmission or storage is perfectly secure, but we work to protect your data.
We and our providers may process information in countries other than yours. Where required, we use appropriate safeguards for such transfers.
The Service is not directed to children under 13 (or the minimum age required in your jurisdiction, or by Telegram/Discord). We do not knowingly collect data from children below that age.
We may update this Policy. Material changes will be indicated by updating the "Last updated" date and, where appropriate, by notice through the Service.
Questions or requests about privacy: [email protected]
Data controller: The Bouncr LLC, a New Jersey limited liability company, 501 Route 17 STE 1 #1068, Paramus, NJ 07652, USA.