Repository navigation
Align public copy with the documented trust model - #542
Merged
Merged
Conversation
- 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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
docs/at-rest/INTERFACES.mdin this repo.TinyCloud.mdis main's February 2025 memo with a dated note on top.Copy changes
Verification
Markdown only; not rendered.
at_restis referenced only from tests on main, which matches the status note indocs/at-rest/INTERFACES.md.Left for the owners