Skip to content

Security

Controls for accounts, workspaces, secrets, and automation.

This page describes controls present in the repository. It does not claim a certification or independent audit.

Access boundary

SiteDeal sample

Checked live

Account

Hashed password and optional two-factor

Workspace

Membership checked before records

Capability

Automation receives declared access

Approval

A person can stop a higher-risk action

Account, workspace, capability, and approval sit in sequence.
Passwords
Hashed by Laravel
Two-factor
Available after sign-in
Workspaces
Membership checked
Secrets
Encrypted at rest
Account to workspace permission boundary Account authentication sits outside workspace membership, capability limits, and human approval. ACCOUNT Hashed password and optional two-factor WORKSPACE Membership checked before records CAPABILITY Declared operations only Human approval Required for higher-risk actions Request
A request must pass account, workspace, capability, and approval checks.

Implemented controls

Only the checks that exist in the repository.

  • 01

    Password hashing

    The user model uses Laravel password hashing.

  • 02

    Two-factor authentication

    Authenticated users can configure two-factor authentication and recovery codes.

  • 03

    Workspace access

    Middleware and policies check workspace membership before access.

  • 04

    Permission checks

    Feature code checks permissions for protected operations.

  • 05

    Encrypted secrets

    Gateway and webhook credentials use encrypted storage.

  • 06

    Automation approvals

    Risk rules can require a person before sensitive automation runs.

Append-only evidence chain Evidence events are written in order. Earlier records stay locked. Event 01 Lead created Locked Event 02 Offer attached Locked Event 03 Approval given Locked Event 04 Next record Append only
A later event can only be added. Existing evidence cannot change.

Evidence

Customer journey records stay append-only.

The evidence model rejects changes and deletion after a record exists.

An operator reviews a printed checklist at a quiet desk with no visible credentials.
Review work This photograph shows review work. It is not a screenshot of the security console.

Honest limits

No certification claim.

SiteDeal does not publish a SOC 2, ISO 27001, PCI, HIPAA, or other compliance claim. Contact the team for a question about a specific control.

What this page shows
Controls in the repository
What it does not show
An independent audit or badge

A real security-console screenshot will appear after the owner captures the screen without credentials, tokens, or workspace data.

Ask a control question

Need a specific control detail?

Send the exact requirement. The team can answer from the implemented system.