Every product needs constraints. Ours are three words: Accessible, Personal, Safe.
They are not marketing language. They are the standards we use when we are arguing internally about whether a feature should ship.
Accessible
If a feature requires a tutorial before it becomes useful, the feature has failed. If the language we use in the UI assumes the reader has a CS degree, we wrote it wrong. If the free tier does not cover what a curious person would want to try on a Sunday afternoon, we set the limits too tight.
Accessible is also a price question. $7 a month for Pro is a deliberate floor; below that, we cannot sustain the model costs, and above that, we exclude users we care about. The full pricing model is designed around this question.
Personal
One-size-fits-all is a synonym for “fits no one perfectly.” Arka adapts to the person in front of it — their language, their expertise, their tone, their goals — and gets more useful the more you use it.
Personal also means yours. Your memory is in your browser, not on our server. Your chats are not training data. Your projects are not visible to anyone but you.
Safe
Safety is not a feature we add at the end. It is a constraint we work within from the beginning. Arka has a constitution that defines what it should and should not do; the model is held to it through a system prompt; we audit responses for refusals that should have happened and refusals that should not have.
The most important safety promise: your data stays yours. We never sell it. We never train on it without your explicit opt-in consent. Read our privacy policy for the specifics. Trust is the entire product, and we treat it that way.