Dbusiness
Data privacy
Data privacy in file transfer is the set of duties that apply when the file contains personal data: collect only what the transfer needs, restrict who can fetch it, keep it only as long as the purpose requires, and protect it in transit and at rest.
GDPR Article 5 states those principles for personal data. NIST SP 800-122 is the confidentiality guide for personally identifiable information. This page is not a privacy-law survey. It is what those duties do to a transfer job.
A file move multiplies copies. The sender's disk, the object store, the CDN edge, the recipient's downloads folder, and the backup each hold the same names and account numbers. A privacy review that only checks the bucket misses four of them. Minimization means not attaching the whole payroll extract when the partner needed one column. Storage limitation means a lifecycle rule that deletes the object, not only a link that expires and leaves the bytes billed.
A clinic sends a 40 MB records PDF to a specialist. HTTPS covers the upload. The bucket encrypts at rest. The link is private to the specialist's account and expires in 72 hours. The lifecycle deletes the object after 14 days. The access log shows one completed download. That set matches the transfer duties. The same clinic emailing the PDF to a shared inbox, with the file then synced to three laptops, has no expiry and no single revoke. Encryption in transit on the mail hop did not fix the extra copies. Residency is adjacent: Article 44-style transfer limits say where personal data may go. Privacy here also says whether it should have been sent at all.
Access control is the who. Privacy adds the why and the how long. A public link to a file of customer names fails both.
Related
Sources
- GDPR Article 5, principles relating to processing
Purpose limit, minimization, and storage limitation on personal data
- NIST SP 800-122, Guide to Protecting the Confidentiality of PII
Confidentiality controls for personally identifiable information