Your firmware is your product. Here is how we protect it
Before you upload a firmware image, you need to know who can see it and what happens to it. Two-step sign-in for everyone, each organisation kept apart in the database, and an audit log the app cannot change. Your data is hosted in India, unless your contract sets another location.
Who can see your firmware, and what happens to it
Only your people get in
Two steps for every account, on every way in.
- An authenticator code after a password, Google Workspace, Microsoft 365 or single sign-on
- Passwords of 12 characters or more, stored as Argon2id hashes
- Five failed attempts lock sign-in for 30 minutes
No other customer sees your data
Each organisation sees only its own data.
- Row level security on every customer table
- Random UUIDs for every public id
- No ids or data in page addresses
Your tokens and keys stay sealed
What you connect is sealed and never shown again.
- Tokens and keys sealed with envelope encryption
- Uploads go straight to storage through a size-locked link
PlannedTLS on every connection and managed keys at rest, rotated automatically.
Your firmware is never run
Nothing from your firmware or code is ever run.
- Archive bombs refused and links kept inside the tree
- Fixed time and size budgets for every analysis
- Every result checked against its schema
PlannedEach analysis on a fresh machine with no route to the internet.
AI only if you turn it on
Off until your admin connects a provider.
- Only the masked snippets a task needs are sent
- Every output labelled with its model
- Your data never trains any model
Every action on record
Every sign-in, change and decision is recorded.
- Person, action, target, time and country
- Append only, each row chained by SHA-256
- Export as CSV from Settings
Your security team will ask where your data lives and who processes it. The answers are there.
You decide how long we keep it
Owners and admins choose how long firmware images, source code, reports, the audit log and closed risks are kept, under Settings, Organisation. Everything else is fixed.
| Data | Default | Choices |
|---|---|---|
| Firmware images | 1 year | 30 days to 10 years |
| Source code | Deleted after each scan | Kept 30 days to 10 years if you choose |
| Reports | 10 years | 1 to 10 years |
| Audit log | 2 years | 1 to 10 years |
| Results | While the organisation exists | Until you delete their release or product |
| Risk decisions | While the organisation exists | Closed risks 1 to 10 years |
| Deleted products, releases, repositories and reports | 14 days in Recently deleted | Fixed |
| Data exports | 7 days | Fixed |
| Webhook records | 30 days | Fixed |
Deleted something by mistake? An owner or admin restores a deleted product, release, repository or report from Settings, Data and privacy, Recently deleted, for 14 days. After that an owner can ask our support team to try a restore from backups while they last; we try, without a guarantee.
Retention you set, and erasing an account or an organisation, are final: that data is never restored.
PlannedBackups of the database and the files for 14 days in India, then expired.
For your security review
The Information Security Addendum sets out these controls in full. MAGDOX has no ISO 27001 certificate or SOC 2 report today; for a security review, write to security@magdox.io and we answer your questionnaire.
Found a vulnerability?
Tell us privately. The responsible disclosure policy says what you may test and how we respond, and its hall of fame credits qualifying reports.