TrackView Privacy Statement and Liability Waiver
1. Privacy Statement
data practices described in this Privacy Statement.
1.1 Scope of the Application
The Application is installed within your Azure subscription. All operational data
processed by the Application remains inside your environment unless explicitly
configured by you to be transmitted externally.
This Privacy Statement applies specifically to:
- The Application’s behavior and data handling
- Any diagnostic or operational data optionally sent to us
- Support interactions initiated by the Customer
1.2 Data Collected
1.2.1 Data Stored in the Customer’s Environment
The Application may process the following types of data within your Azure
subscription:
- Configuration data required for deployment
- Logs generated by the Application
- Operational metadata (e.g., resource names, environment parameters)
- Any customer data explicitly connected to the Application’s functionality
All such data remains fully under Customer ownership and control.
1.2.2 Data Transmitted to Techno Management
By default, the Application does not transmit any data to us.
Only the following data may be collected, and only if the Customer explicitly opts in:
- Error logs or diagnostic reports voluntarily submitted
- Support-related information shared during troubleshooting
- Telemetry (if enabled), such as feature usage statistics or performance data
1.3 Purpose of Data Use
Data collected may be used for:
- Delivering technical support
- Troubleshooting issues and improving reliability
- Enhancing Application performance and functionality
- Identifying usage patterns (if telemetry is enabled)
Data We do NOT:
- Access your environment without authorization
- Sell personal or operational data
- Use Customer data for marketing
1.4 Storage and Security
For any Customer data transmitted to us:
- It is stored in secure, access-controlled systems
- Access is restricted to authorized personnel
- Industry-standard security controls are applied
Data stored within your own Azure subscription is governed by your organization’s security and compliance standards.
1.5 Data Retention
We retain collected data only for as long as necessary to:
- Provide support
- Resolve issues
- Comply with legal or operational requirements
Support-related data may be deleted upon Customer request.
1.6 Customer Control and Access
You maintain full control over:
- All data residing in your Azure environment
- Telemetry or diagnostic data-sharing settings
- Whether and when to provide logs or troubleshooting information
1.7 Third-Party Services
- Your Azure subscription
- Microsoft’s privacy and compliance policies
We do not share Customer data with third parties except when required by law.
1.8 Compliance
Our data handling practices are designed to align with:
- GDPR
- Microsoft Commercial Marketplace requirements 3. Industry best practices for cloud privacy
If required, we can provide additional compliance documents or DPAs upon request.
1.9 Contact Information
Techno Management
contact@techno-management.com
https://techno-management.com/track-view
1.10Updates to This Privacy Statement
2. Liability Waiver
2.1 Purpose of the Liability Waiver
2.2 Scope
2.3 Customer Responsibilities
– Managing their Azure subscription, costs, configurations, networking, and security.
– Maintaining proper Azure resource configurations.
– Performing data backups and implementing retention policies.
– Following Vendor-recommended operational and security best practices.
2.4 Vendor Responsibilities
– Delivering the application package through the Azure Marketplace.
– Ensuring deployment succeeds when Azure resources are correctly provisioned.
– Providing documentation and best‑practice recommendations.
– Support as per published support guidelines.
2.5 Waiver of Liability
2.5.1 Data Loss
– Loss, corruption, or alteration of Customer data.
– Data deletion caused by Customer actions or integrations. – Issues caused by insufficient backup or retention settings.
2.5.2 System Unavailability
– Azure service outages.
– Customer misconfigurations.
– Third‑party system dependencies or failures. – Force majeure events.
2.5.3 Security Breaches
– Breaches caused by Customer-managed Azure settings.
– Weak credentials or compromised identities.
– Malware or malicious scripts introduced through Customer systems.
2.5.4 Other Situations Beyond Vendor Control
– Azure cost overruns.
– Performance issues due to insufficient resource sizing.
– API throttling by Azure or third parties.
