Security & compliance
How we keep your data
honestly safe
The boring truth about CloudNx's security posture — what we do today, what we'll do soon, and the certifications we don't have yet. Written for your CISO and CA to read and forward.
Indian data residency
Everything runs in India (Mumbai), in an ISO 27001-certified data centre (the operator's certification, not ours). Your data stays in India.
TLS 1.2+ everywhere, AES-256-GCM secrets
Every endpoint enforces TLS 1.2 or better, 1.3 preferred. Access keys and TOTP seeds are AES-256-GCM encrypted. Full-disk encryption and customer-managed keys are not shipped yet.
Append-only audit log
Every state-changing request logged with actor, IP, path, status. Edits and deletes are rejected by the database itself. Visible to your account owner.
Backed up nightly
VM disks and the database are backed up every night, in India. There is no off-site copy yet, and we say so rather than imply one.
Data residency
Customer data — VMs, block volumes, S3-compatible objects, database backups — sits on dedicated bare-metal hardware in ISO 27001-certified, GDPR-compliant facilities — that certification is the data centre operator's, not ours; see “Certifications” below. It all runs in our India (Mumbai) region, so your data stays in India.
Compute, storage and backups all stay in that region. If your residency obligations need more detail, see contact.
Encryption
In transit:TLS 1.2+ (1.3 preferred) on every customer-facing endpoint (portal, API, S3, mail). Certificates issued by Let's Encrypt, auto-renewed by certbot, monitored by Prometheus.
At rest: Secrets are encrypted at the application layer with AES-256-GCM — IAM access-key secrets, TOTP seeds, and customer-supplied service credentials. Passwords are bcrypt (cost 12), rehashed on login.
What we do not yet do: host disks are not full-disk encrypted, and database backups are not separately encrypted before leaving the host. If your threat model requires encryption at rest for the underlying block storage, we are not there yet — tell us and we will give you a date rather than a claim. Customer-managed keys (KMS) are on the roadmap; the design uses AES-256-GCM envelope encryption with the root key escrowed offline.
Audit logs
Every state-changing HTTP request across the auth, compute, and storage services is logged to an append-only audit_logstable — actor user_id, account_id, service, method, path, status, IP, user-agent, request-ID, duration. GET/HEAD/OPTIONS, /healthz, and /metrics are skipped by design.
Append-only, enforced by the database. UPDATE, DELETE and TRUNCATE on the audit table are rejected by trigger, so a row cannot be edited or removed after it is written — including by our own application. To be precise about the guarantee: a database superuser could disable that trigger, so this is tamper-evident, not WORM. We do not currently write audit data to external immutable storage, and we would rather tell you that than call it immutable.
Retention: we have never deleted an audit row — the trail runs back to platform launch — but there is no automated retention job yet, so we do not quote a contractual retention period. Visible to your account owner at /portal/audit-logs with filter-by-service and free-text path/IP/UA search. Bulk export for your own SIEM is not built yet; ask and we will pull it manually.
Backups & disaster recovery
Postgres: Nightly logical dumps viapg_dump --format=custom at 02:30 IST, plus WAL archiving every 15 minutes. Retention: 14 days.
Customer VMs: A full disk image of every VM is taken nightly. It is taken online — your VM is never paused or stopped to back it up.
Object storage: Buckets are not backed up to a second location yet. Keep a copy of objects you cannot lose somewhere else.
Where backups live today. This is the part most providers are vague about, so: all backups are currently kept on our own infrastructure in Mumbai, on the same hardware as the data. They protect against mistakes, corruption and accidental deletion, not against losing the server itself. An off-site copy is being set up; this page will say so when it is running.
Restore testing: Restores are done by hand today; an automated restore drill is not running yet. Recovery from total host loss has not been drilled end-to-end, so we will not publish a number for it — ask and we will tell you where we are.
Status: Backup runs publish a textfile metric consumed by Prometheus; alerting fires if no successful backup in the last 26h.
Identity & access
Customer-facing: Sub-users under your account (IAM users), grouped into IAM groups, governed by attached IAM policies. Five managed policies seeded by default (CloudNxFullAccess, CloudNxReadOnlyAccess,CloudNxComputeFullAccess, CloudNxStorageFullAccess,CloudNxBillingReadOnly) plus custom policies you define.
Programmatic: Access key + secret key pairs, signed via AWS sigv4-compatible request signing. Secret keys are encrypted at rest with a service-level AES-256-GCM key separate from the root KMS key.
Owner accounts: Password (bcrypt, cost 12) + TOTP 2FA. TOTP secret is itself AES-256-GCM encrypted in the DB. OAuth via GitHub and Google supported as alternative sign-in.
Compliance posture (the honest version)
Active today
- GDPR (EU 2016/679) — data processing addendum available on request, data-subject access (DSAR) handled via a support ticket or our Contact page within 30 days. Erasure requests are actioned manually by our team.
- India DPDP Act, 2023 — audit logging, data-subject access via portal export, DPO contact published, breach-notification workflow established per Section 8.
- CCPA / CPRA (California)— "Do Not Sell" is N/A (we don't sell user data, ever), DSAR honoured via a support ticket within the statutory window for California residents.
- GST tax invoice flow (India) — a GST-compliant tax invoice for every charge, with GSTIN and CGST/SGST/IGST split per buyer state, downloadable as a PDF.
Not yet certified — being transparent
CloudNx does not hold ISO 27001 or SOC 2. Our data centre operators do, and a certification does not transfer from the facility to the company running inside it: theirs covers the building, power, and physical access, not our software, our access controls, or how we handle your data. If a vendor questionnaire asks whether CloudNx is certified, the honest answer today is no. We would rather lose a deal on that sentence than win one and have it surface during your audit.
- SOC 2 Type II — engineering preconditions (audit logs, KMS, MFA, RBAC, change management) ship across 2026. The formal audit is planned for FY27.
- ISO 27001— same window; we'll start the pre-audit gap analysis after SOC 2.
- PCI-DSS— we don't store card data; Razorpay holds PCI scope. Out-of-scope for us by design.
If your procurement requires "SOC 2 Type II today", we'll tell you that on the first call rather than waste your time. We'll happily share our SOC 2 readiness checklist and interim control evidence under NDA.
Operational practices
- Patches: Unattended OS security updates on the host (no auto-reboots). Weekly Sunday maintenance window (22:00–24:00 IST) for kernel reboots, container deploys, and schema migrations — pre-announced on the status page.
- Renovate bot: Weekend-grouped dependency updates, auto-merge on patch with green CI; majors are manually reviewed.
- Container rollback: Every deploy tags the previous image as
:rollback; a single command reverts to the last-known-good in ~5s with health-check guard. - Incident response: We notify affected customers by email and write up what happened. We have not yet published a post-mortem archive or a hosted status page — both are being built, and until they exist we are not going to claim them.
Reporting a vulnerability
We don't (yet) run a public bug-bounty program — we're small. But we read every report and we credit researchers in release notes when they accept.
Send disclosures through our Contact page (Security, legal & abuse). Please leave out working exploit details until we reply. Standard 90-day coordinated-disclosure window unless we negotiate otherwise.
Procurement team has questions?
We'll happily complete a security questionnaire or share interim control evidence under NDA. Reach us through our Contact page.
Last reviewed 2026-08-14. We re-audit this page quarterly.