From 41ee4920f6b327db58e83906ed96818490352d78 Mon Sep 17 00:00:00 2001
From: fria <138676274+friadev@users.noreply.github.com>
Date: Tue, 2 Sep 2025 10:54:56 -0500
Subject: [PATCH] add quote about how they store personal data

---
 blog/posts/biometrics-abuses.md | 11 ++++++++++-
 1 file changed, 10 insertions(+), 1 deletion(-)

diff --git a/blog/posts/biometrics-abuses.md b/blog/posts/biometrics-abuses.md
index 32b6064a..66735fea 100644
--- a/blog/posts/biometrics-abuses.md
+++ b/blog/posts/biometrics-abuses.md
@@ -47,4 +47,13 @@ They also keep track of "customer history—previous purchases, preferences, and
 
 The tracking is stated to be used for marketing and anti-theft purposes. Since the system is AI-driven, hopefully it doesn't randomly decide you're a thief and sound the alarm on you.
 
-They also market age verification so customers don't have to flash their ID for things like alcohol purchases, but I'd rather show my ID for two seconds than have this permanent tracking 
\ No newline at end of file
+They also market age verification so customers don't have to flash their ID for things like alcohol purchases, but I'd rather show my ID for two seconds than have this permanent tracking profile kept of me.
+
+As for how the data is handled:
+
+> All sensitive personal information (including ID images and biometric data) is encrypted during transmission and while stored on our servers. This means your data is encoded so that only authorized systems with the proper keys can read it. For example, when your ID scan is sent to our server, it travels over an encrypted connection (HTTPS/TLS), and once stored, the file is encrypted at rest.
+
+So your data is not E2EE, they just use transport encryption and then separately encrypt it at rest, meaning they have access to any stored data and hackers have a nice juicy target to attack.
+
+### Target
+