Trust & Security
Here’s what we actually do today
InvoiceSG is a solo-founder operation run from Singapore. This page is the plain-English version of what we actually do today to protect your data — not a wishlist. If we don’t have something yet, it’s in the “gaps” section below. For the contract side (Terms, privacy rights, subprocessor list), see /legal.
Last reviewed: 2026-10-24
How we protect your data
Six things we actually do today. Each one maps to a policy doc or a file in the repo — if we couldn’t point at code, we cut the bullet.
- Encrypted in transit. TLS 1.2+ on every request, with HSTS preload submission planned before public launch. Served via our Cloudflare proxy.
- Encrypted at restwhere our providers support it — our self-hosted Postgres (Supabase stack) in Singapore and Cloudflare R2 object storage.
- Two-factor authentication. TOTP is required for every owner and admin role, enforced by our middleware. New admins get a 14-day onboarding grace window; after that, team and company settings are locked until TOTP is set up. Works with Google Authenticator, Authy, or 1Password.
- Audit log. Every security-sensitive action (login, 2FA change, role change, API token events, sudo elevation) is written with IP, user-agent, and outcome. We keep them for 2 years, then an automated purge.
- Daily database backupwith an automated restore drill every quarter. If a backup doesn’t restore cleanly, we know before we need it.
- Sudo-mode re-auth on sensitive actions (team changes, data export, security settings). A fresh TOTP code is required even inside a valid session, and the elevated window expires after 5 minutes.
Data retention
Different data has different retention periods, mostly dictated by Singapore law. A three-row summary:
| Data category | Retention | Why |
|---|---|---|
| Financial records | 5 years minimum after tax year end | IRAS Income Tax Act + GST Act |
| Personal data | Until you delete your account; 30-day anonymisation on erasure request | PDPA Section 25 |
| Security audit log | 2 years | Automated purge; balances investigability against data-minimisation |
The full retention schedule (account data, email logs, backups, support conversations) lives in our Privacy Policy.
Who else touches your data
We use a small number of cloud subprocessors for things we can’t reasonably run ourselves — regulated payments, global CDN, job scheduling. The full list, what each one sees, and where they’re based is on /legal § Privacy Policy. We keep one source of truth and link to it here so this page stays in sync when the list changes.
What we don’t have yet
We’d rather say “not yet” than fake it. Here’s what isn’t true about us yet:
- Certifications: none today.Cyber Essentials (SS 712:2025) is in preparation; Data Protection Trustmark (SS 714:2025) is deferred to 2027. We’ll add the mark here the day it’s issued — not before.
- External penetration test: planned for post-incorporation, 2026 H2. None today.
- Off-site backup replication: our daily dumps live on the k3s node. A nightly sync to Cloudflare R2 is planned. Our Backup Policy lists this as a disclosed gap.
- SIEM / centralized logging: we rely on direct log greps today. Not on the roadmap yet.
Report a security issue
Found a security issue? Tell us. We won’t call the police on good-faith researchers.
- Email: [email protected].
- Scope:invoices.sg and *.invoices.sg only. Subprocessor domains (stripe.com, cloudflare.com, airwallex.com) are out of scope — report those to the subprocessor directly.
- Safe harbour:good-faith research under this policy is not reported to law enforcement. Please don’t access customer data, don’t publicly disclose before we fix, and give us 90 days to respond.
Our security.txt (RFC 9116) is at /.well-known/security.txt.
Our policies
We maintain six short internal policy documents. They’re quarterly-reviewed and available on request under a light non-disclosure — email [email protected] and we’ll send a PDF copy.
- Incident Response Runbook— PDPC 72-hour notification path, 4-phase response.
- Access Control Policy— role matrix, quarterly MFA access review.
- Data Retention Policy— IRAS 5-year retention + PDPA Section 25.
- Password Policy— Supabase auth + TOTP enforcement + sudo mode.
- Backup Policy— daily dumps plus a quarterly restore drill.
- Change Management Policy —
prisma migrate deploy, rollback within 15 minutes.
Every policy is quarterly-reviewed. Last reviewed: 2026-10-24 · Next review: 2027-01-01.
If anything on this page seems vague, tell me — vague is a bug.