GDPR Compliance guidance for self hosted instance
Hi Team, we are planning to use a self-hosted ZITADEL in production. Are there any best practices or guidelines we can follow to ensure that our self-hosted ZITADEL is compliant with GDPR? We would like to focus on the technical aspects, such as which data should be anonymized, whether we should implement row-based or column-based encryption, and any other relevant considerations. Thank you
1 Reply
Hi @andrey, I'm an AI assistant for ZITADEL. While a team member reviews this question, I'll see if I can find relevant sources for your question.
Answer
I wasn't able to find a direct answer, here are some relevant sources:
1. [GDPR • ZITADEL | ZITADEL] (1) :
Outlines ZITADEL's GDPR compliance, technical and organizational measures, and provides links to the data processing agreement and privacy policy. 2. [Guidance to implement GDPR Compliance on self hosted instance] (2) :
Community discussion on GDPR for self-hosted ZITADEL, mentioning the importance of data subject rights and deletion/anonymization practices. To learn more, see the sources I considered: [1] GDPR • ZITADEL | ZITADEL [2] Guidance to implement GDPR Compliance on self hosted instance Feel free to tag @Ask Inkeep with additional questions.
Outlines ZITADEL's GDPR compliance, technical and organizational measures, and provides links to the data processing agreement and privacy policy. 2. [Guidance to implement GDPR Compliance on self hosted instance] (2) :
Community discussion on GDPR for self-hosted ZITADEL, mentioning the importance of data subject rights and deletion/anonymization practices. To learn more, see the sources I considered: [1] GDPR • ZITADEL | ZITADEL [2] Guidance to implement GDPR Compliance on self hosted instance Feel free to tag @Ask Inkeep with additional questions.