Your relationship memory
Kluro saves the information you connect or add in an encrypted database on your Mac. This includes conversations, people, notes, events, remembered context, search data, reminders and corrections.
Your account and subscription records are separate from this relationship memory.
Source connections
You choose the accounts and local sources Kluro can read. Google connections use the permissions shown by Google. Apple sources use the applicable macOS permissions; protected local Mail or Messages data may require Full Disk Access.
Source credentials are handled by the connection machinery, not sent to a language model as conversation context.
Google user data
Kluro’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Gmail and Google Calendar data you connect is used only to provide the features you use in Kluro: remembering your conversations and events, and answering your own questions with the source behind the answer. It is not sold, not used for advertising, and not used to develop, improve, or train generalized AI or machine-learning models. When you ask a question or enable AI understanding, relevant excerpts may be processed by Kluro’s model providers solely to produce that result for you. People do not read your Google data unless you ask for help with it, it is necessary for security or legal compliance, or it has been aggregated and anonymized for internal operations.
Hosted AI processing
Enabled AI understanding may send relevant text, selected media, the user’s question, and necessary contextual metadata through Kluro’s managed route to its model providers. The selected stack uses Microsoft/Azure GPT routes, Google model routes, and TypeSafe Jev for their respective tasks.
This includes both interactive requests and background understanding. Over time, background processing can cover substantial eligible history. The absence of a cloud canonical database does not mean that no content is processed remotely.
Provider retention and handling follow the configured service. Kluro does not assert universal zero retention or local-only processing.
Account, payments, and support
Account services use device identity, authentication, plan, and operational information to provide access. Payment handling uses the configured payment provider; subscription records are not your relationship memory.
Support receives information you intentionally send. Please do not send credentials, private conversation archives, or your complete local database in a routine help request.
This website
This website does not connect to your accounts or send the text shown in its interactive stories to AI services. Its stories run locally in the browser. On kluro.ai, Google Analytics measures visits and a small set of actions such as download-link clicks. It does not receive the conversations shown here or what you type into the app illustration. Advertising signals are disabled; page URLs are sent without query strings or fragments. Local copies and preview hosts do not load Google Analytics.
Following an external download, support, or source link takes you to that destination, where its own handling applies.
Removing and exporting information
You can disconnect sources and remove imported data through Kluro. Disconnecting access and deleting a local copy are distinct actions. Corrections and removals also need to propagate to related search and derived context.
Exports and backups saved outside Kluro remain under your control. Removing an item from the app cannot erase a copy you exported elsewhere or retroactively unsend an earlier provider request.
Contact
For a privacy question or request, contact kwon@kluro.ai. This policy describes the product’s data-handling design and the website’s operation; the permissions you grant remain visible in the connection experience.