Security
How we protect REM products, and how to report a vulnerability.
- Version
- v2
- Effective
- Last updated
How we protect REM products, and how to report a vulnerability.
How we protect your data
All traffic to REM sites is encrypted with TLS (HTTPS); public certificates are renewed automatically.
Databases, file storage, monitoring and internal tools are reachable only on our private network between our servers, never directly from the internet.
Every REM app signs you in through REM Auth: passwords are stored only as salted hashes, sign-in attempts are limited and repeated failures lock the account for a while, and an e-mail address must be verified before it is trusted.
Secrets (payment gateway keys, connected-account tokens) and form submissions are encrypted in our databases.
Access to production is limited to the people who need it, and is logged. Databases are backed up every night.
Our servers send performance and error data to REM Telemetry, our own monitoring system, so we notice problems early.
Reporting a vulnerability
If you have found a security problem, write to support@remplatforms.com with the steps to reproduce it. We acknowledge within 2 working days and keep you informed until it is fixed.
We will not take action against anyone who reports in good faith, stays within their own account, does not access or change other people's data and does not degrade the service for others. Please give us a reasonable time to fix the problem before you make it public.