The idea
Define the analytical purpose and collect only necessary attributes under an appropriate permission or legal basis. Access and retention should match that purpose. An analyst's ability to download a table does not automatically authorize every possible secondary use.
Worked example
A city-level order-volume report needs counts and city categories, not customer home addresses or passwords. Retaining identifiable raw data forever is not justified simply because it might be useful someday. Follow applicable policy and seek specialist advice when uncertain.
Try it
List fields for a fictional city-volume report. Remove those unnecessary for its purpose and define who needs access. Write a retention and deletion question for the responsible data owner rather than inventing a universal legal deadline.