Legal information
Security at NewEdge360
How NewEdge360 protects identity, tenant data, service communication and operational accountability.
Last updated 13 October 2026
Identity and access
NewEdge360 uses one authenticated identity across authorised organisations and applications. Permissions, application access and branch scope are evaluated explicitly so a user sees only the work assigned to them.
Tenant and branch isolation
Tenant context and branch scope are enforced independently. Missing or inconsistent context fails closed instead of falling back to broader access.
Protected service communication
Internal service-to-service requests use signed, time-bound messages with source identity, key version, timestamp and replay protection. Browser user tokens are not reused as internal service credentials.
Data and file protection
Private files are kept separate from public media and are delivered only after the owning business record authorises access. Stored credentials and reusable tokens are protected rather than exposed in application responses.
Financial and workflow controls
Commercial records, approvals and accounting activity retain clear system ownership. Approved actions carry source, branch, currency and audit context instead of relying on untraceable manual hand-offs.
Operational resilience
Health and readiness checks, monitored deployment gates, release identity and public service status help the team detect and investigate problems without treating a successful build as proof of a healthy service.
Responsible disclosure
If you believe you have found a security issue, use the Contact page and choose the support route. Do not include passwords, private keys, payment details or customer data in the first message.
Questions
If anything is unclear, contact NewEdge360 before purchasing or continuing to use the service.
Contact NewEdge360