Website, app, and operations terms

1. Agreement and scope

• These terms govern access to and use of the Kavach360 public website, blog, contact routes, pricing pages, checkout handoffs, web dashboard, mobile apps, support channels, and related services.
• A signed order form, master services agreement, enterprise agreement, data processing agreement, statement of work, app-store term, or payment provider term may apply in addition to these terms. If those documents conflict with these public terms for the same subject, the signed or provider-specific document controls for that subject.
• By using the website, submitting a form, accessing the app, accepting an invite, creating an account, approving a workflow, or using a checkout route, you agree to these terms on behalf of yourself and, where applicable, the organisation, society, property, or customer account you represent.

2. Eligibility and authority

• You must have the legal capacity and authority required to use Kavach360 and to submit information into the service.
• If you act for a society, residents' association, builder, developer, township, commercial property, employer, vendor, or managed portfolio, you confirm that you are authorised to bind or represent that party for the relevant action.
• Customer admins are responsible for deciding who should be invited, what roles they receive, which modules are enabled, and when access should be removed.
• Kavach360 may refuse, suspend, or remove access if authority, account ownership, payment status, security, compliance, or misuse is in question.

3. Accounts, roles, and credentials

• Users must provide accurate account, contact, and organisation information and keep it current.
• Credentials, OTPs, recovery flows, passkeys, devices, and admin accounts must be protected. You are responsible for activity under your account unless the activity results from a Kavach360 security failure.
• Role-based permissions are only useful when customers configure them carefully. Customer admins should review permissions, remove inactive users, and keep committee, finance, gate, vendor, staff, resident, and support roles aligned with real responsibilities.
• Shared logins are discouraged. Kavach360 may require separate user accounts for auditability, security, payment traceability, or customer support.

4. Website, content, and public information

• The public website, feature descriptions, pricing direction, blog posts, screenshots, product narratives, and examples are provided for commercial evaluation and education.
• Product features, modules, integrations, app screens, pricing, availability, and implementation timelines may change as the platform evolves.
• Website content is not legal, accounting, tax, financial, security, governance, or property management advice. Customers should take professional advice where their local rules, bylaws, contracts, tax duties, or statutory obligations require it.

5. Subscriptions, orders, and payments

• Plans, fees, billing cycles, usage limits, onboarding scope, support commitments, taxes, implementation work, and renewal terms may be stated on the website, checkout page, invoice, order form, or signed agreement.
• Public checkout pages may redirect or hand off to third-party payment providers. Provider-specific terms, authentication, settlement, refund, chargeback, fraud, dispute, and payment data policies apply once a user interacts with that provider.
• Payment confirmation can depend on provider status, bank rails, reconciliation, fraud checks, tax data, or manual review. A submitted payment does not guarantee account activation until Kavach360 or the customer-facing workflow confirms it.
• Refunds, cancellations, credits, downgrades, upgrades, and renewals are handled according to the applicable plan, invoice, checkout provider, order form, or signed agreement. If no separate refund term applies, refund decisions are made case by case based on service delivery, usage, payment status, onboarding work, and applicable law.
• Users must not submit false payment information, initiate fraudulent chargebacks, bypass checkout controls, misuse coupon or plan links, or interfere with payment reconciliation.

6. Customer data and operational records

• Customers and authorised users retain responsibility for the accuracy, legality, quality, and permission basis of data they create, upload, import, approve, or publish inside Kavach360.
• Customer data may include resident records, unit records, visitor logs, dues, invoices, receipts, notices, complaints, service requests, approvals, vendor records, staff records, documents, images, comments, audit logs, and other operational information.
• Kavach360 may process customer data to provide the service, secure the platform, support users, troubleshoot issues, maintain backups, analyse aggregate product performance, comply with law, and enforce these terms.
• Customers must not upload data they are not authorised to process, including data about residents, staff, vendors, minors, vehicles, payment status, or visitors without the required authority, notice, consent, or lawful basis.
• Kavach360 does not independently verify every community notice, dues amount, visitor instruction, vendor credential, governance decision, bylaw, penalty, meeting outcome, or local compliance requirement entered by a customer.

7. Resident, staff, vendor, and visitor use

• Residents, staff, vendors, visitors, and other account users must use Kavach360 only for legitimate community, property, payment, communication, access, support, and service workflows.
• Users must not impersonate others, submit misleading requests, abuse complaint or escalation tools, publish unlawful content, scrape data, harass users, attempt unauthorised access, or interfere with operations.
• Operational notifications, visitor approvals, payment reminders, and service updates are intended to improve coordination. Users should still apply judgement and follow customer instructions, emergency protocols, society bylaws, and local law.

8. Acceptable use and prohibited activity

• Do not probe, scan, attack, overload, reverse engineer, copy, resell, benchmark for competitive purposes, bypass access controls, or use Kavach360 to distribute malware, spam, phishing, harmful code, or unlawful material.
• Do not upload sensitive documents, identification data, payment data, health data, children's data, or private resident information unless the enabled feature requires it and you have the required authority.
• Do not use automated tools, bots, scraping, credential stuffing, denial-of-service techniques, unauthorised integrations, or bulk exports except through approved product features or written permission.
• Do not use Kavach360 to make discriminatory, defamatory, threatening, fraudulent, illegal, or unsafe decisions about residents, staff, vendors, visitors, or customers.

9. Mobile apps, app stores, and permissions

• The Kavach360 mobile app may be distributed through app stores or enterprise distribution channels. App-store account, download, subscription, update, refund, privacy, device, and platform terms may also apply.
• App permissions such as notifications, camera, media, device information, or location are requested only when a feature needs them. Disabling a permission may limit the related feature.
• Users are responsible for keeping app versions, operating systems, and device security reasonably current. Kavach360 may stop supporting old app versions, operating systems, devices, or APIs when security or platform requirements change.

10. Third-party services and integrations

• Kavach360 may integrate with payment providers, notification services, SMS and email services, analytics, CRM, customer support tools, cloud providers, identity services, app stores, maps, accounting tools, or customer-selected integrations.
• Third-party services may have their own terms, fees, availability, uptime, support, privacy, data retention, and compliance obligations. Kavach360 is not responsible for third-party failures outside its control.
• If a customer connects an integration or asks Kavach360 to work with a vendor, the customer confirms that it has authority to share the required data and accepts the operational risks of that integration.

11. Security, privacy, and compliance

• Use of Kavach360 is also governed by the Privacy Policy, security practices, account controls, and any customer-specific data processing or confidentiality agreement.
• Customers must configure roles, permissions, data imports, resident notices, consent flows, retention expectations, exports, and operational rules in line with applicable law and their community governance obligations.
• Users must promptly report suspected account compromise, unauthorised access, payment anomalies, data errors, abusive content, or security incidents through the support or contact channel.
• Kavach360 may access accounts, logs, records, or support context when needed to provide support, investigate abuse, maintain security, comply with law, or enforce these terms.

12. Service availability and changes

• Kavach360 aims to provide a reliable service, but availability can be affected by maintenance, updates, hosting providers, app stores, internet networks, payment providers, customer systems, security events, or force majeure events.
• Features may be added, removed, renamed, redesigned, limited, or moved between plans. We aim to communicate material changes that affect active customers through reasonable channels.
• Beta, pilot, preview, experimental, or early-access features may be less stable, may change quickly, and may be discontinued without the same notice as generally available features.

13. No emergency-use commitment

• Kavach360 is not an emergency dispatch, public safety, ambulance, fire, police, disaster response, life safety, or guaranteed security service.
• Visitor approvals, alerts, service requests, announcements, gate workflows, and resident notifications should not replace emergency calls, security protocols, building safety procedures, or lawful instructions from authorities.

14. Intellectual property and feedback

• Kavach360, the website, app, design, code, product names, workflows, documentation, logos, and related intellectual property are owned by Kavach360, Auvana Ventures, or their licensors.
• Customers retain rights in their customer data, subject to the licence needed for Kavach360 to host, process, transmit, display, secure, back up, support, and improve the service.
• If you provide feedback, suggestions, ideas, or improvement requests, Kavach360 may use them without restriction or compensation unless a signed agreement says otherwise.

15. Suspension, termination, export, and deletion

• Kavach360 may suspend or limit access for non-payment, security risk, unauthorised access, misuse, legal risk, customer instruction, account dispute, or breach of these terms.
• Customers may request export or deletion of account data subject to plan capabilities, signed agreements, payment status, verification, technical feasibility, legal retention, security retention, and backup cycles.
• After termination, some data may remain in backups, audit logs, financial records, legal records, support history, or security archives for a limited period or as required by law.

16. Disclaimers and limits

• Kavach360 is provided on an as-is and as-available basis except where a signed agreement gives specific commitments.
• To the maximum extent permitted by law, Kavach360 does not guarantee uninterrupted operation, error-free operation, perfect data accuracy, full prevention of fraud or misuse, specific collection outcomes, resident adoption, committee approval, payment success, or legal compliance for a customer's own workflows.
• To the maximum extent permitted by law, Kavach360 is not liable for indirect, incidental, special, consequential, exemplary, punitive, loss-of-profit, loss-of-revenue, loss-of-goodwill, loss-of-data, business interruption, third-party provider, or customer-configuration damages.
• Nothing in these terms excludes liability that cannot be excluded under applicable law.

17. Indemnity

You agree to defend, indemnify, and hold Kavach360 and Auvana Ventures harmless from claims, losses, liabilities, damages, penalties, costs, and expenses arising from your unauthorised use, customer data, illegal content, payment misuse, breach of these terms, breach of law, or lack of authority to act for a customer account.

18. Governing law and disputes

• These public terms are governed by the laws of India unless a signed agreement states another governing law.
• Before starting formal proceedings, the parties should try to resolve disputes through good-faith escalation using the relevant support, account, or contact route.
• Subject to any signed agreement and applicable law, courts in Bengaluru, Karnataka, India will have jurisdiction over disputes related to these public terms.

19. Changes to terms

• We may update these terms as the website, apps, dashboard, payment flows, vendors, laws, or product operations change.
• Material changes may be communicated through the website, app, dashboard, email, customer admin channels, or checkout notices. Continued use after an update means the updated terms apply.