Security & Safeguards · Company practice
Drive Content is encrypted at rest but, unlike Wire messaging, is not end-to-end encrypted
Drive Content is encrypted at rest using "industry-standard encryption mechanisms". Unlike Wire's end-to-end encrypted messaging, Wire Drive is not based on a client-side end-to-end encryption model. The schedule does not name the mechanisms used.
Supporting quotations
Drive Content is encrypted at rest using industry-standard encryption mechanisms.
Unlike Wire’s end-to-end encrypted messaging functionality, Wire Drive is not based on a client-side end-to-end encryption model.
Qualifications & exceptions
- The at-rest encryption statement covers Drive Content; file metadata is treated separately in section 2.3.
Not stated here
- The encryption mechanisms and who holds the keys are not described.
Security & Safeguards · Restriction or exception
Private cloud follows the Order Form; with on-prem, the Customer carries infrastructure security and retention
Where Drive runs in a dedicated private cloud, infrastructure isolation and hosting parameters are whatever the Order Form specifies. Where Drive is deployed on Customer-controlled infrastructure, the Customer is responsible for infrastructure security and data retention, Wire's access is limited to the agreed support and maintenance scope, and infrastructure-level compliance obligations remain with the Customer.
Supporting quotations
Where provided in a dedicated private cloud environment, infrastructure isolation and hosting parameters shall be as specified in the Order Form.
Where deployed on Customer-controlled infrastructure: (i) Customer is responsible for infrastructure security and data retention; (ii) Wire’s access is limited to agreed support and maintenance scope; and (iii) infrastructure-level compliance obligations remain with Customer.
Qualifications & exceptions
- Each rule applies only to its own deployment model and does not describe Wire's public cloud.
Not stated here
- The Order Form terms for private cloud, and the agreed support and maintenance scope for on-prem, are not in this document.
Security & Safeguards · Permission or license
Wire may suspend, stop sharing of or remove access to specific content where law or security requires
Wire reserves the right to suspend access to, disable sharing of, or remove access to specific Drive Content where required by law or where reasonably necessary to protect the security or integrity of the service.
Supporting quotations
Wire reserves the right to suspend access to, disable sharing of, or remove access to specific Drive Content where required by law or where reasonably necessary to protect the security or integrity of the Service.
Qualifications & exceptions
- Limited to two triggers: required by law, or reasonably necessary to protect security or integrity.
- Aimed at "specific Drive Content", not stated to cover a whole account.
Not stated here
- The heading is "Suspension/Removal and Preservation", but the clause states no preservation rule.
- The clause does not say whether Wire tells the Customer before or after acting.
Security & Safeguards · Permission or license
Wire may use automated security measures that block, quarantine or restrict risky files
Wire may implement automated security measures, including malware scanning. It may automatically block, quarantine or restrict access to Drive Content that it reasonably identifies as posing a security risk.
Supporting quotations
Wire may implement automated security measures, including malware scanning, and may automatically block, quarantine, or restrict access to Drive Content reasonably identified as posing a security risk.
Qualifications & exceptions
- Applies to Drive Content "reasonably identified as posing a security risk".
- Malware scanning is given as one example of the measures ("including").
Not stated here
- The text does not say how the Customer is told of an automated block or how to challenge it.