Privacy policy
Last updated September 2026
The short version: we collect what is needed to run your dashboard and publish verifiable draws, we never touch your casino credentials, and the only cookie we set is the one that keeps you logged in.
1. What we collect
Buzzeee keeps data collection deliberately narrow:
- Platform identity from OAuth (platform user id, username, display name, avatar URL) when you link Kick;
- Stream events your platform sends us (follows, subscriptions, clips, slot calls) via signed webhooks;
- Content you create in the dashboard (bonus hunts, giveaways, entrant lists, winners);
- Basic operational logs (request timing, error traces) needed to run and debug the service.
2. What we never collect
We never ask for casino account passwords, session cookies or bearer tokens for money-adjacent services. Connecting a casino is done via connectors that use officially supported, read-only data where available. We do not collect payment card data; we do not run paid tiers yet.
3. Why we process it
We process the above to:
- operate your dashboard, stats, hunts and giveaways;
- publish public profiles and verifiable draw records you choose to make public;
- secure the service (webhook signature verification, deduplication, abuse detection);
- communicate service updates.
4. Public records
Draw proof bundles (commitment hash, frozen entrant list hash, revealed seed, participants and winners) are published so anyone can verify them. That is the point of provable fairness - but it also means entrant usernames in a published draw are public. Overlay and public hunt pages expose only what you choose to publish.
5. Cookies
We use one functional cookie, buzzeee_session, an HttpOnly session cookie created when you log in. It is required for the dashboard to work, is not used for advertising, and expires on logout. There are no analytics, marketing or third-party tracking cookies. See our cookies notice for details.
6. Sharing
We do not sell personal data. We share data only with infrastructure providers needed to run the service (hosting, database), and with the platforms you connect, as required by their APIs. Legal requests are honored where valid and, where permitted, documented.
7. Retention
Account and content data is kept while your account is active. Disconnecting a channel stops new event processing; deleting your account removes your personal data, with published proof bundles retained in minimal, non-personally-identifying form because their purpose is public verifiability.
8. Your rights
You can view and edit your account data in the dashboard, export draw records at any time, and request deletion of your account. Depending on where you live (for example the EU/EEA or UK), you may have rights of access, rectification, erasure, restriction, portability and objection - contact us through the help center to exercise them.
9. Security
Sessions use HttpOnly cookies; OAuth tokens are stored encrypted and used only for the scopes you approved; webhooks are signature-verified before processing. No system is perfect - if you find a vulnerability, report it through the help center and we will act on it quickly.
10. Changes and contact
Material changes to this policy are announced before they take effect. Questions or data requests: help center, or the contact details in our terms.
