Data Processing Agreement
For housing societies that use aptzo. The society is the data fiduciary; Aravir Technologies is its data processor.
Last updated 2 November 2026
Parties and Scope
This agreement is between the society that uses aptzo (the society) and Aravir Technologies (we). It covers the personal data the society puts into aptzo to run the society: members and flats, billing and collections, gate entry, and community features. It forms part of the terms of service.
Instructions
We process the society's personal data only to provide aptzo, as the society directs through its settings and its use of the app, and as the law requires. We do not use it for advertising, we do not sell it, and we do not use it for any purpose of our own.
Confidentiality and Our Staff
Only the people who run the service have operator access, and that access shows a society's name, city, plan, counts of flats and members, credit balances and our invoices to it. It does not show residents' names, contact details, gate entries or the society's accounts. Every operator look and change is logged, and every change is also written to the society's own audit log.
Security Safeguards
These map to the reasonable security safeguards in Rule 6 of the Digital Personal Data Protection Rules, 2025.
| Safeguard | What aptzo does |
|---|---|
| Encryption, masking and tokens | HTTPS for every connection. Stored secrets, such as payment gateway keys, encrypted with AES-256-GCM. Sign-in codes and gate pass codes stored only as hashes. Only the last four digits of a visitor's mobile number are stored. |
| Access control | Role-based access inside each society. Each society's data is separated by row-level security forced in the database, so one society can never read another's rows. Operators sign in separately and see counts only. |
| Visibility of access | An append-only audit log of changes. A data access log that residents can read for their own record. A log of every operator action. |
| Continued processing | Nightly database backups, encrypted and kept away from the server, with a tested restore. |
| Logs kept a year | Logs and the related data needed to detect, investigate and fix unauthorised access are kept for at least one year, unless the law needs longer. |
| Breach help within 72 hours | See Personal Data Breaches below. The app has a breach log for the society to record each event and update it. |
| Contracts with sub-processors | Each sub-processor below is bound to protect the data and use it only for its part of the service. |
Personal Data Breaches
If we become aware of a breach affecting the society's data, we tell the society without delay, with what we know of its nature, extent, timing, likely impact and the steps taken. We then give the society what it needs to send its detailed report to the Data Protection Board within 72 hours, and help it tell the people affected.
Rights Requests
The app gives the society the tools to answer requests: export of a person's data, correction, erasure requests, consent records and the access log. If a request reaches us directly, we pass it to the society and help it answer within the time the law sets.
Retention and Erasure
Data is kept for the periods the society sets in its retention settings, within the safe minimums in the app. Gate entries default to 90 days; after that, personal details are erased and only counts remain.
When the society leaves, it can export its data first. We then delete it from the live service within 60 days, and from backups as they expire, within a further 35 days, except what the law requires us to keep: our own invoices for 8 years, and the access and processing logs for one year.
Sub-processors
We use these providers. We will tell the society at least 30 days before adding or replacing one, and the society may object and stop using aptzo before the change.
| Provider | Purpose | Data |
|---|---|---|
| DigitalOcean, data centre in Bengaluru, India | Runs the servers and the database | All service data |
| Google Firebase Cloud Messaging, which may process outside India | Delivers notifications to phones | Device token and the notification text |
| Zoho Mail, data centres in India | Sends sign-in codes, invitations and notices | Email address and the message |
| MSG91, only for societies that turn on SMS [data location to be confirmed] | Sends SMS | Phone number and the message |
| Meta WhatsApp Business Platform, only for societies that turn on WhatsApp; may process outside India | Sends WhatsApp messages | Phone number and the message |
| Payment gateway (Razorpay) | Online payments, only for societies that turn them on, into the society's own account | What the payment needs: payer name, amount and reference |
Children
Where the society records a child's data, it obtains the verifiable consent of a parent or lawful guardian that the law requires.
Cooperation
We answer the society's reasonable questions about how we process its data, and give it the information it needs to show it meets its own duties.
Term
This agreement lasts as long as the society uses aptzo, and its duties on confidentiality and deletion continue after that.