I Asked 100 Companies for My Data — and Some Deleted It Instead

A privacy test across 100 companies found that data requests often ran into confusion, dead ends, and unexpected outcomes. The results matter for anyone building products that handle personal data, because request workflows can fail in ways that frustrate users and complicate compliance.

A recent privacy test of 100 companies found that asking for personal data can still be a messy process. According to the source summary, the requests often led to confusion and dead ends, and in some cases companies deleted the data instead of simply providing it.

That result highlights a practical problem for both users and software teams: data-access and deletion flows are not always clear, reliable, or well-implemented. For developers, this is a reminder that privacy requests are not just a policy checkbox. They are operational workflows that need to be designed, tested, and supported carefully.

Why does this matter? Because companies increasingly handle sensitive personal data, and users expect a straightforward way to see what is held about them. If a request process is confusing or breaks down, it can erode trust and create compliance risk. If a company deletes data when a user asked to access it, that suggests the system may not be matching the request type correctly or handling edge cases well.

The takeaway from this test is simple: privacy tooling and request handling need to work consistently at scale. For software developers and product teams, that means building clearer request paths, better verification, and safeguards to make sure users get the response they asked for.

Source: Ars Technica