Data processing addendum
Last updated 12 November 2026
The terms under which Propnova handles the personal data of your buyers and residents on your behalf. You decide why it is used; we only process it to run the service and keep it secure.
1. Scope and roles
This addendum forms part of the agreement between Shannova AI ("Processor") and the developer that holds a Propnova workspace ("Controller"). It applies to personal data of buyers, prospects, residents, visitors and staff that the Controller or its users put into the platform ("Customer Data"). For the purposes of India's Digital Personal Data Protection Act, 2023 the Controller is the Data Fiduciary and the Processor is the Data Processor.
2. Instructions
The Processor will process Customer Data only on the Controller's documented instructions, which are the agreement, this addendum and the Controller's use of the platform's features. If the Processor thinks an instruction breaks the law it will say so.
3. The Controller's responsibilities
- Having a lawful basis, and valid consent where required, to put Customer Data into the platform.
- Giving buyers and residents the notices the law requires.
- Configuring roles, retention periods and the other settings the platform offers.
4. Confidentiality
Everyone at the Processor with access to Customer Data is bound by confidentiality, and access is limited to those who need it to provide the service.
5. Security
The Processor maintains the measures in the Annex and may improve them over time without reducing the level of protection.
6. Sub-processors
The Controller authorises the sub-processors below. The Processor will give 30 days' notice before adding or replacing one, and the Controller may object on reasonable grounds. The Processor stays responsible for its sub-processors.
| Sub-processor | Purpose | Location |
|---|---|---|
| Supabase | Database, authentication, file storage | India region by default |
| Email delivery provider | Transactional email | As disclosed on request |
| Hosting and edge provider | Application hosting and delivery | As disclosed on request |
The Controller's own OpenRouter account, and its own Razorpay account for collecting payments from buyers, are services the Controller contracts for directly. They are not sub-processors of the Processor.
7. Helping with requests from individuals
The platform lets the Controller export, correct and delete Customer Data. If an individual contacts the Processor about their data, it will refer them to the Controller, and will help the Controller respond within the time the law allows.
8. Personal data breaches
The Processor will tell the Controller without undue delay, and in any case within 72 hours of becoming aware of a breach affecting Customer Data. The notice will say what happened, what data is affected, and what is being done, and the Processor will help the Controller meet its own notification duties.
9. Where data is processed
Customer Data is stored in the India region. The Processor will not move it to a country the Government of India restricts.
10. Return and deletion
On request, and for 30 days after the workspace closes, the Controller can export Customer Data. After that the Processor deletes it, including from active systems, and from backups as they expire, unless the law requires it to be kept.
11. Audits
The Processor will give the Controller the information it reasonably needs to show compliance with this addendum, including answers to a security questionnaire. If that is not enough, the Controller may audit on reasonable notice, once a year, at its own cost, subject to confidentiality and without disrupting other customers.
12. Liability and term
Liability under this addendum is subject to the limits in the terms of service. It lasts as long as the Processor holds Customer Data.
Annex: security measures
- Tenant isolation enforced by the database, tested automatically on every change.
- Role-based access with project-level scoping, enforced in the API and in the database.
- Encryption in transit with TLS and at rest. Secrets such as AI and payment keys use envelope encryption with a master key held outside the database.
- Two-step verification required for Propnova staff, and an append-only audit log of staff and system actions.
- Short-lived access tokens, rate limiting and signature verification on every inbound webhook.
- Private files served through short-lived signed links.
- Personal data masked before it is sent to tracing tools, and a retention schedule that purges visitor and gate records.
- Regular backups with point-in-time recovery, and a tested restore process.
Contact
ceo@shannovaai.com. To sign a countersigned copy, write to us. Last updated 12 November 2026.
Questions about this document? Write to ceo@shannovaai.com.