Security at Porters

Email holds a business's most sensitive conversations. This page describes how we protect it: where it lives, how it is encrypted, who can reach it, and how we recover when things go wrong.

Your mail stays in Kenya, on our hardware

  • Mailboxes run on servers Matmon Technology owns and operates in Kenya, not on a shared public cloud.
  • The mail store sits on a LUKS-encrypted disk, so a removed drive is unreadable.
  • No third party hosts or reads mailbox content. The few providers we use are listed on our sub-processors page.

Encryption

  • Every connection to the portal, webmail, mobile apps and APIs uses TLS.
  • Mail travels between servers over TLS whenever the other server supports it, and our domains publish SPF, DKIM and DMARC.
  • Sign-in sessions are sealed and encrypted cookies; passwords are stored only as hashes.
  • Backups are encrypted before they leave the server. The off-site copy is ciphertext only, and the storage provider has no key.

Signing in

  • Two-step sign-in with an authenticator app, plus single-use backup codes in case a phone is lost.
  • App passwords: a separate password for each mail app or device, revocable on its own.
  • Failed sign-ins are rate-limited per mailbox and per network, and lock out repeated guessing.
  • The Android app can be locked behind your fingerprint, face or screen lock.

Filtering and abuse prevention

  • Inbound mail is scanned for spam, phishing and malware (Rspamd and ClamAV), and suspicious content is quarantined.
  • Remote images in mail are blocked until you choose to load them, so senders can't track when you open a message.
  • Outbound volume, bounces and complaints are watched automatically; a compromised mailbox is paused before it harms others.

Access and operations

  • Administrative tools are reachable only through strongly authenticated access controls, limited to the staff who run Porters.
  • Support and administrative actions are recorded in an audit log.
  • Staff open mailbox content only on your request, to investigate abuse or an incident, or under a court order.
  • Deployments are scripted and reversible; the previous release is kept for immediate rollback.

Backups and recovery

  • Nightly backups of every system, kept for 7 days, 4 weeks and 6 months, verified weekly.
  • An encrypted off-site copy protects against loss of the site.
  • Database restores are tested regularly, not assumed.

Found a vulnerability?

We welcome reports from security researchers and won't take legal action against good-faith research. Email [email protected] or read the Security Response Centre.

Related: Privacy Policy · Data Processing Addendum · Sub-processors