Home/Information Security Policy

Information Security Policy

This policy sets out how Shyaasu Technology Consultancy Pvt. Ltd. protects data in DMSMatrix and across our services, including data received from Amazon. It applies to every employee, contractor and system that handles that data.

Purpose and scope

This policy covers every system, person and supplier that stores, processes or transmits seller data or buyer personal information ("protected data"), including data DMSMatrix receives from Amazon.

It is written to meet Amazon's Data Protection Policy and Acceptable Use Policy and India's Digital Personal Data Protection Act, 2023.

Roles and contacts

  • Information security point of contact: Atul Dravid, Information Security Officer, atul.dravid@shyaasu.com. Owns this policy and the incident response plan.
  • Security reports: security@shyaasu.com, monitored by the security team.
  • Everyone with access to protected data must follow this policy and report suspected incidents immediately.

Data we protect

  • Seller account data, such as listings, inventory, orders and FBA shipments.
  • Buyer personal information needed to ship an order: name, delivery address and phone number.

We collect only the data each feature needs. Buyer personal information is never used for marketing and is shared only as described in our Privacy Policy.

Each seller's data is kept separate and used only for that seller. Amazon data is never combined or aggregated across sellers.

Access control

  • Access follows least privilege and is approved by the information security point of contact.
  • Every person has their own unique account. Shared or generic accounts are not allowed.
  • Access rights are reviewed regularly and removed on a person's last working day or when their role no longer needs them.
  • Access to production systems requires multi factor authentication and a company managed device.

Password policy

  • Passwords must be at least 12 characters long and must not contain the user name.
  • Passwords must be changed at least every 365 days, and immediately if a compromise is suspected.
  • Multi factor authentication (MFA) is required on every account that can reach protected data, including cloud consoles, code repositories, email and DMSMatrix administration.
  • Passwords are kept in a company password manager. They are never shared, written down or sent by email or chat.
  • Accounts are locked after repeated failed sign in attempts.

Encryption and key management

  • Protected data is encrypted at rest with AES-256, including databases, file storage and backups.
  • Data in transit is encrypted with TLS 1.2 or higher. Unencrypted connections are refused.
  • Encryption keys and secrets are kept in Azure Key Vault, never in source code. Access to keys is limited to named administrators, protected by MFA and logged.
  • Keys are rotated at least every 365 days, and immediately if a compromise is suspected.

Logging and monitoring

  • Logs from DMSMatrix, Azure services and administrator access are collected centrally in Azure Monitor (Log Analytics).
  • Logs are kept for at least 12 months and are protected against change or deletion.
  • Logs never contain passwords or buyer personal information.
  • Alert rules notify the security team by email of repeated failed sign ins, new administrator accounts or permission changes, sign ins from unusual locations, and unusual volumes of data access or export.
  • Every alert is reviewed and, where needed, handled as an incident.

Vulnerability management

  • Automated vulnerability scans of our applications, cloud resources and software dependencies run at least every 30 days and after every significant change.
  • Findings are rated by severity. Critical and high severity issues are fixed within 7 days. Medium severity issues are fixed within 30 days. Low severity issues are fixed in normal releases.
  • Operating systems and software are kept on supported versions, and security updates are applied promptly.
  • Code changes are reviewed before release.

Incident response plan

Every security incident is handled in six steps:

  1. Detect and report. Anyone who suspects an incident reports it immediately to security@shyaasu.com.
  2. Assess. The information security point of contact confirms the incident, rates its severity and opens an incident record.
  3. Contain. Affected accounts, keys and systems are isolated, disabled or rotated.
  4. Notify. If Amazon data is or may be involved, we notify Amazon at security@amazon.com within 24 hours of detection. Affected sellers are told without delay, and authorities where the law requires it.
  5. Recover. Systems are restored from clean, verified backups and monitored closely.
  6. Review. A written review records the cause and the actions that stop it happening again.

The plan is reviewed and tested at least every 6 months, and after every significant incident.

Devices and removable media

  • Only company managed devices may access protected data. Personal devices are not allowed.
  • Work devices are enrolled in Microsoft Intune, which enforces full disk encryption, screen lock and endpoint protection with Microsoft Defender.
  • USB storage and other removable media are blocked by Intune device policy, so protected data cannot be copied to them.
  • Every blocked attempt is logged, and an alert is sent by email to the security team, who review it the same working day.
  • Protected data is not stored on local devices unless a task requires it, and is deleted when the task is complete.

Network and cloud security

  • DMSMatrix runs on Microsoft Azure. Network security groups and firewalls allow only the traffic each service needs.
  • Databases and storage are not reachable from the public internet.
  • Production, test and development environments are kept separate, and real buyer data is never used for testing.

Backup and recovery

  • Encrypted backups run every day and are copied to a separate Azure region from the main data.
  • Recovery point objective (RPO): 24 hours. Recovery time objective (RTO): 24 hours.
  • Backups are kept only for a short rolling period, so buyer personal information is never held for more than 30 days after delivery.
  • Restoring from backup is tested at least every 6 months.

Data retention and deletion

  • Buyer personal information is deleted automatically within 30 days of the order being delivered, from live systems and backups.
  • When a seller disconnects DMSMatrix or ends their contract, their data is deleted within 30 days unless the law requires us to keep it.
  • Every deletion run is logged.

People and training

  • Everyone signs a confidentiality agreement before they receive access.
  • Security and data protection training is completed at onboarding and every year after that.
  • Breaking this policy can lead to disciplinary action, up to and including dismissal.

Suppliers

We use only suppliers that protect data to at least the standard of this policy. The suppliers that receive protected data are Microsoft Azure, which hosts DMSMatrix, and the carriers that sellers choose for shipping labels, which receive recipient and parcel details only.

Policy review

This policy is reviewed at least once a year, and whenever our systems or Amazon's requirements change.

Effective date: 29 October 2026
Owner: Atul Dravid, Information Security Officer