Rename app from oAI to Confab

"oAI" reads as easily confused with OpenAI, both visually and in
casual conversation. Renamed to "Confab" throughout: Xcode
target/scheme/bundle ID (com.oai.Confab), Info.plist and Help Book
identity, all user-facing UI text, internal Log subsystem and color
identifiers, localization catalogs (6 languages, including a proper
reworded/retranslated Intel-deprecation notice), Help Book HTML
content, and docs (README/DEVELOPMENT/PRIVACY/SECURITY).

Deliberately cosmetic-only: the on-disk data folder
(~/Library/Application Support/oAI/), database/backup filenames,
Keychain service identifiers, and EncryptionService's key-derivation
inputs are all left untouched so existing conversations, settings,
and stored API keys survive the update with zero migration and no
re-entering credentials. Verified live: a real signed build
successfully decrypted a stored API key and loaded an existing
conversation database after the bundle ID change.

Also includes a small already-completed, previously uncommitted
model-release-date feature (ModelInfo/OpenRouterModels/
OpenRouterProvider/ModelInfoView) that happened to share several
files with this rename.

Gitignored on this branch and updated on disk but not part of this
commit: CLAUDE.md, RELEASE_NOTES.md, and the build*.sh scripts.
This commit is contained in:
2026-08-02 14:58:14 +02:00
parent ae3de3d927
commit 76b58e6fdc
121 changed files with 987 additions and 692 deletions
+15 -15
View File
@@ -2,38 +2,38 @@
**Last updated:** 2026-07-27
oAI is a native macOS app. This document describes what data it handles, where it goes, and what control you have over it.
Confab is a native macOS app. This document describes what data it handles, where it goes, and what control you have over it.
## Summary
- oAI does not collect analytics, telemetry, crash reports, or usage data of any kind. There is no tracking SDK in the app, and the developer has no visibility into how you use it.
- Everything oAI stores — conversations, settings, command history — stays in a local SQLite database on your Mac, unless you explicitly enable a sync or backup feature.
- Confab does not collect analytics, telemetry, crash reports, or usage data of any kind. There is no tracking SDK in the app, and the developer has no visibility into how you use it.
- Everything Confab stores — conversations, settings, command history — stays in a local SQLite database on your Mac, unless you explicitly enable a sync or backup feature.
- The only data that leaves your Mac is data you choose to send: messages sent to the AI provider/model you've selected, and, for optional integrations you turn on yourself (email, Anytype, Paperless-NGX, external MCP servers), whatever those specific features are configured to talk to.
- oAI is free and open source. You can read exactly what it does at **https://gitlab.pm/rune/oai-swift**.
- Confab is free and open source. You can read exactly what it does at **https://gitlab.pm/rune/oai-swift**.
## Data stored locally
oAI keeps its data in a SQLite database at `~/Library/Application Support/oAI/oai_conversations.db`:
Confab keeps its data in a SQLite database at `~/Library/Application Support/oAI/oai_conversations.db`:
- Saved conversations and messages
- App settings and feature toggles
- Command history (last 5,000 entries, auto-pruned)
- Email processing logs, if the email assistant feature is used
Log files (no message content, no credentials) are written to `~/Library/Logs/oAI.log` for troubleshooting.
Log files (no message content, no credentials) are written to `~/Library/Logs/Confab.log` for troubleshooting.
None of this is sent anywhere by oAI itself. Deleting the database file (or uninstalling the app) removes it.
None of this is sent anywhere by Confab itself. Deleting the database file (or uninstalling the app) removes it.
## API keys and credentials
- Provider API keys (OpenRouter, Anthropic, OpenAI, Google) are stored in the macOS **Keychain**, not the database, and not in plaintext anywhere on disk.
- A small number of other credentials that can't use Keychain directly (e.g. email account password, if you set up the email assistant) are stored **encrypted at rest** in the local database, using a key derived from your Mac's hardware identifier — this key never leaves your device and isn't transmitted anywhere.
- oAI never transmits your API keys or credentials to anyone other than the service they belong to (e.g. your OpenRouter key is only ever sent to OpenRouter's API).
- Confab never transmits your API keys or credentials to anyone other than the service they belong to (e.g. your OpenRouter key is only ever sent to OpenRouter's API).
## AI providers — where your messages actually go
oAI is a client for AI providers you choose and configure yourself: OpenRouter, Anthropic, OpenAI, Google, Ollama (self-hosted, stays local), and Apple's on-device Foundation Models (macOS 26+, never leaves your Mac). When you send a message, its content — plus whatever conversation history and system prompt context oAI includes — is sent to whichever provider and model you have selected for that conversation.
Confab is a client for AI providers you choose and configure yourself: OpenRouter, Anthropic, OpenAI, Google, Ollama (self-hosted, stays local), and Apple's on-device Foundation Models (macOS 26+, never leaves your Mac). When you send a message, its content — plus whatever conversation history and system prompt context Confab includes — is sent to whichever provider and model you have selected for that conversation.
Each provider handles that data under its own privacy policy, over which oAI has no control:
Each provider handles that data under its own privacy policy, over which Confab has no control:
- OpenRouter: https://openrouter.ai/privacy
- Anthropic: https://www.anthropic.com/privacy
- OpenAI: https://openai.com/privacy
@@ -50,14 +50,14 @@ The following are **off by default** and require you to explicitly enable them i
- **Bash command execution** — lets the AI run shell commands on your Mac. Off by default; when on, can optionally require your approval before each command runs.
- **MCP file access** — lets the AI read/write files in folders you explicitly allow. Includes PDF text extraction. Folder access is scoped to what you approve, nothing outside it.
- **Email assistant (IMAP/SMTP)** — polls a mailbox you configure and can send AI-generated replies. Your mail server credentials and the email content it processes are stored locally as described above; email content is sent to your selected AI provider to generate a response.
- **Anytype / Paperless-NGX integrations** — connect to instances you run yourself (typically on your own network or self-hosted server). Data flows directly between oAI and your own instance.
- **External MCP servers** — you can connect any third-party MCP server of your choosing; oAI has no visibility into or control over what that server does with data passed to it.
- **Anytype / Paperless-NGX integrations** — connect to instances you run yourself (typically on your own network or self-hosted server). Data flows directly between Confab and your own instance.
- **External MCP servers** — you can connect any third-party MCP server of your choosing; Confab has no visibility into or control over what that server does with data passed to it.
- **Semantic search / embeddings** — if enabled, message text is sent to your selected embedding provider (OpenAI, OpenRouter, or Google) to generate vector embeddings, which are then stored locally.
- **Web search** — when online mode is enabled, your query may be sent to DuckDuckGo, Google Search, or included as `:online` context to OpenRouter, depending on configuration.
## Crash reports
oAI does not include any crash reporting or analytics SDK, and does not automatically collect or transmit crash data. If oAI crashes, macOS writes a local crash log to your own Mac (viewable in Console.app), but it is not sent to the developer automatically — Apple's automatic crash-sharing pipeline for Developer IDdistributed apps like oAI (i.e. not sold through the Mac App Store) does not route reports back to the developer. If you'd like to help fix a crash, you're welcome to attach that log when reporting an issue — see `SECURITY.md` / the contact link below for how.
Confab does not include any crash reporting or analytics SDK, and does not automatically collect or transmit crash data. If Confab crashes, macOS writes a local crash log to your own Mac (viewable in Console.app), but it is not sent to the developer automatically — Apple's automatic crash-sharing pipeline for Developer IDdistributed apps like Confab (i.e. not sold through the Mac App Store) does not route reports back to the developer. If you'd like to help fix a crash, you're welcome to attach that log when reporting an issue — see `SECURITY.md` / the contact link below for how.
## iCloud backup
@@ -73,11 +73,11 @@ Since everything is local, you're always in full control:
## Children's privacy
oAI is not directed at children and does not knowingly collect data from children.
Confab is not directed at children and does not knowingly collect data from children.
## Changes to this policy
If oAI's data handling changes in a meaningful way, this document will be updated and the date at the top revised. Given the app's local-first design, we don't expect that to happen often.
If Confab's data handling changes in a meaningful way, this document will be updated and the date at the top revised. Given the app's local-first design, we don't expect that to happen often.
## Contact