Klor.

Terms of service

Last updated 26 September 2026

Plain terms for using Klor. You own your configuration, we run the service as well as we can, and neither of us pretends this is a bank.

The agreement

These terms cover your use of Klor at klor.dev, the read plane at edge.klor.dev, the management API, and the @klor/react package. Creating an account means you accept them. If you are agreeing on behalf of a company, you are confirming you may bind it.

Your account

  • Keep your credentials to yourself. Anything done with your account is treated as done by you.
  • You are responsible for your API keys. A public key is extractable from any app you ship, by design; a private or management key is not, and must stay on a server.
  • One person, one account. Workspaces are how you share.

Your data stays yours

Your configuration is yours. We claim no ownership of it, and we use it only to run the service for you. You can export it at any time through the management API and delete it at any time from settings.

Acceptable use

Do not use Klor to:

  • Break the law, or help anyone else do so.
  • Store personal data about your users in flag values. Klor is a configuration store; it is not designed, priced or secured to be a user database.
  • Attack the service, work around quotas, or generate load whose purpose is load.
  • Resell Klor as your own configuration service.

We may suspend an account that is doing any of this, and will tell you why where we can.

Availability

We aim to keep Klor up and we design for it: the read plane your apps depend on holds no database and serves from a distributed store, so a dashboard outage does not stop your apps reading config, and the SDK keeps serving its last snapshot when the network is gone.

That said, there is no service level agreement and no uptime guarantee. Klor is provided as it is. Build with fallbacks; the SDK requires one on every read for exactly this reason.

Plans and payment

Klor has a free plan and paid plans, described on the pricing page. Paid plans are monthly subscriptions that include a number of config reads, with reads above that billed per million at the end of each period. Usage is counted from the requests our servers answer.

Payments are processed by Polar (polar.sh), who act as merchant of record: they sell you the subscription, charge you, and handle sales tax and VAT, under their own terms. You can cancel at any time from Manage billing in settings, and the plan continues to the end of the period already paid for. Fees already paid are not refunded, except where the law requires it.

We never stop serving your configuration because of billing. Going over a plan’s included reads, or a failed payment, never cuts your apps off. If a payment fails, the workspace can fall back to the free plan and its limits in the dashboard.

Changes to the service

We will add things, and occasionally remove them. If we have to make a breaking change to the wire format or the SDK, we will version it rather than break applications already in the field, because a shipped mobile binary cannot be patched to keep up with us.

Ending it

You can delete your account whenever you like, from settings, without contacting anyone. We may close an account that breaches these terms. If we ever shut the service down, we will give reasonable notice and time to export.

Liability

To the fullest extent the law allows, Klor is provided without warranties of any kind, and we are not liable for indirect or consequential loss, lost profits, or lost data. Nothing here limits liability that cannot legally be limited.

Contact

Questions about these terms: support@klor.dev.