Skip to content

Align public copy with the documented trust model - #542

Merged
rsvistel merged 2 commits into
mainfrom
docs/align-trust-copy-20261110
Nov 16, 2026
Merged

rsvistel merged 2 commits into
mainfrom
docs/align-trust-copy-20261110

Conversation

@rsvistel

@rsvistel rsvistel commented Nov 10, 2026 •

Copy link
Copy Markdown
Contributor

Copy-only trust alignment

Reworked 2026-11-16 after review. The first version of this PR said hosted data is "plaintext at rest" and hedged revocation; neither statement is in the Security and trust page it cited, and it removed some true statements. This version changes only lines that state a guarantee the Security and trust page or the published privacy policy contradicts. Where it adds a disclosure it says what those two sources say: ordinary data is not end-to-end encrypted, the node that hosts a space can read it in order to serve it, and revoking stops future access without recalling copies already read. Positioning and product naming are back to main.

What this PR does now

  • The README intro is main's. One paragraph says what the node software does today, sourced from docs/at-rest/INTERFACES.md in this repo.
  • TinyCloud.md is main's February 2025 memo with a dated note on top.

Copy changes

File Main's text New text Why
README.md Access control is not encryption. The node does not yet encrypt ordinary KV or SQL values itself, so whoever operates a node can read them unless the application encrypts them first; docs/at-rest/INTERFACES.md tracks the at-rest work. A wallet you run keeps its signing key with you; OpenKey holds and uses its keys in its own service. See Security and trust for key custody, application encryption and authorized-client boundaries. One disclosure, in the wording of the Security and trust page and the privacy policy.
TinyCloud.md > Note (November 2026): this is a February 2025 vision memo. It describes plans, not shipped behavior. For what the node does today, see the README and Security and trust. Dated note on a historical memo instead of rewriting it.

Verification

Markdown only; not rendered. at_rest is referenced only from tests on main, which matches the status note in docs/at-rest/INTERFACES.md.

Left for the owners

  • Update the README sentence when sealed KV storage lands.

- README: restore the intro; say what the node does today (it does not
  yet encrypt ordinary KV or SQL values itself; docs/at-rest tracks the
  work) instead of a claim about hosted deployments.
- TinyCloud.md: restore the February 2025 memo and add a dated note
  that it describes plans, not shipped behavior.
@rsvistel
rsvistel merged commit 92f0336 into main Nov 16, 2026
28 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant