Skip to content

Trust

Local by default. Plain about the rest.

How OmniConflux is designed to handle your data and access, what this website stores today, and where security reports go. Local by default, no landlord.

A closed glass vault with a round door wheel, a private local model glowing green-white inside

What stays on your machines

In the design, your code, files, on-device context and everything a local model reads or writes stay on hardware you own, agents work in git worktrees on your machines, results land in your own repositories, and no landlord holds a copy. OmniConflux is a desktop coding app for Omarchy, macOS on Apple silicon and Windows, version 0.3.0, in closed beta.

What leaves, and when

The first four rows describe the software design; version 0.3.0 is in closed beta.

You pick a cloud model for a task
The prompt and the code or files the agent sends go straight to that vendor, through its own tool on your machine or your own API key, under that vendor's terms. Not through us.
You publish a social post
The finished post goes to the network you connected, through that network's own sign-in. Bluesky uses an app password, and Substack and Medium use assisted publishing.
Your machines talk to each other
Fleet traffic between your own machines is designed to travel over an encrypted connection.
You sign in to OmniConflux
In the design, we hold your account email and sign-in identity so you can use the service.

The last two describe what this website does today.

You send a form on this site
We store what you entered, the time you sent it and an HMAC hash of your IP address for abuse prevention, and email your entry to our team so we can reply.
You pre-register for the closed beta
We store your email, agent goal, registration ID, registration time and form source, plus HMAC hashes of your IP address and browser user-agent for abuse prevention. One consent at registration covers the optional answers you choose to save. We record the consent time and wording version and store your saved fleet when you build one. If you give no country, we use the country from your connection. The product-email switch starts off; the text-message opt-in is separate and optional. Our team receives an email notification of your registration and any answers you saved.

Retention

Form submissions are kept so we can answer you, and are deleted on request. In the design, local work is not held by us, so there is nothing for us to retain. A full retention schedule will be published before launch.

Beta answers can include your role, company, team size, machines and operating systems, AI tools and plans, agent harnesses, security and privacy needs, referral source, and interview preference. We use them to plan the closed beta. Delete your registration and answers any time: email us. See the privacy page for the full list.

Access

Inside OmniConflux, only the people who answer requests can read form submissions. In the design, connected accounts use OAuth with PKCE, exact redirect matching and refresh rotation, so you can revoke any connection from the vendor's or network's own settings. Bluesky connects with an app password instead of OAuth. A managed fleet is planned, not live. It will run on your API keys or enterprise tokens, which you can rotate at any time.

A status beacon: a glowing orb on a mast sending out signal arcs

Vulnerability reporting

Email dev@omniconflux.com with the subject Security. The disclosure terms are in the information security statement on the legal page. Please keep details of a suspected issue private until we have fixed it.

Subprocessors

The list of services that process data on our behalf, and what each one does, will be published before launch.

Certifications

None claimed. Independent audits are on the roadmap. We list a certification here only after it is issued.

Questions

Does OmniConflux see my code?

Not by default, by design: code, files and local model work are designed to stay on your machines. When you choose a cloud model, that vendor receives what the agent sends it, directly from your machine.

Where are my API keys and vendor logins kept?

In the design, on your own machines, with subscription logins inside the vendor's own tool. By design, we never pass a personal seat login through a hosted backend.

Do you hold SOC 2 or ISO certifications?

No. We claim none today. Audits are on the roadmap, and this page will list a certification only after it is issued.

How do I report a security issue?

Email dev@omniconflux.com with the subject Security. The disclosure terms are in the information security statement on the legal page. Please do not post details of a suspected issue in public.