[rsvistel]

Copy-only trust alignment

Capability scopes are not encryption. Align public copy with current ordinary hosted plaintext-at-rest storage and link the existing Security and trust source. No product behavior, APIs, legal policies or technical trust-model changes. OpenKey service custody is not described as user-exclusive wallet custody.

Copy changes

File	Original text	New text	Reason
README.md	TinyCloud Node is the server component of the TinyCloud Protocol — a framework for creating interoperable software applications where users retain full sovereignty over their data. It provides a decentralized or user-controlled "cloud" that can serve as the backend for multiple apps, allowing users to maintain control over their data without ceding ownership or privacy to third parties.	TinyCloud Node is the server component of the TinyCloud Protocol — a framework for interoperable applications built around user-controlled data spaces and capability-based access. Users decide which scopes to grant to apps and agents.	Distinguish scoped authorization from confidentiality; state current hosted plaintext storage and link the existing trust model without changing technical behavior.
README.md	(No disclosure.)	Access control is not encryption. Ordinary data on hosted nodes is currently stored in plaintext at rest; TinyCloud does not currently provide encryption at rest or end-to-end encryption for that stored data. Operators can access unencrypted values. Your own wallet keeps its signing key under your control; OpenKey-managed keys have a separate custody boundary. See Security and trust for storage, key custody, application encryption and authorized-client boundaries.	Distinguish scoped authorization from confidentiality; state current hosted plaintext storage and link the existing trust model without changing technical behavior.
TinyCloud.md	TinyCloud is an emerging framework for creating interoperable software applications where users retain full sovereignty over their data. As the cost of writing software approaches zero—largely due to advances in AI and the commoditization of development—the true competitive moats are shifting to data and network effects. TinyCloud is designed to give individuals and organizations control over their data and the ability to layer new interoperable apps on top of it without ceding ownership or privacy to third parties.	TinyCloud is a framework for interoperable applications built around user-controlled data spaces and capability-based access. As the cost of writing software approaches zero—largely due to advances in AI and the commoditization of development—the true competitive moats are shifting to data and network effects. TinyCloud lets individuals and organizations grant apps and agents scoped access to shared data without tying that data to one application. This product vision includes proposed capabilities, not guarantees of current deployment behavior.	Distinguish scoped authorization from confidentiality; state current hosted plaintext storage and link the existing trust model without changing technical behavior.
TinyCloud.md	• TinyCloud is built so that each user controls their data outright. Requests to access or compute on that data must be explicitly permissioned.	• TinyCloud uses capabilities to let users approve scoped access to their data. Hosted operators and authorized processing services remain within the trust boundary.	Distinguish scoped authorization from confidentiality; state current hosted plaintext storage and link the existing trust model without changing technical behavior.
TinyCloud.md	• Data is stored, streamed, and computed upon in ways that minimize leakage. • Encryption strategies (e.g., eventually adopting fully auditable or decentralized approaches) ensure users do not need to trust an external party with their raw data. • Fine-grained permissioning allows you to decide, for instance, whether someone can see if you are “in NYC” without giving away your exact coordinates or entire location history.	• Capability-based access lets users choose the scopes granted to apps and agents. • Ordinary data on hosted nodes is currently stored in plaintext at rest. TinyCloud does not currently provide encryption at rest or end-to-end encryption for that stored data; operators can access unencrypted values. • A limited answer, such as whether you are in a city, can reduce what a recipient receives; it does not hide the underlying location from the service processing it.	Distinguish scoped authorization from confidentiality; state current hosted plaintext storage and link the existing trust model without changing technical behavior.
TinyCloud.md	• Compute Layer: The ability to run functions or queries on your data. E.g., “Am I within 1 km of my friend?” without revealing the exact coordinates to any third party. • Encryption / Capabilities: Fine-grained permission tokens or data-logic (“DataLog” / “biscuit tokens”) letting you define, for instance, “Friend X can see only yes/no if I’m in Berlin today.”	• Compute Layer: Functions or queries can return limited answers, such as “Am I within 1 km of my friend?” The service processing the query may still read the underlying data. • Capabilities: Scoped permissions define which resources and actions an app or agent may use. They do not encrypt those resources.	Distinguish scoped authorization from confidentiality; state current hosted plaintext storage and link the existing trust model without changing technical behavior.
TinyCloud.md	• ‘Find My Friends’ Clone: A privacy-preserving way to see if your friend is nearby or in a particular city—without ceding real-time location data to a third party’s servers.	• ‘Find My Friends’ Clone: A proposed app that shares a nearby-or-in-city result with a friend rather than an entire location history. Hosted processing still has access to the underlying data.	Distinguish scoped authorization from confidentiality; state current hosted plaintext storage and link the existing trust model without changing technical behavior.
TinyCloud.md	4. Encryption and Permissioning • Key Management • Each artifact or data bucket is encrypted under keys that live with the user. • To share or compute on data, the user issues ephemeral permissions that can be revoked or narrowly scoped. • Path Forward • Adopting standardized approaches to capabilities-based security (e.g., biscuit tokens or DataLog for flexible policy logic). • Ensuring that “post-quantum” or advanced cryptographic methods can be integrated over time.	4. Access Control and Encryption Boundaries • Users grant apps and agents capability scopes for the data they need. • Signing with your own wallet keeps its key under your control. OpenKey-managed keys use a separate service custody model; signing keys do not by themselves encrypt stored data. • Revocation support and limits depend on the access path. Ending access cannot recall copies already read. • Encryption at rest is planned, not a current hosted-storage guarantee. See the at-rest implementation status. • See Security and trust for operator access, application-specific encryption, key custody and authorized-client boundaries.	Distinguish scoped authorization from confidentiality; state current hosted plaintext storage and link the existing trust model without changing technical behavior.
TinyCloud.md	• AI-powered storyboarding, brainstorming, or rewriting using your entire knowledge base—without exposing it to third parties.	• AI-powered storyboarding, brainstorming, or rewriting using the knowledge base you authorize it to read. The processing service receives the context it uses.	Distinguish scoped authorization from confidentiality; state current hosted plaintext storage and link the existing trust model without changing technical behavior.
TinyCloud.md	5. Expand Encryption & Permissioning: Consider DataLog-based approaches and integrated encryption schemes, ensuring robust privacy in all workflows.	5. Expand Encryption & Permissioning: Continue the planned at-rest work and evaluate additional encryption approaches without presenting them as shipped guarantees.	Distinguish scoped authorization from confidentiality; state current hosted plaintext storage and link the existing trust model without changing technical behavior.
TinyCloud.md	These steps will push TinyCloud and its related products from an innovative concept to a thriving ecosystem that preserves user privacy, fosters sovereignty, and harnesses the full potential of personal AI.	These proposals aim to support interoperable personal AI with user-controlled access. Current security boundaries and implementation limits remain those described in Security and trust.	Distinguish scoped authorization from confidentiality; state current hosted plaintext storage and link the existing trust model without changing technical behavior.

Verification

README and product vision rendered with Marked and inspected in Chromium. Copy-only: no node runtime or API changes. Technical at-rest and trust-model sources unchanged.

Human review — not guessed

• At-rest work is explicitly planned in docs/at-rest/INTERFACES.md; no shipping date promised. Verify backup deletion, host-removal propagation and specific crypto deployment assumptions before claiming operator exclusion.

Non-repository follow-through

Review exported/PDF/Keynote/Google Slides decks and recordings; social bios/pinned posts; app-store and connector-directory listings; email/CRM investor templates; cached previews/OG cards and externally hosted collateral. These sources were not edited.