Not a privacy policy
Data Practices are plain-English operating principles. Product privacy policies remain the formal documents for specific apps where they exist, such as the PercentKit Privacy Policy.
What we look for
Purpose-driven collection
A product should collect information for a defined reason: to provide a feature, keep the service reliable, support a purchase, improve the product, or operate a sustainable business. “It might be useful someday” is not enough by itself.
Data minimization
Useful software does not need to remember everything. Where a feature works with local data, aggregated data, shorter retention, or no account identity, that option should be considered before collecting more.
Transparency before surprise
Important data practices should be visible in plain English. Users should not have to reverse-engineer a product or decode vague policy language to understand consequential collection, sharing, or commercial use.
Retention with a reason
Data should not drift into permanent storage by accident. Retention should match the product purpose, legal or operational need, and user expectation as closely as practical.
Recipients and sharing
When data leaves a product, users deserve to know who receives it and why. That can include service providers, app stores, advertising networks, analytics systems, support tools, or user-authorized destinations.
Commercial use
Kaiser Works is not promising that data can never create commercial value. The commitment is that meaningful commercial use should not be hidden. If data creates value for someone other than the user, the user deserves to know.
User access
Where practical, products should help users understand, access, export, or authorize use of data they create. This matters most when the same data can help people understand their own lives, purchases, habits, or decisions.
Product-level differences
A simple calculator, a household inventory assistant, and a future analytics product will not have identical data practices. The right standard is not pretending every product is the same; it is explaining the differences clearly.
Verifiable privacy, where practical
The long-term direction is simple: privacy claims should become easier to inspect. Future Kaiser Works apps may include a path such as Settings → Privacy → My Data Receipt, where users can see categories of data collected, why they are collected, retention rules, recipients, commercial use, and — where technically appropriate — the actual analytics events a product sends.
This website work does not add telemetry or a backend analytics system. It establishes the public structure those future product experiences can grow into.