Privacy Policy

This policy explains what personal data Bytescare collects through bytescare.com and when you contact us, why we use it, who receives it, how long we keep it, and the choices and rights you have.

Who we are

Bytescare is the brand of Naxap Technology Private Limited, a company registered in India, with its registered office at E-92, First Floor, Lajpat Nagar-I, New Delhi, Delhi 110024, India. Bytescare Inc., at 16192 Coastal Highway, Lewes, DE 19958, USA, is also a Bytescare company. In this policy, “Bytescare”, “we”, “us” and “our” mean these companies.

Naxap Technology Private Limited is responsible for the personal data collected through this website. It is the Data Fiduciary under India’s Digital Personal Data Protection Act, 2023 and, where they apply, the controller under the EU and UK GDPR. Where a contract or order names Bytescare Inc., Bytescare Inc. is responsible for the personal data it handles under that contract or order.

How to contact us

• Questions or complaints about this policy or your personal data: our Grievance Officer, Mr. Mukul Dev, at grievance@bytescare.com.
• General enquiries: contact@bytescare.com.
• Job applications: join@bytescare.com.
• By post: Naxap Technology Private Limited, E-92, First Floor, Lajpat Nagar-I, New Delhi, Delhi 110024, India.

What we collect

Information you give us

Our forms ask for the following. You need to fill in a form’s required fields to send it, and without them we can’t answer you. Most forms mark them with an asterisk (*). Your phone number is always optional.

• Contact Us, Partnership Request and Retraction Request: your name, email address, phone number, company name and message.
• Chat: your name, email address, phone number and message.
• Book a Demo: your name, email address, phone number, company name, company website and message.
• Report Infringement: your name, email address, phone number and company name; your role (owner, follower or subscriber, or ally or helper); the type of infringement; the rights owner’s name and official website or profile; links to the infringing content; and your message.
• Report an Incident: your name, email address, phone number and company name, your website or social media handle, the infringing URL and your message.
• Careers: your name, email address, phone number, the department you’re applying to, a link to your résumé, your LinkedIn profile and your message.

Please don’t send passwords, payment card details or health information through our forms. Reports often include information about other people, such as the name of an account that copies content. Please share only what we need to review the report.

Client onboarding

When you become a client, we ask you to complete our onboarding form on Google Forms. It collects identity and contact details and documents, such as a government-issued photo ID or company registration and tax registration certificates, your registered and mailing addresses, your authorised signatory’s details, and proof that you own or license the content or brand we will protect. We use them to verify you and to act on your behalf. Google asks you to sign in with a Google account to upload files, and Google’s privacy policy applies to that sign-in.

Emails and messages

If you email us, we keep your message and our reply in our email system, which runs on Google Workspace. If you message us on WhatsApp or through our Telegram bot, we receive your phone number or Telegram account details and what you send; WhatsApp and Telegram handle those messages under their own terms and privacy policies.

Information collected automatically

• Your country. When you send a form, our server adds the country that Cloudflare, our hosting provider, works out from your connection, as a two-letter code such as IN or US, so we can route your message. The phone field uses the same country to preselect your dialling code. Our forms don’t send your IP address, and our server function doesn’t store it.
• Campaign tags. If a link with campaign tags (utm_source, utm_medium and utm_campaign) brings you to our site, most of our forms send the tags in the address of the page you send them from, so we know which campaign brought you. If you choose “Accept all”, we also keep the campaign tags of a form page you visit in your browser, and our forms send them from later pages too (see Cookies and similar technologies).
• Spam checks. When you start filling in one of our forms, Cloudflare Turnstile checks that a person, not an automated program, is using it (see Hosting and security).
• Technical data. Like any website, ours receives your IP address, browser details and the pages you request. Cloudflare processes them to deliver and protect the site, and Cloudflare Web Analytics counts visits and measures page speed for us (see Hosting and security).
• How your visit reached us. When you come to our site from another site or app, or directly, the page you land on works out a short label of where you came from: the source and medium in the link’s campaign tags, the ad network if you clicked an ad (such as google/cpc), the site or app that sent you (such as google/organic, chatgpt/ai, linkedin/social or example.com/referral), or direct/none. The label never includes the full address of a page, your name or your email address. When you open a “Book a call” link, or the calendar on our Book a Demo page, we add the label to it as utm_term, and Calendly keeps it with your booking (see Booking a call). When you send one of our forms, other than Report an Incident, the label goes with your submission, and we keep it with our stored copy of the submission (see Where form submissions go); the Google Form doesn’t receive it. Until you choose “Accept all”, and if you reject, only the page you land on adds the label, from its memory, and nothing is stored in your browser. If you accept, we keep the label in your browser until you close the tab, so later pages add it too.
• Form and booking events. When a form is sent, the page passes an event such as “generate_lead” to Google Tag Manager, with the form’s name and, on the Report Infringement form, the role you picked. When you book a call in the calendar on our Book a Demo page, Calendly tells the page, and the page passes the event “calendly_event_scheduled”. These events don’t include your name, contact details, message or the details of your booking. Google Analytics receives them as described under Cookies and similar technologies.

Searching our blog

When you search our blog, the words you type become part of the address of the results page (for example, bytescare.com/blog/search?query=telegram), and the page shows them. The search runs in your browser, on files from our own website: no search provider receives your words, and the search sets no cookies and stores nothing in your browser. Like the address of any page you visit, the address with your words reaches Cloudflare (see Hosting and security) and, if you accept them, the analytics and marketing tools described under Cookies and similar technologies; Google Analytics records the words as a site search. Until you choose, and if you reject, Google’s tags may include the address in the basic signals they send without cookies. Please don’t type personal information, such as names or email addresses, into the search box.

Where form submissions go

Our forms send your answers to a server function we run on Cloudflare, which passes them to a Google Form (Google). The answers are kept in our Google Workspace account, where our team reads them.

Before it passes them on, the function stores a copy in a database on Cloudflare (Cloudflare D1), so that a submission isn’t lost if the Google Form doesn’t record it. The copy holds the same answers the Google Form receives: your name, email address, phone number and company, your message together with the other answers the form collects (such as your website or the links you report) and the country our server adds, and the campaign tags. It also records which form you used, when you sent it and whether the Google Form recorded it, and the label of how your visit reached us when the form sent one (see “How your visit reached us” under What we collect). It doesn’t include your IP address, your browser details or the spam check’s token. We keep it for 24 months, after which it is deleted automatically (see How long we keep it). A submission that our checks refuse, such as one that fails the spam check, is neither stored nor passed on.

Google and Cloudflare process your answers for us as our service providers.

Hosting and security

Cloudflare hosts and delivers this website and protects it from attacks and abuse. To do this, it processes your IP address and the details of each request, such as the page, the time and your browser. See Cloudflare’s privacy policy (opens in a new tab).

We also use Cloudflare Web Analytics to count visits and see how fast our pages load, for visitors everywhere, including the EU, whatever you choose in the cookie banner. Cloudflare adds a small script to our pages (from static.cloudflareinsights.com) that reports each page view and how quickly the page loaded. Cloudflare says Web Analytics uses no cookies or other storage in your browser and doesn’t fingerprint visitors by their IP address, browser details or other data.

Our forms use Cloudflare Turnstile to tell people from automated programs that send spam. The first time you click or tab into a form, your browser loads Turnstile from Cloudflare (challenges.cloudflare.com). It usually needs nothing from you; if it can’t tell, it asks you to tick a box. For its check, Cloudflare processes signals such as your IP address, details of your browser and connection (its User-Agent header and TLS fingerprint), and our site’s Turnstile key and address. When you send the form, our server function asks Cloudflare whether the check passed and refuses the submission if it didn’t. Cloudflare says it uses these signals solely to detect and block bots, and to improve that detection, not to identify, profile or target anyone. See Cloudflare’s Turnstile privacy addendum (opens in a new tab).

Booking a call

Our “Book a call” links open our booking page on Calendly (Calendly, LLC) in a new tab. On our Book a Demo page, you can also pick a time without leaving the page: when you press “Show available times”, your browser loads Calendly’s script and booking page from Calendly’s servers, which receive your IP address and browser details, and Calendly may set its own cookies and show its own cookie notice there. Nothing from Calendly loads on our pages before you press that button. What you enter, such as your name, email address and the time you choose, is processed by Calendly for us to arrange the call. Calendly’s privacy notice (opens in a new tab) covers the cookies and other data Calendly collects for its own purposes, on its pages and in the calendar on ours. Each link, and the calendar on our Book a Demo page, carries campaign tags that tell us which page or form you came from (for example, utm_medium=form and utm_campaign=book_demo), and Calendly keeps them with the booking. They can also carry the short label of how your visit reached us (see “How your visit reached us” under What we collect).

Cookies and similar technologies

When you first visit, a banner asks for your choice. “Accept all” turns on the analytics and marketing tools described below, and lets the site keep the entries listed under “What the site stores only if you accept”. “Reject non-essential” keeps them off. Until you choose, they are off too, apart from the cookieless signals Google’s tags may send (see Google Analytics below).

What the site stores whatever you choose

These entries aren’t cookies, and they stay in your browser.

• bytescare_cookie_consent (local storage): your cookie choice and when you made it.
• bytescare_country (session storage): the country used for the phone field’s dialling code, kept until you close the tab.

An earlier version of the site saved your country and IP address in your browser under bytescare_geo. The site now deletes that entry. Earlier versions also kept the campaign tags whatever you chose; the site now deletes them unless you have chosen “Accept all”. Cloudflare may also set cookies it needs for security, for example after a browser check.

What the site stores only if you accept

These entries aren’t cookies either. If you reject non-essential cookies, or later change your choice, the site deletes them.

• utm_source, utm_medium and utm_campaign (local storage): the campaign tags of a form page you visited, kept until you clear them or change your choice. Our forms send them with a later submission, as described under What we collect.
• bytescare_source (session storage): the label of how your visit reached us, kept until you close the tab, for the “Book a call” links, the calendar on our Book a Demo page and our forms.

Analytics and marketing tools, only if you accept

We load these tools through Google Tag Manager (Google), which runs on every page and starts each tool according to your choice.

• Google Analytics (Google) shows us how visitors use the site, such as the pages they view, how they arrived and which forms they send. If you accept, it sets cookies such as _ga. We use Google Consent Mode: until you accept, and if you reject, Google’s tags don’t set or read analytics or advertising cookies, but they may send Google basic signals without cookies, such as the time, your browser type, the page that referred you and your consent choice, which Google uses to estimate overall figures.
• Google Ads. Our Google Analytics account is linked to our Google Ads account. If you accept, Google can use its advertising cookies, such as _gcl_au, and the analytics data to measure which of our ads lead to visits and enquiries, and to personalise ads.
• Microsoft Clarity (Microsoft) records how visitors use our pages, such as clicks, scrolling and mouse movements, so we can find and fix problems. It hides what you type into form fields. It sets cookies such as _clck and _clsk. If you accept, Microsoft may also use this data for its own purposes, such as improving its services and Microsoft Advertising, as the Microsoft Privacy Statement describes.

To learn how these providers use data, see how Google uses information from sites that use its services (opens in a new tab) and the Microsoft Privacy Statement (opens in a new tab).

Changing your choice

You can change your choice at any time. Use “Cookie settings” at the foot of any page or the button below, or delete the site data for bytescare.com in your browser’s settings, which also removes the cookies these tools have set on bytescare.com. The banner then appears again, the site deletes the entries it keeps only if you accept, and the tools stay off until you choose.

Show the cookie banner again

The button removes your stored choice and reloads the page. It doesn’t delete cookies already set; deleting the site data does.

Content from other services

Some pages show content hosted by other services. When your browser loads it, that service receives your IP address and browser details and may set its own cookies, under its own privacy policy:

• YouTube (Google): videos in some blog posts. See Google’s privacy policy (opens in a new tab).
• Calendly (Calendly, LLC): the booking calendar on our Book a Demo page, which loads only when you press “Show available times” (see Booking a call). See Calendly’s privacy notice (opens in a new tab).

Links to other sites, such as our social media pages, take you to sites with their own privacy policies.

Client engagements

If your organisation is our client, our Services Agreement governs the personal data we process to deliver the services, such as details of the accounts, listings and content we find and report. Under that agreement, the client decides how that data is used, and we process it on the client’s instructions. This policy covers the rest of our dealings with you, such as your enquiries, onboarding and our business relationship.

Takedown notices and reports we file for a client include the details the platform or the law requires, which can include the client’s name and contact details. Platforms may pass notices to the person whose content was reported, or publish them: Google, for example, may send a copy to the Lumen database, which removes the sender’s personal contact details.

If information about you is part of our work for a client, please contact that client, or write to us and we will forward your request to them. If you think your content was reported by mistake, send us a retraction request.

Why we use personal data, and on what grounds

We use personal data to:

• answer your enquiries and requests and follow up on them, including demo, partnership and retraction requests and infringement and incident reports;
• learn which campaigns and websites bring us enquiries and bookings;
• provide our services to clients, including onboarding and verification, and manage our relationship with them;
• consider job applications;
• keep the site and our systems secure and prevent abuse;
• with your consent, measure and improve the site and our marketing;
• comply with the law, respond to lawful requests from authorities, and establish, exercise or defend legal claims.

We rely on these legal grounds:

• Consent for the analytics and marketing tools, which run only if you accept. You can withdraw it at any time, as easily as you gave it (see Changing your choice).
• Information you give us for a purpose. When you send a form or an email, we use what you give us for that purpose. Indian law allows this for personal data you provide voluntarily for a specified purpose, unless you tell us you no longer agree.
• Contract, where the EU or UK GDPR applies: to provide services to clients and to take steps you ask for before entering into a contract.
• Legal obligation, where the law requires us to process or keep data.
• Legitimate interests, where the EU or UK GDPR applies: to answer business enquiries and follow up with businesses, to learn which campaigns and websites bring us enquiries and bookings, and to keep the site and our systems secure. You can object to this processing (see Your rights).

We don’t make decisions about you based solely on automated processing that have legal or similarly significant effects on you.

Who receives personal data

• Service providers that process it for us: Cloudflare (hosting, delivery, security, the spam check and the stored copy of form submissions, and Web Analytics), Google (Google Forms, Google Workspace, Tag Manager, Analytics and Ads), Microsoft (Clarity) and Calendly (bookings). Some of them also use data for their own purposes under their own policies, as described above.
• Bytescare companies, where needed to answer you or to deliver our services.
• Platforms, hosts and other recipients of the notices and reports we file for clients, as described under Client engagements.
• Rights owners and clients concerned: if you report content that infringes someone else’s rights, we may contact the rights owner and share your report with them, or act on it for them if they are our client; and we may pass a retraction request to the client a notice was filed for. Tell us in your message if you don’t want your name or contact details shared.
• Professional advisers, such as lawyers, accountants and auditors, where needed.
• Courts, regulators, law enforcement and other authorities, when the law requires it.
• A buyer or successor, if all or part of our business is merged, sold or transferred. The personal data would then be used as this policy describes, or as the law allows.

International transfers

Our service providers process personal data in many countries, including India, the United States, the United Kingdom and countries of the European Union. When we transfer personal data across borders, we do so as the applicable law allows. Where the EU or UK GDPR applies, we rely on the safeguards those laws provide for, such as adequacy decisions or the standard contractual clauses in our providers’ terms.

How long we keep it

We keep personal data for as long as we need it for the purpose we collected it for, and longer only where the law requires or allows, for example for tax and accounting records or legal claims. In practice:

• enquiries and requests: while we deal with them and follow up, and while we have a business relationship with you;
• the copy of each form submission stored on Cloudflare: 24 months. Older copies are deleted automatically each time a new submission is stored;
• client records: for the engagement, and afterwards for as long as the Services Agreement and the law require;
• job applications: for the recruitment process and for a reasonable time afterwards to consider you for other openings, unless you ask us to delete your application sooner;
• analytics data: for the retention period set in each tool.

When we no longer need personal data, we delete it or make it anonymous.

Security

We use reasonable security safeguards to protect personal data against loss, misuse and unauthorised access. For example, this site and its forms work only over encrypted (HTTPS) connections, and we rely on providers that protect the data they handle for us. No way of sending or storing data is completely secure, so we can’t guarantee absolute security. If a breach of personal data affects you, we will tell you and the authorities as the law requires.

Children

Our website and services are meant for businesses and adults. They are not directed at children under 18, and we don’t knowingly collect their personal data. If you believe a child has sent us personal data, contact our Grievance Officer and we will delete it, unless the law requires us to keep it.

Your rights

Your rights depend on where you live and which law applies.

India

The Digital Personal Data Protection Act, 2023 and the Digital Personal Data Protection Rules, 2025 are coming into force in stages. As each provision takes effect, you have the right to:

• get a summary of the personal data we process about you and how we process it, and the identities of those we have shared it with;
• have your personal data corrected, completed, updated or erased;
• withdraw your consent at any time, as easily as you gave it, without affecting processing before you withdrew it;
• have your grievances about how we handle your personal data redressed;
• nominate another person to exercise your rights if you die or become unable to exercise them.

If you aren’t satisfied with how we handle a grievance, you can then complain to the Data Protection Board of India, once it can hear such complaints.

Until those provisions take effect, section 43A of the Information Technology Act, 2000 and the Information Technology (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information) Rules, 2011 made under it also apply. Under the Rules, you can ask to review the information you gave us and have it corrected, and you can withdraw your consent by writing to us.

The EU, the EEA and the UK

Under the EU GDPR and the UK GDPR, you can ask us to give you access to your personal data, correct it or erase it, restrict how we use it, or give it to you in a portable format, and you can object to processing based on our legitimate interests. Where we rely on your consent, you can withdraw it at any time without affecting processing before you withdrew it. You can also complain to a data protection supervisory authority, in particular in the country where you live or work or where you believe the problem happened (see the list of EU and EEA authorities (opens in a new tab); in the UK, the Information Commissioner’s Office (opens in a new tab)). We would welcome the chance to address your concern first.

Elsewhere

You have the rights that your local law gives you.

How to use your rights

Email our Grievance Officer, Mr. Mukul Dev, at grievance@bytescare.com. Tell us which right you want to use and which data it concerns, with the name and the email address or phone number you used with us. We may ask for information to confirm your identity before we act, and we will respond within the time the applicable law sets. You can also tell us at any time to stop contacting you about our services.

Changes to this policy

We may update this policy when our practices or the law change. The date at the top of this page shows when it last changed. If the law requires us to tell you about a change or to ask for your consent again, we will.