What needs protection before sync?
The security paper identifies client behavior, protected vault material, and the data path as questions that need current engineering evidence.
Security
Security needs clear boundaries, not louder promises.
The sensitive parts of a household plan deserve more than a reassuring label. The working security note marks the evidence a current technical review must establish and the decisions a person should still be able to understand.
The review boundary
Keep the record separate from the routine around it.
This review frame separates a household record from service operations so the final technical paper can state exactly what is protected, what metadata exists, and where the product still depends on people or systems.
Client reviewHousehold recordBoundary to verify
Service reviewStored recordOperational context to document
Conceptual review frame only. It is not a protocol diagram, a product behavior claim, or a substitute for current technical evidence.
Questions worth asking
Trust begins with specifics.
A good security page makes it easier to understand the system without pretending that every risk disappears.
What can the service still see?
Account and operational metadata are not automatically the same as vault content. The distinction belongs in the public documentation.
What still depends on people and systems?
Client version, deployment, recovery design, account behavior, and release policy all matter alongside cryptography.
Who it must convince
Written to be read by a household, not only an auditor.
The technical paper matters, and so does the person who depends on the answer. The same boundary has to make sense at a kitchen table as in a formal review.
How we earn trust
Documentation should be as accountable as the product.
A public security posture is only useful when the words, policies, and implementation remain aligned. That is the standard this site is being built to meet.
Bounded statements
We describe a protection boundary and its limits. We do not turn a design goal into an absolute promise.
Useful documentation
Technical details, product policies, and legal terms should agree with one another and remain easy to find.
Evidence before badges
No certification, audit, or compliance badge appears here until there is current, publishable evidence behind it.
Read the record
Questions about privacy, policy, or the technical model should have a clear home.
Find the current security documentation, review the privacy policy, or ask the team a direct question.