What we collect
Kavach360 is designed around the everyday work of communities: governance, resident communication, visitor coordination, maintenance, amenities, and records. The information collected will depend on the workflows a community chooses to use.
Workspace information
Community name, building details, configuration, contacts, and account settings needed to operate a workspace.
People and access
Names, contact details, role assignments, and access records needed to give each person the right view.
Operational records
Requests, approvals, announcements, visitor details, maintenance records, and other information entered by authorized users.
Product signals
Basic device, browser, and usage information that helps us keep the service reliable and understand which workflows need improvement.
How we use information
We use information to provide the service a community requests, protect accounts, support product operations, communicate important changes, and improve the clarity of the platform.
- Provide the product: operate workflows, permissions, notifications, records, and requested community services.
- Keep access accountable: authenticate users, apply roles, investigate suspicious activity, and maintain an audit trail where the product supports one.
- Support the people using it: respond to questions, troubleshoot issues, and communicate service or policy updates.
- Improve responsibly: use aggregated or de-identified signals where practical to understand product performance and usability.
Controls for your community
Community administrators should be able to see who has access, choose role permissions, correct records, and decide which workflows are enabled. Individual requests should be coordinated with the authorized community administrator where the information belongs to a shared workspace.
Design principle: the person responsible for a workflow should not automatically receive access to every workflow. Kavach360 separates views by role so access can follow responsibility.
Requests we support
Depending on the workspace and applicable law, people may ask to access, correct, export, restrict, or delete personal information. We may need to verify the requester and coordinate with the workspace owner before acting.
Retention and deletion
Information should be kept only for as long as it serves the community’s operational, contractual, security, or legal needs. Retention periods will vary by record type and workspace settings. When a workspace or personal-data deletion request is approved, the request is scoped first so that necessary records are not removed accidentally.
See Data deletion for the request path.
Questions or requests
For privacy questions, use the contact path and include the community name, your role, the request type, and the best way to follow up. Avoid sending sensitive personal information in an initial message.
Contact Kavach360