⚖️Legal and Compliance
Legal, branding, and compliance requirements for FormSG deployments.
This document covers legal and compliance requirements you must follow when deciding to go to production with FormSG. Review these requirements as you progress through this guide.
🚫 Remove Singapore Government Branding 🇸🇬
FormSG is open source, but you must not use the official Singapore Government masthead or any associated branding in deployments outside authorized Singapore Government contexts.

What you can do is remove it completely, or replace it with your agency branding. Here's an example of an alternative masthead

Starting Removal Checklist
Frontend Components:
Environment Variables:
Singapore-Specific Services:
Verification Script:
This doesn't guarantee it will find every SG-tied code, but it's a decent simple starting script
# check frontend
grep -r -i \
"singapore\|gov\.sg\|VDP\|vulnerability.*report\|singpass\|corppass\
|myinfo\|masthead" \
frontend/src/ \
--exclude-dir={mocks,__tests__,__mocks__,assets} \
--exclude="*.{stories,test,spec}.{ts,tsx}" \
--exclude="*.svg" | nl
# also check backend
grep -r -i "gov\.sg\|singapore" backend/src/ \
--exclude-dir={__tests__,__mocks__} \
--exclude="*.{test,spec}.{ts,js}" \
It's basically a grep script that scans the codebase for occurrences of SG keywords. Here's a simple output as an example
# Example output
...
182 frontend/src//features/admin-form/preview/PreviewFormPage.tsx: <GovtMasthead />
183 frontend/.../EditMyInfoChildren.tsx:import { SINGPASS_FAQ } from '~constants/links'
189 frontend/.../EditEmail.stories.tsx: allowedEmailDomains: ['@open.gov.sg'],
...
Why This Matters
Using Singapore government branding without authorization could:
Mislead citizens about your service's legitimacy
Violate trademark laws
Result in legal action
What You MUST Do
If you fork or deploy FormSG:
Remove or replace the masthead in all templates and front-end code
Clearly indicate your deployment is not affiliated with the Singapore Government
Use your own branding and disclaimers
Open Source License Compliance
MIT License Requirements
FormSG is licensed under the MIT License, which for you means
✅ You CAN: Use commercially, modify, distribute, use privately
❌ You MUST: Include original license, maintain copyright notices
⚠️ You CANNOT: Use FormSG trademark without permission
Third-Party Dependencies
FormSG includes many open source dependencies with various licenses:
Dependency License Review
License Audit Script:
npx license-checker --summary --out licenses.txt
Disclaimer and Liability
FormSG Project Disclaimer
FormSG is provided "AS IS" under the MIT License. The original developers:
Provide no warranty or guarantee of fitness for purpose
Are not liable for damages from your use of the software
Do not provide commercial support or SLA guarantees
Your Deployment Responsibility
As the deploying organization, you are responsible for:
Security - Proper configuration and hardening
Compliance - Meeting all applicable laws and regulations
Support - Helping your users and maintaining documentation
Operations - Keeping the system running and updated
Recommended Legal Actions
Before deployment, confirm:
⚖️ Legal Principle: You are responsible for ensuring your FormSG deployment complies with applicable laws, regulations, and organizational policies in your jurisdiction.
Last updated
Was this helpful?