Submission guidelines
We are accepting case study talks on the following topics:
- Architecture:
- REST API design for Personally Identifiable Information (PII).
- Libraries used. For e.g., how Twilio does PII compliance where fields are marked as privacy sensitive or not.
- Data collection patterns.
- Data science aspects of data management including anonymization, masking, etc.
- Development practices and precautions that are privacy-centric.
-
Engineering and operations processes, including DevOps, and hand-off points from check-in to release; multiple processes that every functional team has to follow for compliance.
-
Design and UX - if you are doing privacy-first development, how are you doing design, in terms of:
- What is the data that is collected?
- How is the data collected?
- Design and UX of consent management practices.
- What is the design language and templates you have evolved that will help other practitioners to learn from? For e.g., use of dark patterns.
- Reusable libraries, design language, design templates.
- Process case studies:
- How compliance is done, with emphasis on organization structure, how teams communicate, cost (budget), and why this approach is justified.
- Cross-functional and cross-geography compliance done by SaaS companies. For example, data privacy in Distributed Cloud environments i.e., data moving between data centres for multi region setups; what laws apply?
- Incident reporting processes and practices; dealing with data vulnerabilities and security-related threats.
Apart from large-scale internet organizations, we encourage fintech and next generation startups to submit case studies.
Content can be submitted in the form of:
- 15 minute talks
- 30 minute talks
- 1,000 word written articles
All content will be peer-reviewed by practitioners from industry.
Make a submission
Submissions close 22 Apr 2021, 11:45 PM
