Privacy notice

Who decides

Data from your cameras, such as footage of residents, visitors and staff, vehicle plates and the faces of enrolled staff, belongs to your society. Under India's Digital Personal Data Protection Act, 2023 and the DPDP Rules, 2025, the society (its association or committee) is the data fiduciary and Pehra is its data processor. We handle that data only to run Pehra for the society and on its instructions, as set out in the terms.

Your account data, such as the name and email of the people who sign in, is ours to look after: we decide how it is used, as described here.

What we store

• Account: names, emails and Google account ids, the society's name and time zone, and each member's role.
• Cameras: names, purposes, stream addresses (which can include a camera's password), and the zones and lines drawn on them.
• Footage: stills and short clips from watched cameras, and a record of what was seen in them, such as people, vehicles and times, which the watches and their backtests use.
• Logs: vehicles at the gates (time, direction, kind of vehicle, plate text and colour when read, a picture) and staff attendance (first seen and last seen each day).
• Staff enrolment: for each enrolled adult staff member, their name, their work, a record of their consent, and face templates, which are numbers made from 3 to 5 photos. The photos are not kept after enrolment.
• Alerts: what happened, the reason given, and who acknowledged it or marked it a false alarm, and when.
• Telegram: the id of the group your society connects.
• Billing: your plan and subscription status from Polar. We never see card or bank details.
• Security logs: sign ins, clip views, cameras added, enrolments and exports.
• Access logs from our web server, which hold IP addresses.

Faces

Pehra names only adult staff, such as maids, drivers, cooks and guards, who agreed to be enrolled, with their consent recorded. It never enrols, identifies or estimates the age of children, and it has no watches about children. Residents and visitors are never identified: to Pehra they are a person, a car or a cab.

Staff can say no. Not enrolling is the option without a face, and the society should keep another way to log their work. When a worker leaves or withdraws consent, the society deletes their enrolment and their face templates are deleted with it.

Telegram and clips

Alerts sent to Telegram carry a still picture, the reason, the camera and the time. Faces of people who are not enrolled staff are blurred in that picture. Blurring is automatic, so a face can occasionally be missed. Video is never sent to Telegram: clips stay behind sign in, open only to the society's team by role, and every view of a clip is recorded. There is no bulk download of footage.

Your society chooses who is in its Telegram group. Messages there are handled by Telegram under its own policy.

Notices at each camera zone

The society puts up a notice at each camera zone saying what the camera is for, how long footage is kept and whom to contact with a grievance. Pehra makes a printable notice for each zone.

How long we keep it

• Free: footage kept 7 days.
• Society: footage kept 30 days.
• Large sites: footage kept as long as agreed.

When that period ends, footage, clips, stills, gate log rows and attendance rows are deleted automatically. Incident clips are kept for the same period. On AWS clips are kept in a private S3 bucket until their date, then deleted.

To close your society's account, email hello@dijmo.com from the owner's account email. We then delete its data, except records the law requires us to keep, such as invoices. Access logs, which hold IP addresses, are kept for a year.

AI checks

OpenCV on our servers does the watching. When it flags a moment that needs a closer look, Pehra can send a few stills of that moment and the watch's words to an AI vision model through Amazon Bedrock on AWS. Amazon Bedrock does not use this data to train models. The AI never sees the live stream or whole clips, and a daily limit caps how many checks each society makes.

Where it is kept

On Amazon Web Services in Mumbai, India. It is encrypted in storage and in transit. Storage is private, and pictures and clips open through short lived links.

Who else handles data

• Amazon Web Services: hosting, storage and Amazon Bedrock.
• Telegram: alerts to the group your society connects.
• Polar: checkout, subscriptions, tax and invoices, as merchant of record.
• Google: sign in.
• Cloudflare: our domain and the network that carries traffic to Pehra.

We do not sell data and we do not use advertising or tracking cookies. One cookie keeps you signed in.

Your rights and grievances

If you are a resident, visitor or staff member and want to see, correct or erase data about you in your society's footage or logs, ask your society's committee first, as it decides; we help it answer. For your own account data, email hello@dijmo.com from your account email.

Our grievance contact is Hamid Mahmood Siddiqui, at hello@dijmo.com. If you are not satisfied with the answer, you can complain to the Data Protection Board of India.

Breaches

If a breach affects personal data, we tell the societies affected within 72 hours of finding out.