Developer terms · v1
Developer terms
Last updated: June 2026 · v1 (one-pager). A lawyer-reviewable v2 will follow.
Konshus is operated by Responsible Intelligence Labs LLC.
1. You must use Konshus OAuth.
No scraping. No credential reuse. No shared tokens between members. Every member you serve must complete the Konshus authorization flow on their own.
2. You must honor revocations within 24 hours by deleting all member data you pulled.
When a member revokes your app's access on vault/connections, your token stops working immediately. You then have 24 hours to delete every piece of data you pulled from that member's Vault — atoms, artifacts, Whisper, Briefing, relationship recall, derived embeddings, summaries, anything. This is modeled on the Google Calendar API's revoke obligation. We can't reach into your servers, so this term is the basis on which we let you connect.
3. You must not resell, share, or use member data to train any model.
Member data is the member's. Not yours. Not someone you sell it to. Not a model you fine-tune. Not a dataset you publish.
4. You must disclose to your users that data comes from their Konshus.
When your app surfaces context pulled from a member's Vault, the member should know that's what's happening. A line of UI is enough.
5. We may suspend or ban any app we become aware of violating these terms.
We can revoke your registered client at any time, with or without notice, if we believe in good faith you're violating any of the above. We may publicly list banned apps so members know who not to trust.
6. No warranty on the API itself.
Tools, scopes, and rate limits may change while this is in the early-access phase. We'll give reasonable notice for breaking changes once there are production integrations to protect.