Privacy Policy
Effective Date: October 13, 2026
Operated by Gourav Kumar (sole operator), India — contact: varuoog755@gmail.com · expanded company info on our About page.
This policy describes what BigRedHub (“we”, “us”) actually collects and stores when you use bigredhub.info (the “Service”). It is written against the running system rather than a generic template: if a table or field is not named here, we do not store it.
1. Information We Collect
Account data. When you sign in with Google we store your email address, your Google display name and your Google profile picture URL, together with your BigRedHub workspace name and plan.
YouTube channel data. When you connect a channel we store its channel ID, title, custom URL, thumbnail, subscriber count, video count and view count, plus the OAuth access and refresh tokens needed to act on your behalf.
Comment data — including data about other people. This is the most sensitive category and we want it to be explicit. To decide whether to reply, and to prove whether a reply was delivered, we store for each comment on your videos:
- the comment text, in full;
- the commenter’s display name and YouTube channel ID;
- the video ID and video title it was posted on;
- the buyer-intent category and confidence score we assigned;
- the reply text we posted and YouTube’s ID for that reply;
- the delivery status and, if a reply failed, the error message.
These are comments left by members of the public, not by you. We process them solely to deliver the automation you configured on your own channel. We do not use them to build any profile of those commenters, and we do not share them with anyone except as described in section 4.
Your campaign configuration. The keywords, negative keywords, reply templates, CTA URLs, spintax settings, reply delays, daily caps, cooldowns and targeting rules you create.
Tracked links and conversions. The short link slug, its destination URL, campaign name, click count, lead and conversion counts, and attributed revenue. When you report a conversion, you may supply a customer identifier and an order value; we store those on your workspace so the attribution can be shown back to you.
Visitor telemetry on your tracked links. When somebody clicks one of your tracked links we record the browser user-agent string, the HTTP referrer it arrived with, and whether it looked like a desktop or a mobile device. We do not store the visitor’s IP address, and we do not geolocate it. The country and ip_hash columns on that table exist in the schema but are never written to, so in practice nothing derived from an IP address reaches this system.
Usage data. Number of channels connected, replies sent, tracked clicks and API calls attributable to your workspace in the current billing period.
Competitor information. If you use the competitor tracking feature we store the public channel ID, title, thumbnail and public statistics of the channels you add.
2. How We Use It
We use this data to operate the Service: authenticating you, polling comments on the channels you connected, classifying buyer intent, posting the replies your rules authorise, recording that a reply succeeded, resolving short links, attributing clicks and conversions to your campaigns, enforcing the limits attached to your plan, and notifying you when a channel needs reauthorisation or a reply fails.
We do not sell your data. We do not use your workspace content to train general-purpose models. We do not run third-party advertising or behavioural tracking scripts on bigredhub.info.
3. YouTube API Data and Limited Use
The Service uses the official YouTube Data API v3. Authorised scopes let us read comments on the videos on channels you connect, read public channel statistics, and post comments as part of your automation.
YouTube API data is handled under the Google API Services User Data Policy and its Limited Use requirements. Concretely, that means we:
- use API data only to provide and improve the Service you asked for;
- keep it in encrypted transit and at rest, and never expose comment content to another workspace;
- not transfer it to any third party except the service providers named in section 4, who process it on our instructions under equivalent confidentiality obligations;
- not use it to serve advertising, and not sell or share it to build audiences for unrelated products;
- retain it only for as long as section 6 describes.
5. Service Providers
These providers process data on our behalf to run the Service. Each is used only for the purpose listed.
| Provider | Purpose |
|---|---|
| Sign-in via OAuth; YouTube Data API v3 access to read comments and post replies. | |
| Supabase | Managed Postgres database and authentication that hold the data listed in section 1. |
| Vercel | Hosting and serverless runtime that execute this application. |
| Cloudflare | DNS, CDN and edge layer in front of bigredhub.info, including request metadata in edge logs. |
6. Retention and Deletion
Revoking Google access. You can revoke BigRedHub’s access at any time from your Google account permissions page. That immediately stops the Service using your token.
Disconnecting a channel. A channel is disconnected by removing it from your workspace. On removal, the row holding its OAuth tokens is deleted, and the stored comments and reply history attached to that channel are deleted with it through cascading foreign keys. Tracked links survive but lose the link to that channel, because they may still be resolving for links already posted.
Access tokens. OAuth refresh tokens are held only on the channel row and are destroyed when that row is deleted. We do not keep a second copy.
Account deletion. To delete your account and everything attached to your workspace, email us at varuoog755@gmail.com. We action account deletion requests within 30 days and confirm completion by email.
What we keep after deletion.Aggregated, non-identifying counts needed for billing and abuse prevention may be retained in de-identified form. Comment text and commenter identifiers are deleted with the workspace and are not retained.
7. Security
Traffic is served only over HTTPS. Session cookies are HTTP-only and signed, so a tampered token is rejected rather than trusted. Server-side access to the database uses a service-role key that exists only on the server and is never sent to the browser. Administrative access is restricted to accounts configured on the deployment, and the list of those accounts is not published in source.
No system is perfectly secure. If a breach affects your personal data we will notify you and any regulator as required by applicable law.
8. Your Rights
Depending on where you live, you may have the right to access, correct, delete, restrict or object to processing of your personal data, to receive it in a portable format, and to withdraw consent. Because the Service is authorised through a Google account and operates on your own YouTube channel, we cannot create an account for a child — see section 10.
To exercise any of these rights, email varuoog755@gmail.com. We respond within 30 days. You also have the right to complain to your local data protection authority.
Note on comment data: we hold comment text and commenter names on behalf of the channel owner whose videos received those comments. If you commented on a channel that uses BigRedHub and want that comment removed, contact us and we will forward your request to that channel owner, who controls the channel.
9. International Transfers
Our providers process data outside your country. Supabase, Vercel and Google process in the regions they operate, and Cloudflare serves traffic from points of presence worldwide. Where data leaves your jurisdiction we rely on the providers’ standard contractual protections.
10. Children’s Privacy
BigRedHub is not directed at children under 13 (or under 16 where that is the applicable threshold) and we do not knowingly collect their personal data. Because accounts are tied to a Google login connected to a real YouTube channel, the Service is intended for adults operating their own channels. If you believe a child has provided us personal data, email us and we will delete it.
11. Changes to This Policy
We will update this page when our data practices change. The effective date at the top always reflects the current version. Material changes affecting existing users will be announced by email before they take effect.
12. Contact
For privacy questions, data requests, or to reach our data protection contact, write to varuoog755@gmail.com.