> For the complete documentation index, see [llms.txt](https://guide.form.gov.sg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.form.gov.sg/introduction/what-data-can-formsg-handle.md).

# What data can FormSG handle?

The platform can handle security classification and info sensitivity as shown below:

<table data-header-hidden><thead><tr><th>Response data</th><th>Security Classification </th><th>Info Sensitivity</th><th data-hidden></th></tr></thead><tbody><tr><td><strong>Response Data</strong></td><td><strong>Security Classification</strong></td><td><strong>Info Sensitivity</strong></td><td>Stored in email inbox</td></tr><tr><td>Stored on FormSG database (GCC-OGP) encrypted and sent to admin's email inbox<br><br>Data residency in Singapore</td><td>up to <br><strong>Confidential (Cloud-Eligible)</strong></td><td>Up to <br><strong>Sensitive (High)</strong></td><td>up to <strong>Sensitive (High)</strong></td></tr></tbody></table>

FormSG systems have been endorsed with Medium-Risk RML, with the mandatory controls. WOG users may refer to the [Digital Governance platform](http://dgp.grc.tech.gov.sg/RSAarcher/apps/ArcherApp/Home.aspx) and look for FormSG (5745963). *You may also later refer to the* [*WOG IM8 portal*](http://portal.standards.tech.gov.sg/)*.*\
\
In addition, OGP/FormSG does not dictate who agencies' disclose such data to via the platform, as this is subject to the agency's operational considerations and own internal governance processes to implement the relevant IMs. Ensure that receiving systems can support the security classification and info sensitivity. The unauthorised disclosure of information can cause damage to an agency, business or individual. \
\
If you require further clarification, you may wish to approach your CDO or the Government's Data Office (i.e. GDO) at SNDGO, which oversees the various WOG IMs on data security, governance and sharing.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://guide.form.gov.sg/introduction/what-data-can-formsg-handle.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
