Principles
Shared direction, bounded claims
These principles guide project decisions. They are not a substitute for the exact processing, network, storage, telemetry, and security disclosures owned by each product.
01
Local-first where practical
Prefer local processing when it meaningfully reduces unnecessary data exposure and remains technically appropriate. Local processing is not universally superior for every workload, device, or maintenance model.
02
Minimal unnecessary data exposure
Request, transmit, store, and retain only what a product actually needs for its documented purpose.
03
Transparent network behavior
Users should be able to understand when requests occur, what data is involved, and why the request is needed.
04
Privacy-aware defaults
Lower-exposure behavior should generally be the default where it is practical, understandable, and technically sound.
05
Auditable and open implementation where practical
Public source, understandable dependencies, and documented boundaries improve auditability. Openness supports inspection but does not by itself prove security or privacy.
06
Traceable deployment
For official web applications, users should be able to understand how deployed content relates to public source and deployment history where practical.
Review Hub deployment transparencyPrivacy model
Products have different requirements
Learn how the ecosystem distinguishes shared philosophy from product-specific guarantees.
Read the ecosystem privacy model