Security

Found a bug?
Tell us first.

We run an open responsible-disclosure policy. If you've found a security issue in an Olilo system, get in touch - we'll investigate quickly, fix fast, and credit you if you'd like.

Security contact

security@olilo.co.uk

Email is the fastest route. We aim to acknowledge reports within one working day and provide a substantive update within five working days. If the issue is actively being exploited, mark the subject “URGENT” and we'll escalate immediately.

Email security team

Rules of engagement.

Follow these and we'll treat your report as good-faith research under our safe harbour.

Good-faith research only

Test against your own account. Don't touch other customers' data, don't pivot between environments, and don't exfiltrate more than the minimum needed to prove the issue.

Respect privacy

If you accidentally access personal data, stop, don't save copies, and tell us in the report. We treat this as evidence of a finding, not an abuse.

Disclose responsibly

Give us reasonable time to investigate and ship a fix before you go public. We'll agree a disclosure window with you and credit you when it's fixed if you'd like us to.

We won't take action against you

If you act in good faith and follow this policy, we won't pursue legal action or contact law enforcement. You're helping us, not attacking us.

Scope.

What's in scope for this policy, and what you shouldn't touch.

In scope
  • olilo.co.uk and all *.olilo.co.uk subdomains we operate
  • The customer portal and order flow
  • Our public APIs
  • Network routing / BGP configuration as it relates to customer traffic
Out of scope
  • Denial-of-service attacks (automated or manual)
  • Social engineering of Olilo staff or customers
  • Physical attacks against offices or infrastructure
  • Vulnerabilities in third-party services we depend on - report to them directly
  • Volumetric scanning, brute forcing, or spam

What to include in a report.

A good report gets triaged and fixed faster. We're happy with prose, proof-of-concept code, screen recordings, or all three. The more reproducible, the better.

  • A clear description of the vulnerability
  • The exact endpoint, page, or system affected
  • Steps to reproduce, in order
  • Impact - what an attacker could actually do
  • Any proof-of-concept code, screenshots, or recordings
  • Suggested remediation if you have one
  • How you'd like to be credited (or “anonymous”)

Recognition.

We don't currently run a paid bug bounty, but we're happy to credit researchers publicly on this page (if you want), and we send a genuine thank-you. As we grow, we'll look at formalising a bounty - if that matters to you, tell us in your report.