Security built into every layer of DeskOS.
Your members, your billing and your doors run on DeskOS. We protect them the way an enterprise expects: isolated tenants, encryption throughout, a permission check on every admin action, and independent penetration testing. DeskOS is ISO/IEC 27001:2022 certified.
- ISO/IEC 27001:2022 certified
- Encrypted in transit and at rest
- Isolated per organisation
- Independently penetration tested
What holds for every customer, every day.
How the platform treats your members’ records, your invoices and your access logs, whichever plan you are on.
Isolated by design
Every operator is a separate tenant, and every query is scoped to the organisation making it. One customer’s data is never reachable from another customer’s account.
Encrypted throughout
Data is encrypted in transit with TLS and at rest, on disk and in backups. Sessions run on short-lived tokens that rotate.
Least-privilege access
Every admin screen and every admin endpoint checks a permission code. Staff see only the locations they are assigned to, and financial figures are gated separately.
Payments kept off our servers
Card details go straight from your member to Razorpay or Stripe. Every payment is verified server side against the order we created before anything is marked paid.
Independently tested
An external team runs vulnerability assessment and penetration testing against the platform. Findings are fixed by severity and retested.
Monitored in production
Errors, failed jobs and unusual activity alert the engineers who run the platform the moment they happen.
Recoverable
Scheduled backups, regular restore tests, and recovery point and recovery time objectives set out in our disaster recovery report.
A full audit trail
Invoice edits, door access events and member activity are recorded with who did what and when.
Privacy by default
Member consent is recorded when your terms are accepted. Exports and deletion are available on request, and shared screens show the minimum personal data.
ISO/IEC 27001:2022 certified
Certificate 26MEQXD44 · Valid to 21 September 2029
The three documents a security review asks for.
The certificate downloads here. The penetration test and disaster recovery reports are shared under NDA with a named reviewer, because they describe our systems in detail.
- Public
ISO/IEC 27001:2022 certificate
The certificate of registration for our information security management system, issued after an independent audit of how we run, staff and review security.
- Certificate number, issue date and expiry
- The certified scope
- The surveillance audit schedule
Download PDFCertificate 26MEQXD44. Valid to 21 September 2029.
- On request
Penetration test report
The findings from our vulnerability assessment and penetration testing, with what was found, what severity it was rated and what we did about it.
- Scope of the test and the methodology behind it
- Findings by severity, with our remediation against each one
- Retest results for anything that was fixed
- The tester, the dates and the tooling
Request accessSent under NDA to a named reviewer, usually the same working day.
- On request
Disaster recovery report
How your data is backed up, how quickly it is restored, and the results of our latest restore test.
- Backup schedule, retention and where copies are held
- Recovery point and recovery time objectives
- The restore test, when it was run and what it measured
- Failover and the order things come back in
Request accessSent under NDA to a named reviewer, usually the same working day.
Every control, in one list.
For your security questionnaire. Each line is something you can confirm in your own account or in the documents above.
Your data
- Every operator is a separate tenant, scoped by organisation on every query
- Encrypted in transit with TLS, and at rest on disk and in backups
- Card details never touch our servers: payments go through Razorpay or Stripe
- Exports of your own data on request, in standard formats
- Data removed on request, subject to the tax retention your own law imposes
Who can see it
- Permission codes on every admin screen and every admin endpoint
- Staff access is per location, so a centre manager sees their own centre
- Financial figures are gated separately from the rest of the record
- Two factor authentication on our own internal administration
- Internal access granted on need and revoked when no longer required
Keeping it running
- Scheduled backups with regular restore tests
- Recovery point and recovery time objectives stated in the DR report
- Monitoring and alerting on production systems
- Changes reviewed before release, with a rollback for every deploy
- A published vulnerability disclosure policy and security contact
Bring your security questionnaire to the demo. We answer it on the call.
Tell us what your review needs.
The penetration test report, the disaster recovery report, a completed security questionnaire, a DPA, or an answer to one specific question. Say which in the last box and a person replies, usually the same working day.
- Answered by a named person, usually the same working day
- We sign your NDA if your side needs one first
- Reporting a vulnerability instead? Email bugbounty@deskos.net or read the bug bounty policy
Request security documents
A work email, so we know who is asking and where the documents are going.
A security review with people on the other end.
DeskOS is built and supported from offices in New Delhi and Delaware. The people who answer a security question are the people who wrote the code it is about.
What happens next
- 1
You ask for what your review needs
The certificate downloads from this page. For the penetration test or disaster recovery report, use the form above.
- 2
A person reads the request
We confirm who is asking, sign your NDA if you need one, and send the documents.
- 3
Your security team gets a real answer
If your questionnaire has a question these documents do not answer, we will answer it directly rather than pointing you back at a PDF.
What reviewers ask us
Is DeskOS ISO 27001 certified?
Yes. DeskOS is certified to ISO/IEC 27001:2022, certificate 26MEQXD44, valid to 21 September 2029. The certificate downloads from this page.
How is our data kept separate from other operators?
Every operator on DeskOS is its own tenant, and every query the application makes is scoped to the organisation making it. One operator’s members, invoices and access logs are never reachable from another operator’s account.
Who at DeskOS can see our data?
Only the people who need to, to support you or run the service. Internal access is granted on need and revoked when it is no longer required.
How do we control what our own staff can see?
Every admin screen and endpoint checks a permission code. You decide who can view or change each area, which locations each person can see, and whether they see financial figures at all.
Can we see your penetration test report?
Yes, on request and under NDA if your side needs one. We do not publish it, because it describes our systems in detail. Ask through the form on this page and a person sends it, usually the same working day.
What happens to our data if something goes badly wrong?
Backups are taken on a schedule and restores are tested regularly. The disaster recovery report states the backup schedule, the retention, the recovery point and recovery time objectives, and what the last restore test actually measured. It is available on request.
Where is our data held?
Your data is held with our cloud infrastructure provider, and the region is stated in your agreement. If you have a requirement to keep data inside a particular country, raise it before you sign and we will confirm whether we can meet it.
Do you handle card details?
No. Payments run through Razorpay or Stripe, and card details go from your member to the gateway without passing through DeskOS. We hold the result of the payment, not the instrument.
We found a vulnerability. Where do we send it?
To bugbounty@deskos.net. The reporting policy, what is in scope and what we ask you not to do is on our bug bounty page, linked at the foot of every page on this site. Reports are read by the engineers who can fix them.