What stays.
What is processed.

Local memory, source connections, and AI processing have different jobs. Here is the distinction.

Your sources and your Mac

Chosen source providers supply available history to Kluro’s local memory. Local Apple sources are read on the Mac under their permissions. A provider account and the saved local copy are separate.

AI understanding

Interactive questions and enabled background enrichment send bounded content through the appropriate managed model route. Microsoft/Azure handles the selected GPT tasks; Google handles embeddings and selected multimodal work; TypeSafe handles selected Jev judgments.

Representations and useful derived understanding are stored with the local memory. Background work can cumulatively process earlier history, not only the latest question.

Account and subscription

The account service handles device access, plan state, and the operational records required to run the service. Payment processing is separate from your messages and relationship history.

The website

The website’s interactive stories use bundled local content. They do not open your source accounts, call a model, register notifications, or complete purchases. Google Analytics measures public-site visits and selected buttons on kluro.ai. Page queries, fragments, conversation text and app inputs are excluded. Local copies and preview hosts do not load it. Download and support destinations are separate handoffs.

Your controls

Connection, removal, and processing choices belong in the app. The privacy overview and policy explain those choices in context.

Be the person
who remembers.

Download for Mac