Skip to content

Security

How we protect REM products, and how to report a vulnerability.

Version
v1
Effective
Last updated

You are reading version 1. Read the current version (v2).

How we protect the platform, and how to reach us about a vulnerability.

How we protect your data

  • Encrypted in transit with TLS, and at rest

  • Access to production is limited, and every access is logged

  • Backups are taken regularly and restores are tested

  • Dependencies are monitored and patched

Reporting a vulnerability

If you have found something, we want to hear about it. Write to security@remplatforms.com with the steps to reproduce. We acknowledge within 2 working days and will keep you updated until it is closed.

We will not pursue action against anyone who reports in good faith, stays within the bounds of their own account and does not degrade the service for others.

Certifications

[List certifications and audit reports here as they are obtained.]

Change history

  1. v218 Nov 2026Rewritten in full: complete, product-specific text replaces the starter text.
  2. v18 Sept 2026Version recorded when REM Blogs became the content hub.