Privacy policy
In effect from 17 November 2026.
Chennai Stream is the name under which Malargal Systems, 41 Bunder Street, Chennai, Tamil Nadu 600001, India ("we", "us") provides streaming services to organisations. This policy explains what personal data we handle, why, and what you can ask of us. It covers this website, enquiries made to us, and the streaming services we provide for our customers.
1. This website
This website is a set of plain pages. It has no sign-in, no forms and no advertising, and the pages of this website do not set cookies. Cloudflare (see below) may set a security cookie that it needs to tell people from automated traffic; it is not used for advertising.
The website is delivered through Cloudflare, a network provider that sits between visitors and our server to protect the site and speed it up. As with any website, our server and Cloudflare record standard access details for each visit: the visitor's internet (IP) address, the time, the page asked for and the type of browser. We use these records to keep the site secure and working, and to count visits. Cloudflare's visit counting does not use cookies and does not follow visitors across other websites.
2. When you contact us or become a customer
If you email or call us, we keep your name, your contact details and what you tell us, so that we can reply and, if you become a customer, provide the service. For each customer we also keep a record of what was ordered and of the payments made, to provide the service and to keep our accounts. We do not add you to a mailing list.
3. The streaming services we provide
Our customers include event organisers, institutions and schools. Each customer decides what is streamed and who may watch it. We handle the video, and the records about the customer's viewers and staff, on the customer's behalf and on the customer's instructions. In the terms of the Digital Personal Data Protection Act, 2023, where it applies, the customer is the data fiduciary for that data and we are its data processor. For the accounts and contact numbers of our own staff, and for the data described in sections 1 and 2, we are the data fiduciary.
What we handle
Our private live streams are being moved to a new streaming platform. Where a point below, or in sections 7 and 8, applies only to streams already on it, we say so.
- Video and audio that a customer streams through us: a live event, recordings the customer gives us to host, or a private live stream (continuous live video from the customer's premises, meant for an audience the customer chooses and not for the public). For a school, the private live streams are continuous live video of its classrooms and other rooms through the day, and they show children and staff.
- Recordings of private live streams. Whether a private live stream is recorded, and how long the recording is kept, are as agreed with the customer (see section 7). On our new streaming platform, authorised staff can play a recording back, and can save a clip from it as a video file, for example when the customer asks for one; every such export is logged.
- Access checks. A private live stream is opened from the customer's own app or page, and the customer decides who is given access. For a school's streams, the school's app opens our viewing page with an access token and a reference issued by the school. We send both to the school's system, which tells us whether to show the stream. Our own staff can also open the viewing page themselves, to test a stream as a viewer sees it. We keep no database or list of these values, and they do not tell us who anyone is; but they are part of the address of the viewing page, so they are recorded in our web server's access log (see section 7).
- Viewing records. When someone watches a private live stream on our new streaming platform, the server logs the time, the stream watched, the viewer's IP address, the type of browser or app and the page the stream was opened from, and we work out the country the address belongs to. The viewing page also keeps a random identifier in the browser and sends it with each viewing, so that repeat visits count as one viewer. In our statistics the identifier is stored in scrambled form and the IP address is not stored; where a viewing arrives without the identifier, a scrambled value made from the IP address and the type of browser is stored in its place. For our other services, and for private live streams still on our older system, the servers keep standard access logs: the time, what was requested, the viewer's IP address and the type of browser or app.
- Accounts of the people who manage streams (our own staff and, where a customer has been given access, the customer's staff): name, sign-in name, password (stored only in scrambled form), two-step sign-in settings, permissions, and a log of their sign-ins, the changes they make and the recordings they export, with the time and the IP address used.
- Names and mobile numbers of the staff who receive service messages on WhatsApp, as described in section 5.
Why we handle it
- To deliver the stream to the people the customer has authorised.
- To let our own support staff set up the streams, check that they are working and fix faults.
- To keep the service secure, and to investigate faults and misuse.
- To give the customer viewing statistics, such as how many people were watching a stream and from which countries.
- To let recent video be looked at again where a customer's streams are recorded, for example when a school needs to check what happened in a classroom.
We do not sell personal data. We do not use customers' video, or records about viewers, for advertising, and we do not use the video to identify or profile the people in it.
4. Children
Some of the private live streams we carry for schools show classrooms, and so show young children. Parents and guardians reach the streams through the school's own app or page, and the school decides who is given access. School staff to whom the school has given access can also see these streams. So can members of our own support staff who have an account, so that they can run the service and fix faults.
Where the school has agreed to it, these streams are also recorded; the school, or we, can tell you whether a stream is recorded and for how long a recording is kept. On our new streaming platform, a recording can be played back, or a clip saved from it, by members of our own staff, and of the school's staff where the school has been given access, whose accounts allow it.
Each school decides whether its classrooms are streamed and who may watch. The school is responsible for telling parents and staff about the streaming and for obtaining any consent the law requires. If you are a parent and have a question or a concern about a classroom stream, or want access changed or removed, please speak to your child's school first. We act on the school's instructions, and we will help the school answer you.
This website and our services are not meant to be used by children themselves, and we do not knowingly collect personal data from children directly.
5. Service messages on WhatsApp
We use WhatsApp to send operational messages about the private live streams we run: a short status report each morning on the days the streams are due to run, and alerts when a stream goes offline or comes back online. They go only to a small number of staff who look after the streams (our own and, in some cases, a customer's), each of whom has agreed beforehand to receive them on WhatsApp. To send them we store the person's name and mobile number and, for about three months, a log of the messages sent. The messages contain the names of the locations and streams concerned, and times, and nothing about children, parents or viewers. They are delivered by WhatsApp (Meta), which handles them under its own terms.
We do not send marketing messages on WhatsApp, and these messages are not sent to parents or other viewers. Anyone receiving them can ask us to stop at any time, by telling us directly or by using the contact details in section 10, and we will then remove their number from the list.
6. Who we share data with
We share personal data only as needed to run the services:
- with the customer whose stream it is;
- with the companies whose infrastructure we use: data-centre and network providers that host and carry our customers' streams, the content-delivery services from which the viewing page for private live streams loads its video player and fonts, Cloudflare for our web pages, and WhatsApp (Meta) for the messages described in section 5. Some of these companies process data on servers outside India;
- with a court, regulator or law-enforcement authority, when the law requires us to.
7. How long we keep it
- When a private live stream runs, whether it is recorded and how long a recording is kept are as agreed with the customer. The customer, or we, can tell you whether a stream is recorded and for how long its recording is kept.
- On our new streaming platform, the recordings of a stream that is in use are deleted automatically soon after the agreed period ends. Video from a stream that is not being recorded is not kept beyond the couple of minutes needed to deliver it.
- A clip saved from a recording stays on our new streaming platform for 24 hours, so that it can be downloaded, and is then deleted there. The downloaded file is given to the customer who asked for it.
- Recordings that a customer gives us to host are kept for as long as the customer has us host them.
- Viewing records of private live streams on our new streaming platform: the server log that holds viewers' IP addresses is kept for about two weeks, for security. The record of each viewing (time, stream, country and the scrambled identifier, without the IP address) and the totals made from it are kept for about 13 months. The standard access logs of our other servers, including the web server that serves the viewing page (its log holds the access token and the school's reference described in section 3), are kept for a limited period, for security.
- Accounts of people who manage streams are kept while the person has that role. The log of sign-ins, changes and exports is kept, for security, for as long as we run the service.
- Names and numbers of staff who receive WhatsApp messages are removed from the recipient list when they ask us to stop or leave that role. The log of messages sent, which includes the number each message went to, is kept for about three months. The log of changes keeps a note that the person was added or removed, with their name and a partly hidden number.
- Enquiries, customer correspondence and our records of orders and payments are kept for as long as we deal with you, and afterwards for as long as tax and other laws require.
8. How we protect it
On our new streaming platform:
- Video is delivered to viewers, and the admin panel is reached, over encrypted (HTTPS) connections.
- A private live stream can be opened only with a signed link that expires.
- Everyone who signs in to the admin panel has an account of their own with only the permissions they need, and signs in with a second step (a code from an authenticator app).
- Sign-ins and changes made in the admin panel are logged.
Private live streams not yet moved run on our older system until the move is complete, and the points in this section and in section 7 that mention the new platform do not all apply to them yet. The customer concerned, or we, can tell you which system a stream is on.
No system can be made perfectly secure. If we learn of a breach that affects personal data, we will tell the customer concerned, and we will tell the authorities and the people affected where the law requires it.
9. What you can ask of us
You may ask us what personal data we hold about you or your child, ask us to correct it or delete it, withdraw a consent you have given, or raise a complaint. Write to the Grievance Officer at the address in section 10. We will reply within one month, and within that time we will settle anything that is ours to decide.
Where we hold the data on behalf of an organisation, for example a school, we will pass your request to that organisation and help them to answer it, because the decision is theirs.
10. Contact and grievances
Questions about how we handle personal data, the requests described in section 9, and complaints all go to our Grievance Officer:
Prem Anand, Grievance Officer
Malargal Systems (Chennai Stream)
41 Bunder Street, Chennai, Tamil Nadu 600001, India
Email: contact@chennaistream.com
Phone: +91 44 4204 6468
If you are not satisfied with our answer, the Digital Personal Data Protection Act, 2023 provides, where it applies, for a complaint to the Data Protection Board of India, once you have first raised the matter with us (or, where we hold the data on behalf of an organisation such as a school, with that organisation). The Act is being brought into force in stages, and this part is due to take effect in May 2027.
11. Changes to this policy
When we change this policy we will publish the new version on this page with a new date. This policy is governed by the laws of India.
