How ClickWerxs Command Center protects your data

Multi-tenant isolation

Each customer is a tenant. Your records are separated from every other customer's at the database layer, not just in the application.

• Every table carries a tenant identifier, and Postgres row-level security enforces that a session can only read or write rows belonging to its own tenant.
• A server-side tenant guard aborts any write that arrives without a tenant filter, so a coding mistake fails closed instead of leaking.
• Automated audits run on every commit: more than 100 separate checks in continuous integration verify isolation and access rules before code can merge.

Encryption

• All traffic between your browser, our application, and our services uses TLS.
• Data at rest is encrypted by the hosting providers for both the database and file storage.
• Uploaded files live in private buckets and are served only through time-limited signed URLs. There are no public file paths.

Authentication and access control

• Email and password sign-in with a 12-character minimum and password strength scoring.
• Optional multi-factor authentication using time-based one-time codes (TOTP). A tenant administrator can make MFA mandatory for all of their users.
• Idle sessions are signed out after 2 hours.
• Role-based access for office staff, field staff, the customer portal, and the partner portal. Roles are enforced at the edge, before a page renders.

Audit logging

• Every write records who made it and when.
• When ClickWerxs platform staff act on a customer tenant, for example during support, the action is logged separately and attributed to the platform, never to the customer's own staff.

Data residency

• The primary database and file storage run in Canada (Montreal region).
• The PDF rendering service that produces quotes, inspection reports, and signed documents also runs in Montreal.
• Application compute runs on Vercel in the United States, so customer data is processed there in transit. It is stored only in Canada.
• See the sub-processor table below for where each supporting service operates.

Backups and continuity

• Logical database dumps are taken and held off-platform, independently of the hosting provider. These are captured manually today; an automated off-site job is being stood up.
• A documented restore runbook exists and has been exercised.
• Recovery objective targets: 24 hours for both recovery point (RPO) and recovery time (RTO).

Payments

• ClickWerxs never stores card numbers. Card data is collected and tokenized by a PCI-compliant payment processor.
• Command Center holds only the token and the transaction record it needs to show status and history.

E-signatures

• Each signed document records the signer's identity, a timestamp, the signing IP address, and a tamper-evident hash of the document.
• Our retention policy for signed documents and their evidence is 7 years. Nothing deletes them on a shorter schedule.

Vulnerability management

• A dependency audit and secret scanning run on every commit and block the change when they fail.
• Dependabot alerts are enabled on the platform repository and reviewed on a regular cadence.

Compliance program

ClickWerxs is running a SOC 2 program covering the Security, Availability, and Confidentiality criteria. The audit has not yet been completed, so we do not claim SOC 2 certification.

• The policy library is written: information security, access control, encryption, change management, incident response, business continuity, vendor management, and the supporting policies.
• Evidence collection draws on the same per-commit checks described above, plus dated access, backup, and dependency snapshots. Those snapshots are captured manually today; the automated monthly job is being brought up, and we can show your reviewer the dated artifacts we hold.
• We will update this page when the audit is complete. Until then, we can walk your reviewer through the controls directly.