Platform & Customer FAQs

Data Security, Support and Vendor Continuity

Review documented access controls, data access, support responsibilities, and continuity requirements.

Burton Platform Customers / Operations / IT 6 min Version 2026.10 Updated 2026-10-12
0assets 2026-10-12Updated on

01 How should we assess data security?

Compare your IT requirements with documentation for the proposed environment. Burton product workflows use workspace or role permissions and authorization controls; the exact boundaries must be tested with the intended user roles. Security approval should rely on evidence for the deployed service.

TopicEvidence to review
Identity and accessLogin controls, role and workspace scope, account removal, and privileged actions.
Data handlingHosting location, encryption requirements, retention, deletion, and permitted data use.
AuditAvailable activity or approval logs, visibility, and retention.
Service protectionBackup/restore responsibilities, incident handling, and recovery requirements.
Third parties and AIData exchanged with providers, access scopes, and handling restrictions.

Confirm any required certification, independent report, or contractual protection explicitly. A product description is not evidence of a certification or a guarantee that every protection is included.

02 What support should we expect?

Agree support channels, operating hours, severity levels, escalation contacts, and responsibility for customer configuration and third-party connections. Response targets, service levels, implementation assistance, and incident commitments belong in the applicable service agreement.

When reporting a problem, include the affected workflow, time, sanitized record identifier, expected result, and observed behavior. Do not send passwords, API secrets, or unnecessary personal data.

03 What if a smaller vendor has a service problem?

Assess continuity through implementation ownership, support processes, data export options, documentation, and recovery arrangements. Confirm which data can be exported, in what format, and how access works during and after the contract. Test an agreed export and restoration or transition process where it is part of your requirements.

Vendor size and experience are useful context, but acceptance should also use project evidence. Apply the same checks to Burton and larger providers, and use a pilot to verify critical workflows before commitment.

See the privacy information, service terms, and implementation planning guide.

BurtonSoftware.Ai Data Security, Support and Vendor Continuity · Version 2026.10