Privacy Policy
Effective Date: 01-January-2015
Company: Dhru Cloud Private Limited (“Dhru”, “we”, “us”, “our”)
Company: Dhru Cloud Private Limited (“Dhru”, “we”, “us”, “our”)
This Privacy Policy explains how Dhru Cloud Private Limited collects, uses, discloses, and protects personal information in connection with our e-commerce software and services, whether delivered as Software-as-a-Service (SaaS) or Self-Hosted. By using our software, websites, or services, you agree to the terms of this Privacy Policy.
1. Information We Collect
1.1 Account Information, When you register for an account, we collect your name, company name, email address, phone number, billing details, and account credentials.
1.2 Verification Data, For license activation, your account is permanently bound to your registered email and verified phone number. These details cannot be changed once activated.
1.3 Payment & Transaction Data, We collect information necessary for billing and payment processing, such as invoices, subscription details, and payment confirmations.
1.4 Usage & Technical Data (SaaS and Self-Hosted), We may collect IP addresses, browser type, operating system, device identifiers, server environment details, license keys, domain names, telemetry data, and usage logs for:
• license validation,
• security monitoring,
• abuse prevention, and
• product improvement.
1.5 Customer Data (SaaS only), When you use our hosted services, we process data you upload, store, or manage (including customer names, orders, payment data, and other e-commerce content).
1.6 Cookies & Tracking Technologies (Website & SaaS), We may use cookies, pixels, and similar technologies to:
• authenticate users,
• store preferences,
• analyze usage, and
• deliver relevant communications.
1.2 Verification Data, For license activation, your account is permanently bound to your registered email and verified phone number. These details cannot be changed once activated.
1.3 Payment & Transaction Data, We collect information necessary for billing and payment processing, such as invoices, subscription details, and payment confirmations.
1.4 Usage & Technical Data (SaaS and Self-Hosted), We may collect IP addresses, browser type, operating system, device identifiers, server environment details, license keys, domain names, telemetry data, and usage logs for:
• license validation,
• security monitoring,
• abuse prevention, and
• product improvement.
1.5 Customer Data (SaaS only), When you use our hosted services, we process data you upload, store, or manage (including customer names, orders, payment data, and other e-commerce content).
1.6 Cookies & Tracking Technologies (Website & SaaS), We may use cookies, pixels, and similar technologies to:
• authenticate users,
• store preferences,
• analyze usage, and
• deliver relevant communications.
2. PayerOne (Crypto Payment & Gateway Aggregation Services)
2.1 PayerOne is a payment orchestration and gateway aggregation platform provided by Dhru. PayerOne enables merchants to integrate, manage, and route multiple payment methods, blockchain networks, and third-party payment gateways through a unified interface.
2.2 Merchants using PayerOne may connect their own third-party payment service provider accounts, including cryptocurrency gateways and traditional payment providers (such as PayPal, Stripe, or similar services), by supplying their own API keys, credentials, or configuration details. Dhru does not issue, own, operate, or control merchant accounts with such third-party providers.
2.3 For cryptocurrency payments, PayerOne operates as a non-custodial blockchain payment infrastructure. Dhru does not store, control, manage, or have access to users’ private keys, wallet credentials, seed phrases, or digital assets. All crypto payments are executed directly on public blockchain networks via smart contracts or merchant-provided wallet addresses.
2.4 Dhru does not process, custody, intermediate, pool, or settle funds on behalf of merchants or customers. Payment transactions are processed directly by the connected third-party payment providers or public blockchain networks according to the merchant’s configuration.
2.5 Transactions initiated through PayerOne may occur on public blockchain networks or third-party payment systems. Blockchain data, including wallet addresses and transaction hashes, is publicly accessible, immutable, and maintained independently of Dhru. Dhru does not control, modify, delete, or obscure blockchain records or third-party payment transaction data.
2.6 For operational, reconciliation, analytics, and support purposes, Dhru may collect and store limited transaction-related metadata, including payment status, selected payment method, timestamps, blockchain network, transaction hash, and internal merchant reference identifiers. Dhru does not store private keys, payment card data, or sensitive financial credentials.
2.7 PayerOne utilizes automation logic and, where applicable, smart contracts to route payment requests based on merchant-defined rules. Payment transactions, once initiated or confirmed, may be irreversible. Merchants and customers are solely responsible for verifying payment details, wallet addresses, blockchain networks, and third-party provider configurations prior to initiating payments.
2.8 Dhru provides PayerOne as a software and infrastructure service only. Dhru does not operate as a financial institution, payment service provider, money service business, or virtual asset custodian. Compliance with applicable laws, regulations, and third-party provider terms remains the responsibility of the merchant.
2.2 Merchants using PayerOne may connect their own third-party payment service provider accounts, including cryptocurrency gateways and traditional payment providers (such as PayPal, Stripe, or similar services), by supplying their own API keys, credentials, or configuration details. Dhru does not issue, own, operate, or control merchant accounts with such third-party providers.
2.3 For cryptocurrency payments, PayerOne operates as a non-custodial blockchain payment infrastructure. Dhru does not store, control, manage, or have access to users’ private keys, wallet credentials, seed phrases, or digital assets. All crypto payments are executed directly on public blockchain networks via smart contracts or merchant-provided wallet addresses.
2.4 Dhru does not process, custody, intermediate, pool, or settle funds on behalf of merchants or customers. Payment transactions are processed directly by the connected third-party payment providers or public blockchain networks according to the merchant’s configuration.
2.5 Transactions initiated through PayerOne may occur on public blockchain networks or third-party payment systems. Blockchain data, including wallet addresses and transaction hashes, is publicly accessible, immutable, and maintained independently of Dhru. Dhru does not control, modify, delete, or obscure blockchain records or third-party payment transaction data.
2.6 For operational, reconciliation, analytics, and support purposes, Dhru may collect and store limited transaction-related metadata, including payment status, selected payment method, timestamps, blockchain network, transaction hash, and internal merchant reference identifiers. Dhru does not store private keys, payment card data, or sensitive financial credentials.
2.7 PayerOne utilizes automation logic and, where applicable, smart contracts to route payment requests based on merchant-defined rules. Payment transactions, once initiated or confirmed, may be irreversible. Merchants and customers are solely responsible for verifying payment details, wallet addresses, blockchain networks, and third-party provider configurations prior to initiating payments.
2.8 Dhru provides PayerOne as a software and infrastructure service only. Dhru does not operate as a financial institution, payment service provider, money service business, or virtual asset custodian. Compliance with applicable laws, regulations, and third-party provider terms remains the responsibility of the merchant.
3. How We Use Information
3.1 To deliver, operate, maintain, and improve our Software, products, and services, including ensuring reliable performance and availability.
3.2 To verify licenses, enforce account binding, prevent unauthorized access or misuse, and protect the integrity of our systems.
3.3 To process subscriptions, service renewals, billing-related activities, and access to paid features, in accordance with applicable terms.
3.4 To provide customer and technical support, respond to inquiries, troubleshoot issues, and communicate service-related information.
3.5 To analyze usage patterns, monitor performance, and improve functionality, features, reliability, and security of our Software and services.
3.6 To comply with applicable legal and regulatory obligations, including export control laws, sanctions regulations, and lawful requests from authorities.
3.7 To send service-related communications, product updates, and marketing messages where permitted by law, with appropriate opt-out mechanisms available.
3.2 To verify licenses, enforce account binding, prevent unauthorized access or misuse, and protect the integrity of our systems.
3.3 To process subscriptions, service renewals, billing-related activities, and access to paid features, in accordance with applicable terms.
3.4 To provide customer and technical support, respond to inquiries, troubleshoot issues, and communicate service-related information.
3.5 To analyze usage patterns, monitor performance, and improve functionality, features, reliability, and security of our Software and services.
3.6 To comply with applicable legal and regulatory obligations, including export control laws, sanctions regulations, and lawful requests from authorities.
3.7 To send service-related communications, product updates, and marketing messages where permitted by law, with appropriate opt-out mechanisms available.
4. Self-Hosted Deployments
4.1 In the case of Self-Hosted deployments, you act as the sole data controller for all customer, transaction, and operational data stored, processed, or managed on your own servers or infrastructure.
4.2 Dhru does not have access to, visibility into, or control over data stored in Self-Hosted environments and bears no responsibility for data protection, privacy compliance, security controls, system configuration, or backup management related to such deployments.
4.3 You are solely responsible for ensuring compliance with all applicable data protection, privacy, and security laws and regulations, including but not limited to GDPR, CCPA, and other local or international requirements, when operating Self-Hosted versions of the Software.
4.4 Upon expiration or termination of support, maintenance, or subscription services, Dhru is not obligated to provide continued access to downloads, updates, patches, or data copies. You are responsible for securely retaining, maintaining, and backing up your last obtained version of the Software and any associated data.
4.2 Dhru does not have access to, visibility into, or control over data stored in Self-Hosted environments and bears no responsibility for data protection, privacy compliance, security controls, system configuration, or backup management related to such deployments.
4.3 You are solely responsible for ensuring compliance with all applicable data protection, privacy, and security laws and regulations, including but not limited to GDPR, CCPA, and other local or international requirements, when operating Self-Hosted versions of the Software.
4.4 Upon expiration or termination of support, maintenance, or subscription services, Dhru is not obligated to provide continued access to downloads, updates, patches, or data copies. You are responsible for securely retaining, maintaining, and backing up your last obtained version of the Software and any associated data.
5. Sharing of Information
5.1 Dhru may share information with trusted third parties strictly for the purposes described in this Privacy Policy and only to the extent necessary to provide, operate, and support our Software and services.
5.2 Payment Processors – for billing, invoicing, subscription management, and related financial operations. Dhru does not share cryptocurrency private keys or wallet credentials with payment processors.
5.3 Hosting Providers (SaaS Deployments Only) – cloud infrastructure and hosting service providers (such as AWS, GCP, or similar platforms) used to operate and maintain our SaaS services.
5.4 Service Providers – third-party vendors that support our operations, including analytics, monitoring, email delivery, SMS communications, customer support systems, and related tooling.
5.5 Legal and Compliance Authorities – where required to comply with applicable laws, regulations, legal processes, enforce this Agreement, protect our rights, or respond to lawful requests from competent authorities.
5.6 Dhru does not sell, rent, or trade personal data to third parties for marketing or commercial purposes.
5.7 Dhru engages vetted third-party sub-processors solely to support service delivery (such as hosting, analytics, and communications). A current list of sub-processors is available upon request and may be updated from time to time in accordance with this Privacy Policy.
5.2 Payment Processors – for billing, invoicing, subscription management, and related financial operations. Dhru does not share cryptocurrency private keys or wallet credentials with payment processors.
5.3 Hosting Providers (SaaS Deployments Only) – cloud infrastructure and hosting service providers (such as AWS, GCP, or similar platforms) used to operate and maintain our SaaS services.
5.4 Service Providers – third-party vendors that support our operations, including analytics, monitoring, email delivery, SMS communications, customer support systems, and related tooling.
5.5 Legal and Compliance Authorities – where required to comply with applicable laws, regulations, legal processes, enforce this Agreement, protect our rights, or respond to lawful requests from competent authorities.
5.6 Dhru does not sell, rent, or trade personal data to third parties for marketing or commercial purposes.
5.7 Dhru engages vetted third-party sub-processors solely to support service delivery (such as hosting, analytics, and communications). A current list of sub-processors is available upon request and may be updated from time to time in accordance with this Privacy Policy.
6. Data Retention & Deletion
6.1 Account-related information is retained for as long as your account remains active and thereafter for the duration required to comply with applicable tax, legal, accounting, or regulatory obligations.
6.2 For SaaS deployments, customer data is retained for the duration of your active subscription. Upon account termination or subscription cancellation, such data may be permanently deleted within a reasonable period, typically within thirty (30) days, unless retention is required by law.
6.3 For Self-Hosted deployments, all data storage, retention, backups, and deletion are entirely your responsibility. Dhru does not store, process, or back up Self-Hosted data and has no access to such data.
6.4 Requests for deletion of account-related data will be honored where technically feasible and legally permissible. Dhru aims to process verified deletion requests within thirty (30) days, subject to applicable legal, regulatory, or contractual retention requirements.
6.5 You may request deletion of your account data, subject to the limitations described above, by contacting us at privacy@dhru.com.
6.2 For SaaS deployments, customer data is retained for the duration of your active subscription. Upon account termination or subscription cancellation, such data may be permanently deleted within a reasonable period, typically within thirty (30) days, unless retention is required by law.
6.3 For Self-Hosted deployments, all data storage, retention, backups, and deletion are entirely your responsibility. Dhru does not store, process, or back up Self-Hosted data and has no access to such data.
6.4 Requests for deletion of account-related data will be honored where technically feasible and legally permissible. Dhru aims to process verified deletion requests within thirty (30) days, subject to applicable legal, regulatory, or contractual retention requirements.
6.5 You may request deletion of your account data, subject to the limitations described above, by contacting us at privacy@dhru.com.
7. Security
7.1 Dhru implements reasonable and industry-standard technical and organizational security measures designed to protect information from accidental loss, unauthorized access, disclosure, alteration, or destruction.
7.2 While Dhru takes appropriate measures to safeguard data, no system, network, or transmission method can be guaranteed to be completely secure. You are responsible for maintaining the security of your own devices, accounts, credentials, access controls, and backups.
7.3 For Self-Hosted deployments, you are solely responsible for the security, configuration, monitoring, patching, and protection of your infrastructure, systems, networks, and data. Dhru has no responsibility for security incidents, breaches, or data loss occurring within Self-Hosted environments.
7.4 Access to Dhru systems and services is restricted to authorized personnel and service providers who require such access for operational purposes and are subject to confidentiality and security obligations.
7.5 Dhru may periodically review, update, and improve its security practices to address evolving threats, operational requirements, and industry standards.
7.6 In the event of a security incident affecting data under Dhru’s control, Dhru will take reasonable steps to investigate, mitigate, and, where legally required, notify affected parties in accordance with applicable law.
7.7 Dhru is not responsible for security vulnerabilities, incidents, or losses arising from third-party services, blockchain networks, payment gateways, or integrations used by you through PayerOne or other Dhru products.
7.8 You acknowledge that blockchain-based transactions are executed on decentralized networks outside of Dhru’s control and that risks inherent to such networks, including network congestion, protocol changes, or malicious activity, are not the responsibility of Dhru.
7.2 While Dhru takes appropriate measures to safeguard data, no system, network, or transmission method can be guaranteed to be completely secure. You are responsible for maintaining the security of your own devices, accounts, credentials, access controls, and backups.
7.3 For Self-Hosted deployments, you are solely responsible for the security, configuration, monitoring, patching, and protection of your infrastructure, systems, networks, and data. Dhru has no responsibility for security incidents, breaches, or data loss occurring within Self-Hosted environments.
7.4 Access to Dhru systems and services is restricted to authorized personnel and service providers who require such access for operational purposes and are subject to confidentiality and security obligations.
7.5 Dhru may periodically review, update, and improve its security practices to address evolving threats, operational requirements, and industry standards.
7.6 In the event of a security incident affecting data under Dhru’s control, Dhru will take reasonable steps to investigate, mitigate, and, where legally required, notify affected parties in accordance with applicable law.
7.7 Dhru is not responsible for security vulnerabilities, incidents, or losses arising from third-party services, blockchain networks, payment gateways, or integrations used by you through PayerOne or other Dhru products.
7.8 You acknowledge that blockchain-based transactions are executed on decentralized networks outside of Dhru’s control and that risks inherent to such networks, including network congestion, protocol changes, or malicious activity, are not the responsibility of Dhru.
8. International Data Transfers
8.1 Dhru operates and provides its services on a global basis. As a result, information may be processed, stored, or accessed in jurisdictions outside your country of residence, including countries where Dhru, its affiliates, or service providers maintain operations or infrastructure.
8.2 Dhru makes no representation that data protection or privacy laws in other jurisdictions are equivalent to those in your country of residence. By using the services, you expressly acknowledge and accept that information may be transferred to, processed in, and stored in jurisdictions with different or lesser data protection standards.
8.3 Where required by applicable law, Dhru will implement appropriate and lawful safeguards for international data transfers, including the use of Standard Contractual Clauses or other recognized transfer mechanisms. Such safeguards shall apply only to the extent legally mandated.
8.4 By accessing or using Dhru’s services, you explicitly consent to the international transfer, processing, and storage of information as described in this Privacy Policy and waive any claims against Dhru arising solely from such cross-border transfers, to the maximum extent permitted by law.
8.5 Dhru shall not be liable for any access, use, or disclosure of information resulting from lawful requests, regulatory requirements, or actions of authorities in jurisdictions where data is processed or stored.
8.2 Dhru makes no representation that data protection or privacy laws in other jurisdictions are equivalent to those in your country of residence. By using the services, you expressly acknowledge and accept that information may be transferred to, processed in, and stored in jurisdictions with different or lesser data protection standards.
8.3 Where required by applicable law, Dhru will implement appropriate and lawful safeguards for international data transfers, including the use of Standard Contractual Clauses or other recognized transfer mechanisms. Such safeguards shall apply only to the extent legally mandated.
8.4 By accessing or using Dhru’s services, you explicitly consent to the international transfer, processing, and storage of information as described in this Privacy Policy and waive any claims against Dhru arising solely from such cross-border transfers, to the maximum extent permitted by law.
8.5 Dhru shall not be liable for any access, use, or disclosure of information resulting from lawful requests, regulatory requirements, or actions of authorities in jurisdictions where data is processed or stored.
9. Your Rights
9.1 Depending on your jurisdiction and subject to applicable law (including GDPR, CCPA, or similar regulations), you may have certain rights in relation to your personal data. Such rights apply only to the extent mandated by law and are not absolute.
9.2 These rights may include the ability to request access to, correction of, or deletion of personal data, to restrict or object to certain processing activities, to request data portability where technically feasible, and to opt out of certain marketing communications.
9.3 Dhru reserves the right to verify the identity of any individual submitting a request and to refuse, limit, defer, or deny requests where permitted by law, including where requests are manifestly unfounded, excessive, repetitive, technically impracticable, or where compliance would impair the rights of others, security, legal obligations, or legitimate business interests.
9.4 Certain information may be retained or excluded from deletion or access requests where retention is required or permitted by law, necessary for legal compliance, dispute resolution, fraud prevention, enforcement of agreements, or protection of Dhru’s rights and interests.
9.5 Dhru does not guarantee that all data can be modified, deleted, or provided in a specific format, particularly where such data is stored on public blockchain networks, derived from third-party systems, or subject to technical or legal constraints.
9.6 Requests to exercise applicable rights must be submitted to privacy@dhru.com. Dhru will respond within the timeframes required by applicable law, where such obligations apply.
9.7 Where permitted by law, Dhru shall not be liable for any consequences arising from the exercise or non-exercise of rights, including delays, refusals, or limitations imposed in accordance with this Privacy Policy and applicable regulations.
9.2 These rights may include the ability to request access to, correction of, or deletion of personal data, to restrict or object to certain processing activities, to request data portability where technically feasible, and to opt out of certain marketing communications.
9.3 Dhru reserves the right to verify the identity of any individual submitting a request and to refuse, limit, defer, or deny requests where permitted by law, including where requests are manifestly unfounded, excessive, repetitive, technically impracticable, or where compliance would impair the rights of others, security, legal obligations, or legitimate business interests.
9.4 Certain information may be retained or excluded from deletion or access requests where retention is required or permitted by law, necessary for legal compliance, dispute resolution, fraud prevention, enforcement of agreements, or protection of Dhru’s rights and interests.
9.5 Dhru does not guarantee that all data can be modified, deleted, or provided in a specific format, particularly where such data is stored on public blockchain networks, derived from third-party systems, or subject to technical or legal constraints.
9.6 Requests to exercise applicable rights must be submitted to privacy@dhru.com. Dhru will respond within the timeframes required by applicable law, where such obligations apply.
9.7 Where permitted by law, Dhru shall not be liable for any consequences arising from the exercise or non-exercise of rights, including delays, refusals, or limitations imposed in accordance with this Privacy Policy and applicable regulations.
10. Children’s Privacy
10.1 Dhru’s services are not intended for use by individuals under the age of eighteen (18) or the applicable age of majority in their jurisdiction. Dhru does not knowingly collect personal data from children.
10.2 Dhru does not verify the age of users and relies on users and account holders to represent that they meet the minimum age requirements. Use of the services by a minor in violation of this policy is the responsibility of the user or legal guardian.
10.3 If Dhru becomes aware that personal data has been collected from a child without appropriate legal consent, Dhru may take reasonable steps to delete such information, subject to applicable legal obligations and technical limitations.
10.4 Dhru has no obligation to actively monitor, investigate, or validate the age of users or to screen content or data forcompliance with children’s privacy laws beyond what is required by applicable law.
10.5 To the maximum extent permitted by law, Dhru disclaims all liability arising from the use of its services by minors or from any misrepresentation of age by users.
10.2 Dhru does not verify the age of users and relies on users and account holders to represent that they meet the minimum age requirements. Use of the services by a minor in violation of this policy is the responsibility of the user or legal guardian.
10.3 If Dhru becomes aware that personal data has been collected from a child without appropriate legal consent, Dhru may take reasonable steps to delete such information, subject to applicable legal obligations and technical limitations.
10.4 Dhru has no obligation to actively monitor, investigate, or validate the age of users or to screen content or data forcompliance with children’s privacy laws beyond what is required by applicable law.
10.5 To the maximum extent permitted by law, Dhru disclaims all liability arising from the use of its services by minors or from any misrepresentation of age by users.
11. Legal Basis for Processing (GDPR-specific)
11.1 Where the General Data Protection Regulation (GDPR) or similar data protection laws apply, Dhru processes personal data only to the extent permitted and required by applicable law and under one or more lawful bases.
11.2 The lawful bases relied upon by Dhru may include, as applicable:
-(a) Contractual Necessity – where processing is necessary to perform a contract with you or to take steps at your request prior to entering into a contract, including the provision of services;
-(b) Legitimate Interests – where processing is necessary for Dhru’s legitimate business interests, including service operation, security, fraud prevention, system monitoring, analytics, and product improvement, provided such interests are not overridden by your fundamental rights and freedoms;
-(c) Legal Obligation – where processing is necessary to comply with applicable legal, regulatory, tax, sanctions, export control, or law enforcement requirements;
-(d) Consent – where you have provided explicit consent for specific processing activities, such as marketing communications, which may be withdrawn at any time where required by law.
11.3 Where applicable, Dhru processes personal data in accordance with the Digital Personal Data Protection Act, 2023(India), the GDPR, and other applicable data protection laws. Compliance obligations shall apply only to the extent such laws are legally binding on Dhru.
11.4 Dhru uses cookies and similar technologies for authentication, security, service functionality, and analytics purposes. Where required by applicable law, Dhru will display a cookie consent mechanism and honor applicable user preferences.
11.5 Refusal, withdrawal, or restriction of consent for certain processing activities may limit or prevent access to specific features or services, and Dhru shall not be liable for any resulting impact on service availability or functionality.
11.2 The lawful bases relied upon by Dhru may include, as applicable:
-(a) Contractual Necessity – where processing is necessary to perform a contract with you or to take steps at your request prior to entering into a contract, including the provision of services;
-(b) Legitimate Interests – where processing is necessary for Dhru’s legitimate business interests, including service operation, security, fraud prevention, system monitoring, analytics, and product improvement, provided such interests are not overridden by your fundamental rights and freedoms;
-(c) Legal Obligation – where processing is necessary to comply with applicable legal, regulatory, tax, sanctions, export control, or law enforcement requirements;
-(d) Consent – where you have provided explicit consent for specific processing activities, such as marketing communications, which may be withdrawn at any time where required by law.
11.3 Where applicable, Dhru processes personal data in accordance with the Digital Personal Data Protection Act, 2023(India), the GDPR, and other applicable data protection laws. Compliance obligations shall apply only to the extent such laws are legally binding on Dhru.
11.4 Dhru uses cookies and similar technologies for authentication, security, service functionality, and analytics purposes. Where required by applicable law, Dhru will display a cookie consent mechanism and honor applicable user preferences.
11.5 Refusal, withdrawal, or restriction of consent for certain processing activities may limit or prevent access to specific features or services, and Dhru shall not be liable for any resulting impact on service availability or functionality.
12. Changes to This Policy
12.1 Dhru reserves the right to modify, update, or revise this Privacy Policy at any time, at its sole discretion.
12.2 Any changes to this Privacy Policy shall become effective immediately upon posting on Dhru’s website or through the applicable service interface, unless otherwise required by applicable law.
12.3 Your continued access to or use of the Software or services after the effective date of any changes constitutes your acknowledgment and acceptance of the updated Privacy Policy.
12.4 Dhru may, but is not obligated to, provide notice of material changes through the Software, website, or other communication channels, except where such notice is expressly required by applicable law.
12.2 Any changes to this Privacy Policy shall become effective immediately upon posting on Dhru’s website or through the applicable service interface, unless otherwise required by applicable law.
12.3 Your continued access to or use of the Software or services after the effective date of any changes constitutes your acknowledgment and acceptance of the updated Privacy Policy.
12.4 Dhru may, but is not obligated to, provide notice of material changes through the Software, website, or other communication channels, except where such notice is expressly required by applicable law.
13. Contact Information
13.1 If you have any questions, concerns, or requests regarding this Privacy Policy, our data practices, or the handling of personal information, you may contact us using the details below.
Dhru Cloud Private Limited,
Dhru Base, 80 Foot Road
City: Anand
PIN: 388001
State: Gujarat
Country: India
Email: privacy@dhru.com, legal@dhru.com
Dhru Cloud Private Limited,
Dhru Base, 80 Foot Road
City: Anand
PIN: 388001
State: Gujarat
Country: India
Email: privacy@dhru.com, legal@dhru.com
12. Law Enforcement & Government Requests
12.1 Dhru may disclose information where such disclosure is required by applicable law, regulation, court order, subpoena, governmental request, or other valid legal process, or where Dhru reasonably believes disclosure is necessary to protect its rights, users, systems, or the public.
12.2 Dhru retains sole discretion to determine the validity, scope, and applicability of any law enforcement or governmental request and may comply with such requests without prior notice where disclosure is legally required or where notice is prohibited or impracticable.
12.3 Where legally permitted and reasonably practicable, Dhru may, but is not obligated to, provide notice to affected users prior to disclosure.
12.4 Dhru shall not be liable for any disclosure of information made in good faith reliance on a legal obligation, lawful request, or authority having jurisdiction.
12.2 Dhru retains sole discretion to determine the validity, scope, and applicability of any law enforcement or governmental request and may comply with such requests without prior notice where disclosure is legally required or where notice is prohibited or impracticable.
12.3 Where legally permitted and reasonably practicable, Dhru may, but is not obligated to, provide notice to affected users prior to disclosure.
12.4 Dhru shall not be liable for any disclosure of information made in good faith reliance on a legal obligation, lawful request, or authority having jurisdiction.
13. Compliance with Laws
13.1 You represent and warrant that you will not use Dhru’s software, services, or related technologies in violation of any applicable laws, regulations, or governmental requirements, including but not limited to Indian, United States, European Union, or United Nations export control laws, trade sanctions, and embargoes.
13.2 You are solely responsible for determining whether your access to or use of the services is permitted under applicable export control, sanctions, or trade compliance laws and for ensuring ongoing compliance with such requirements.
13.3 Dhru reserves the right, at its sole discretion, to restrict, suspend, or terminate access to the software or services, without prior notice, where required by law or where Dhru reasonably believes such action is necessary to comply with export control regulations, sanctions programs, embargoes, or related legal obligations.
13.4 Dhru shall not be liable for any loss, damages, or consequences arising from actions taken to comply with applicable export control, sanctions, or trade laws, including any restriction or termination of access.
13.2 You are solely responsible for determining whether your access to or use of the services is permitted under applicable export control, sanctions, or trade compliance laws and for ensuring ongoing compliance with such requirements.
13.3 Dhru reserves the right, at its sole discretion, to restrict, suspend, or terminate access to the software or services, without prior notice, where required by law or where Dhru reasonably believes such action is necessary to comply with export control regulations, sanctions programs, embargoes, or related legal obligations.
13.4 Dhru shall not be liable for any loss, damages, or consequences arising from actions taken to comply with applicable export control, sanctions, or trade laws, including any restriction or termination of access.
14. Governing Language
14.1 This Privacy Policy is authored and governed in the English language.
14.2 Any translations of this Privacy Policy are provided solely for convenience and informational purposes and shall have no legal effect.
14.3 In the event of any conflict, inconsistency, or discrepancy between the English version and any translated version, the English version shall prevail and be binding to the maximum extent permitted by law.
14.2 Any translations of this Privacy Policy are provided solely for convenience and informational purposes and shall have no legal effect.
14.3 In the event of any conflict, inconsistency, or discrepancy between the English version and any translated version, the English version shall prevail and be binding to the maximum extent permitted by law.
