Skip to content
Security

Strategy data needs explicit boundaries.

B4Math separates public rehearsals from private saved history and enforces access to decision records on the server.

Run a decision rehearsal
Input

Sanitized and bounded.

Decision briefs reject arbitrary HTML. Submitted text and report payloads are sanitized and size-limited before storage.

Public use

Run without creating an account.

A public rehearsal does not require login. An account is needed only when you choose to keep private report history.

Saved history

Private to its owner.

Saved decision records are private. Workspace users can list, open, rename, duplicate, and delete only their own records.

Access

Enforced on the server.

Authenticated changes require permission and ownership checks; hiding a control in the interface is never treated as authorization.

Requests

Protected against misuse.

Authenticated changes use request nonces, and public analysis and report mutations are rate-limited.

Data boundary

Share business context, not secrets.

Do not submit passwords, credentials, regulated data, or customer personal information. Reports identify their source and remain decision support rather than professional advice.