Published: July 1, 2026

Our Commitment to Transparency

Drive. is committed to being transparent about how we handle government and law enforcement requests for user data. Because of our zero-knowledge architecture, we cannot provide file content — even if legally compelled. This report details all requests received and how we responded.

Government Requests for User Data

Request Type Received Complied Period
Subpoenas 3 2 H1 2026
Court orders (2703(d)) 1 1 H1 2026
Search warrants 0 0 H1 2026
National security letters 0 0 H1 2026
International requests (MLAT) 0 0 H1 2026

Data We Could Provide

In the cases where we complied with legal requests, the information provided was limited to basic account metadata — account creation date, last login timestamp, and device type. In all cases:

User Notification

We notify users when their information has been requested, unless prohibited by law. In H1 2026:

Content Removal Requests

Request Type Received Action Taken
DMCA takedown notices 2 1 warning issued to user; 1 rejected (no valid copyright claim)
Reported content (AUP violations) 27 12 warnings, 4 suspensions, 2 permanent bans, 9 dismissed
CSAM reports 0 N/A — reported to NCMEC if detected

Security Incidents

Incident Type Count Status
Data breaches 0
Unauthorized access attempts (blocked) 1,847 All blocked by rate limiting and WAF
Account takeover attempts (blocked) 23 All blocked by device binding and risk detection
Vulnerability reports (H1 2026) 8 2 confirmed (low severity), 6 dismissed

Uptime & Availability

Contact

Questions about this report? Email transparency@drivedot.cloud