Privacy policy
Last updated 24 September 2026 · ViralBulls Digital Media, Noida, India
This policy explains what ViralBulls Digital Media ("we") does with personal information inside ViralLeads, the internal customer-relationship system at crm.viralbulls.in.
ViralLeads is a private, internal business tool. It is not a public service and has no self-service sign-up: accounts are created by us for our own staff. If you are not a member of our team, you have no account here.
1. Who is responsible
ViralBulls Digital Media, Noida, Uttar Pradesh, India, is the data controller for everything described below.
| What you need | Who to write to |
|---|---|
| A question about this policy, or a request about your own data | hello@viralbulls.com |
| Anything about the system itself — an account, a login problem, a technical fault | deepanshu.gera@viralbulls.com |
2. What the system holds
| Category | What it is | Why we hold it |
|---|---|---|
| Business enquiry details | Name, phone number, email address, company name and website, the service enquired about, stated budget, industry, and where the enquiry came from | To respond to a business enquiry and to manage our sales pipeline |
| Contact history | Notes our staff write about calls and meetings, follow-up dates, status changes, and meeting times and outcomes | So the next colleague to speak to an enquirer knows what was already discussed |
| Client records | Company name, contact person, retainer value, renewal date and internal remarks | To manage ongoing client relationships and renewals |
| Staff accounts | Name, work email address, role, a hashed password, and a record of actions taken in the system | To control access, and to keep an accurate internal audit trail |
| Notification registrations | A browser push subscription, per member of staff, per browser they choose to enable | To send desktop reminders about follow-ups and meetings |
| Google authorisation | Encrypted access and refresh tokens, and the email address of the Google account a member of staff connected | See section 4 |
Enquiry details reach us because someone submitted an enquiry form on one of our websites, contacted us directly, or was added by a member of our team from a business conversation. We do not buy contact lists, and we do not scrape them.
What the system does not hold
- No payment card details, bank details or financial account numbers.
- No government identifiers.
- No special category data — nothing about health, religion, ethnicity, politics or biometrics.
- No tracking of visitors to our public websites. This system has no analytics, no advertising tags and no third-party trackers of any kind.
3. Cookies
Two cookies, both strictly necessary, both first-party: one holds the signed-in session and one carries the security token that prevents cross-site request forgery. There are no analytics, advertising or profiling cookies, which is why this system shows no cookie banner — there is nothing optional to consent to.
4. Google account access
A member of our staff may connect a Google account so that ViralLeads can put their meetings into their own calendar and read a spreadsheet of enquiries. Connecting is optional and can be withdrawn at any time.
| Permission requested | What we do with it |
|---|---|
calendar.events |
Create, update and cancel only the calendar events this system itself booked, and request a Google Meet link for them. We do not read, alter or delete any other event in the calendar. |
spreadsheets.readonly |
Read the rows of a spreadsheet a member of staff has specifically pointed us at, to import business enquiries. Read-only: nothing is ever written back. |
drive.metadata.readonly |
List the names of spreadsheets the connected account can open, so the person choosing one can pick it from a list instead of pasting a URL. This permission does not allow reading the contents of any file. |
openid, email |
Show which Google account is connected, so nobody connects the wrong one by mistake. |
Tokens are stored encrypted and are never shown in the interface, written to logs, or shared between members of staff — each person's connection is their own and is not readable by a colleague. Disconnecting in Settings → My calendar deletes the stored tokens immediately and asks Google to revoke them. Access can also be withdrawn from Google's side at any time, at myaccount.google.com/permissions.
5. Who else can see this information
Access is limited to our own staff, each through a named account, and only as far as their role requires. We do not sell personal information, we do not rent or share it for anyone else's marketing, and we do not use it for automated decision-making or profiling.
The only third parties involved are the services that run the system:
- Hostinger — hosting and email delivery for the application and its database.
- Google — only where a member of staff has connected a Google account, as in section 4.
- Google, Mozilla or Microsoft push services — deliver desktop notifications to the browser of a member of staff who switched them on. A notification contains a lead or client name and the reason for the reminder.
We may also disclose information where we are legally required to, or to establish or defend a legal claim.
6. Where it is held, and for how long
The application and its database run on servers in the Asia region. A Google connection may involve processing outside India, under Google's own terms.
- Enquiries that did not become clients are reviewed periodically and removed once there is no realistic prospect and no legal reason to keep them.
- Client records are kept for the duration of the relationship and afterwards for as long as tax and contract law requires.
- Staff accounts are deactivated rather than deleted when someone leaves, so the internal audit trail continues to record who did what. The account can no longer be used to sign in.
- Read notifications are deleted automatically after 60 days.
7. How it is protected
- All traffic is encrypted in transit over HTTPS.
- Passwords are stored as one-way hashes; nobody, including us, can read them back.
- Google tokens are encrypted at rest with an application key held separately from the database.
- Access needs a named account, and every account is limited to what its role requires.
- Changes to records are written to an audit trail that identifies the member of staff responsible.
No system is perfectly secure. If we become aware of a breach affecting personal information, we will act on it promptly and notify those affected and any regulator where we are required to.
8. Your rights
Whether or not you are one of our staff, you may ask us to confirm what information we hold about you, to correct it if it is wrong, to delete it, or to stop using it for a particular purpose. You may also object to us holding it at all.
Write to hello@viralbulls.com. We will respond within 30 days. We may need to verify your identity first, to avoid disclosing someone else's information to the wrong person.
If you are a member of our team and the problem is with the system rather than with your data — a password you cannot use, an account that will not open, something not working — write to deepanshu.gera@viralbulls.com instead.
If you would rather we did not contact you about your enquiry again, say so in a reply or ask us at that address, and we will stop.
9. Changes to this policy
If we change how the system handles personal information, we will update this page and the date at the top of it. Where a change is significant, we will tell the people affected directly rather than relying on them to notice.
10. Contact
ViralBulls Digital Media
Noida, Uttar Pradesh, India
Privacy and data requests: hello@viralbulls.com
The system, accounts and logins: deepanshu.gera@viralbulls.com