How we promise to treat you

Most of the trust that developer tools lose, they lose at the billing page and the changelog — not in the code. We’ve watched it happen. These are the commitments we hold ourselves to, and we’d rather you hold us to them too.

We publish the numbers we enforce

Your plan’s limits are stated as actual numbers — not “generous,” not “limited,” not footnotes. The usage you see inside the app is the exact usage we meter. The pricing page and the product show the same figures.

We never say “unlimited” unless it is

No asterisks that quietly mean “until a pool runs out.” If something is metered, we tell you how it’s metered, before you rely on it.

You hear about changes before they bite

Every pricing or plan change gets a dated post and a changelog entry — never a silent switch discovered on your invoice. When a change costs you more, we say so in plain words.

Grandfathering means what it says

If we let you keep an existing plan, that promise carries an explicit end date from the start. We will not remove an opt-out and then call it a bug, or decide after the fact that it was “only for a limited time.”

Leaving is as easy as joining

Cancellation is self-service and takes effect cleanly. No retention mazes, no vanishing cancel button. Where the law gives you a withdrawal or refund right, you get it — we don’t write it away in the fine print.

A person answers

Support is handled by people. If we ever put an assistant in front, it will be labeled as one and it will never invent a policy. Our policies live here and in the docs, not in a chatbot’s imagination.

Your code is never the product

We don’t train on your code — unconditionally, with no mode to toggle. See the Privacy Policy for exactly what we store and how to delete it.

This is a statement of intent we’re publishing before launch, not a contract. The binding terms live in the Terms of Service and Privacy Policy. If we ever fall short of what’s written here, tell us — holding us to it is the point.