Why we built EU-native time tracking (and what Schrems II has to do with it)
The Schrems II decision invalidated the EU‑US Privacy Shield, raising legal risks for transferring personal data to US processors. Cadensa was created to address this by offering a time‑tracking service hosted entirely on German infrastructure, ensuring GDPR compliance across all plans. The platform includes built‑in data‑subject rights such as deletion, portability, and a transparent data processing agreement.
- ▪The European Court of Justice's Schrems II ruling declared US surveillance laws incompatible with EU data protection standards, affecting SaaS providers with US ownership.
- ▪Cadensa runs on Hetzner Cloud in Frankfurt, a German company subject to German law and not the CLOUD Act, providing full EU data residency.
- ▪The service implements GDPR rights as core API functions, including a 7‑day reversible soft‑delete, hard‑delete across multiple databases, and data anonymization where required.
- ▪Cadensa’s architecture isolates each tenant in its own MongoDB database, preventing cross‑tenant data breaches despite higher operational costs.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 4003346) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Cadensa Posted on Jun 26 Why we built EU-native time tracking (and what Schrems II has to do with it) #sass #webdev #buildinpublic #gdpr In 2020, the Court of Justice of the European Union invalidated the EU–US Privacy Shield. The ruling — known as Schrems II — declared that US surveillance law makes it impossible for US companies to guarantee the privacy of EU citizens' data, even if that data is stored "in Europe." Most SaaS founders in the US probably shrugged.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
