Terms and Conditions

1. Agreement#

These Terms govern the Customer’s access to and use of DhanushGuard.

The agreement consists of:

• these Terms;
• the applicable Order Form;
• the Data Processing Agreement;
• any Statement of Work;
• any support or security schedule; and
• documents expressly incorporated by reference.

A person accepting the agreement for an organisation represents that they are authorised to bind that organisation.

In case of conflict, the Order Form takes precedence, followed by the Data Processing Agreement for data-protection matters, the Statement of Work, these Terms and then the Documentation.

2. Definitions#

“Approved Operation” means a cloud action, query, assessment or retrieval function authorised by CyberCube and made available through DhanushGuard.

“Authorised User” means a user authorised by the Customer.

“Cloud Account” means a supported cloud-provider account, tenant, subscription, project, organisation or equivalent environment connected to DhanushGuard.

“Cloud Information” means configuration, metadata, evidence, logs or other information retrieved from a Cloud Account.

“Customer Content” means Cloud Information and other information supplied, generated or stored by or for the Customer through DhanushGuard.

“Finding” means an observation, control result, risk, alert, evidence item, recommendation or other output.

“Predefined Query” means a controlled and approved domain query provided through the DhanushGuard interface.

“Services” means DhanushGuard and related software, APIs, connectors, support and professional services purchased by the Customer.

3. Subscription Licence#

Subject to payment and compliance with the agreement, CyberCube grants the Customer a limited, non-exclusive, non-transferable and non-sublicensable right during the Subscription Term to:

• access DhanushGuard;
• connect authorised Cloud Accounts;
• execute Approved Operations;
• review Findings;
• generate reports; and
• use the output for internal security, risk, audit and compliance purposes.

Usage may be limited by:

• user count;
• cloud-account count;
• framework count;
• module;
• API volume;
• scan frequency;
• storage;
• region;
• feature entitlement; and
• subscription plan.

4. Customer Authority#

The Customer represents that it has all necessary authority to:

• connect each Cloud Account;
• create or assign each cloud role;
• provide each token or service identity;
• access relevant resource configuration;
• retrieve Cloud Information;
• execute selected checks;
• retain evidence;
• process personal data; and
• instruct CyberCube to provide the Services.

The Customer must not connect or assess a third party’s Cloud Account without written authorisation.

5. Accounts and Access#

The Customer is responsible for:

• appointing administrators;
• managing users;
• assigning roles;
• maintaining authentication controls;
• enabling multi-factor authentication where available;
• protecting credentials;
• reviewing account activity;
• removing unauthorised users; and
• promptly reporting suspected compromise.

The Customer is responsible for actions taken through its accounts unless caused solely by CyberCube’s breach.

6. Cloud Roles, Credentials and Permissions#

The Customer should configure the minimum permissions reasonably required for the purchased functionality.

The Customer must not provide:

• root credentials;
• unrestricted administrator access;
• shared credentials without controls;
• expired credentials;
• credentials belonging to an unauthorised party; or
• credentials prohibited by the cloud provider.

Where practicable, the Customer should use:

• temporary credentials;
• role assumption;
• read-only access;
• dedicated service identities;
• external identifiers;
• conditional policies; and
• customer-managed secret storage.

The Customer is responsible for permissions it grants and for cloud changes made through any write-enabled functionality it elects to use.

7. Predefined Queries and Governed Operations#

DhanushGuard may allow users to select Predefined Queries that are interpreted and mapped to Approved Operations.

The Customer acknowledges that:

• users are not granted unrestricted cloud-operation authority merely by using natural-language interfaces;
• execution remains subject to configured permissions;
• a Predefined Query may map to one or more cloud API calls;
• CyberCube may modify or withdraw an Approved Operation for security, compatibility or compliance reasons; and
• all material output should be reviewed by qualified personnel.

The Customer must not attempt to manipulate a query, request or integration to bypass approved controls.

8. Customer Content#

The Customer retains ownership of Customer Content.

The Customer grants CyberCube and its approved subprocessors the limited right to:

• access;
• retrieve;
• host;
• transmit;
• normalise;
• analyse;
• classify;
• map;
• summarise;
• display;
• back up; and
• otherwise process Customer Content

as necessary to provide, secure and support DhanushGuard or comply with law.

The Customer is responsible for the lawfulness and accuracy of Customer Content.

9. Data Protection#

Each party will comply with applicable privacy and data-protection laws according to its role.

Where CyberCube processes personal data for the Customer:

• the Customer is the controller, data fiduciary or equivalent;
• CyberCube is the processor or service provider;
• processing will be based on documented instructions; and
• the parties may execute a Data Processing Agreement.

The Customer is responsible for providing notices and obtaining any consent or authority required for its personnel, cloud users and other individuals whose data may appear in Cloud Information.

10. Cloud Provider Terms and Charges#

The Customer’s relationship with its cloud provider is governed by the Customer’s agreement with that provider.

The Customer is responsible for:

• cloud-provider charges;
• API-request charges;
• logging charges;
• data-transfer charges;
• storage charges;
• rate limits;
• service quotas;
• cloud-provider outages;
• account restrictions; and
• compliance with cloud-provider policies.

CyberCube does not control cloud-provider availability, APIs, pricing or service changes.

11. Assessment Limitations#

DhanushGuard provides configuration-based security and compliance assessment. It does not guarantee:

• complete detection of every risk;
• uninterrupted cloud access;
• coverage of every cloud service;
• identification of every vulnerability;
• prevention of a breach;
• regulatory compliance;
• audit certification;
• successful remediation;
• correctness of third-party data; or
• continued validity of a result after a cloud configuration changes.

A result represents the configuration or evidence available at the relevant time and scope.

12. Compliance Frameworks#

DhanushGuard may map findings to laws, standards or frameworks.

Framework mappings are informational and may require:

• customer-specific interpretation;
• manual evidence;
• compensating controls;
• scope confirmation;
• risk acceptance;
• legal review;
• auditor validation; or
• professional judgement.

A “pass” does not constitute certification. A “fail” does not necessarily establish a legal violation.

13. Artificial Intelligence and Automated Output#

DhanushGuard may use AI-assisted functionality to interpret approved queries, classify evidence, summarise Findings or draft remediation guidance.

The Customer acknowledges that AI-assisted output may:

• contain errors;
• omit context;
• become outdated;
• misinterpret configuration;
• produce incomplete remediation; or
• require human verification.

The Customer must not treat AI output as the sole basis for:

• production changes;
• credential revocation;
• resource deletion;
• regulatory reporting;
• legal conclusions;
• disciplinary action;
• business-critical shutdown; or
• acceptance of material risk.

Customer Content will not be used to train general-purpose AI models unless expressly agreed in writing and lawfully permitted.

14. Remediation and Write Actions#

Unless the Order Form expressly includes authorised remediation functionality, DhanushGuard is provided on an assessment and advisory basis.

Where a write or remediation action is enabled:

• the action must be initiated or approved by an Authorised User;
• the Customer is responsible for reviewing its scope;
• the Customer must maintain backups and recovery procedures;
• the Customer should test changes in a non-production environment;
• cloud-provider permissions will control the technical action; and
• CyberCube is not responsible for an action incorrectly approved by the Customer.

Material production changes should require explicit confirmation and appropriate role segregation.

15. Acceptable Use#

The Customer must not:

• connect an unauthorised Cloud Account;
• use stolen or improperly obtained credentials;
• bypass query controls;
• attempt prompt injection or operation manipulation;
• seek access beyond granted permissions;
• interfere with logs or audit trails;
• use DhanushGuard for unlawful surveillance;
• attack a cloud provider or third party;
• upload malware except under a separately authorised security-testing engagement;
• reverse engineer proprietary functionality except where legally permitted;
• use DhanushGuard to build a competing service;
• overload APIs or infrastructure;
• evade usage limits;
• access another customer’s data;
• misrepresent Findings or reports; or
• violate applicable law or cloud-provider terms.

16. Customer Responsibilities#

The Customer is responsible for:

• cloud security;
• identity and access management;
• access-key rotation;
• role design;
• network controls;
• workload security;
• data classification;
• incident response;
• backups;
• business continuity;
• review of Findings;
• remediation decisions;
• risk acceptance;
• regulatory interpretation; and
• maintaining qualified personnel.

DhanushGuard supplements but does not replace the Customer’s security programme.

17. Support, Maintenance and Changes#

CyberCube may update:

• cloud connectors;
• supported APIs;
• query mappings;
• framework mappings;
• assessment logic;
• control descriptions;
• user interfaces;
• reports; and
• technical requirements.

Changes may be required because a cloud provider modifies its services or APIs.

CyberCube will use commercially reasonable efforts to notify customers of material deprecations where practicable.

Emergency security changes may be made without advance notice.

18. Availability#

Any service-level commitment applies only where stated in a signed Order Form or service-level agreement.

Availability commitments do not apply to:

• cloud-provider outages;
• internet failure;
• Customer systems;
• identity-provider failure;
• invalid credentials;
• revoked permissions;
• API throttling;
• maintenance;
• force majeure;
• beta functionality; or
• suspension permitted under the agreement.

19. Fees and Taxes#

The Customer will pay fees stated in the Order Form.

Unless otherwise stated:

• fees are exclusive of taxes;
• subscriptions are non-cancellable;
• payments are non-refundable;
• excess usage may incur additional fees;
• cloud-provider charges are excluded; and
• late amounts may accrue lawful interest.

20. Suspension#

CyberCube may suspend affected access where reasonably necessary due to:

• non-payment;
• material breach;
• security risk;
• suspected credential compromise;
• unlawful access;
• unauthorised Cloud Account connection;
• threat to another customer;
• excessive harmful usage;
• legal requirement; or
• cloud-provider restriction.

Where practicable, CyberCube will provide notice and an opportunity to cure.

21. Intellectual Property#

CyberCube and its licensors retain all rights in:

• DhanushGuard;
• source and object code;
• APIs;
• models;
• prompts;
• predefined queries;
• mapping logic;
• control libraries;
• frameworks;
• workflows;
• connectors;
• Documentation;
• reports and templates;
• user interfaces;
• trademarks; and
• improvements.

The Customer retains ownership of Customer Content.

The Customer may use generated reports internally and for its auditors, regulators, customers and professional advisers, subject to confidentiality and the agreement.

22. Feedback#

The Customer may provide feedback. CyberCube may use that feedback without restriction or payment, provided CyberCube does not identify the Customer or disclose Customer Confidential Information without permission.

23. Confidentiality#

Each party will protect the other party’s Confidential Information and use it only for the agreement.

Access may be provided to personnel, contractors and advisers who need the information and are bound by confidentiality.

Confidentiality obligations do not apply to information lawfully public, previously known, independently developed or lawfully obtained from another source.

A party may disclose information where legally required after providing notice where legally permitted.

24. Warranties and Disclaimers#

CyberCube warrants that it will provide the Services with commercially reasonable skill and care.

Except as expressly stated, the Services, Findings and recommendations are provided “as available.”

To the maximum extent permitted by law, CyberCube disclaims implied warranties including:

• merchantability;
• fitness for a particular purpose;
• uninterrupted operation;
• error-free operation;
• non-infringement;
• complete security;
• complete compliance; and
• accuracy of third-party cloud information.

25. Indemnification#

The Customer will defend and indemnify CyberCube against third-party claims arising from:

• an unauthorised Cloud Account;
• Customer Content;
• unlawful credential use;
• Customer’s breach of law;
• Customer’s misuse;
• Customer-approved remediation actions; or
• Customer’s breach of the agreement.

CyberCube will provide reasonable notice and cooperation.

Any CyberCube intellectual-property indemnity must be set out in the applicable enterprise agreement.

26. Limitation of Liability#

To the maximum extent permitted by law:

• neither party is liable for indirect, special, incidental, punitive, exemplary or consequential damages;
• neither party is liable for lost profits, lost revenue, lost opportunity, lost goodwill or anticipated savings;
• CyberCube is not liable for cloud-provider outages, API changes, cloud charges, customer-approved changes, excessive permissions or customer configuration; and
• aggregate liability will not exceed the fees paid or payable for the affected Services during the twelve months before the event giving rise to the claim.

Separate liability caps or exclusions may be included in the Order Form for confidentiality, data protection, intellectual-property infringement, fraud, wilful misconduct and liabilities that cannot legally be limited.

27. Term and Termination#

The agreement continues for the applicable Subscription Term.

A party may terminate for an uncured material breach after the applicable cure period.

CyberCube may terminate or suspend immediately for unlawful, fraudulent or materially dangerous use.

On termination:

• the Customer’s access ends;
• connected roles and credentials should be revoked;
• outstanding fees become due;
• the Customer may request an available export during the retrieval period;
• Customer Content will be deleted according to the agreement and backup lifecycle; and
• surviving provisions remain effective.

28. Data Export and Deletion#

Before termination, the Customer should export required reports and evidence.

Any post-termination retrieval period must be stated in the Order Form. After that period, CyberCube may delete Customer Content unless retention is required by law.

Deletion from active systems may occur before deletion from protected backups.

29. Publicity#

CyberCube may use the Customer’s name or logo only where authorised in writing, in the Order Form or under another applicable agreement.

30. Compliance with Laws#

Each party will comply with applicable:

• privacy laws;
• cybersecurity laws;
• anti-bribery laws;
• sanctions;
• export controls;
• intellectual-property laws; and
• cloud-service restrictions.

The Customer must not use DhanushGuard for prohibited persons, territories or purposes.

31. Governing Law and Jurisdiction#

Unless a signed agreement or Order Form states otherwise, these Terms are governed by the laws of India, without regard to conflict-of-law rules.

The courts of competent jurisdiction located in Delhi NCR, India will have exclusive jurisdiction, subject to applicable law.

The final contract should identify a specific court city where required for enforceability.

32. General Terms#

Neither party may assign the agreement without consent, except in connection with a merger, acquisition, restructuring or sale of substantially all relevant assets.

CyberCube may use subcontractors while remaining responsible for its contractual obligations.

Neither party is liable for delay caused by events beyond reasonable control.

A waiver must be explicit and does not waive future enforcement.

If a provision is invalid, it will be modified to the minimum extent necessary and the remaining agreement will continue.

The agreement is the entire agreement concerning its subject matter.

33. Contact#

CyberCube Services Private Limited Address: Third Floor, Plot No - 880, Udyog Vihar Phase V, Sector 19, Gurugram, Haryana 122016
Legal Email: info@cybercube.co
Support Email: Shailesh.kumar@cybercube.co
Website: https://dhanushguard.com/