Security & Data Protection

Effective date: March 18, 2026

Dezi-Q is built to help medical device teams manage sensitive design-control and traceability work. That includes product requirements, risk files, specifications, FMEAs, post-market signals, and other engineering records that may contain valuable confidential information and intellectual property.

This page summarizes how Dezi-Q approaches customer data protection, access control, confidentiality, and operational safeguards.

Customer confidentiality and IP

Dezi-Q is intended to operate as a confidential engineering workspace. Customer medical device content is not sold, published, or transferred except as needed to operate the service, comply with law, or perform services requested by the customer.

Customer project content remains under customer control. Final released records and downstream quality records remain the customer's responsibility and may be stored in the customer's own repository, document control system, or QMS.

Workspace separation

Dezi-Q is designed with organization-scoped access boundaries so customer workspaces are separated by organization context. User accounts, projects, audit records, and collaboration features are associated to organization-level data boundaries within the application.

Within a customer workspace, project access can be restricted by user role and project-level permissions.

Access control

• Users authenticate with named accounts and role-based permissions.
• Project access can be limited to view or edit access depending on assigned permissions.
• Administrative actions are restricted to elevated roles.
• Active collaboration locks help reduce accidental overwrite during concurrent editing.

Application safeguards

• Password hashes are stored instead of plaintext passwords.
• Session handling is used to maintain authenticated access.
• Rate limiting is applied to API, login, admin, password recovery, and export endpoints.
• Security headers are used to reduce common browser-based attack exposure.
• Audit logging is used to record important system and workspace activity.

Operational data handling

Dezi-Q collects and retains only the account, workspace, and operational information needed to authenticate users, run collaboration workflows, preserve auditability, support exports, and maintain the service.

Where customer-specific deployment or hosting arrangements apply, additional operational and infrastructure safeguards may also be available based on the hosting environment and customer contract.

Security commitments and current posture

Dezi-Q is focused on practical application security, access control, and workspace accountability. At this stage, customers evaluating Dezi-Q for highly sensitive engineering IP should review deployment details, contractual terms, and available operational controls with Dezi-Q directly.

Dezi-Q does not represent on this page that it has completed any specific third-party certification, formal security audit, or compliance framework attestation unless separately stated in writing.

Customer responsibilities

• Assign roles and project access carefully.
• Control exported files and released records outside the platform.
• Use internal procedures for document approval, retention, and distribution.
• Evaluate whether additional contractual, deployment, or validation controls are required for the customer's specific environment.

Available on request

For customer evaluations, Dezi-Q can provide additional discussion around product access controls, deployment assumptions, confidentiality expectations, and security roadmap items as available.