Skip to content
FeaturesPricingAffiliateBlogHelpAboutContact
Get StartedSign In
Back to Blog
industry2026-05-238 min read

I deleted my account three months ago, and 1,200 customers' phone numbers are still in the database — GDPR Art. 17's silent gap: the erase-user wipe set

Joana (38), owner of "Bairro do Mar" seafood restaurant in Lisbon, deleted her thMenu account. Three months later her old POS provider sent her a CSV of 1,247 loyalty members' phones + emails — she froze. Forensic: handler wiped only 8 D1_OPS + 5 D1_SOCIAL tables; 30+ others (loyalty_members, customer_profiles, pos_connections, allergen_incidents, etc.) + R2 images survived. PR #611 batch DDD F1: canonical `erase-tables.ts` whitelist + paginated R2 sweep + structured per-table warn. GDPR Article 4(7) controller liability angle.

th

thMenu Team

thmenu.com

Found this helpful? Share it.

Related articles

✦📈
industry

Why Digital Menus Increase Restaurant Revenue by Up to 30%

Studies show restaurants using digital QR menus see measurable increases in aver…

✦🔻
industry

When a Customer Downgrades, What Happens to Old Features? — The Silent Feature-Drift Problem in SaaS

Most SaaS apps run a single line of code when a customer downgrades — but old fe…

✦🛡️
industry

JWT alg-confusion attack — why Supabase's HS256 → RS256/JWKS migration breaks legacy verifiers

Verifiers that never decode the JWT header are wide open to `alg=none` and alg-c…