Privacy Policy

This page is worth reading, but here is the whole of it in five lines:

• We collect what you type into a form, and nothing else you have not handed us.
• This site sets two cookies, and both are ours for counting visits - there is no advertising cookie here and nothing that follows you to another website.
• Google reCAPTCHA checks the forms, so that bots cannot flood them. It is the only reason a form touches Google at all.
• We never sell, rent or trade your details, and we do not send them abroad to be profiled.
• Ask us to delete your details and we will, without making it difficult.

Only what you hand over. When you submit a form on this site we receive:

• your name, email address and phone number;
• the course, batch or attendance mode you asked about, and anything you write in the message box;
• for a placement enquiry, the field you want to work in, how long you have been working, and your resume, if you attach one - see resumes and placement files below;
• which page you submitted the form from, so whoever calls you back knows what you were reading.

Our server also writes ordinary web logs - IP address, browser and device type, the page requested and the time. Those keep the site up and stop bots hammering the forms. They are not joined to your enquiry to build a profile of you.

We do not ask for and do not want your date of birth, your government ID numbers, your bank or card details, or anything about your health, religion, caste or politics. If you put something like that in a message box or a resume, it is because you chose to, and we would rather you did not.

If you register with the placement cell you can attach a resume. A resume usually carries more about you than an enquiry form does - past employers, salary history, sometimes an address - so it is handled separately from everything else on this site:

• it is stored on our own server, not in the public part of the website, and it cannot be opened by anyone who is not signed in to our system;
• it is saved under a randomly generated filename, so the web address of the file gives away nothing about whose resume it is, even to someone who knows your name;
• inside our system it is visible only to the placement and counselling staff who work on your profile;
• it goes to an employer only for a role you have agreed to be put forward for. We do not circulate resumes to build a database for recruiters, and we do not post your profile on job boards.

Ask us to withdraw your profile or delete your resume and we will remove the file, not just hide it. We cannot pull it back out of the inbox of an employer it has already gone to, so tell us before rather than after if you have second thoughts.

Each thing we collect is used for the reason you gave it to us, and not repurposed:

• to call or email you back about the course or the role you asked about;
• to run the training you enrol in, and to send you batch, schedule and certification information;
• to answer support questions and placement-cell enquiries;
• to present your profile to employers, where you have asked the placement cell to do that;
• to keep the site working and to stop automated abuse of the forms - the reCAPTCHA check on each form and the per-address submission limit exist for this;
• to count visits and see which pages and courses people actually read, so the catalogue gets better. This is read as totals, never as a list of named people, and nobody here looks up what any one visitor did;
• to tell you about a new course or batch, only where you have asked to hear from us. Every such message has a way out, and one line back to us is enough.

We do not use your details to advertise to you elsewhere, and we do not build behavioural profiles. The analytics cookies are for counting; the advertising half of Google Analytics is switched off, and the next section says exactly which switches those are.

Three cookies can end up on your device from this site, and not one of them is for advertising. Here is the whole list, with what each is actually for:

• _ga and _ga_<stream> - set by Google Analytics, and ours. They hold a randomly generated number so that a second page you read is counted as the same visit rather than a new stranger. They do not hold your name, email address or phone number, and they last about two years unless you clear them.
• _GRECAPTCHA - set by Google when a form on this site is verified, to tell a person apart from a bot. It belongs to Google rather than to us, and it is the reason the forms touch Google at all.

And one thing that is not a cookie:

• one entry in your browser's local storage, named rst-theme, written only if you switch between the light and dark appearance. It records that choice and nothing else, it never leaves your browser, and clearing your browsing data removes it.

What we have switched off

Google Analytics can do a great deal more than count. Each of those capabilities is a setting, and the settings this site ships with are:

• Analytics measurement: on. Visits, pages, how people arrive. This is what the two _ga cookies are for.
• Advertising storage: off. No advertising cookie is set.
• Advertising user data: off. Nothing from this site is sent to Google for advertising purposes.
• Ad personalisation: off. Your visit does not feed a remarketing audience, here or anywhere else.
• Google Signals: off. Your visit is not joined to your signed-in Google account to build a cross-device advertising profile.

There is no session recording, no heatmap tool, no fingerprinting and no chat widget. If we ever turn one of those switches the other way - for instance to run a Google Ads campaign - this list changes in the same release, because it is written one switch at a time rather than as a general reassurance.

Why there is no consent banner

You are not being asked to dismiss a cookie banner, and you are owed the reasoning rather than just the outcome. What runs here is first-party counting of our own pages, with the advertising side turned off, so there is no profile of you being built and nothing being shared for anyone else to target you with. A banner would make that feel like a bigger decision than it is, and the honest alternative - telling you plainly what is set and how to refuse it - is the paragraph below.

How to refuse it

It takes one of these, and all of them work whether we like it or not:

• block cookies for this site in your browser settings, or browse in a private window - the analytics cookies are not needed for anything on the site to work;
• install Google's own Analytics opt-out add-on, which stops the measurement on every site, not only ours;
• or turn on your browser's tracking protection, which blocks the analytics request before it is made.

Refusing any of this changes nothing about how we treat you, and nothing on the site stops working. The reCAPTCHA check is the one exception worth knowing about: block Google entirely and the forms fall back to a simple arithmetic question instead, so you can still reach us.

Every script, font, image and stylesheet that makes this site look and work the way it does is served from our own servers. Three features reach outside, all three of them Google, and you should know what each is for:

• Google Analytics, on every page. It tells us how many people came, which courses they looked at and whether a page is worth keeping. It receives the page you are on, roughly where in the world you are, and your device and browser type. Google sees your IP address in order to answer the request; it is not stored in the reports we read, and we never ask for it.
• Google reCAPTCHA, on pages with a form. It scores whether a submission came from a person, which is what keeps the enquiry forms from being flooded. Google looks at how the page was used to produce that score, under its own policy. It runs on the form pages, not on every page, and if you block it the form falls back to an arithmetic question we check ourselves.
• A Google Maps frame on /enroll and /contact-us, showing the Dadar classroom. Loading it means your browser contacts Google and Google may set its own cookies. Those two pages are the only ones that do it, and the address and a plain link to directions are written out on both, so you never have to load the map to find us.

Nothing else is permitted to load. The site sends a content security policy that names the handful of outside hosts allowed to serve anything on it - the ones above and no others - so an advertising tag, a tracking pixel or a chat widget cannot appear by accident, through a plugin or through a pasted snippet. That is what it is for, and we are not going to oversell it: it is a list of permitted hosts, not a guarantee against every possible flaw.

Elsewhere we link out to WhatsApp, to vendor certification pages and to other sites. Following a link or starting a WhatsApp chat hands you over to that company - a WhatsApp message to us is processed by WhatsApp, not only by us - and their policies govern from that point.

We do not sell, rent or trade your personal information - not to advertisers, not to lead brokers, not to other institutes. It is seen by:

• our own counselling, training and placement staff, so they can actually help you;
• the providers that run our servers and deliver our email, who hold data on our instructions and are not allowed to use it for anything of their own;
• an employer, for a role you have agreed to be put forward for;
• a court, regulator or law-enforcement body, where the law requires it of us. We hand over what is asked for and no more.

We keep each thing for as long as the reason we collected it still applies, and then we get rid of it:

• an enquiry that goes nowhere is kept while the conversation is live and for a while after, so a counsellor picking your file up later is not starting from nothing;
• a resume is kept while you are on the placement cell's books, and is deleted when you tell us you are no longer looking;
• records tied to a course you enrolled in - attendance, assessments, certification - are kept longer, because you may need us to confirm your training history years afterwards, and because our own tax and company-law obligations require it;
• server logs are short-lived and are used for operations, not marketing.

You do not have to wait for any of that. Ask us to delete something and we will, unless we are legally required to keep it - in which case we will tell you which part we have to keep, and why.

Concretely, rather than as a reassurance:

• the whole site is served over HTTPS;
• every form is rate-limited per address and screened by reCAPTCHA, so the forms cannot be harvested or flooded;
• the site sends a content security policy and the usual security headers, which fix the list of outside hosts allowed to load anything and stop the pages being framed by someone else;
• enquiry and student records sit behind staff accounts with roles - a staff member sees the enquiry queue, not everything;
• resumes are access-controlled and stored under unguessable filenames, as described above;
• this website never asks you for a password or card number, so there is no password or card number of yours on it to lose.

No system is perfectly secure and we are not going to claim otherwise. If something does go wrong in a way that puts your details at risk, we will tell the people affected and the authorities we are required to tell, rather than keeping quiet about it.

You can ask us at any time to:

• tell you what we hold about you, and who we have shared it with;
• correct or complete anything that is wrong or out of date;
• delete your details, or withdraw a resume from the placement cell;
• stop sending you anything promotional, while still answering the course question you asked;
• withdraw your consent altogether. Where we were relying on your consent, withdrawing it stops the processing that depended on it - it does not undo what was already done lawfully.

Email info@rstforum.net from the address you gave us, or call the office, and say what you want done. There is no form to fill in and no charge. We aim to deal with it within 30 days, and to tell you if something will take longer than that. If we cannot act on part of a request, we will say which part and why rather than ignoring it.

If you think we have mishandled your information, raise it with us first - most of these turn out to be something we can simply fix. Write to info@rstforum.netwith “Privacy” in the subject line, or ask the office for the person responsible for privacy questions, and you will get a considered reply rather than a brush-off.

If our answer does not satisfy you, you are entitled to take the matter to the data-protection authority in India. Doing so does not require our permission and we will not treat you any differently for it.

Our courses are built for working professionals and students in higher education. We do not knowingly collect the details of anyone under 18 without a parent or guardian's involvement. If you are under 18, please have a parent or guardian make the enquiry with you. If you believe a child's details have reached us, write to info@rstforum.net and we will remove them.

We update this page when what we do changes - if we add a chat widget, an advertising tag or any other third-party code, this page changes in the same release rather than months later. The effective date at the top is always the current version. If a change materially affects people who have already enquired, we will do more than quietly edit the page.

For the record, because a privacy policy that hides its own history is not worth much: until October 2026 this site set no cookies and ran no analytics, and this page said so. Page analytics and the reCAPTCHA check on the forms were added then, and the cookies and third-parties sections above were rewritten to describe them. Nothing about what we do with the details you send us changed.

RST Forum (Routing Switching Tigers Pvt. Ltd.), 3rd Floor, Sunshine Plaza, MMGS Marg, Gautam Nagar, Dadar East, Mumbai - 400014, Maharashtra, India.
Email: info@rstforum.net
Phone: +91 91672 24466