Security

Firm boundaries, built into the product.

ConsciousRM treats tenant isolation, secure sessions, auditability, and recoverability as part of the application’s operating model.

01

Data boundaries

Firm isolation is enforced in the database.

Authenticated requests run inside a firm-scoped row-level-security boundary. The active firm identifier is carried into the database session so records outside that boundary are not available to the request.

02

Sessions

Application sessions stay on the application host.

Production sessions use signed, secure, HTTP-only cookies. They are host-only rather than shared across payroll.ninja subdomains, and state-changing authentication requests are origin-checked.

03

Operational controls

Requests remain traceable.

Requests carry identifiers for correlation, application errors use a consistent envelope, and firm activity is recorded in an audit trail for review.

04

Abuse protection

Rate limits protect shared application capacity.

Application requests are rate-limited by authenticated identity or client address, and login attempts are throttled across application replicas.

05

Recovery

Database backups are encrypted and copied offsite.

ConsciousRM is covered by the platform’s encrypted PostgreSQL backup process, including daily backups and continuous write-ahead-log archiving to offsite object storage.

06

Honest posture

Security claims stay specific.

This page describes controls documented in the running product. It does not claim a certification, audit, or compliance designation that has not been established.

Security in context

Talk through your firm’s requirements.

Use a product walkthrough to discuss access, roles, operating controls, and the questions that matter to your practice.

Request a demo