Trust & security

Security at
GavelNet.

An overview of the controls, practices and responsibilities that support the GavelNet platform.

Security is not a single feature. It is a set of technical and operational controls that should be reviewed in the context of how the platform is deployed and used.

Data protection

  • In transit: Traffic is protected using HTTPS/TLS.
  • At rest: Stored data is protected using encryption provided by the underlying platform and services.
  • Secrets: Credentials and application secrets are kept separate from ordinary application content.

Identity and access

  • Access should follow least-privilege principles.
  • Privileged administrative access should use stronger authentication controls.
  • Enterprise identity requirements can be assessed as part of deployment planning.

Infrastructure and monitoring

  • Operational logging and monitoring are used to support troubleshooting and security review.
  • Backups and recovery procedures form part of platform operations.
  • Security controls are reviewed as the platform and deployment model evolve.

Data handling and privacy

GavelNet is operated by Aria Data Labs Pte. Ltd. Personal data handling should be limited to what is required for the service and managed in accordance with applicable Singapore privacy obligations and customer requirements.

Where customer systems or repositories are integrated, access should remain scoped to the permissions and deployment agreed with that customer.

Responsible disclosure

If you believe you have identified a security issue, contact security@ariadatalabs.com with enough information for us to investigate. Please avoid testing that could disrupt service or access data belonging to other users.

This page is a high-level security overview and is not a substitute for deployment-specific security documentation or contractual commitments.

Questions

Need a security discussion?

For security or enterprise deployment questions, contact the GavelNet team.

Contact security