← Back to Karamba
KARAMBA AI

App privacy notice

How the Karamba Mac app stores data and connects to the providers and tools you choose.

Last updated: . Karamba AI is currently in development; this notice describes its current app behavior.

The essentials

Karamba is a Mac client for AI services you choose. It has no Karamba account, telemetry, or hosted AI service. Chats are stored locally. Requests go directly to your selected provider or tool server using your configuration. We do not receive those requests through a Karamba server.

You decide which provider to connect, what context to add, and when to send it. Cloud provider usage is billed through your own provider account. Its handling of requests follows its policies, your API agreement, and your account settings.

Publisher and privacy contact

Karamba AI is published by the person below. In this notice, “we” refers to this publisher. We are responsible for personal information you provide to us, for example in a support enquiry.

Matthias Wissel
c/o MDC Management#4782
Welserstraße 3
87463 Dietmannsried
Germany

This page covers the app. Our separate website and support privacy policy describes website hosting, technical logs, and correspondence.

Information stored on your Mac

Karamba stores saved conversations locally in its Application Support folder. History can include messages, replies, included image or extracted file content, and retained message revisions. The current app keeps up to 50 saved conversations; older entries are removed as newer conversations take their place. It does not automatically delete history when a trial ends.

Provider settings, model lists, assistant instructions, custom actions, and app preferences are stored locally. Provider API keys and MCP sign-in tokens are stored in macOS Keychain. MCP configuration files in a folder you select may contain credentials you add, such as server headers or environment settings.

These records let you continue conversations, recover work, and reuse your selected configuration. Karamba does not sync them to a Karamba cloud service. macOS backups or copies you make may retain information separately.

Sending requests to an AI provider

When you press Send, Karamba sends your question, the active conversation, assistant instructions, and explicitly added context to the provider endpoint you selected. Context can include pasted clipboard text, extracted PDF or text content, and images where supported. Files may be extracted, scaled, or truncated as shown in the composer.

Custom actions prepare a request for you to review before Send. Karamba does not poll the clipboard, monitor your screen, or capture another app's selected text in the background.

Your API key is sent to the configured endpoint for authentication when required. That endpoint also receives the network information needed to handle the connection, such as your IP address. Changing the selected provider changes the destination of future requests.

Refresh models and Test connection are separate actions that contact the configured endpoint and send authentication credentials when needed. They do not send chat messages or attachments. A connection test checks endpoint reachability rather than sending a chat for generation.

Your provider's handling of data

You use cloud services through your own credentials and account. The selected service handles requests under its own terms and privacy information. Its retention, processing locations, and available controls depend on that service and your account configuration. A custom endpoint may be run by a different operator from the provider name you give it.

For the built-in cloud provider choices, see OpenAI's API data information and the OpenRouter privacy policy. For another compatible endpoint or tool server, consult its operator. Services may process data outside your country, including outside the European Economic Area; consult their applicable transfer information and account terms.

We do not operate a chat relay or hold a server copy of your conversations. If you want an external service to delete information it received, use its privacy contact or account controls. Deleting a chat in Karamba does not delete the service's copy.

On-device models and local servers

Apple's on-device Foundation Models processes chat requests on your Mac when the model is available on your device and system. This route does not need a cloud provider API key.

Ollama and llama.cpp process requests at the server address you configure. A server running on this Mac is local to it. A server on another computer receives the request there, even if you label the provider “local.” The server operator's settings and policies govern any logging or retention.

MCP tools and sign-in

Tool discovery connects to the MCP server you configure to request its tool list. Running a tool sends the arguments you confirm to that server and can carry out the action described by the tool. Karamba asks separately before discovery and execution.

Manual Run places returned text in the composer for review before Send. If a model requests a tool call, approved results are returned to the selected AI provider as the conversation continues. The provider can also receive descriptions of the tools enabled for that conversation.

Some remote servers require sign-in through their authorization service. Karamba opens that sign-in flow and stores resulting tokens in Keychain. The server and sign-in service receive information needed for their respective operations and have their own privacy rules.

Optional dictation

Dictation uses your microphone and Apple's speech-recognition service with system permission. Karamba requests on-device recognition when supported. Otherwise, Apple's speech service may process audio. The resulting text enters the composer for review before Send.

You can stop recording and revoke microphone or speech permission in System Settings. Typed chat remains available. See Apple's privacy information for its services.

Optional local diagnostics

Diagnostics are off by default. If enabled, Karamba keeps up to 100 error entries locally to help investigate problems; new entries replace the oldest. Entries include the time, source, and error message. Provider errors can contain sensitive details.

The app does not automatically upload this log. Turning diagnostics off stops new entries; use Clear in Settings → Diagnostics to delete existing entries. Review logs before copying or voluntarily sending them to support.

App Store purchases and restoration

Apple handles trial activation, purchase, and restoration through StoreKit. Karamba reads verified transaction information, including the product and purchase date, to determine access and the original trial start date. Purchase checks communicate with Apple's services. They do not send chat content as part of the purchase.

We do not receive your payment-card details. Apple manages its purchase records and account information under its own policies. App Store business reports may provide aggregate download and sales information; Karamba does not implement its own in-app analytics.

Resetting Karamba does not erase Apple's transaction history or start another trial. Use Restore Purchases with the Apple Account used for the original purchase.

Deleting data and changing your choices

  • Delete a conversation to remove it from saved history, or use Clear chat history to remove all saved conversations.
  • Delete all settings removes provider configuration, keys, and preferences while keeping chat history.
  • Reset and restart also removes history and local diagnostics. It does not delete an external MCP configuration file in the folder you selected; manage that file separately.
  • Stop using or remove a provider or tool server to stop future requests to it. For external sign-in access, you can also use that service's authorization controls.
  • Revoke microphone and speech permissions in System Settings, and turn off or clear diagnostics in Karamba.

Local deletion does not erase information already sent to a provider, tool server, Apple, or support, or copies in your backups and exports. Use the relevant recipient's controls or contact to request deletion of information it holds.

Information you send to support

The support action opens your email app with Karamba and macOS version information in a draft. It does not attach chats, API keys, provider configuration, or diagnostics. You review and send the message yourself.

If you send it, we receive your email address, message, and any details or attachments you include. Please leave out API keys, passwords, and private chat content, and check screenshots for sensitive details.

Support mail is forwarded by IONOS to a mailbox at netcup. Contract-related enquiries are handled under Article 6(1)(b) GDPR. Other enquiries are handled under Article 6(1)(f), based on our interest in answering questions and resolving problems. Where legal retention duties apply, Article 6(1)(c) applies. Correspondence is kept while needed for your enquiry and follow-up, then deleted unless legal retention duties or a specific legal claim require longer storage. See our website and support policy for the service providers and further details.

Privacy questions and your rights

For personal information we hold, you can request access, correction, deletion, restriction, or portability, and object to processing based on legitimate interests, subject to applicable GDPR conditions. Where processing relies on consent, you may withdraw it for the future. Email info@getkaramba.com to exercise these rights.

We cannot remotely read or delete data stored only on your Mac. The app's controls let you manage that data. Contact your selected provider, tool server, or Apple about information they hold under your account.

You can complain to a data protection authority, including the Bavarian State Office for Data Protection Supervision (BayLDA). We do not use support information for profiling or automated decisions with legal or similarly significant effects.

Changes to this notice

We will update this notice when the app's data handling changes. The date above identifies the latest revision. Opening links to our website follows the separate website privacy policy.