+917972484197 Ask@StomatoBot.com

Customer Onboarding Terms

Last updated: 8th November 2026 · StomatoBot Technologies Private Limited

 

These are the commitments a customer accepts at signup / first camera-add for Digital WatchMan. They work together with the Privacy Policy, the Terms of Service, and the Refund & Cancellation Policy published on this site.

 

1. Customer-side equipment commitments

  1. Uninterrupted power for the camera chain (the UPS clause). Digital WatchMan watches your cameras from the cloud. Everything on your premises — DVR, router, and internet modem — must be connected to a UPS / power backup. If these lose power, your cameras go dark and NO service can see what happens at your premises during that time. Alerts about the outage itself (feed loss / site down) will still reach you, but footage during a power cut at your premises cannot be recovered. Keeping the DVR + router + modem on backup power is the customer’s responsibility and a condition of the service’s coverage promise.
  2. Working internet connection. The service monitors what your connection carries; sustained internet outages at the premises pause monitoring (you are alerted when the site goes dark and when it returns).
  3. Software updates. We update Digital WatchMan’s cloud software from time to time to fix problems and add protection. While an update is installed, your cameras may not be watched for a short time, usually no more than 1–2 minutes typically during your non-busy hours. We time updates to keep this as small as we can, and we avoid any hours you tell us are critical for you. Your cameras keep recording to your own DVR throughout; only our alerts pause.
  4. DVR/camera health. Cameras must remain connected to the DVR and the DVR reachable on the local network. We alert on feed loss, blinding, and tampering — repairs to customer-owned hardware remain with the customer.

2. Connection sizing (bandwidth calculation)

Digital WatchMan continuously pulls each camera’s sub-stream (~512 kbps CBR) to the cloud. Per camera that is:

  1. ~0.6 Mbps of UPLOAD bandwidth, continuously (0.512 Mbps stream + protocol overhead), plus ~0.5 Mbps extra per camera being watched live at that moment, plus small bursts for alert photos and daily reels.
  2. Data volume ≈ 5.5 GB/day ≈ 165 GB/month per camera — fine on fibre broadband, NOT suitable for mobile-hotspot or tightly capped plans.

Rule of thumb: minimum upload speed = (0.6 × number of cameras) + 1 Mbps. Examples: 2 cameras → ≥2.2 Mbps up; 4 cameras → ≥3.5 Mbps up;
8 cameras → ≥6 Mbps up. Any standard Indian fibre plan (30 Mbps+) comfortably covers a small shop; verify the UPLOAD figure, not the download headline.

3. DVR clock: timer + NTP settings (required at onboarding)

Alert times, daily-reel overlays, and evidence credibility all depend on the DVR’s clock being right. At setup (2 minutes in the DVR menu):

  1. Enable NTP: Configuration → Network → NTP → Enable, server time1.google.com, port 123, interval 60 min → Apply.
  2. Set the timezone to IST (UTC+5:30) so NTP lands on the correct local time.
  3. Keep the on-screen timestamp (OSD) displayed on each channel — the burned-in time is part of the evidence.

Note on timestamps (the ±few-seconds disclosure): the DVR’s burned-in time is the moment of capture; the Digital WatchMan overlay stamps the frame on arrival at our servers, typically 1–3 seconds later. That gap is normal network transit for off-site evidence, not an error, and it may vary slightly with connection load. Footage deliberately shows both clocks — the DVR’s and ours — so the capture time and the receipt time are each independently verifiable. Our servers’ clock is set from the National Physical Laboratory’s time servers, India’s official time.

4. Face recognition: camera placement (the honest physics)

Face recognition or any detection quality and accuracy is decided by CAMERA PLACEMENT more than by any software. One decent camera at face height, aimed at the entry choke-point (the door everyone must walk through), is worth more than any AI model upgrade. A high wide-angle camera sees tops of heads; a face-height camera at the entrance sees faces. For reference, the famous “found in a 50,000 crowd” cases  worldwide worked because cameras watched the entry gates at face height — not because software scanned the crowd.

At onboarding we advise:

  1. one camera at ~1.6–1.8 m height facing the entrance, walking path toward it;
  2. adequate lighting on the face side (light behind the camera, not behind the person);
  3. other cameras cover areas; THIS one identifies people.

5. What we commit to in return

  1. Alerts for feed loss / site-down within seconds of detection, with the last good frame as evidence.
  2. 24×7 detection while your equipment is powered and online, apart from the short pauses for software updates in section 1, off-site storage of alert evidence and daily reels based on the features you have subscribed to and per your plan’s retention.
  3. Outage credit and refund terms per the published Refund & Cancellation Policy.

6. Data protection — who is responsible for what (DPDP Act, 2023)

This section allocates responsibility under India’s Digital Personal Data Protection Act, 2023 and the DPDP Rules, 2025. It is not boilerplate: the allocation decides who answers to a person who was recorded, and it is easier to agree now than to argue later.

  1. You are the Data Fiduciary for your footage. You choose the cameras, where they point, what they capture and why. Under the Act that makes you the Data Fiduciary for the video and for every person who appears in it.
  2. StomatoBot is your Data Processor. We process that video, and everything derived from it — detections, alerts, evidence snapshots, clips and face templates — only on your instructions and only to provide Digital WatchMan to you. The single exception is a binding legal direction — a court order or a competent authority acting under statutory powers — which we comply with to the extent it requires and no further, as set out in section 8a of the Privacy Policy, and the use of your data to improve Digital WatchMan described in item 12 below, which is a condition of using the service.”
  3. Notice at your premises is yours to give, and it is a condition of using the service. You agree to display clear signage at every entrance stating that the area is under camera monitoring and — where you enable face recognition — that face recognition is in use and that the data could be used for training and quality analysis purposes. This is your responsibility as the Data Fiduciary; we cannot do it for you, because we are not at your premises. We supply printable notices in English and Marathi (or in your local language) so there is nothing to write: ask us, or download them from your account. Put them where a person can read them before they walk in.
  4. No subscription, no face recognition. Face recognition is a paid feature subscribed per camera. On a camera where it is not subscribed, no faces are recognized at all — no templates, no face images, for anyone.
  5. Children’s faces are blurred automatically, and you cannot switch it off. Where Digital WatchMan judges a face to belong to a child, it blurs that face in the stored image and keeps no face template or face picture for it. A face the system estimates to be under 18 is treated as a child — 18 being the age the DPDP law itself uses. Age judged from a camera image is approximate, so a face close to that line may be judged either way. This is because the DPDP law requires verifiable parental consent to process a child’s personal data, which cannot be obtained from a child walking into your premises. A person you mark as under 18 is the one case where we keep face templates, because recognising them is how we know to blur them (item 13). Recognition is less reliable at night, when the cameras switch to infrared and the picture loses all colour: a child is more likely to go unblurred after dark than during the day.
  6. Who may see face data. At your premises, face data is available to you and to the staff you authorise on your account, for the cameras you let each of them see. You are responsible for what your staff do with it. On our side, StomatoBot staff may access it only to operate or support the service — for example, to investigate a fault you have reported to us — and for the purpose in item 12.
  7. Face recognition carries an extra condition. You may enable it only where you have a lawful basis to do so for the people who will be recognised (for example, your own staff for attendance, on signage notice to them). You must not use it to identify members of the public against any external list, and Digital WatchMan provides no such capability.
  8. Requests from people who were recorded come to you. If someone asks for access to, correction of, or erasure of footage they appear in, they are your data principal and the request is yours to answer. We will help: tell us what to delete or produce and we will act on it promptly. If such a person contacts us directly, we will pass the request to you rather than act on our own — disclosing your footage to a third party without your instruction would itself be a breach. A request about our own use under item 12 we answer ourselves.
  9. What deletion does. When you discard an unnamed face, we erase its face templates and face pictures. On closure we erase your recorded video and your unnamed face data. When you close your account, your alerts, their photos and clips, your daily summaries and the people you have named are kept for 400 days for legal, audit and security reasons. After those 400 days we keep the pictures only with every face blurred and the link to your shop removed. While your account is open, a named identity is erased on your request to our Grievance Officer, as the Privacy Policy explains. When you remove an alert, it leaves your app; the alert and its photos and clips are kept by us under item 12 below. We also erase what a law requires us to erase. We keep billing records as tax or company law requires.
  10. If something goes wrong, you hear it from us first. In the event of a personal data breach affecting your data, we will notify you without undue delay with what we know and what we are doing, so that you can meet your own obligations as Data Fiduciary. We will also make the intimations the law requires to the Data Protection Board of India and report cyber-security incidents to CERT-In, as soon as possible to the best of our abilities within the 6 hours mandate.
  11. Timeline. The Act’s full obligations — notice, consent, data-principal rights, retention limits and breach reporting — and the Board’s penalties apply from 13 May 2027. These terms are written to that standard from the start so that nothing has to change under deadline pressure.
  12. Using your data to improve Digital WatchMan (a condition of the service): Digital WatchMan learns from the footage it works on. By using it you agree that StomatoBot may use the following to train, test and improve its models and products, for any commercial purpose and without time limit: your verdicts on alerts (real, false, dismissed); and the evidence frames and detections attached to alerts. StomatoBot may sell or license the models, weights and products it builds this way. StomatoBot never sells, rents or shares your raw footage, evidence frames, face images, face templates or any dataset made of them. Out of scope: footage of minors. Data and models already made from it stay with StomatoBot, because they cannot be taken apart. For this purpose StomatoBot decides why the data is used, so under the Act we act as a Data Fiduciary for it. The notice at your premises stays yours (item 3) and should say that footage may be used to improve the product.
  13. Age marking is your declaration, and your responsibility: Digital WatchMan blurs the faces of children it recognises as children. In your People gallery, you can mark a person as 18 or over, or as under 18. When you mark a person 18 or over, we treat that person as an adult and do not blur them, even if our age model disagrees. When you mark a person under 18, we keep their face templates so that we can recognise them, and on cameras with face recognition we blur them whenever we recognise them; on a camera without face recognition only our age model can blur them. Marking someone 18 or over is your statement that you know their age. If a child is marked 18 or over, the unblurred image follows from your marking, and responsibility and legal liability for it rests with you as Data Fiduciary (items 1 and 3). Only mark someone 18 or over if you are certain they are.

Full detail of what we collect, where it is stored and how long we keep it is in the Privacy Policy on StomatoBot.com.

7. Contact

StomatoBot Technologies Private Limited ·
U72300PN2015PTC156223 ·
12-A, 3rd Floor, RM Corner, VS1 Building, Near Maharaja Complex, Paud Road, Kothrud, Pune – 411038, Maharashtra, India ·
support(at)stomatobot(dot)com