1. What we hold, and why this page matters
Digilight PMS holds a hotel's operating record: who is staying, when they arrived, what they paid, and the identity document they presented at the front desk. That is a more sensitive dataset than most software of this size carries, and this page has to be worth the trust it asks for.
So it is written to a rule: every sentence here is checkable against the code, and where a control does not exist, we say so rather than reaching for a comfortable word.
2. What we do not claim
Digilight India holds no security certification of any kind:
- No ISO 27001.
- No SOC 2.
- No PCI-DSS attestation of our own.
- No third-party penetration test has been carried out.
We are a young company and we have not been audited. Anyone telling you otherwise — including any page on this website — is wrong, and we would like to know about it.
We also do not currently offer:
- Multi-factor authentication. Sign-in is by password only.
- Application-level encryption of identity documents. See §6.
Stating this plainly is the entire point of the section. A security page that gestures at certifications it does not hold is worse than no page at all, because the buyer who relies on it has been misled about the one thing they came here to check.
3. How we protect your data
Each control below exists in the product today and was verified in the source code.
3.1 Tenant isolation
Every hotel's data is scoped to its own property. The property a request may touch is taken from the signed session token, never from anything the browser sends — so a user cannot ask for another hotel's data by changing a parameter.
An automated isolation test asserts that one property cannot read, modify, or switch into another.
3.2 Passwords
Passwords are stored as one-way bcrypt hashes with a cost factor of 12. We never store them in a recoverable form, we cannot read them, and we cannot tell you what yours is — only reset it.
3.3 Sessions
Signing in issues a signed session token, held in a cookie that is HttpOnly (unreadable by JavaScript), Secure (sent only over HTTPS) and SameSite=Lax. The token is valid for 7 days.
Be aware of what this means: the token is stateless. Signing out clears the cookie from your browser, but it does not revoke the token on our servers. Anyone who had already copied it could continue to use it until it expires. Because of this, remove the accounts of staff who leave promptly, and treat a shared or leaked token as a reason to reset.
3.4 Roles and permissions
Staff accounts carry roles — owner, manager, front desk, accountant, housekeeping, inventory, food service and read-only — and each role maps to a defined set of permissions.
3.5 Audit logging
Changes to bookings, payments and sensitive settings are recorded in an audit log capturing the acting user, the action, the affected record, the IP address and the time.
Where a member of Digilight India's staff enters a customer's account to provide support, that session is time-limited to 30 minutes, requires a written reason, can be revoked, and is logged. It is described in full in the DPA — we would rather tell you it exists than have you discover it.
The audit log is not tamper-proof. It is an ordinary database table. It records what happened; it is not a legal evidentiary record and we do not present it as one.
3.6 Rate limiting
Sign-in, sign-up and password-change endpoints are rate limited per client IP address.
3.7 Payment integrity
Payment amounts are always derived on our server from the plan catalogue — the browser cannot propose a price. Notifications from the payment gateway are cryptographically signature-verified before they are acted on, and payment capture is idempotent, so a replayed notification cannot double-charge you.
4. Where it runs
The application and the database both run in Singapore — see the Privacy Policy, which explains what that means for you.
Database connections are encrypted in transit and refuse to connect otherwise. The website and the application are served over HTTPS.
5. Backups and recovery
Customer data is held in a managed PostgreSQL database with continuous point-in-time recovery. Our infrastructure provider's platform supports a recovery point objective of around 5 minutes and a recovery time objective of around 1 hour. We present these as the platform's capability rather than a measured guarantee, because we have not yet rehearsed a full end-to-end restore.
6. Encryption
We want to be exact here, because this is the sentence companies most often fudge.
- In transit: encrypted. HTTPS to the browser, TLS to the database.
- At rest: encrypted by our database provider at the storage layer.
- Application-level: Digilight PMS does not apply its own field-level encryption to guest identity documents. A passport, Aadhaar or driving-licence number entered at the front desk is stored as ordinary text in the database.
That last line is not a comfortable thing to publish, and it is why it is here.
7. Reporting a vulnerability
If you believe you have found a security vulnerability in Digilight PMS, we want to hear about it before anyone else does.
- Write to support@digilightpms.com
- Tell us what you found and how to reproduce it
- Give us reasonable time to fix it before disclosing it publicly
- Do not access, alter or remove any data that is not your own while testing
We will acknowledge your report, keep you updated, and credit you if you would like us to. If you act in good faith and follow these guidelines, we will not pursue legal action against you for your research.
8. If something goes wrong
If guest or hotel data is exposed, we will tell the affected hotels and give them what they need to meet their own notification duties to the Data Protection Board and to their guests.
The deadline we commit to is set in the DPA — within 72 hours of becoming aware of a breach — and that is the deadline that is operationally binding.
9. Your side of it
The security of a hotel's data also depends on the hotel:
- Give every member of staff their own login. Do not share one.
- Remove accounts for staff who leave — and see §3.3 for how long their session can outlive the account today.
- Use a strong, unique password.
- Lock the front-desk computer when you walk away from it.
10. Changes to this policy
Every change is recorded in the version history at the foot of this page.
11. Contact us
- Business: Digilight India
- Product: Digilight PMS
- Website: www.digilightpms.com
- Support email: support@digilightpms.com
- WhatsApp: +91 95488 38588
- Support hours: Monday to Saturday, 10:00 AM – 6:00 PM IST
- Business address: Meerut, Uttar Pradesh, India
To report a vulnerability, see §7. Auditors who need more detail than this page carries can write to the support address above.