Privacy policy.

01Who this policy covers

This policy describes the omai desktop plugin and this website, maintained by pablousx. omai is an independent open-source project. It does not run a hosted configuration service or require an omai account.

02What the plugin accesses

omai reads supported global configuration for Codex, Claude Code, and OpenCode: instructions, rules, text skills and resources, selected settings, MCP declarations, and supported hooks, agents, commands, and plugin declarations. It can also manage a non-secret personal text file that you explicitly enroll.

Connection settings, provider choices, computer labels, sync timestamps, conflict decisions, and recovery records are stored locally. Project configuration, account and credential stores, sessions, histories, and caches are excluded from the synchronized source.

omai uses your existing Git and SSH authentication. It does not ask for AI-provider passwords or copy their account databases. Credential literals identified by its content checks stay local; those checks are not a guarantee that arbitrary text contains no secrets.

03Where data goes

Without a configured remote, reconciliation stays on your computer. With a remote, validated files in ~/.config/omai/source/ and their Git history are sent to the Git destination you choose. People and services with repository access may read that content. Public repositories make it public.

The project maintainer does not receive your configuration simply because you use omai. Your Git host handles repository contents, authentication, and connection metadata under its own policies. Git commits use the application identity omai <omai@localhost>; your computer labels are local annotations.

Installation and updates may contact GitHub for the plugin or release assets. An optional source build may contact Go module and toolchain distributors. The AI providers and any MCP servers you run have their own data practices; omai does not operate those services.

04Local storage and retention

Configuration is stored under ~/.config/omai/, the executable and Git repository under ~/.local/share/omai/, and recovery/state records under ~/.local/state/omai/. Custom XDG base directories are respected.

Local recovery records can contain full preimages of mixed configuration files, including local fields that are not eligible for Git sync. Keep those records private. They are not uploaded as sync inputs.

Automatic recovery cleanup defaults to 30 days, 100 journals, and 512 MiB. Pending or unreadable records and the latest rollback generation are protected, so usage can exceed those limits. These limits do not delete Git history from your local or remote repository.

05Your choices and controls

You choose the repository and its access rules. You can pause or stop sync, inspect your source, change supported settings, review conflicts, and use local recovery through the plugin.

Clear settings (keeps configs) stops sync and removes omai’s connection settings and preferences. It keeps provider files, canonical source, Git history, and recovery records. Removing the bar plugin alone does not stop the companion service.

To remove stored data, first stop the service, then use the operations guide to review the local paths. Delete remote repositories or history through your Git host separately. Removing a file from the current source does not erase earlier Git commits.

06This website

The site is static HTML, CSS, and JavaScript hosted with GitHub Pages. Its code uses no advertising, analytics, tracking pixels, cookies, external font services, or embedded third-party content.

If you change the color theme, the site stores only that choice in your browser’s local storage under omai-theme. It is not sent to the maintainer and can be removed by clearing site data. Copy buttons access the clipboard only when clicked.

GitHub may process technical information such as IP addresses and request logs to serve and secure the website. See GitHub’s Privacy Statement. Following an external link takes you to a service with its own policies.

07Support and privacy requests

If you open a GitHub issue or send information to the maintainer, that information is used to respond to your request and maintain the project. Public issues are visible to others. Do not include credentials, private configuration, or recovery journals.

For a privacy question, use the contact options on the maintainer’s GitHub profile or open a minimal issue requesting a private channel. For vulnerabilities, follow the security reporting instructions. The maintainer cannot remove data held independently by your Git host or AI providers; contact them for those requests.

08Policy changes

Updates to this policy will appear here with a revised effective date. Material changes to the project’s data handling will be described in its release documentation.