RefundWall Trust Centre
Security
How RefundWall protects merchant and customer data
RefundWall is designed with security, data isolation and controlled production change as core engineering concerns.
Our approach focuses on practical safeguards across infrastructure, software delivery, access control and data lifecycle management.
Environment isolation
RefundWall operates isolated development, staging and production environments on AWS.
Production infrastructure, application configuration and credentials are isolated from development and staging environments. Environment boundaries are maintained throughout the deployment and operational lifecycle.
This separation helps protect production services and merchant data from development and testing activity.
Controlled production releases
RefundWall uses a staged release process for production changes:
Application artifacts that pass Stage acceptance are promoted to production as immutable release artifacts.
The production deployment therefore uses the same application artifacts that completed the required pre-production checks, providing a clear relationship between what was tested and what is subsequently deployed.
Production access
Production access is controlled using dedicated role-based permissions.
Deployment authentication uses short-lived credentials, and routine production changes are made through the controlled release process.
Production access and deployment responsibilities are separated from normal development activity.
Secrets and credentials
Sensitive application credentials and operational secrets are stored separately from application source code.
Credentials are isolated by environment, with dedicated production secrets for production services.
Sensitive application credentials and cryptographic secrets are managed as protected runtime secrets.
Data protection and isolation
Public RefundWall application and API traffic is protected using HTTPS.
Access between application workloads and internal data services is restricted through infrastructure-level network controls.
RefundWall uses separate durable and ephemeral storage layers, with security and retention controls appropriate to their purpose.
Customer identity is merchant-scoped. Customer behaviour associated with one merchant remains within that merchant's RefundWall identity context.
Data minimisation
RefundWall is designed to process the Shopify data required to provide refund decision intelligence and associated application functionality.
Access to Shopify data is explicitly declared through the permissions granted to the RefundWall application.
Data requirements are considered as part of product and engineering design so that processing remains aligned with the functionality being provided.
Data lifecycle and retention
Retention controls apply to both durable and ephemeral application data.
RefundWall implements lifecycle processing for customer and merchant data, including handling Shopify privacy and deletion events.
These processes remove or minimise applicable data when lifecycle requirements are triggered.
Lifecycle behaviour is tested in the deployed staging environment, including durable deletion and minimisation behaviour and repeat processing.
Testing and release assurance
RefundWall combines automated testing with deployed-environment acceptance checks before production promotion.
Release validation covers application behaviour, infrastructure configuration, Shopify integration, data lifecycle behaviour and service health.
Production promotion is part of the release process itself rather than a separate ad-hoc deployment activity.
Monitoring and operational visibility
RefundWall maintains production health checks, application logging and operational telemetry.
These provide visibility into service health and runtime behaviour and support investigation when something requires attention.
RefundWall also maintains a separate public status service for communicating material service availability information.
Security and privacy engineering
Security and privacy requirements are treated as part of the engineering lifecycle.
Infrastructure controls, release processes, data retention, privacy lifecycle behaviour and operational safeguards are implemented alongside the product rather than handled solely as administrative activities.
RefundWall's security practices are designed to remain proportionate to the platform's risk profile and to evolve as the service grows.
Reporting a security concern
Security concerns can be reported to support@refundwall.com.