Local processing
The browser receives a concept and rule knowledge base from Kerkito. Your text is analyzed client-side; raw content is not required by the knowledge API.
The text belongs to the person thinking it
The new architecture is designed to work without an account, tracker or sending content to an AI provider.
Explicit persistence
By default, the project remains in session memory. Local persistence is triggered voluntarily by the user. Server synchronization is not required for core operation.
No third-party AI
Kerkito does not call OpenAI, Anthropic, Google or another LLM to interpret content. A prompt can be exported later if the user chooses to work with an external tool.
No behavioral telemetry
No advertising pixel, tag manager or third-party analytics is loaded by the application. Hosting technical logs may still contain the usual network metadata required to operate the service.
Explicit local learning
Interpretation confirmations and rejections are stored only after an explicit user action. They remain on-device, can be cleared and are not used to build a remote profile.
Voice: a browser capability
Voice playback and dictation are optional. Kerkito detects what the browser exposes. When local recognition is available it is preferred; otherwise the interface states that the browser provider may process audio. Kerkito does not receive dictation audio.
Zero-Knowledge evolution
Encrypted synchronization can later be added with browser-side encryption. In that case the server stores ciphertext and cannot run semantic queries on encrypted content; that limitation must remain explicit.