Privacy and data ownership
Burz Suite CRM privacy policy
Burz Suite CRM is designed for accountable business environments where infrastructure control, data boundaries, and governance accountability are mandatory.
Policy details
Privacy commitments in practical terms
The sections below explain how data is handled when Burz Suite CRM runs in Microsoft Azure.
Where data is stored
Burz Suite CRM runs in the customer's Azure subscription. Application data, records, and storage remain in the tenant chosen and administered by the customer.
Access boundaries and control
Access controls are configured in the customer environment. The developer does not receive automatic privileged access to CRM data. Any optional support access is explicit, time-limited, and customer-approved.
Telemetry and analytics
The product is built for controlled operation. Any diagnostics, monitoring, or telemetry pipelines are configured by the customer and remain inside customer-selected Azure services.
Cookies and tracking
Burz Suite CRM does not introduce marketing trackers by default. Session and security behavior depend on customer identity configuration and organizational policy settings.
Compliance and retention responsibility
Data retention, regional residency, and compliance operations are governed by customer tenancy policies. The developer provides the software platform and deployment guidance, while governance ownership remains with the customer organization.
Legal entity and contact
Burz Suite CRM is developed by the developer. Company and legal details are available on the Legal page. For privacy or deployment questions, use the support contact channel.
Need a privacy review for your deployment?
Burz Software can walk through data boundaries, operational controls, and Azure deployment architecture with your team.