Trust

What is collected, who decides, and where it lives.

Understand what WorkLedger collects, who can approve decisions, and how your data is handled.

Privacy

What is collected, and what is not.

Four categories, so you can see at a glance what never leaves your computer, what is collected with secrets removed, what is stored under an alias, and what only authorized people see.

Not collected
01Secrets: removed on your computer before anything leaves it
02A contractor's work, when they choose to run unrecorded
03Anything from a tool you did not connect
04Cursor chats (counted, not imported) and ChatGPT desktop history
Collected, with secrets removed first
01Prompts and the agent's answers
02Commands that ran, with their output or the change they made
03Test runs, and what each step cost
Stored under an alias
01Tool accounts: a fingerprint and a label, never the e-mail address
02Computers: an alias, with the real name visible to its owner and admins only
Visible only to authorized people
01A person's e-mail address, once they hide it
02Usage and account switches: admins see every member's, a contributor sees their own
03Decisions: only the project owner, lead, a named approver or a workspace admin may answer
Secrets

Secrets are removed on your computer.

Removal runs before anything is sent, and the server refuses a secret it recognises in a comment, an import or a saved note.

Who decides

A person decides, unless you set a rule.

Agents propose decisions and ask questions. A person approves, rejects or sends them back, on the web, on the desktop or from the phone.

By default every decision waits for a person.

A workspace owner can let routine decisions (low or medium risk, not security) be approved on the recommended option by a rule the owner set. Those approvals are labelled “workspace policy”, audited and reversible.

High-risk and security decisions always wait for a person. The phone never widens who may decide, and one human admin always remains.

Evidence

Done, with evidence attached.

A work item can be marked complete once its evidence is on file: the change, the test run, the commit, the review.

Evidence completeness is not work quality: it counts what is on file and does not judge whether the work is good.

The rule applies to work recorded through WorkBridge on a connected computer; it is not a control on your repository. When WorkLedger cannot be reached, the update waits on the computer and is sent later.

Honest record

The record is tamper-evident.

It is sealed as it is written and checked when it is read. If anything is changed after the fact, the record reads as broken, and you see where.

Your data

Your data stays yours.

Plain answers to what a security review asks. Where a fact is not on file here, we say ask us.

What leaves your computerPrompts, what the agent did with its result, and the cost, after secrets have been removed on the computer. Nothing from a tool you did not connect. A contractor can run WorkBridge with nothing leaving at all.
Where it runsA European cloud provider's managed Kubernetes in its United Kingdom (London) region. One PostgreSQL database per deployment; every workspace sealed by row-level security, so another workspace's data answers not found.
BackupsDaily base backups with the continuous write-ahead log, kept for 14 days, at the same provider in the same region. The application-level export dump is off.
EncryptionIn transit: TLS everywhere, from the browser, from WorkBridge and over MCP. Disk encryption at rest: ask us for the current statement.
Retention and deletionRetention rules are stored and reported, not yet enforced. Deletion of a workspace and its backups on request, within 14 days.
Who can get inPeople sign in with GitHub on your verified domains; there is no password form. Two roles, admin and contributor; project authority sits with the project owner and lead; one human admin always remains. Agents hold their own credentials and follow the same rules as people.
Controls in place todayEvery change to the record keeps who made it and the values before and after. A model allow-list and a per-session cost cap are applied when switched on; other policies are stored for reporting.
ExportYour workspace exports as CSV, JSON or PDF whenever you ask.
ComplianceDigital Disruptors holds ISO 27001 certification and a SOC 2 report, and claims nothing beyond them; scope and documents through the security review pack.
Limits

What it does not do.

  1. It is tamper-evident, not tamper-proof.
  2. A computer without WorkBridge records nothing, and a supported tool is not full capture.
  3. Secret removal catches what it recognises; it is not a guarantee.

Tool compatibility