Nashi OS Security and Data Protection
This page summarises the security practices Nashi OS actually uses today, without disclosing technical details that could help someone with bad intentions. No system is completely free of risk, so we review and improve our measures continuously.
- Effective:
- 1 September 2026
- Last updated:
- 12 September 2026
- Document versions:
- Terms of Service v1.0 · Privacy Policy v1.0
Separation of data between hotels (multi-tenant security)
- Every record is tied to the property code of the hotel that owns it
- Access is enforced in the database with Row Level Security, not only checked on screen
- A user's membership and role in the hotel are checked on the server every time
- Property codes sent from the user's side are never trusted without a permission check
Authentication
- We use an authentication system that stores passwords only as hashes, never in readable form
- Sign-in with email/password and external providers (Google)
- Sessions expire and are renewed securely, and signing out ends the session
- Password resets use a time-limited link sent to the user's email
- Two-step verification (MFA) with Google Authenticator is required for every account and cannot be turned off
Data protection
- All data in transit is encrypted with HTTPS/TLS
- Database data and backups are encrypted at rest, as provided by our infrastructure providers
- Keys, secrets and tokens for external connections are kept only in server-side secret storage
- Secrets and tokens are never shown on web pages, in URLs, in client-side logs or in error messages
- Attachments and documents are stored privately and are accessible only after a permission check
Application security
- Input is validated on both the client and the server
- SQL injection is prevented with parameterised database calls through standard clients
- Rate limiting for sign-in, public endpoints and webhooks
- Only approved origins may call the system (CORS allowlist)
- Webhook signatures or verification tokens are checked before processing data from external providers
- Idempotency for payments, bookings and integration events prevents duplicate transactions
- Libraries are kept up to date and code security is reviewed regularly
Monitoring and incident response
- Audit logs for important actions such as permission changes, financial document edits and reservation status changes
- Monitoring of system errors and suspicious access
- Regular backups and periodic restore tests
- An incident process: detect, assess impact, contain, fix and review afterwards
- Personal data breaches are reported to affected parties and regulators within the time required by applicable law
Certification status
Nashi OS is not currently certified to ISO 27001, SOC 2 or PCI DSS, and we do not claim certifications we do not hold. Our processes are designed with reference to industry good practice, and we will let you know if we obtain certification in future. Card payments are handled by external payment providers; Nashi OS does not store full card numbers.
The hotel's responsibilities
- Use strong passwords that are not reused on other services
- Do not share user accounts between employees
- Remove or disable access for departing employees without delay
- Review user roles and permissions regularly
- Keep external connection details confidential, such as OTA, LINE or Meta tokens
- Tell us immediately if you suspect unauthorised access to an account
Reporting a security issue
If you find a vulnerability or a suspicious event, please report it to support@nashios.com with the details needed to investigate, and please avoid accessing or changing other people's data.
We do not currently run a paid bug bounty programme, but we welcome reports and will get back to you once we have investigated. See how we process personal data in our Privacy Policy
