Last updated: 29 October 2026
We treat your growth history as something worth protecting. This page summarises our engineering practices in plain terms. It is not a certification or a guarantee, but a real account of how we think about security at a small, early company.
01Our security philosophy
Security and privacy are the same idea from two angles: your data should be yours, and it should be safe while we hold it for you. We design onWard to collect as little as possible, keep your content on your device by default, and protect everything that does sync. Because we are a small team, security is everyone’s job here — not a silo.
02Data in transit and at rest
- All communication between the app, website and our servers uses modern TLS so nothing travels in the clear.
- Synced data is encrypted at rest on managed infrastructure in vetted regions.
- Secrets and credentials are stored in dedicated secret managers, never hard-coded or committed.
03Offline-first, on-device by default
onWard writes to your device first. If you use it without signing in, your content never leaves the device at all. Sync only happens when you are signed in and connected, and it is scoped to your own account — one person’s data is never mixed with or visible to another’s.
04Access controls and authentication
We follow least-privilege: staff and systems get only the access a task requires, and that access is reviewed. Sign-in is protected through secure, standard authentication, and we encourage strong, unique credentials for your account.
Production data access is logged. We do not hand your raw content to anyone inside the company without a clear, documented reason.
06Data portability and deletion
You can export your full history whenever you like and delete your account and content permanently. Deletions are honoured across our systems within 30 days, subject only to narrow legal-retention exceptions.
07How we operate
- Dependencies are kept updated and scanned for known vulnerabilities.
- Infrastructure is monitored, with alerts for suspicious activity.
- Backups are encrypted, tested for restore, and access-controlled.
- Security is part of how we build, not a step bolted on at release.
08Your part
A lot of security is shared. Please keep your password unique, enable any available device lock or verification, do not share your account, and treat your own share links like anything else you have published. Tell us immediately if you suspect your account is compromised.
09Report a vulnerability
Found a weakness? We want to know. Email security@gigslabs.example and we will acknowledge promptly and work with you.
Safe harbour: good-faith research on your own account, without disrupting others or exfiltrating data, will not lead to legal action against you. Please give us reasonable time to fix before disclosing publicly.
10Incident response
If a material breach affecting your data occurs, we will investigate, contain it, and notify affected users and any relevant authorities within the timelines the law requires — no slower than we would want to be told ourselves.
11Questions
For anything security-related, contact security@gigslabs.example. For how we handle data day-to-day, read our Privacy Policy.
Questions about this document?
Write to us and a human at GIGS Labs will read it.