> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/platform/guides/security-and-privacy-guide/security-and-privacy-guidelines-for-product-developers.md).

# Security & Privacy Guidelines For Product Developers

1. Secure Application Development
   * Adhere to Secure Coding Standards: Manual and Automated Code Reviews to ensure OWASP guidelines are followed for secure coding to prevent vulnerabilities.
   * Data Storage: Leverage Persister Service when storing data and Encryption Service to encrypt sensitive data before storage.
   * Data Anonymization: Anonymize PII before emitting data for analysis or reporting.
   * Third-Party Security Testing: Conduct 3rd security penetration testing and vulnerability assessments.
     * [Security and Vulnerability Testing Certificate](https://drive.google.com/file/d/1ziQPSTuKVoJ8bq7JfqeKU6Prmg2fuNRc/view)
2. Data Minimization: Collect and process only the data necessary for the functionality of the product.
   * Data Collection: Design forms to capture only such data from users that have well-defined purposes.
3. User Privacy
   * Purpose Limitation: Ensure users are informed about what data is collected, who will access the data and for what purpose. This information should be updated in the Terms and Conditions.
   * User Access: Provide citizens with the ability to view and request changes to their personal data, e.g. corrections in spelling of names, updating address, etc.
4. Notice and Consent
   * Create a privacy policy, which details what information is collected, which roles have access to it, and the purpose of such access / usage.
   * Publish a notice, with a link to the privacy policy, on the login page. Users should indicate that they have read and accepted these terms before they are able to login.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.digit.org/platform/guides/security-and-privacy-guide/security-and-privacy-guidelines-for-product-developers.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.