LawsOf Robots

This is the product's privacy commitments — a versioned public statement of record. For how this website itself handles data (cookies, logs, contact), see the site privacy policy.

Version v1.1 2026-07-07 Permanent link: /privacy-commitments/v1.1/

Privacy Commitments Statement

Version: 1.1 Status: Public-facing statement of record; versioned; digest-pinnable Identity: Laws of Robots (product-side governance artifact) Authorship: Owner-authored verbatim Date: 2026-07-07 Relationship: Companion to the internal erasure-posture doctrine. Cited by the privacy whitepaper. Consistent with both by construction.


§1 — Purpose and scope

This document is the binding public statement of the system's privacy commitments. It is not a privacy policy, not legal terms, and not a feature description.

"Binding" here means published, versioned, and changed only in the open. The commitments below govern the system's design and operation. Any revision is itself a visible, dated act.


§2 — The four commitments

2.1 Bystander exclusion

The machine's perception of anyone other than the owner does not enter the record. This includes visitors, children, neighbors visible through windows — anyone merely present in its environment. Interacting with the machine, speaking to it, or answering its questions does not create a route into the record. Admission, defined below, is the only route.

Information about a person other than the owner may enter the record only through an explicit act of admission. That act must be deliberate, attributed to the person performing it, and tied to a clear reason for accountability. There is no passive or automatic route by which a bystander's information becomes part of the machine's record.

2.2 The hard gate

The system will not collect personal data about any person other than the owner until the capability to erase that data completely and provably is operational.

Because that capability does not yet exist, the record today contains no personal data about any third party. The gate does not merely slow collection — it forbids it.

2.3 Erasure semantics

Erasure is performed by destroying the key that makes an entry's content readable. The content itself becomes permanently unrecoverable. The sealed entry remains in the record — its position in the sequence, its integrity, and the fact that a decision occurred stay intact and verifiable.

This approach makes privacy and accountability complements rather than opposites. A person's information can be destroyed on request, but the tamper-evident record of what the machine did cannot be altered or erased by anyone, including the owner.

2.4 No permanent carve-outs

The erasure guarantee applies to every surface where a person's data can reside. There are no permanent exceptions.

Where a gap exists during construction, that gap must be explicitly named and given a completion deadline internally. An unnamed or unclocked gap is treated as a violation of the commitment, not an oversight.


§3 — What these commitments do not claim

Stated plainly, in one place:

  • The erasure mechanism is not yet built.
  • The empty state cannot be inspected from outside.
  • No third party audits or certifies these commitments today.
  • The commitments bind this system's design and operation, not the law of any jurisdiction.

§4 — Change discipline

These commitments may be strengthened or added to. They may not be weakened or removed. Every version is retained and publicly comparable to the last.


§5 — Definitions

  • Bystander — Any person the machine perceives who is not the owner.
  • The record — The sealed, tamper-evident sequence of the machine's decisions.
  • Key destruction — Erasure performed by destroying the key that makes an entry's content readable, leaving the sealed entry in place.
  • Admission — The deliberate, attributed act by which information about a person other than the owner is entered into the record.

The definitions in this Statement are authoritative. The privacy whitepaper's corresponding definitions conform to them.


Verification hooks

  • Version number: 1.1 (this document)
  • Publication date: 2026-07-07
  • Stable URL: [To be assigned at publication]
  • Digest: [Optional — publish if desired for stronger change visibility]

Version history

  • v1.0 — 2026-07-07 — initial text (superseded before URL assignment; never published)
  • v1.1 — 2026-07-07 — §2.1 first paragraph tightened to admission-only; §3 meta-commentary sentence removed

End of Privacy Commitments Statement v1.1

Verify

sha256 48737110f1b1ee69b6cc7c8c25b69308ce32da28ae9019015d476b2e283152cc · 4441 bytes

View the source file

The digest above is computed at build time over the exact bytes of the linked source file. Fetch that file and hash it yourself to confirm it matches the digest shown here.