Home/Security and Compliance

How we protect seller data

Every marketplace sets rules for how seller data is handled, including Amazon's Data Protection Policy and Acceptable Use Policy. This page summarises how we meet them in DMSMatrix and in our services.

Our commitments

The principles behind how we handle seller and customer data, in DMSMatrix and in our services.

  • You choose our permissions in each marketplace and can remove them at any time.
  • We never ask for your password, by email, phone or any other way.
  • We access only the data each service needs.

What we do, in detail

Data protection

Seller and customer data is used only to deliver the services a client has agreed to.

  • AES-256 encryption at rest and TLS 1.2 or higher in transit
  • Encryption keys held in Azure Key Vault, with restricted and logged access
  • Never sold. Shared only with the carrier shipping an order and our hosting provider, Microsoft Azure

Personal information (PII)

We store customer personal information only when a service needs it, such as creating a shipping label.

  • Limited to authorised staff with a business need
  • Used only to ship orders and provide tracking
  • Deleted within 30 days of the order being delivered

Access and passwords

Access is granted through marketplace user permissions or official app authorisation, with least privilege roles.

  • Unique accounts with passwords of at least 12 characters, changed at least every 365 days
  • Multi factor authentication on every system with protected data
  • Access removed when an engagement ends or a team member leaves

Network and devices

Our cloud environment and work devices are protected by technical controls, not just rules.

  • Hosted on Microsoft Azure behind network security groups and firewalls
  • Full disk encryption and endpoint protection on all work devices
  • USB storage blocked by Intune device policy, with email alerts to the security team

Logging and monitoring

Security events from our applications and cloud services are collected in one central place.

  • Central logs kept for 12 months
  • Alert rules for failed sign ins, permission changes and unusual data access
  • Alerts sent by email to the security team and reviewed

Vulnerability management

We look for weaknesses continuously and fix them on a fixed timetable.

  • Automated vulnerability scans at least every 30 days
  • Critical and high severity issues fixed within 7 days
  • Medium severity issues fixed within 30 days

Incident response

A written incident response plan covers detection, containment, notification, recovery and review.

  • Incidents reported to security@shyaasu.com and logged
  • Amazon notified at security@amazon.com within 24 hours when Amazon data is involved
  • Plan reviewed and tested at least every 6 months

Backup and recovery

Encrypted backups let us recover quickly from a failure.

  • Daily encrypted backups copied to a separate Azure region
  • Recovery point objective (RPO) of 24 hours
  • Recovery time objective (RTO) of 4 hours

Staff practices

Everyone who handles seller data is trained and bound by confidentiality.

  • Signed confidentiality agreements
  • Security awareness training at onboarding and every year
  • Personal devices are not allowed to access protected data

Report a security concern. If you believe data handled by Shyaasu Technology Consultancy Pvt. Ltd. or DMSMatrix may be at risk, email security@shyaasu.com. Our information security contact is Atul Dravid, Information Security Officer (atul.dravid@shyaasu.com). We log every report and respond promptly.

Read our Information Security Policy and Privacy Policy for full details.

Questions about how we handle data?

We are happy to walk you through our security practices before you start.