Security Policy

Last updated 20 November 2026

The controls that protect CustomerBond and your data, what happens when something goes wrong, and how to report a vulnerability to us.

1. Scope and ownership

This policy covers the CustomerBond web application, Android application, APIs and the infrastructure that runs them, operated by Govindani Infotech Private Limited. A named member of our leadership team is responsible for security, and every employee and contractor with system access is bound by confidentiality obligations.

2. Access control

  • In the product: access is role-based. Twelve system roles ship ready and about 110 action-level permissions can be combined into custom roles. By default, agents see only the leads assigned to them.
  • Seats: users without a seat can view but cannot change data.
  • Sign-in: handled by a dedicated identity service, separate from the CRM's database.
  • Our staff: administrative access to production is limited to named personnel who need it, granted on least privilege, logged, and removed when no longer needed.

3. Data protection

  • All traffic to the web app, Android app and API is encrypted in transit with TLS.
  • Each customer's data is separated by workspace, and that separation is enforced on every request.
  • API keys are issued per integration, can be revoked at any time, and their use is recorded.
  • Databases are backed up on a schedule; backups are access-restricted.

4. Secure operations

  • Changes to the product are reviewed before release, and dependencies are kept up to date.
  • Application and security logs are kept for at least 180 days, as required by the CERT-In directions, and system clocks are synchronised to a reliable time source.
  • Background jobs monitor the health of lead intake and message sending, and alert when something is stuck.

5. Incident response

When we detect or are told about a security incident, we:

  1. contain it and preserve evidence;
  2. assess what data and which customers are affected;
  3. report it to CERT-In within six hours of becoming aware, where the incident is of a reportable type under the CERT-In directions of 28 April 2022;
  4. notify affected customers without undue delay, so that they can meet their own obligations as Data Fiduciaries, and, for data we hold as a Data Fiduciary, inform the Data Protection Board of India and affected individuals as the DPDP Act and Rules require;
  5. fix the cause, and review what we can improve.

6. Third parties

We use established providers for hosting, sign-in, email and payments, and assess their security before we rely on them. Their obligations are described in our Data Processing Addendum.

7. Certifications

We do not currently hold ISO/IEC 27001 or SOC 2 certification. We are happy to answer customer security questionnaires.

8. Responsible disclosure

If you believe you have found a security vulnerability in CustomerBond, please tell us privately at support@customerbond.com with the subject line "Security". Include what you found, how to reproduce it and any proof of concept.

  • Give us a reasonable time to fix the issue before telling anyone else.
  • Do not access, change or delete data that is not yours, and stop as soon as you have shown the issue exists.
  • Do not run denial-of-service tests, social engineering or physical attacks.

If you act in good faith and within these rules, we will not pursue legal action against you for your research, we will keep you informed as we fix it, and we will credit you if you would like. We do not currently run a paid bug bounty.