New

AI summaries now on every product page

See how →
ratingsly

Security

What we do to protect your data, stated plainly — including the certifications we do not have.

Review before publishing. This page describes intended practice. Verify each control against your live infrastructure before publishing, and remove any line that is not currently true — a security page that overstates protections is worse than none.

Last updated 19 November 2026

Our approach

Reviews sit on your product pages, which means an outage costs you sales and a breach costs you trust. We optimise for both being unlikely, and for telling you plainly when something goes wrong.

We are a small team, so we do not claim certifications we have not earned. Below is what we actually do, and what we do not yet have.

Encryption

  • All traffic to and from Ratingsly is served over TLS 1.2 or higher, with HSTS enabled.
  • Data at rest is encrypted at the storage layer, including database volumes and backups.
  • Session tokens are signed with HMAC-SHA256 and stored in HttpOnly, Secure, SameSite cookies.
  • Passwords are stored using scrypt with a per-user salt — never in plain text, never reversibly.

Access control

  • Staff access to production data is restricted to those who need it for a specific task.
  • Multi-factor authentication is required on every administrative account.
  • Access is granted per incident and reviewed; it is not standing access.
  • Administrative actions are logged with the actor and timestamp.

Infrastructure

The application runs on managed hosting with automated patching at the platform layer. The database is not exposed to the public internet; it is reachable only from within the private network.

Dependencies are pinned and updated on a schedule, with automated alerts for known vulnerabilities. We do not run our own hardware.

Backups and recovery

  • Database backups run daily and are encrypted.
  • Backups are retained for 30 days on a rolling basis.
  • Restore procedures are tested, not assumed.
  • Customer data is included in backups and therefore in deletion — a deletion request removes the data from backups as they roll over within 30 days.

Monitoring

We monitor error rates, latency and availability, with alerting on anomalies. Failed logins and permission changes are logged and reviewed. Unusual submission patterns — the kind that indicate review fraud — feed the detection described in our Fake review policy.

Incident response

If we detect a security incident, we contain it first, then assess what data was affected. Affected customers are notified without undue delay, with enough detail to meet their own regulatory obligations. Where GDPR applies, we support the controller's 72-hour notification duty.

We publish a post-incident summary for significant events rather than quietly moving on.

Sub-processors

We use a small number of infrastructure providers: hosting, database, email delivery, messaging and payment processing. Each is bound by a written agreement restricting them to our instructions. The current list is in our Data Processing Agreement, and customers are notified before a new personal-data sub-processor is added.

What we do not have yet

We think this matters more than the list above, so we are stating it plainly:

  • We are not SOC 2 Type II certified. We may pursue it as we grow; we will not pretend to have it now.
  • We are not ISO 27001 certified.
  • We do not offer a contractual SLA beyond the 99.9% target unless agreed separately in writing.
  • We do not currently run a paid bug bounty, though we welcome reports and credit researchers who ask to be credited.

Responsible disclosure

If you find a vulnerability, email hello@ratingsly.com with 'Security disclosure' in the subject. Please give us a reasonable window to fix it before publishing details.

  • Do not access, modify or exfiltrate other customers' data to prove a point.
  • Do not run automated scanners that degrade the service.
  • Tell us what you found, how to reproduce it, and how you would like to be credited.
  • We acknowledge within 48 hours and aim to fix critical issues within 7 days.

Questions about this page? Email hello@ratingsly.com. We answer policy questions properly rather than with a template.