Security Overview
This overview describes how RestoHQ Technologies protects Project Workflow Management (the "Service") and the data Customers keep in it. It is part of the Terms of Service and is Annex II's fuller description in the Data Processing Agreement.
1. Hosting and network
- The application and its database run with established cloud providers in Singapore (see the Subprocessor List).
- All connections are encrypted with TLS. Traffic reaches the application only through Cloudflare's protected network; the hosting provider's own direct address is switched off.
- When the application is being updated, visitors see a maintenance page rather than an error.
2. Each company kept apart
- Every Customer company has its own database schema, its own file folder and its own sign-in keys. A session issued for one company is refused by every other.
- The Service refuses any database request that does not name a company, instead of falling back to a default.
- Automated tests build a test company and check that data, files, settings and sign-ins cannot cross between companies.
3. Accounts and access
- Passwords are stored only as bcrypt hashes and must meet length and common-password rules. Password reset and invitation links are single-use and expire (30 minutes and 24 hours).
- Sign-in attempts are throttled and repeated failures are locked out and recorded.
- Sessions are signed, expire after 12 hours, and are revoked when a password changes, an account is deactivated or a role changes.
- Every action is checked on the server against a configurable role-permission matrix; the screen and the server use the same rules.
- Administrators who view the Service as another user, and platform staff giving support, do so in time-limited sessions that are clearly shown on screen and recorded in the company's audit trail.
4. Data protection
- Stored secrets such as mail-server passwords and Jira access tokens are encrypted (AES-256-GCM).
- Uploaded files are checked for size and type before they are accepted, stored outside the web root, and served only to users allowed to see them. Document previews are rendered in a sandbox in the browser with strict limits, and risky formats are offered as downloads instead.
- Email bodies built from forwarded messages are cleaned so they cannot load remote images or trackers.
5. Logging and monitoring
- An audit trail records who did what and when inside each company.
- Unexpected errors are recorded with a reference number users can quote; the platform team monitors health, background jobs, storage space and email delivery.
6. Backups and recovery
- The database is backed up nightly and stored files weekly, per company.
- Backups are encrypted with a key held offline and digitally signed, stored separately from the hosting provider, and kept for 90 days.
- Restores are rehearsed: the full restore drill completed successfully on 16 September 2026.
7. Development and testing
- Changes are tested by an automated suite of more than 100 test scripts before release, including security-focused checks.
- Third-party packages are checked for known vulnerabilities.
- The Service has been through repeated independent security reviews, with every finding fixed and covered by a test.
8. Incidents
If a security incident affects Customer personal data, we notify affected Customers without undue delay, as set out in the Data Processing Agreement. To report a vulnerability, see Security Contact and Vulnerability Disclosure ([email protected]).
9. Your part
Customers should keep administrator accounts few, remove people who leave promptly, use strong passwords, review role permissions, and configure retention periods that suit their obligations.