Security posture

Layered protection for mailbox data, customer access, and private media.

Mailbox operators handle sensitive workflows every day: customer identities, mailbox relationships, package activity, mail images, staff actions, notifications, and billing follow-up. MailroomIQ is built around layered controls that keep those workflows scoped, traceable, and tied to authorized store relationships.

Store-scoped trust

Security starts with the mailbox relationship.

MailroomIQ access is organized around the store, the customer, and the mailbox relationship. A customer sign-in alone is not enough to expose mailbox data. Customer access depends on an active mailbox relationship enabled by the participating store.

Store operators control customer enrollment, access changes, and revocation. This helps ensure that customer-facing mail, package, image, and request workflows stay tied to the correct mailbox relationship.

Private media

Private media stays private.

Mail and package images are treated as private customer media. MailroomIQ is designed around controlled media access patterns, authenticated customer context, and store-scoped relationships.

Customer-visible images are not intended to be exposed through public links or public storage. Access is routed through controlled paths so media visibility follows the customer's active mailbox access.

Media lifecycle and retention are treated as governance controls and are configured to align with store requirements, deployment settings, and applicable obligations.

A layered access model

Multiple layers narrow access instead of relying on a single gate.

  1. Store contextWorkflows and records are organized around the participating store.
  2. Authenticated identityUsers sign in before accessing customer or staff experiences.
  3. Active mailbox accessCustomer access depends on an enabled mailbox relationship.
  4. Staff workflow boundariesStaff tools are organized around operational responsibilities.
  5. Controlled media deliveryPrivate images are delivered through controlled access patterns.
  6. Event historyKey workflow events are designed to be traceable.
  7. Support boundariesSupport review is handled with scoped, reasoned access.

Built for auditability

MailroomIQ is designed to leave a trail for important operational activity: mailroom events, customer requests, notification attempts, billing workflow states, package handling, and support diagnostics.

That audit-friendly posture helps stores investigate questions, review exceptions, and understand what happened without relying on memory, sticky notes, or disconnected spreadsheets.

Notifications with guardrails

Customer notifications are event-based and preference-aware when enabled. Package pickup notices, mail updates, invoice reminders, account notices, and support messages can be tracked through delivery-attempt history.

SMS workflows are designed around consent, opt-out handling, provider approval, and suppression controls. Mobile numbers and SMS consent information are not sold, rented, or shared for marketing or promotional purposes.

Careful companion-system boundaries

MailroomIQ is designed to sit beside the systems mailbox operators already use. PostalMate® and CashMate® remain source-system authority.

MailroomIQ avoids changing source-system records unless a reviewed and approved integration path is in place. This companion-layer approach helps stores modernize surrounding workflows while protecting the integrity of core mailbox and POS systems.

Support with boundaries

Support workflows are designed to be scoped, reasoned, and auditable. When support information is needed, MailroomIQ favors focused diagnostics and support context rather than unnecessary exposure of customer media or sensitive records.

Please do not email passwords, reset links, private images, scanned contents, or sensitive documents. Security concerns can be sent to [email protected].