Skip to content

Privacy

Private by default.

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

Private by default is a design: local models and on-device context. Read the privacy principles behind the OmniConflux fleet and what the closed-beta form stores.

Local models

The design puts local models at the foundation of the platform. The fleet is designed around your machines, so privacy starts with where the work runs. A model that runs on your hardware is designed to keep its work there.

On-device context

The design keeps context on the devices in your fleet. This principle connects the workspace to the computing resources you own.

What leaves the machine, and when

Local model work is designed to stay on the machine it runs on. When you choose a cloud model for a task, the agent sends that vendor what the task needs, directly from your machine, under the vendor's terms. Your keys and vendor logins are designed to stay on your machines and never pass through a hosted backend. The trust page lists the designed data flows.

Open by design

Privacy includes the freedom to leave. OmniConflux is designed to work with any vendor, keep your work in your own git repositories, and let you swap a cloud model for a local one task by task. No landlord, no walled garden. Read more on digital sovereignty.

Closed-beta pre-registration

We use your email and the work you want your agents to do to plan the closed beta and email you about access. We assign a registration ID and record when you register and the form source. Further questions are optional.

Pre-registration asks one consent sentence covering the details you choose to provide. We store your answers and saved fleet, including the machines and operating systems you add. Optional answers can include your role, company, team size, AI tools and plans, agent harnesses, security and privacy needs, referral source, and interview preference. We record the consent time and wording version. The product-email switch starts off. The text-message opt-in is separate and optional. If you give no country, we store a country taken from your connection.

For abuse prevention, we store HMAC hashes of your IP address and browser user-agent, rather than the raw values. Your registration and answers are saved in our database first; our team then receives them by email. A signed registration cookie lets you continue the optional questions and open your account page from this browser for up to 30 days. If you arrive through a referral link, a second cookie holds that referral code for up to 30 days. Never enter keys, tokens or subscription credentials.

Delete your pre-registration and answers any time on your account page, or email us. Join the waitlist with just your email and goal.

Site analytics

This website uses Google Analytics to count visits and see which pages and links bring people here. It sets first-party cookies that tell one visit from another and sends page and device details to Google. Google signals and ad personalization are turned off, and Google Analytics does not log or store IP addresses. Visitors in the European Economic Area, the United Kingdom and Switzerland are asked before it starts, and anyone can change the choice on the cookie policy. Block it with Google's opt-out add-on or any content blocker; the site works the same either way. The token in a sign-in link is never sent to Google Analytics.

Understand the boundaries before connecting

Local models and on-device context describe the platform's privacy foundation. Data flows, permissions and supported integrations will be documented at launch so you can assess each connection.