Privacy should be as inspectable as infrastructure.
This demo notice describes the data categories, purposes, disclosures, and retention approach that a production Devopsify deployment must make precise before launch.
Who this notice is for
This notice applies to visitors of the public website and people evaluating the Devopsify demo. In a production deployment, the organization operating the service will need to identify itself as the controller or determine its role contractually for each processing activity.
Data categories and why they are used
| Category | Examples | Purpose |
|---|---|---|
| Account and access | Email, login state, organization membership, roles | Create and secure a demo workspace, authenticate requests, and apply authorization. |
| Workspace data | Resource labels, topology relationships, policy results, audit events | Render the control-plane experience and preserve operational context within a tenant. |
| Technical data | Route, browser/device signals, timestamps, error and request metadata | Maintain availability, troubleshoot failures, prevent abuse, and improve the demo. |
| Support data | Message content, attachments, reproduction steps, contact details | Investigate requests and communicate about a reported issue. |
Do not place secrets, credentials, private keys, or unnecessary personal data in workspace fields, support messages, prompts, logs, or uploaded files.
Sources, sharing, and international use
Data may come directly from a visitor or user, from the browser and service runtime, or from integrations deliberately connected by an authorized operator. A production service may need to share data with hosting, authentication, monitoring, support, or infrastructure providers. This demo does not name production processors or promise a particular transfer mechanism; those details belong in the completed production notice and applicable agreements.
Retention and deletion
Data should be kept only for the time needed for the stated purpose, security, dispute handling, and legal obligations. The demo does not publish a production retention schedule. A production operator must document periods for account records, workspace and audit records, support correspondence, backups, and deletion propagation, then provide an appropriate deletion process.
For rights and deletion request guidance, see the GDPR and data rights page.
Changes and questions
Material changes should be posted with a revised effective date and, where required, communicated to affected users. This demo notice is informational and is not a substitute for a production privacy program or legal review.
For demo questions, use the contact page. The only listed mailbox is a demo-only placeholder.