Our Covenant
This is not a privacy policy and it is not a legal substitute for product terms. It is the public standard we want Kaiser Works products to live up to: useful software, plain explanations, restrained monetization, and data practices people can actually understand.
Privacy you do not have to take our word for.
Six principles
We build software that acts on your behalf
Our products should create value for the people using them, not manufacture inconvenience so we can monetize the solution.
That means keeping useful things simple, treating advertising with restraint, and refusing to hide consequential data practices behind policies most people will never read.
When our interests and yours are not perfectly aligned, you deserve to understand that too.
People should benefit from the data they create
Data about how people use products can create enormous value for businesses. We do not believe that value should flow in only one direction.
When practical, people should be able to understand their data, access it, and authorize products they trust to use it on their behalf.
Purchase history should not become valuable only when it helps someone sell to you. It can also help you understand what you own, what you waste, what you need, and where your money goes.
Data creates responsibility
We do not collect information simply because technology makes it possible. Data should have a purpose.
When we collect it, users should be able to understand what is collected, why it is collected, how long it is retained, who receives it, and whether it is used commercially.
If data creates value for someone other than you, you deserve to know.
We do not collect data just because we can
Modern software makes it easy to collect enormous amounts of information. That does not mean every field belongs in a database.
Kaiser Works should collect information when there is a defined purpose, not simply because it may become useful or valuable later.
Good software deserves a sustainable business model
Kaiser Works intends to build a successful company. Revenue should not require making useful software deliberately frustrating, exploiting attention, or obscuring how data creates value.
Advertising, subscriptions, analytics, services, and other models can all be legitimate. The difference is how they are implemented.
We would rather earn a little fairly from many people who trust our products than extract as much as possible from every person who uses them.
Privacy should be understandable — and provable
People should not need to be lawyers, security researchers, or data engineers to understand what a product knows about them.
Where practical, Kaiser Works products should allow users to see what information is collected and how it is used.
Privacy you do not have to take our word for.
The trust stack we are building toward
The Covenant explains what Kaiser Works believes. Data Practices explain how those beliefs show up in engineering and business decisions. Product Data Receipts explain what individual products actually collect. Privacy policies and terms remain the formal legal documents where they exist.
Next: data practices
The next layer is implementation: purpose, retention, recipients, commercial use, access, and product-level differences.
Read Data Practices