Tag: GDPR

Load Application Insights in Power Pages only after consent: the SDK lifecycle, withdrawal, renewed consent and an important technical limitation.

Power Pages consent management connects consentmanager, web templates and React. Control external services separately and keep responsibilities clear.

Before launch, I reviewed my architecture for more than scaling. I also examined implicit security assumptions and found two small gaps that could quickly become costly in production.

I do not treat the choice of embedding model as an interchangeable environment variable. In Qdrant, it becomes part of every collection. Using different vector spaces locally and in production creates an expensive future migration.

A sequential await chain in the DELETE account endpoint means that if Qdrant fails, S3 data and the Zitadel identity remain. That is a GDPR Article 17 risk. The solution is Promise.allSettled with structured failure reporting. Alongside that: how batching prevents an OOM crash in the export endpoint.

Before going live, I read through the entire backend again. I found six concrete problems and fixed them all. Here is what I found, where I found it and why each issue mattered.