sayed.developer
Region: AT
Sunday 23 August 2026 15:32:50 GMT
130769
8344
226
302
Music
Download
Comments
plexigras :
rookie mistake, no backup = no problem
2026-08-23 19:31:12
1604
tool2k :
Complete nonsense. 30 days retention is completely okay according to GDPR if part of a documented concept.
2026-08-24 02:29:58
95
Willow Binx :
Very cool concept, and GDPR compliant! Gotta store that in the back of my noodle.
2026-08-25 22:51:53
0
Jerry Rapp :
It is a clever method but having timed backups of gdpr protected data is specifically allowed. The European Data Protection Board has specifically mentioned that erasing disaster recovery data can be an undue burden. You will not get fined for this as long as you have proper documentation and aren't keeping backups forever.
2026-08-24 06:41:18
25
Professor Farnsworth :
30 Day data retention is absolutely fine. You just have to make sure you remove the data again if you restore any backups and it will naturally disappear.
2026-08-23 18:40:55
98
Luffy :
just use 30 day grace period
2026-08-23 16:34:08
152
Bort LeBort :
It is GDPR compliant, because they have 30 days to provide proof your data is deleted, and after 30 days there is no data left.
2026-08-23 22:01:13
84
Simp :
How do you backup encryption keys then?
2026-08-23 17:39:39
6
Lex :
Yes until we get that quantum computer and all their backed up data is once again accessible
2026-08-23 18:25:03
17
X :
List all the companies who have been fined for this reason only?
2026-08-24 07:37:00
8
gatesofshawn :
but you also have to backup the key otherwise if you lose it the backup is worthless
2026-08-23 18:46:12
22
Ceo Dexie :
And then how do you delete the key from the backups?
2026-08-24 03:49:07
5
SAM :
where do you store keys?
2026-08-23 21:17:10
5
ohzrdddd :
No need for all this mambo jambo. If backup rotation is less than 30days all data will be erased before
2026-08-25 00:43:17
7
google_prepper :
And when quantum computing suddenly destroys current encryption methods everyone is non compliant
2026-08-23 18:57:20
7
Katapata :
Encryption keys become single point of failure. Been there - cried on that. Imagine one service goes wrong and used multiple encryption keys for same user 💀
2026-08-23 23:34:36
6
Marcel :
Common procedure is to just leave it in the backups until it got wiped by rotation
2026-08-23 23:19:55
11
. :
❌ Auditors ✅ Editors
2026-08-24 12:17:06
6
katlimruiz :
Optimizing the delete side, sounds good. But now the reads are too slow, and i cannot run a report across many users.
2026-08-23 20:38:45
5
Jamie 🍉 :
auditors, not editors
2026-08-23 18:20:47
6
32.8oz :
This doesn’t sound scalable at all
2026-08-25 15:21:47
2
Aidy :
"What's that ma'am? You don't have your account number to hand, can we not just search for your name? No, personal data can't be searched because we took advice from tiktok"
2026-08-24 00:02:01
1
SwiftPunk :
But then you would end up with dead data! How you want get ride of them? If deleting user data is expensive! Then you would carry dead data for ever!
2026-08-23 21:14:09
2
ステファノ (Stefano) :
How do your search on encrypted data? Let’s assume you will encrypt every user with their own key. Now you need to do a query like SELECT all people with age more than 20. Data are encrypted so you can’t do the query on the database… will you download the entire database and decrypt everything to search?
2026-08-24 01:26:58
5
j0hn_char :
im confused.. doesn't that destroy the whole reason for having a backup?
2026-08-23 23:33:02
1
To see more videos from user @sayed.developer, please go to the Tikwm
homepage.
