# A client's file spawns copies you cannot promise to delete

> Paid Slack keeps data for the life of the workspace by default, so a copy tracker helps FDEs promise to delete only what they actually control.

Original: https://fdetimes.net/en/guides/client-data-copies-deletion-tracking/

On the third day of the engagement, the client emails you the file `customer_export_full.csv` with a single line: "so you can look at the real data". That afternoon, one of the client's engineers posts an updated version to the Slack Connect channel the two sides share.

You download both to your laptop, push them to a test bucket and run a notebook. Each step has a reason; everyone wants to move fast.

Now count how many places that dataset lives: your inbox, the inboxes of everyone on cc, the Slack channel, your Downloads folder, the bucket, and possibly the notebook's output. Three months later, when the project ends or the client asks "have you deleted our data?", could you answer?

For an FDE, this is not a matter for the legal team alone. You received the file, so you are also the person who knows best where the copies are. Rules for receiving, storing and deleting data belong in the first week, while the copies are still few.

## How many copies does one client file create?

Treat every file a client sends as a set of copies, each governed by its own deletion rules. The difficulty is that the rules differ from place to place, and most of them are not in your hands.

Slack is the clearest example. Slack's help documentation states that on paid plans, data is kept for the life of the workspace by default.

Retention settings apply to all messages, files, canvases and lists, but only if an administrator deliberately sets a period. If nobody does, that CSV will still be there long after the contract expires.

You are usually not the person who holds that setting either. So the first question to ask is who in your company administers Slack retention.

Slack Connect is messier still. According to Slack, your organisation's retention settings apply only to content sent by your own people; content that outsiders post to a shared channel is kept or deleted under their organisation's policy. The update the client's engineer posted is therefore beyond your power to delete.

Email is not simple either. With Google Vault, retention rules keep data even after users delete messages or empty the bin, and holds take precedence over rules.

Data is purged from Google's systems only when the last applicable rule has expired. So do not tell the client "it's all deleted" just because you pressed delete in your inbox.

## Retention periods need an owner

Guidance from the ICO, the UK's data protection regulator, is blunt: personal data must not be kept longer than needed. Organisations need a policy setting standard retention periods wherever possible, and should periodically review the data they hold to delete or anonymise what is no longer needed.

Article 5(1)(e) of the GDPR sets a similar requirement: data that identifies a person may be kept no longer than necessary for the purposes of processing. The `old_exports/` folder on many FDEs' laptops, kept in case it comes in handy one day, sits uneasily with that principle.

The ICO's data minimisation principle goes further: do not hold more than you need for the stated purpose. If the problem is inventory forecasting, there is no reason for a customer phone-number column to be in the file.

**Key point:** Before you open a client's file, know how many copies it will create and who deletes each one.

## Example: a tracker for the day-three CSV

Back to `customer_export_full.csv`. Instead of opening it straight away, spend ten minutes logging it in a data tracker. The tracker can be nothing more than a spreadsheet shared with the client, but each row corresponds to a copy, not a file.

| Copy | Location | Purpose | Who can delete it | Delete by | How to confirm |
|---|---|---|---|---|---|
| Original email + attachment | Company Gmail | First receipt | Workspace admin (check Vault rules and holds) | Immediately after moving to the bucket | Ask the admin which rules still apply |
| Updated version | Slack Connect channel | Second receipt | Client organisation | Under the client's policy | Ask the client's admin |
| Downloaded copy | Laptop, Downloads folder | Temporary | You | End of the day received | Check yourself |
| Column-trimmed copy | Test bucket | Inventory forecasting | You + team | End of engagement | Log the deletion, send to client |

The "Who can delete it" column matters most. It forces you to admit that the second row is not yours to control. The right move is to tell the client that this copy falls under their own retention policy.

Then send the client a short message to settle the rule for next time. A template:

> "So that your data doesn't end up scattered across many places, from now on please send it through [one agreed channel], containing only the columns [list]. We will log each file in the shared tracker with a deletion date, and send confirmation once it has been deleted."

The message shows the client you take this seriously, and it heads off the next round of emailed attachments.

## Five steps from the first week

1. Agree on a single channel before the client sends the first file, and record it in the kickoff notes.
2. Ask the client only for the columns the project's purpose requires, in the spirit of data minimisation.
3. Log every copy in the tracker as soon as it appears, including temporary copies on laptops.
4. Ask your company's Slack and Workspace admins three questions: what the current retention period is, who can change it, and whether any hold applies to the team's mailboxes.
5. Schedule a periodic review, say every two weeks, to delete expired rows and record the deletion date.

When the engagement ends and drives or servers need to be decommissioned, device-level erasure has its own guidance. NIST SP 800-88 Rev. 2 recommends establishing a media sanitisation programme with appropriate techniques and controls. Point your IT team to that document rather than inventing your own erasure method.

## The mistakes that cost FDEs a client's trust

The most dangerous mistake comes from people with good intentions: an engineer who wants to tidy up and shortens Slack's retention period on their own initiative.

Slack warns that data deleted under retention settings is gone permanently, and the deletion job runs once a day. Changing a single number can wipe out conversation history that other teams still need.

The second mistake is forgetting backups. The ICO notes that copies in backup systems may not be overwritten immediately, and the essential point is to put that data beyond use. A deletion promise to a client must therefore account for those copies too.

The third mistake is promising to delete data the client sent through Slack Connect, which you do not control. The fourth is reporting "deleted" while mail is still retained by a Vault rule or a hold.

These mistakes share one trait: the promise exceeds what you control. The tracker shows clearly which parts are yours, so you promise only those.

## How to put this skill on your CV

If you have worked with real client data, do not just write "security-conscious". A specific line such as "set up a client data intake and deletion process for an engagement, with a copy tracker and deletion confirmation at handover" shows an employer how carefully you handle that data.

In interviews, when asked "what do you do when a client emails you a sensitive file?", answer in order: copies, deletion rights, retention period, confirmation. Answering that way shows the interviewer you know exactly what you can and cannot promise a client.

Do not wait for a security meeting to deal with this. Have the six-column tracker ready before the first file lands in your inbox.

**Try this week:**

- Find every file clients have sent you in the past 30 days, and log each copy in a tracker: location, purpose, who can delete it and the deletion date
- Ask your company's Slack admin what the current retention period is and who can change it
- Send the client a short message agreeing on a single channel for transferring data from now on

## Sources

- [Customize data retention in Slack](https://slack.com/help/articles/203457187)

- [How data management features apply to Slack Connect](https://slack.com/help/articles/115004152843-How-data-management-features-apply-to-Slack-Connect)

- [Principle (e): Storage limitation | ICO](https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/data-protection-principles/a-guide-to-the-data-protection-principles/storage-limitation/?reqp=1)

- [Principle (c): Data minimisation | ICO](https://ico.org.uk/for-organisations/guide-to-data-protection/guide-to-the-general-data-protection-regulation-gdpr/principles/data-minimisation)

- [How retention works | Google Vault | Google Workspace Help](https://knowledge.workspace.google.com/vault/retention/how-retention-works)

- [Right to erasure | ICO](https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/individual-rights/individual-rights/right-to-erasure/)

- [NIST SP 800-88 Rev. 2, Guidelines for Media Sanitization](https://csrc.nist.gov/pubs/sp/800/88/r2/final)

- [Art. 5 GDPR – Principles relating to processing of personal data](https://gdpr-info.eu/art-5-gdpr/)
