Security

Security & Trust

Each company's data is kept apart by the database, connections are encrypted, and card payments run through Stripe.

  • Each company kept apart

    The database itself keeps each company's records apart from every other company's.

  • Encrypted connections

    The web app, the field app and the customer portal all connect over encrypted links.

  • Cards through Stripe

    Card payments run through Stripe. Plenum does not store card numbers.

Kept apart by the database

Each company's records are kept apart by the database itself. A screen or report cannot reach another company's records, even by mistake.
  • Every request works for one company.
  • The database refuses reads and writes for any other company.
  • A request that does not say which company it is for stops.

Not left to each screen

Separation does not depend on a page remembering to hide another company's data. The database checks every request.

Encryption

Connections to Plenum are encrypted, on the web, in the field app and in the customer portal.

What is encrypted

In transit: Every connection to Plenum uses HTTPS.

Card data: Card details are handled by Stripe, not stored in Plenum.

Hosting and questions

  • Hosting

    • Errors and outages alert the team as they happen.
    • We target 99.9% monthly availability, subject to the exclusions in our Terms.
    • The database is backed up for recovery.
  • Questions

    Write to security@plenum.pro about any control on this page. We answer with what is in place today.

Access by role

Each person signs in to their own account, and their role decides what they can see and do.
  • Staff sign in to their own account.
  • Roles limit what each person can see and do.
  • Customers open the portal from a private link, with no password to manage.
  • Changes are kept in an activity log.

Incident response

We investigate reported security issues, contain confirmed incidents, and provide notices when required by applicable law or contract.

Reporting security issues

Send vulnerability reports and security questions to our security contact.

security@plenum.pro

Our security practices

1Separation by company

Each company's records are kept apart by the database itself. One shop's data cannot show up in another shop's account.

2Encrypted connections

Connections to the web app, the field app and the customer portal are encrypted.

3Access by role

Staff sign in to their own account. What each person can see and do follows their role, and cost can be hidden from field staff.

4Activity log

Plenum keeps a log of changes, so an admin can see who did what and when.

5Card payments

Card payments run through Stripe. Card numbers are handled by Stripe and are not stored in Plenum.

6Vulnerability reports

We review security updates for the software we depend on and fix the riskiest first. Reports can be sent to security@plenum.pro.

7Backups

The database is backed up so the service can be restored. Backups are for recovery, not a customer archive.

8Staff access

Access to the live system is limited to the people who run and support it.

Security, clearly scoped

We list only the controls we can describe accurately, and we update this page when they change.