Data Security & Protection Policy

1. PURPOSE OF THIS POLICY

The purpose of this Policy is to establish principles for protecting information against:

• Unauthorised access;
• Unauthorised disclosure;
• Unauthorised modification;
• Unauthorised destruction;
• Accidental loss;
• Data leakage;
• Malware;
• Cybersecurity threats;
• Unauthorised use; and
• Other security risks.

2. INFORMATION SECURITY PRINCIPLES

Hyphenet Enterprises seeks to maintain the following core information-security principles:

Confidentiality

Information should only be accessible to authorised persons.

Integrity

Information should be protected against unauthorised or improper modification.

Availability

Systems and information should be available to authorised users when reasonably required.

These principles collectively support the security of our business operations and customer services.

3. SCOPE

This Policy may apply to:

• Customer information;
• Customer contact information;
• Employee information;
• Website information;
• Support tickets;
• Service records;
• Asset information;
• Equipment information;
• Device information;
• Network information;
• Server information;
• Configuration information;
• Business information;
• Commercial information;
• Technical information;
• Credentials and access information;
• Service reports; and
• Other information handled as part of our business operations.

4. DATA WE MAY HANDLE

Depending on the services provided, Hyphenet Enterprises may handle information including:

• Name;
• Business email;
• Telephone number;
• Company name;
• Designation;
• Business address;
• Billing information;
• Asset details;
• Serial numbers;
• Device information;
• IP addresses;
• Support-ticket information;
• Service history;
• Engineer visit information;
• Network information;
• Server information;
• System configuration information; and
• Other information required to provide contracted services.

5. CUSTOMER DATA

Where Hyphenet Enterprises provides IT support, rental or infrastructure services, Customer information may be accessed or processed solely to the extent reasonably necessary to deliver the contracted Services.

The Customer generally remains responsible for:

• Its business data;
• User data;
• Applications;
• Backups;
• Data classification;
• Data retention;
• User permissions; and
• Internal information-security requirements,

unless otherwise agreed in writing.

6. DATA OWNERSHIP

Unless otherwise agreed:

• Customer data remains the property of the Customer;
• Hyphenet Enterprises does not acquire ownership of Customer business data merely by providing IT Services;
• Hyphenet Enterprises retains ownership of its own tools, methodologies, systems, documentation and intellectual property.

7. PURPOSE LIMITATION

Information accessed through our Services will generally be used only for legitimate business purposes, including:

• Service delivery;
• Troubleshooting;
• Maintenance;
• Support;
• Asset management;
• Billing;
• Contract administration;
• Security;
• Compliance;
• Service improvement; and
• Other purposes authorised by the Customer or permitted by law.

8. LEAST PRIVILEGE

Hyphenet Enterprises seeks to apply the principle of least privilege.

Personnel should receive only the level of access reasonably required to perform their assigned responsibilities.

9. ACCESS CONTROL

Access to internal systems may be controlled through:

• User accounts;
• Passwords;
• Multi-factor authentication where implemented;
• Role-based permissions;
• Administrator controls;
• Device controls;
• Network controls; and
• Other appropriate security measures.

10. AUTHORISED PERSONNEL

Access to Customer information should be limited to authorised employees, engineers, contractors or service providers who require such access for legitimate business purposes.

11. EMPLOYEE CONFIDENTIALITY

Employees and authorised personnel may be subject to confidentiality obligations concerning:

• Customer information;
• Technical information;
• Commercial information;
• Credentials;
• System configurations;
• Business information; and
• Other confidential information.

12. PASSWORD SECURITY

Hyphenet Enterprises may maintain password-security requirements appropriate to the systems being used.

Where applicable, security controls may include:

• Strong passwords;
• Password complexity;
• Password rotation;
• Account lockout;
• Unique credentials;
• Prohibition of password sharing; and
• Secure credential storage.

13. MULTI-FACTOR AUTHENTICATION

Where technically available and appropriate, Hyphenet Enterprises may use multi-factor authentication ("MFA") to protect systems and accounts.

MFA requirements may vary depending on:

• System;
• Risk;
• Customer requirements;
• Technical capability; and
• Service scope.

14. ADMINISTRATIVE ACCESS

Privileged or administrative access may be restricted to authorised personnel.

Administrative access may be:

• Role-based;
• Logged;
• Reviewed;
• Time-limited where appropriate; and
• Removed when no longer required.

15. REMOTE ACCESS

Remote access may be used for:

• IT support;
• Troubleshooting;
• Monitoring;
• Configuration;
• Maintenance;
• Security operations; and
• Other authorised activities.

Remote access should be restricted to legitimate service requirements.

16. REMOTE SUPPORT SECURITY

Where remote support tools are used, Hyphenet Enterprises may apply appropriate safeguards such as:

• Authentication;
• Access restrictions;
• Session controls;
• Encryption where supported;
• Logging;
• Authorisation; and
• Access termination.

17. CUSTOMER APPROVAL FOR ACCESS

Where practical, Customer approval may be obtained before accessing systems containing sensitive or confidential information.

Emergency access may be required where necessary to prevent significant service disruption or security impact, subject to applicable contractual arrangements.

18. DATA ENCRYPTION

Where appropriate and technically feasible, Hyphenet Enterprises may use encryption to protect information:

• During transmission;
• During storage;
• During backup;
• During remote access; or
• During other security-sensitive processes.

The specific encryption mechanisms may vary by system and service.

19. NETWORK SECURITY

Security controls may include:

• Firewalls;
• Network segmentation;
• Secure remote access;
• Access control;
• Monitoring;
• Endpoint protection;
• VPN;
• Secure protocols; and
• Other appropriate controls.

20. ENDPOINT SECURITY

Company-managed endpoints may use appropriate security measures such as:

• Antivirus;
• Endpoint protection;
• EDR/XDR where implemented;
• Firewall;
• Security updates;
• Device encryption;
• Access control;
• Screen-lock controls; and
• Other security technologies.

21. MALWARE PROTECTION

Hyphenet Enterprises may deploy reasonable measures to protect systems against:

• Viruses;
• Trojans;
• Ransomware;
• Spyware;
• Worms;
• Malicious scripts;
• Other malware.

22. SECURITY PATCHING

Where applicable, systems may be regularly updated with:

• Operating system patches;
• Security patches;
• Firmware updates;
• Application updates; and
• Security fixes.

Patch timing may depend on:

• Severity;
• System criticality;
• Vendor availability;
• Testing requirements;
• Customer approval; and
• Operational considerations.

23. VULNERABILITY MANAGEMENT

Where security management is included, Hyphenet Enterprises may identify and address vulnerabilities through:

• Security updates;
• Configuration changes;
• Endpoint protection;
• Vulnerability scanning;
• Security monitoring; or
• Other appropriate measures.

24. SECURITY MONITORING

Where appropriate, Hyphenet Enterprises may monitor systems for:

• Suspicious activity;
• Security events;
• Malware;
• Unauthorised access;
• Service anomalies;
• System failures; and
• Other security events.

25. LOGGING

Systems may maintain logs relating to:

• Authentication;
• Administrative actions;
• Security events;
• Support activity;
• System events;
• Network activity; and
• Other relevant activities.

Logging practices may vary by system and service.

26. LOG RETENTION

Security and service logs may be retained for a reasonable period based on:

• Security requirements;
• Operational needs;
• Contractual obligations;
• Legal requirements;
• Audit requirements; and
• Storage considerations.

27. DATA BACKUP

Where backup services are included, backup arrangements may include:

• Backup frequency;
• Retention period;
• Backup location;
• Encryption;
• Recovery procedures; and
• Restoration testing.

The applicable agreement will determine the specific backup scope.

28. CUSTOMER BACKUP RESPONSIBILITY

Unless expressly contracted, Customers remain responsible for maintaining backups of their critical data.

Hyphenet Enterprises does not automatically assume responsibility for Customer data backup merely because it provides IT support.

29. DISASTER RECOVERY

Disaster recovery services are provided only where specifically agreed.

Where contracted, disaster recovery arrangements may include:

• Recovery objectives;
• Backup infrastructure;
• Recovery procedures;
• Testing;
• Failover;
• Restoration; and
• Business continuity support.

30. DATA RECOVERY

Data recovery may be provided as a separate service.

Recovery success may depend on:

• Condition of storage media;
• Extent of damage;
• Overwriting;
• Encryption;
• Hardware condition;
• Available backups; and
• Other technical factors.

No data recovery outcome can be guaranteed unless expressly agreed.

31. DATA CENTRE SECURITY

Where Hyphenet Enterprises operates or supports equipment at a data centre, reasonable security measures may include:

• Physical access controls;
• Restricted entry;
• CCTV where available;
• Environmental controls;
• Power protection;
• Fire protection; and
• Other appropriate controls.

Where equipment is located in a third-party data centre, the third party's security controls also apply.

32. PHYSICAL SECURITY

Hyphenet Enterprises may use reasonable physical security controls for:

• Offices;
• Equipment;
• Storage areas;
• Server rooms;
• Documents;
• Networking equipment; and
• Other business assets.

33. EQUIPMENT SECURITY

Rented or managed Equipment should be protected against:

• Theft;
• Loss;
• Unauthorised access;
• Tampering;
• Physical damage; and
• Unauthorised modification.

Customer responsibilities for rented Equipment are also governed by the IT Equipment Rental Terms & Conditions.

34. ASSET MANAGEMENT

Where asset management is provided, Hyphenet Enterprises may maintain records including:

• Asset number;
• Serial number;
• Model;
• Customer;
• User;
• Location;
• Deployment date;
• Return date;
• Service history; and
• Asset status.

35. ASSET TAGGING

Equipment may be identified through:

• Asset tags;
• Barcodes;
• Serial numbers;
• QR codes;
• Security labels; or
• Other identification mechanisms.

Customers should not remove or alter such identification.

36. DATA SANITISATION

Before Equipment is:

• Reassigned;
• Returned to inventory;
• Re-rented;
• Disposed of; or
• Decommissioned,

Hyphenet Enterprises may perform data sanitisation where included or required.

37. DATA ERASURE

Where appropriate, data may be removed through:

• Secure deletion;
• Drive formatting;
• Cryptographic erasure;
• Manufacturer tools;
• Secure wipe procedures; or
• Other appropriate methods.

The exact method may depend on the equipment and storage technology.

38. CUSTOMER RESPONSIBILITY BEFORE RETURN

Customers should remove their:

• Files;
• Accounts;
• Passwords;
• Tokens;
• Credentials;
• Browser sessions;
• Cloud accounts; and
• Other confidential information

before returning Equipment.

39. DATA RETENTION

Hyphenet Enterprises may retain information for as long as reasonably necessary for:

• Service delivery;
• Contract management;
• Billing;
• Legal compliance;
• Security;
• Audit;
• Dispute resolution; and
• Legitimate business purposes.

40. DATA DELETION

Where information is no longer required and no legal or contractual obligation requires retention, Hyphenet Enterprises may delete or anonymise it.

41. CUSTOMER REQUEST FOR DELETION

Customers may request deletion of applicable personal information, subject to:

• Applicable law;
• Contractual obligations;
• Legal retention requirements;
• Accounting requirements;
• Security requirements; and
• Legitimate business purposes.

Requests should be directed to the contact details in this Policy.

42. PERSONAL DATA PROTECTION

Personal information will be handled in accordance with our Privacy Policy and applicable Indian data-protection requirements.

Privacy Policy: www.hyphenet.net/privacy-policy

43. DATA MINIMISATION

Hyphenet Enterprises seeks to collect and process only information reasonably necessary for:

• Service delivery;
• Business operations;
• Customer communication;
• Security;
• Billing;
• Compliance; and
• Other legitimate purposes.

44. ACCURACY OF INFORMATION

Where appropriate, Customers should provide accurate and updated information.

Incorrect information may affect:

• Service delivery;
• Asset tracking;
• Support;
• Billing;
• Security; and
• Communication.

45. CUSTOMER ACCESS TO DATA

Where applicable, Customers may request information concerning personal data processed by Hyphenet Enterprises, subject to applicable law and contractual limitations.

46. DATA BREACH

A data breach may include:

• Unauthorised access;
• Unauthorised disclosure;
• Accidental loss;
• Destruction;
• Alteration;
• Data leakage; or
• Other security incident affecting protected information.

47. INCIDENT DETECTION

Potential security incidents may be identified through:

• Monitoring;
• Alerts;
• Employee reporting;
• Customer notification;
• Security tools;
• Audit;
• Vendor notification; or
• Other mechanisms.

48. INCIDENT RESPONSE

Where a security incident is identified, Hyphenet Enterprises may take reasonable steps to:

• Identify the incident;
• Contain the incident;
• Investigate the incident;
• Protect affected systems;
• Restore services;
• Assess impact; and
• Take corrective action.

49. CUSTOMER NOTIFICATION

Where a security incident materially affects Customer information within Hyphenet Enterprises' responsibility, Hyphenet Enterprises may notify the Customer in accordance with:

• Applicable law;
• Contractual requirements;
• The applicable SLA; and
• The nature and severity of the incident.

50. SECURITY INCIDENT COOPERATION

Customers should reasonably cooperate during security investigations.

This may include providing:

• Logs;
• System information;
• Access;
• Incident details;
• Affected asset information; and
• Other relevant information.

51. THIRD-PARTY SECURITY INCIDENTS

Where a security incident occurs within a third-party service provider's environment, Hyphenet Enterprises may depend on that provider for:

• Investigation;
• Notification;
• Remediation;
• Logs; and
• Other incident information.

52. VENDOR SECURITY

Where appropriate, Hyphenet Enterprises may assess technology vendors based on factors such as:

• Security capabilities;
• Reliability;
• Service availability;
• Data handling;
• Contractual protections; and
• Business requirements.

53. THIRD-PARTY PROCESSORS

Hyphenet Enterprises may use third-party service providers for:

• Cloud services;
• Hosting;
• Email;
• IT tools;
• Ticketing;
• Analytics;
• Security;
• Payment processing;
• Communication; and
• Other business functions.

Such providers may process information according to their contractual and legal obligations.

54. CLOUD SERVICES

Where cloud services are used, security controls may include:

• Authentication;
• Access controls;
• Encryption;
• Monitoring;
• Backup;
• Logging; and
• Vendor security controls.

Actual controls depend on the relevant cloud service.

55. EMAIL SECURITY

Hyphenet Enterprises may use reasonable controls to protect business email, including:

• Spam filtering;
• Malware protection;
• Authentication;
• Access control;
• Multi-factor authentication where implemented; and
• Other security controls.

56. PHISHING PROTECTION

Employees and customers may be advised to remain alert to:

• Phishing;
• Credential theft;
• Suspicious attachments;
• Malicious links;
• Impersonation;
• Business email compromise; and
• Other social-engineering attacks.

57. EMPLOYEE SECURITY AWARENESS

Hyphenet Enterprises may provide employees with security awareness regarding:

• Password security;
• Phishing;
• Data handling;
• Confidentiality;
• Device security;
• Remote working;
• Social engineering; and
• Incident reporting.

58. DEVICE SECURITY

Company-managed devices may use controls such as:

• Screen lock;
• Password/PIN;
• Encryption;
• Antivirus;
• Firewall;
• Security updates;
• Endpoint security; and
• Device management.

59. REMOTE WORKING

Where employees work remotely, reasonable security measures may include:

• Secure authentication;
• VPN;
• Device encryption;
• Endpoint protection;
• Screen locking;
• Access controls; and
• Secure communication.

60. USB AND REMOVABLE MEDIA

Where appropriate, removable media may be:

• Restricted;
• Controlled;
• Scanned;
• Encrypted; or
• Disabled.

Specific controls may depend on the environment.

61. PHYSICAL DOCUMENT SECURITY

Physical documents containing confidential information may be protected through:

• Controlled access;
• Secure storage;
• Restricted distribution;
• Secure disposal; and
• Other reasonable measures.

62. SECURE DISPOSAL

When information or equipment is no longer required, Hyphenet Enterprises may use appropriate disposal methods.

These may include:

• Secure document destruction;
• Data wiping;
• Device sanitisation;
• Secure disposal; and
• Certified destruction where required.

63. SECURITY TESTING

Where appropriate, Hyphenet Enterprises may perform:

• Vulnerability assessments;
• Configuration reviews;
• Security checks;
• Patch verification;
• Access reviews; and
• Other security assessments.

64. PENETRATION TESTING

Penetration testing or vulnerability assessment of Customer systems will only be performed where:

• Specifically contracted;
• Authorised by the Customer; or
• Otherwise legally permitted.

65. CHANGE CONTROL

Security-sensitive changes should be reviewed and authorised where appropriate.

This may include:

• Firewall changes;
• Server changes;
• Access changes;
• Network changes;
• Security policy changes; and
• Major configuration changes.

66. ACCESS REVIEWS

Where appropriate, user and administrator access may be periodically reviewed.

Access may be removed when:

• An employee leaves;
• A role changes;
• Access is no longer required; or
• A security risk is identified.

67. EMPLOYEE OFFBOARDING

When personnel leave Hyphenet Enterprises, access to relevant systems may be:

• Disabled;
• Removed;
• Revoked;
• Passwords rotated; and
• Equipment recovered.

68. CUSTOMER EMPLOYEE OFFBOARDING

Where Hyphenet Enterprises manages Customer equipment, the Customer should promptly inform Hyphenet Enterprises when an employee:

• Leaves;
• Changes role;
• No longer requires equipment; or
• Should no longer have system access.

69. SECURITY OF CUSTOMER EQUIPMENT

Where Hyphenet Enterprises manages or rents equipment, appropriate security controls may include:

• Asset identification;
• Secure configuration;
• Password protection;
• Encryption;
• Endpoint security;
• Secure boot;
• BIOS controls; and
• Other agreed controls.

70. CUSTOMER SECURITY REQUIREMENTS

Customers may specify additional security requirements.

Such requirements should be agreed before implementation and may require additional:

• Software;
• Hardware;
• Engineering;
• Licensing;
• Monitoring; or
• Support charges.

71. SECURITY STANDARDS

Hyphenet Enterprises may use recognised security principles and industry practices appropriate to the size, nature and risk profile of the relevant service.

Where a specific standard or certification is required, it must be expressly agreed in writing.

72. NO CERTIFICATION CLAIM

Unless expressly stated otherwise, nothing in this Policy should be interpreted as representing that Hyphenet Enterprises is certified under:

• ISO 27001;
• SOC 2;
• PCI DSS;
• HIPAA;
• GDPR;
• ISO 27701; or
• Any other specific security or compliance framework.

Where a customer requires compliance with a particular standard, the requirement should be addressed contractually.

73. CUSTOMER SECURITY RESPONSIBILITY

Security is a shared responsibility.

Customers remain responsible for their own:

• Users;
• Passwords;
• Applications;
• Data;
• Network;
• Internet;
• Cloud services;
• Security policies;
• Backups; and
• Business continuity.

74. SHARED RESPONSIBILITY

Depending on the service, responsibilities may be divided between:

• Hyphenet Enterprises;
• Customer;
• Hardware manufacturer;
• Software vendor;
• Cloud provider;
• ISP;
• Data centre; and
• Other third parties.

The applicable agreement shall determine responsibility for specific systems.

75. SECURITY OF RENTED EQUIPMENT

Customers renting Equipment from Hyphenet Enterprises are responsible for protecting Equipment while it is in their possession.

The IT Equipment Rental Terms & Conditions apply to:

• Loss;
• Theft;
• Damage;
• Unauthorised modification;
• Return; and
• Equipment security.

76. CUSTOMER DATA ON RENTED DEVICES

Customers should ensure that confidential data is protected on rented devices through appropriate:

• Encryption;
• Authentication;
• Access control;
• Backup; and
• Security measures.

77. DEVICE RETURN

Before returning rented Equipment, Customers should:

• Backup required information;
• Sign out accounts;
• Remove credentials;
• Remove confidential data;
• Remove authentication tokens; and
• Follow agreed data-erasure procedures.

78. SECURITY OF ENGINEER ACCESS

Hyphenet Enterprises personnel should use Customer system access only for legitimate service purposes.

Personnel should not intentionally:

• Copy Customer data unnecessarily;
• Disclose Customer information;
• Access unrelated systems; or
• Use Customer information for unauthorised purposes.

79. CONFIDENTIAL INFORMATION

Confidential information may include:

• Customer business data;
• Credentials;
• Network diagrams;
• IP addresses;
• Server configurations;
• Security configurations;
• Commercial information;
• Contracts;
• Financial information; and
• Other non-public information.

80. CONFIDENTIALITY OBLIGATION

Confidential information shall be handled according to applicable contractual and legal obligations.

Additional confidentiality requirements may be included in an NDA.

81. DATA SHARING

Hyphenet Enterprises may share information with authorised third parties where reasonably necessary for:

• Service delivery;
• Hardware warranty;
• Software support;
• Cloud services;
• Security;
• Payment;
• Legal compliance; or
• Other legitimate business purposes.

82. LEGAL DISCLOSURE

Information may be disclosed where required by:

• Law;
• Court order;
• Government authority;
• Regulatory authority; or
• Other lawful process.

83. SECURITY AUDITS

Where contractually agreed, Customers may request reasonable information regarding security controls relevant to the contracted Services.

Such requests should not require disclosure of:

• Security-sensitive internal information;
• Other customer information;
• Proprietary systems;
• Trade secrets; or
• Information that would itself create security risk.

84. CUSTOMER SECURITY AUDITS

Where expressly agreed, Hyphenet Enterprises may cooperate with reasonable Customer security audits.

Audit scope, frequency, confidentiality and costs should be agreed in advance.

85. SECURITY QUESTIONNAIRES

Hyphenet Enterprises may respond to reasonable customer security questionnaires relevant to the Services.

Detailed technical or confidential information may require an NDA or other appropriate arrangement.

86. DATA LOCATION

Information may be stored or processed in India or other locations depending on the systems and service providers used.

Where specific data-location requirements apply, they should be expressly agreed in writing.

87. INTERNATIONAL TRANSFERS

Where information is transferred or processed outside India, Hyphenet Enterprises will seek to handle such processing in accordance with applicable law and contractual requirements.

88. DATA PROTECTION RIGHTS

Applicable individuals may have rights concerning their personal information, subject to applicable law.

Requests should be made through the contact details in our Privacy Policy.

89. SECURITY INCIDENT NOTIFICATION CONTACT

Security incidents affecting Customer systems or information should be reported promptly to the designated Hyphenet Enterprises support contact.

Support Email: support@hyphenet.net

Phone: +91 93540 45878

90. CUSTOMER SECURITY INCIDENT REPORTING

Customers should provide, where available:

• Incident description;
• Affected system;
• Affected asset;
• Date/time;
• Known indicators;
• Contact person; and
• Other relevant information.

91. INCIDENT PRIORITY

Security incidents may be prioritised according to:

• Business impact;
• Number of affected systems;
• Data sensitivity;
• Security risk;
• Availability impact; and
• Other relevant factors.

92. INCIDENT COMMUNICATION

During significant incidents, communication may be coordinated through designated Customer contacts.

Information may be shared progressively as investigation develops.

93. BUSINESS CONTINUITY

Hyphenet Enterprises may maintain reasonable operational continuity measures appropriate to its business.

However, no business continuity plan can guarantee uninterrupted service under all circumstances.

94. BACKUP OF INTERNAL SYSTEMS

Hyphenet Enterprises may maintain backups of critical internal business information according to its operational requirements.

Backup availability and recovery objectives may vary between systems.

95. EMPLOYEE ACCESS TO CUSTOMER DATA

Employee access to Customer information should be limited to personnel who require access for legitimate business purposes.

96. CONTRACTOR ACCESS

Where contractors or third-party personnel are used, access may be limited according to:

• Contractual requirements;
• Business need;
• Security requirements; and
• Customer instructions where applicable.

97. SECURITY TRAINING

Personnel may receive periodic security awareness and operational training appropriate to their responsibilities.

98. SECURITY IMPROVEMENT

Hyphenet Enterprises may periodically review its security controls and implement improvements based on:

• New threats;
• Technology changes;
• Customer requirements;
• Business risks;
• Security incidents; and
• Applicable legal requirements.

99. POLICY REVIEW

This Policy may be reviewed periodically to ensure that it remains aligned with:

• Business operations;
• Technology;
• Security requirements;
• Customer expectations; and
• Applicable law.

100. CHANGES TO THIS POLICY

Hyphenet Enterprises may update this Policy from time to time.

The latest version will be published on:

www.hyphenet.net/data-security-protection

101. GOVERNING LAW

This Policy shall be governed by the laws of India.

Subject to any specific contractual dispute-resolution or jurisdiction provision, disputes shall be subject to the jurisdiction of the appropriate courts having jurisdiction over Hyphenet Enterprises.

102. GRIEVANCE REDRESSAL

For data-security or protection-related concerns, Customers may contact:

Grievance Officer: Rahul Kumar Designation: Sr. Manager Email: sales@hyphenet.net Phone: +91 93540 45878

Working Hours: Monday to Saturday, during normal business hours

103. CONTACT INFORMATION

Hyphenet Enterprises

Sales / Privacy Email: sales@hyphenet.net

Support Email: support@hyphenet.net

Phone: +91 93540 45878

Registered / Principal Office:

7th Floor, Devika Tower, Lala Lajpat Rai Road, Nehru Place, New Delhi, Delhi – 110019, India

Grievance Officer: Rahul Kumar

Designation: Sr. Manager

Grievance Email: sales@hyphenet.net

Grievance Phone: +91 93540 45878

Working Hours: Monday to Saturday, during normal business hours

104. CUSTOMER ACKNOWLEDGEMENT

By using Hyphenet Enterprises' Website or engaging Hyphenet Enterprises for IT rental, IT support, infrastructure or other technology services, the Customer acknowledges that it has reviewed this Data Security & Protection Policy.

Where a specific contract or SLA contains additional security obligations, those obligations shall apply to the relevant engagement.

105. FINAL NOTICE

This Policy describes Hyphenet Enterprises' general approach to information security and data protection.

The exact security controls applicable to a particular Customer may depend upon:

• Services purchased;
• Customer requirements;
• System architecture;
• Data sensitivity;
• Contractual obligations;
• Technical feasibility;
• Third-party services; and
• Applicable law.

Where a Customer requires specific security controls, certifications, audits, data-processing terms, breach-notification timelines or compliance obligations, those requirements should be expressly documented in the applicable agreement.

Hyphenet Enterprises www.hyphenet.net

© Hyphenet Enterprises. All Rights Reserved.