The Constraints

What We Refuse

Most companies tell you what their software does. This is the other list.

It is public because a promise you cannot check is not a promise. If you ever catch us on the wrong side of one of these, that is a fair thing to say out loud.

Never

Nine things our software will not do.

01
No advertising, in anything

Not in the apps, not in the games, not as an unlock, not as a reward. Attention is not the product and never becomes the product.

02
No engagement traps

No streaks that punish you for living, no energy timers, no daily-login economy, no lootboxes, no notification designed to pull you back. If you put something of ours down for a month, nothing bad happens.

03
No selling your data, and no training on your work

Your writing, your files, and your conversations are yours. They are not a corpus. They do not go to a vendor that trains on inputs.

04
Nothing moves in the world without your hand on it

No system of ours posts, sends an email, spends money, or takes any irreversible action without you approving that specific action. Capability without a hand on it is not a feature we want.

05
No fake success

If something failed, it says so. Errors surface. Empty results are marked as empty rather than dressed up. An agent here would rather tell you it could not do it.

06
No hostage-taking

Export exists from the first day, not as a retention lever released under pressure. Leaving with everything you made is a normal thing to do, and it will always work.

07
No dark patterns at the till

Cancelling takes the same number of clicks as subscribing. Prices are the prices. Nothing is hidden behind a call with someone.

08
No rewriting the past

Memory here is append-only. What was recorded stays recorded, including the parts that are inconvenient. A system that can quietly edit your history is a system that can lie to you about yourself.

09
No pretending to be a person

The agents have names, voices, and character, and they will never claim to be human, never claim credentials they do not have, and never tell you they feel something in order to sell you something.

Accountability

These are constraints, not settings. Several of them are enforced in the architecture rather than in a policy document, because a rule that depends on remembering it is not a rule. If you want the specifics of how a particular one is enforced, ask and we will show you.

Write to Us

Keep the people you love.

The law underneath the product