This Privacy Policy explains how HALFORD SUCKS LTD, company number 14173794 (“Company”, “we”, “us”, or “our”) collects, uses, stores and protects information in connection with the Streamneeds platform, website, software, applications and related services (the “Services”). By accessing or using Streamneeds, you acknowledge and agree to the practices described here.
1. Who we are
Streamneeds is operated by:
- HALFORD SUCKS LTD
- Company Number: 14173794
- United Kingdom
- Contact: streamneeds@sucksmedia.com
2. Information we collect
2.1 Account information
When you register for or use Streamneeds, we may collect:
- email address;
- a password — only for accounts that sign in with a password (e.g. moderator accounts); passwords are stored as a one-way bcrypt hash and are never stored or visible in plain text;
- display name and avatar / profile image;
- your Kick username, where used to authenticate the chat bot;
- subscription details — your plan tier, status and trial dates, and a Stripe customer / subscription identifier (see Section 3);
- optional onboarding details you choose to provide, such as a Discord or Telegram contact handle, plan interest, and how you heard about us.
Account sign-in is provided through Google OAuth and/or email-and-password credentials. Where you sign in with Google, we receive your basic profile details (such as email, name and image) from Google in order to create and authenticate your account.
2.2 Platform integration information
Where you connect third-party services to Streamneeds, we may collect and store:
- Discord account identifiers, usernames and display names;
- Kick account identifiers, usernames and display names;
- Twitch account identifiers, usernames and display names;
- OAuth access tokens for the platforms you authorise (e.g. Kick, Twitch), stored encrypted and used solely to read and send messages and perform actions on your behalf — we never receive or store your platform password;
- channel / stream information and related integration metadata.
If you configure stream alerts, we may also process inbound event data sent to us from third-party platforms including Twitch and YouTube (for example follows, subscriptions, tips, super chats and chat events) so we can display alerts.
2.3 Viewer and engagement information
Streamneeds processes viewer and engagement information on behalf of creators using the Services, including:
- viewer usernames, display names, avatars and platform user IDs;
- chat messages. When a creator connects their channels, chat messages sent in those channels — on Discord, Kick, Twitch and Hype (casino-site chat) — are stored in our database. A stored message includes the message text, your username and display name, your platform user ID, the channel, a timestamp and, where your message is a reply, the name of the person you replied to and a preview of their message. Stored chat is retained for 30 days and then automatically deleted (see Section 10). You can opt out and erase your stored chat at any time — see Section 11;
- chat activity and message counts;
- participation and engagement data — points balances, gifted subs, giveaway and raffle entries, store purchases, slot requests and balance guesses;
- moderation activity (e.g. bans, flags and related notes).
Viewers may also voluntarily provide additional details through features a creator enables, such as casino account usernames, cryptocurrency wallet addresses, affiliate codes, and — where a creator ships physical prizes — a name and postal address. We do not collect casino passwords or account balances.
For viewer data, the creator is the data controller and Streamneeds acts as a data processor on the creator’s instructions. Creators are responsible for telling their viewers what data they collect and for having a lawful basis to do so in their jurisdiction.
2.4 Discord data
Where a creator invites the Streamneeds bot into their Discord server, the bot reads the following data about members of that server:
| What we read | Why | Retention | Who can see it |
|---|---|---|---|
| Messages you post in connected servers — text, username, display name, Discord ID, channel and timestamp, plus the quoted author and message preview when you reply | Bot commands, chat points, automated moderation, poll votes, live cross-platform chat in the creator’s dashboard and overlays, and support-ticket transcripts | 30 days; ticket transcript content is kept for 12 months after the ticket closes | The creator and their moderators; live chat can also appear on the creator’s public overlay and stream (see Section 7) |
| Server join events (username, display name, avatar) | On-stream “new member” alerts, on plans that include them | Relayed in real time; a log entry is kept for 90 days | The creator, their moderators and their stream viewers |
| Member details — account-creation date (derived from your Discord ID), the date you joined the server, and your roles | The creator’s verification / anti-alt gate (minimum account age, minimum membership duration, role checks) | While the server is connected; purged 30 days after the bot is removed (see Section 10) | The creator and their moderators |
| Reactions (the 🎉 emoji and configured reaction emoji) | Giveaway entries and reaction-based chat points | Kept as giveaway entries and point transactions so results and balances stay auditable | The creator and their moderators |
| A per-account record — your Discord ID, account-creation date, first-seen date and a count of servers where you have been banned from bot features. Your per-server profile also records the time of your last message | Abuse prevention and moderation: detecting throwaway accounts, ban evasion and inactivity | Until erased on request (see Section 11) | Creators’ moderators, via moderation commands (see the cross-server note below) |
The per-account record above is created the first time you interact in any connected server and is shared across servers that use Streamneeds.
Cross-server ban reputation. When a creator bans you from bot features, a ban record is created and a global count of such bans is incremented. Moderators in other connected servers can see that count and the servers involved through moderation commands. Automatic enforcement (denying verification once the count passes a threshold) is enabled by default for every connected server — each creator can disable it, or change the threshold, for their server.
Chat messages and join alerts are relayed in real time through Pusher, our real-time messaging sub-processor (see Section 6), to render the creator’s dashboard and overlays.
2.5 Technical and usage information
We may automatically collect technical information including:
- IP addresses;
- browser and user-agent information;
- request, activity and diagnostic logs;
- a probabilistic device fingerprint derived from hardware and browser characteristics (such as GPU, screen and timezone), collected when your overlay renders or you use the app.
This information is used primarily for security, rate limiting, abuse prevention and debugging. The device fingerprint is used solely to detect sharing of a single subscription across multiple people — a legitimate-interest basis (abuse prevention); we never use it for advertising and never sell it. Streamneeds does not currently load third-party web analytics products (such as Google Analytics) on the site.
2.6 Uploaded content
You may upload files, graphics, overlays, logos, media and related assets through the Services. Uploaded files are stored using our hosting provider’s blob storage. You remain solely responsible for all content you upload.
2.7 Booking a call with us
Our booking pages (/book/[handle]) let you schedule a call with a member of our team without creating an account. When you book, we collect and store:
- the name you enter;
- your email address;
- your timezone, detected from your browser, so times are shown and sent to you in your own local time;
- an optional free-text note — please don’t include sensitive information in it; and
- the slot you chose and whether the booking is still live or cancelled.
We use this solely to schedule and run the call and to email you about it. On booking (and on any reschedule) we send you a confirmation email containing a calendar invite (.ics) — your note, if you left one, appears in the invite’s description — and we email you a reminder about an hour before the call. If you cancel or reschedule, the team member you booked with is emailed your name, email address and the affected time. These emails are sent through Resend, our transactional email sub-processor (see Section 6). Our lawful basis is our legitimate interest in responding to a meeting you asked us for.
We check the email address you give against existing Streamneeds accounts. If it matches one, the booking is linked to that account and a note is added to that account’s internal customer record so our team knows a call is scheduled; that note forms part of the account record and is kept for as long as the account is. If it does not match an account, no such record is created.
Every confirmation and reminder email contains a private link that lets you reschedule or cancel the booking yourself — no login, and no further contact with us needed. Bookings are deleted automatically 12 months after the scheduled time (see Section 10), and you can ask us to delete yours sooner by email (see Section 11).
3. Payment processing
Streamneeds does not directly store or process payment card information. Payments are processed by Stripe, our third-party payment provider. We retain only billing metadata such as a Stripe customer ID, subscription ID and plan/status information. Your use of payment services is subject to Stripe’s own terms and privacy policy.
4. How we use information
We may use collected information to:
- provide and operate the Services;
- manage accounts and subscriptions;
- authenticate users;
- process billing and payments via Stripe;
- provide moderation and automation functionality;
- operate real-time overlays and live updates;
- send transactional email (e.g. verification and password reset);
- schedule, confirm and remind you about calls you book with us, and notify the team member you booked with of changes;
- maintain platform security and prevent abuse;
- investigate misuse;
- communicate account or service-related notices;
- improve platform features and performance; and
- comply with legal obligations.
We may use aggregated and anonymised statistics for research, platform optimisation and related business purposes. Such information is not intended to identify individual users or viewers. We do not sell your personal data, and we do not use it to train third-party AI models.
5. Cookies and similar technologies
Streamneeds uses cookies and similar technologies to:
- maintain authenticated user sessions;
- remember preferences (such as your light/dark theme);
- support core platform functionality.
These are limited to what is necessary to operate the Services. We do not currently use third-party advertising or analytics cookies. If we introduce analytics providers in the future, we will update this policy accordingly.
6. Third-party services and sub-processors
We rely on the following third-party services to operate the Services. Each is bound by its own terms and data-protection obligations.
- Vercel — application hosting and file/blob storage
- Neon — managed PostgreSQL database
- Railway — bot hosting
- Stripe — payment processing
- Pusher — real-time messaging; chat messages, alerts (including Discord join alerts) and live updates transit Pusher to reach dashboards and overlays
- Resend — transactional email
- Upstash — rate limiting
- Discord, Kick, Twitch — platform integrations you authorise
- YouTube — optional inbound alert event source
We are not responsible for the privacy practices of third-party services. You should review their privacy policies separately.
7. Data shared through creator integrations and public pages
Creators can generate API keys and connect their own integrations (for example their website or a third-party service they use). API-key-gated endpoints return viewer data belonging to that creator — including viewer display names and platform user IDs, such as Discord IDs — to whatever integration the creator connects. This sharing is directed by the creator, is limited to that creator’s own community data, and each key carries scopes limiting what it can access.
Creators’ overlay pages (/o/[slug]) are public and do not require login — they are designed to be loaded in streaming software. Where a creator adds a live-chat widget to an overlay, chat messages (including usernames and message text) are rendered on that public page in real time and are typically visible on the creator’s stream. Other creator pages, such as leaderboards, stores and public hunt pages, can likewise display viewer usernames and engagement data at the creator’s direction.
8. Data storage and security
We implement reasonable technical and organisational measures designed to protect information against unauthorised access, misuse, disclosure, alteration and destruction. These include encryption in transit (TLS); encryption at rest at the storage layer, provided by our database provider (Neon); additional application-level AES-256-GCM encryption of platform integration tokens; bcrypt hashing of passwords; scoped access controls and audit logging. Our primary database is hosted on Neon in the EU (eu-west-2) region. However, no method of transmission or storage can be guaranteed to be completely secure, and use of the Services is at your own risk.
9. International users
Streamneeds is available globally and is operated from the United Kingdom. By using the Services, you understand and agree that information may be transferred, processed and stored in jurisdictions outside your country of residence, including the United Kingdom, the European Economic Area and the United States. Where required, we rely on appropriate safeguards such as the UK International Data Transfer Agreement or the EU Standard Contractual Clauses.
10. Data retention
We retain information only for as long as reasonably necessary for the operation of the Services, legal obligations, security, dispute resolution, fraud prevention, enforcement of agreements and legitimate business interests. Specific retention periods, enforced by automated daily jobs:
- Chat messages (Discord, Kick, Twitch and Hype), including reply previews — deleted 30 days after they were sent;
- Support-ticket transcripts — message content deleted 12 months after the ticket closes (the ticket record itself is kept for audit);
- Raw platform webhook payloads for Twitch cheers and gifted subs — scrubbed after 30 days (aggregate statistics are kept);
- Activity and diagnostic logs — deleted after 90 days;
- Discord server data — purged 30 days after the bot is removed from a server; re-inviting the bot within that window cancels the purge;
- Twitch channel data — purged when the channel is disconnected or the authorisation is revoked;
- Call bookings (your name, email, timezone and note) — deleted 12 months after the booked time, whether the call went ahead or was cancelled. Cancelling a booking stops the emails immediately, but the row is removed on that same schedule; ask us if you want it gone sooner (see Section 11).
Where a creator deletes their account through the account page, deletion is processed immediately on confirmation: their data — including their community’s stored chat — is deleted, and activity-log rows are anonymised rather than deleted so security audit trails remain intact. Certain information may be retained where reasonably necessary for legal, security or compliance purposes.
11. Erasure, amendment and your rights
Depending on applicable law and your jurisdiction, you may have rights to request access to, correction of, deletion of, or a portable copy of your personal information, and to restrict or object to certain processing. There are five ways to exercise erasure and amendment:
- In chat: run
/forgetmein Discord, or type!forgetmein Kick or Twitch chat. After confirmation, this deletes your stored chat messages for that creator’s community, removes previews of your messages quoted in other people’s replies, blanks the content of ticket messages you wrote, and stops your future chat from being stored there; - Through the creator: creators and their moderators can erase a viewer’s stored chat data from the viewer’s admin page;
- Amendment: details you submitted through a viewer info form (such as casino usernames or wallet addresses) can be viewed and updated through your personal form link — request it with
/myinfoin Discord; - Call bookings: use the private link in your confirmation or reminder email to cancel the call. Cancelling stops all further emails about it; email us if you also want the booking record deleted before its 12-month retention period ends;
- By email: send requests to streamneeds@sucksmedia.com. We action erasure requests within 30 days.
Chat erasure does not remove points balances, point-transaction history, purchases or linked-account records — these are retained so that balances, prize records and audit trails remain intact. We may verify your identity before processing a request. For viewer data, the creator whose channel you interacted with is the data controller (see Section 2.3), so you may also contact them directly.
12. Eligibility and user responsibility
You are solely responsible for ensuring that your use of Streamneeds complies with the laws, regulations and eligibility requirements in your jurisdiction. The Company accepts no responsibility for unlawful or non-compliant use of the Services.
13. User responsibility for content
You are solely responsible for all content, uploads, files, messages and activity processed through the Services. The Company does not actively monitor all activity, does not endorse user content, and accepts no responsibility or liability for user-generated content or creator activity.
14. Legal disclosures
We may disclose information where reasonably necessary to comply with applicable laws, respond to lawful requests, enforce agreements, investigate misuse, prevent fraud or abuse, protect platform integrity, or protect the rights, safety or security of the Company, our users or third parties.
15. Children
The Services are not directed at children under 18 and we do not knowingly collect personal data from anyone under 18. If you believe a child has provided us data, contact us and we will delete it.
16. Changes to this Privacy Policy
We may modify or update this Privacy Policy at any time. Continued use of the Services following an update constitutes acceptance of the revised policy.
17. Contact
For privacy-related enquiries or requests, contact:
- streamneeds@sucksmedia.com
- HALFORD SUCKS LTD
- Company Number: 14173794
- United Kingdom
If you are in the UK and believe we have not handled your data correctly, you also have the right to complain to the Information Commissioner’s Office (ico.org.uk).