Skip to content

Security

Keeping your data and money safe.

Security is part of how we build every olloo product. Here's what we do, and how to tell us if you find a problem.

Encrypted in transit

Every olloo website and app is served over HTTPS, so data between your device and our servers is encrypted.

We never see your card or PIN

Payments are handled by Paystack, a licensed payment processor. olloo does not receive or store card numbers or mobile money PINs.

Least-privilege access

Only the people who need access to production systems have it, and access is reviewed as the team changes.

Backups and monitoring

Our hosting providers keep our services backed up and monitored, so we can recover quickly if something goes wrong.

Reporting a vulnerability

If you believe you've found a security vulnerability in any olloo product, please email olloocompany022@gmail.com with:

  • the product and URL affected,
  • a description of the issue and its potential impact,
  • clear steps to reproduce it, and
  • how we can reach you for follow-up questions.

We will acknowledge your report within 3 working days, keep you updated while we investigate, and let you know when it is fixed.

In scope

  • olloo.app (this website)
  • invoice.olloo.app (olloo invoice)
  • slip-builder.com (Slip Builder)
  • brocchure.com (Brocchure)

Please don't

  • access, change or delete data that isn't yours, beyond the minimum needed to show the issue,
  • run denial-of-service tests, spam, or automated scanners that degrade our services,
  • use social engineering or phishing against our staff or customers,
  • test physical security, or our providers' systems (such as Paystack), or
  • disclose the issue publicly before we have had a reasonable chance to fix it.

Safe harbour

If you act in good faith and follow this policy, we will not pursue or support legal action against you for your research, and we will work with you to understand and resolve the issue. We don't currently run a paid bug bounty, but we are glad to credit researchers who help us, with their permission.

Our machine-readable security contact is published at /.well-known/security.txt. See also our Acceptable Use Policy and Privacy Policy.