Legal and governance
Legal terms and policies
Legal terms, privacy policies, and acceptable use guidelines for OmniConflux. All documents below are drafts pending formal review and approval by legal counsel.
Draft pending counsel. Version 0.12, 12 November 2026.
Terms of Service (Draft pending counsel)
1. Who We Are and Acceptance: OmniConflux (we, us) operates omniconflux.com and publishes the OmniConflux software. The business is being organized as OmniConflux Inc., a Wyoming corporation, and this page will name the registered company and its address once that filing is complete. These terms cover the website, your account, the software, and Aura by OmniConflux. By creating an account, installing the software or using any of them, you agree to these terms. If you do not agree, do not use them.
2. Eligibility and Access: You must be at least 18. If you accept these terms for a company or organization, you confirm that you may bind it. Access is by closed beta: you join the waitlist, we approve accounts, and the download is inside the account of an approved person. Joining the waitlist does not promise access. You sign in with a link we email you, so keep your email account secure and tell us at once if someone else has used your account. One person, one account.
3. License to Software: Subject to these terms, OmniConflux grants you a revocable, non-exclusive, non-transferable license to install and run its client applications, orchestration daemons, command-line tools and fleet coordination utilities on computers you own or control. The software is licensed, not sold. A seat licenses one person, on as many of their own machines as they use.
4. User Ownership of Work Product: You keep full intellectual property ownership of all source code, software architecture, configuration files, prompts, data and artifacts that you provide or that agents produce in your private fleet. OmniConflux claims no ownership of, and no license to, code generated on your hardware, apart from what you choose to send us, for example in a support request. You are responsible for having the rights to what you put into the software.
5. Third-Party Models and Services: The software is designed to work with models and tools from many vendors and to let you use local models. When you use a third-party model, tool or service, you do so under that provider's terms, including any limits on automated use or account sharing, and you keep your own keys and logins secure. OmniConflux is not responsible for third-party services, their availability, their output or how they handle your data.
6. Review Before You Rely: AI models can be wrong. OmniConflux uses cross-model verification, which reduces but does not eliminate errors. You remain responsible for reviewing and approving any code, content or action before you deploy or rely on it. Do not use the software as the only safeguard where an error could cause injury, loss of life or serious financial or property damage.
7. Restrictions and Acceptable Use: You may not copy, modify, reverse engineer, decompile, sublicense, rent, resell or offer the software to others as a service, remove its notices, or get around its license or usage controls, except where the law or an open-source license allows it. Components released under open-source licenses are governed by those licenses. You must follow the acceptable use policy on this page.
8. Seats, Price and Billing: A seat costs 20 US dollars a month per person. The license is per person, not per machine: one person on five machines needs one seat, and a team of five people needs five seats. We do not take payment yet. When billing opens, a seat is billed monthly in advance and renews each month until you cancel. You can cancel at any time and keep your seat to the end of the month you have paid for. We do not refund part of a month unless the law requires it. Prices do not include taxes we are required to collect. We will give at least 30 days' notice of a price change, and it applies from your next renewal. Before the first charge we will show you the price, the billing date and how to cancel, and ask you to accept them.
9. Referral Credits: The referral offer is open only to founding members, meaning accounts that pre-registered during the closed beta. An account created after the closed beta ends cannot earn referral credits under it. If you are a founding member and someone joins through your referral link, you earn half of what they pay for their first seat month, and a tenth of the referral fee OmniConflux receives on what they buy in the marketplace for as long as they keep their account. Joining the waitlist earns no credit by itself. A credit is recorded in your Aura wallet when the payment that earns it has cleared, and it is reversed if that payment is refunded or reversed. Referral is one level only: you earn nothing from the people your referrals bring. Clause 10 says how credits can be used and paid out. We will post the date the closed beta ends on this page before it ends. We may change or end the offer for referrals made after the change, and we may withhold credits earned through fraud, self-referral or abuse.
10. Aura Wallet: The Aura wallet is a ledger on your account. It records referral credits under clause 9 and, if you turn Aura on, half of what the ads shown to you earn and half of each marketplace referral fee, credited when the payment behind it has cleared. A credit is pending until it clears, can be held for review, and is reversed if the payment behind it is refunded, reversed or found to be invalid. You cannot buy credits or add money to the wallet, and credits cannot be moved between accounts. The wallet is not a bank account or a deposit, and credits earn no interest. Earnings are never promised. Cleared credits can pay your OmniConflux seat or fund ad credit for your own campaigns on the Aura network. We plan to offer payout by ACH to a United States bank account in your own name through a licensed payment provider. Payout is not available yet. When it opens, a payout will need at least 10 US dollars of cleared credits and will be reviewed before it is sent, the provider will confirm your identity and collect your bank details, and we will collect and report the tax information the law requires. We will post the date here before payouts open. If you delete your account, its unused credits end with it. If we end your access for fraud, abuse or breach of these terms, we may cancel the credits earned through it.
11. Aura Advertising Network: Aura by OmniConflux is opt-in and off by default, and it runs for approved closed beta accounts. If you turn it on, short labeled ads appear in set places in OmniConflux, under the network governance rules published at /earn/network-governance, including the daily caps on credited views, clicks and earnings. Views and clicks you make on your own campaigns, automated activity and other invalid traffic earn nothing. Advertisers must follow the advertising policies published at /advertise/policies, every campaign is reviewed before it runs, and we may pause or remove any campaign. We do not bill advertisers yet. Before we do, advertisers will be asked to accept the price and payment terms for their campaign.
12. Beta Software, Updates and Feedback: OmniConflux 0.3.0 is beta software. We may update it, change or remove features, or require an update for continued use, and beta access can end. If you give us feedback, we may use it without restriction or payment.
13. Intellectual Property: OmniConflux and its licensors own the software, the website, and the OmniConflux and Aura by OmniConflux names and marks. These terms grant no rights other than the license in clause 3. The trademark guidance on this page says how you may use our names.
14. Disclaimer of Warranties: The software, the website and Aura are provided as is and as available, without warranties of any kind, express or implied, including merchantability, fitness for a particular purpose, non-infringement and the accuracy of AI output, to the fullest extent permitted by law. We do not warrant that they will be uninterrupted or free of errors.
15. Limitation of Liability: To the fullest extent permitted by law, OmniConflux is not liable for indirect, incidental, special, consequential or punitive damages, or for lost profits, lost data or business interruption, arising from the software, the website or Aura, including software execution, compilation errors, AI output, third-party services or local hardware interruptions. Our total liability for any claim is limited to the greater of what you paid us in the 12 months before the claim and 100 US dollars. Nothing in these terms excludes liability that the law does not allow to be excluded.
16. Termination: You may stop using the software and delete your account at any time. We may suspend or end your access if you breach these terms, if we must by law, or if the closed beta ends. When your access ends you must stop using the software and delete it. Clauses 4, 13, 14, 15, 19 and 20 continue to apply.
17. Export Controls and Sanctions: You may not use or export the software in breach of United States export control or sanctions law, and you confirm that you are not in a country, and are not a person, that those laws bar us from dealing with.
18. Changes to These Terms: We may change these terms. We will post the new version on this page with its version number and date, and tell you by email if the change is material and you have an account. If you keep using the software after a change takes effect, you accept it.
19. Governing Law and Disputes: These terms are governed by the laws of the State of Wyoming, without regard to its conflict of law rules. You and we agree to the exclusive jurisdiction of the state and federal courts located in Wyoming, except that either of us may ask any court for an order to stop misuse of intellectual property or confidential information. If you are a consumer, the mandatory protections of the law where you live still apply. Write to dev@omniconflux.com first, so that we can try to settle a dispute before either of us goes to court.
20. General: These terms, with the policies on this page, are the whole agreement between you and us about their subject. If a court finds part of them unenforceable, the rest stays in force. A delay in enforcing a term is not a waiver of it. You may not transfer your rights without our written consent; we may transfer ours to a successor of the business. No one else has rights under these terms.
21. Status and Contact: OmniConflux 0.3.0 is released for Omarchy, macOS on Apple silicon and Windows, and access is by closed beta. These terms are a draft pending review by legal counsel, and they apply to your use of the software from the time we give you access. We will ask you to accept the reviewed terms before any payment. Contact: dev@omniconflux.com.
Draft pending counsel. Version 0.12, 12 November 2026.
Privacy Policy (Draft pending counsel)
1. Who We Are and Scope: OmniConflux (we, us) decides how and why the personal information described here is used, and is its controller. Contact: dev@omniconflux.com. This policy covers this website and its forms, your account, the agent self-registration service, email with us, the OmniConflux software as described in clause 8, and Aura by OmniConflux as described in clause 9. OmniConflux 0.3.0 is released and access is by closed beta.
2. What We Collect: When you visit, our hosting and network providers process your IP address, browser type and the pages requested in standard server logs, so the site can be delivered and protected. We use Google Analytics to count visits and see which pages and links bring people here: it sets the cookies named in the cookie policy and sends page and device details to Google, with Google signals and ad personalization turned off. When you pre-register for the closed beta, we store your email address, the work you want your agents to do, a registration ID, the time, the form source, your saved fleet when you build one and your country as a two-letter code, taken from your connection when you give none. Each registration gets a place in line and a referral code, and if you arrive through someone's referral link we record which registration referred you. One consent at registration covers the optional answers you choose to save (your role, company or project, team size, machines and operating systems, AI tools and plans, agent harnesses, security and privacy needs, how you heard about us, or interview preference), which we store with a record of your consent. The product-email switch starts off; the text-message opt-in is separate and optional.
3. Other Forms and Agent Registration: If you write to us through a form, we store what you enter, the time, your country as a two-letter code and, if you choose to give one, a mobile number with your SMS consent choice. When an AI agent registers an owner for the closed beta, we store the agent's name, description and framework, an optional goal and the owner's details. We keep only one-way hashes of the agent's API key and claim token, and nothing is added to the beta list until the owner confirms by email.
4. Abuse Prevention: For forms and the agent registration service we store keyed one-way (HMAC) hashes of your IP address and your browser user-agent, not the raw values, to limit abuse and duplicate submissions.
5. What We Do Not Collect: We do not ask for passwords, API keys, tokens, subscription credentials, government identification numbers, payment card or bank account details, biometric data or precise location. Please do not enter them in any form. When payouts from the Aura wallet open, the payment provider will collect bank and identity details itself, and we will update this policy before then.
6. How We Use and Share It: We use this information to run the closed beta, answer you, confirm agent owners, keep the site secure, plan the product in aggregate, and send product email while your product-email switch is on. The switch starts off when you register. You can turn it on then, and turn it on or off at any time on your account page. Our service providers for hosting, DNS and network delivery, server and database hosting, email and website analytics process it for us under limits on their use. Our team and professional advisers see it as needed. We disclose it if the law requires, or in a merger or sale of the business. We do not sell personal information and we do not share it for cross-context behavioral advertising.
7. Retention, Access and Deletion: We keep a registration, its answers and its wallet ledger for as long as the account exists. If the closed beta ends and you have no approved account, we delete your registration within 12 months. We keep a form submission for up to 24 months. We keep records of consent, and records we need for tax, accounting or legal claims, for as long as the law requires. Our providers' server logs follow their own retention periods. You can change your details or delete your pre-registration yourself on your account page, which opens from a sign-in link we email you. To see, correct or delete a form submission, your pre-registration or an agent registration, you can also email dev@omniconflux.com, and we answer within one month. You can turn product email off at any time: from your account, or with the link each product email carries, which stops it in one press without a sign-in. You can pre-register with only your email and goal.
8. Software Data Practices: The software is designed so that work stays on machines you own. Code, files, prompts and local model work are designed to stay on the machine where they run, and your API keys and vendor logins are designed to stay on your machines and never pass through a hosted backend of ours. When you choose a cloud model for a task, the agent sends that vendor what the task needs, directly from your machine, through the vendor's own tool or your own API key, under the vendor's terms and privacy policy. Traffic between your own machines is designed to travel over an encrypted connection. To run your account we hold your account email, your sign-in identity and whether your account is approved. Optional features that connect to us or to another service, such as publishing a post to a network you connected or the Aura network in clause 9, send only what that feature needs, after you set them up. We will update this clause before the software sends us anything it does not describe.
9. Aura by OmniConflux: The Aura wallet is the ledger on your account where we record credits: the amount, its kind, its status, the time and, for a referral credit, the registration ID of the account whose payment earned it. No payment is taken yet, so no referral credit has been earned. If you delete your account, a credit someone else earned from your payment stays in their ledger with your registration ID, which then points to no stored details about you. The Aura advertising network is opt-in, off by default, and runs for approved closed beta accounts. If you turn it on, the topic of your work is classified on your own device against a fixed list of topics, and only coarse topic tags, and at most one short summary built from those tags, leave your machine to choose an ad. Source code, repository contents, file paths, prompts, replies, environment variables and keystrokes are never sent for ad matching, and the check that a person is present runs on your device. Advertisers receive no code, file paths, prompts or replies and no personal profile of you, and we do not track you across other sites or sell this data. We record the views, clicks and sales credited to your wallet so that the ledger can be checked.
10. Children: The site and the closed beta are for business and professional use and are not directed to anyone under 18.
11. Your Rights and Our Legal Bases: If you are in the European Economic Area, the United Kingdom, Switzerland or California, you may have rights to access, correct, delete or restrict the use of your information, to object, to move your data, and to withdraw consent. We rely on your consent for optional answers, product email, text messages and the Aura network; on steps taken at your request for your registration and account; on our legitimate interests in running and securing the beta, preventing abuse and counting visits; and on legal obligation where the law requires us to keep or disclose a record. Our systems are in the United States, so information is transferred there. Email dev@omniconflux.com to use your rights. We confirm a request by replying to your registered email address and answer within one month. You may also contact your local data protection authority.
12. Security and Incidents: The information security statement on this page lists the measures in place. If a security incident puts your personal information at risk, we will tell you and the authorities where the law requires it.
13. Changes: We will post any update on this page with its version and, if the change is material and you registered, tell you by email.
For the closed-beta form in full, read the privacy page.
Draft pending counsel. Version 0.10.
Information security (Draft pending counsel)
1. Scope: This covers the website, the content management system, the database and email. It does not describe the OmniConflux software, which is designed to keep work on your own machines.
2. Measures in Place: The site is served over HTTPS. IP addresses and user-agent strings are stored only as keyed one-way hashes, and agent API keys and claim tokens only as hashes. The website database and the content database are separate, with separate credentials, and secrets are kept out of source repositories. Administrative access to the content system requires a login. Forms and the content system are rate limited and validate their input. Published insights and changelog entries are immutable snapshots released through verification gates.
3. What We Do Not Claim: We do not currently hold third-party security certifications or audit reports, and no system is perfectly secure.
4. Report a Vulnerability: Email dev@omniconflux.com with the subject Security. Give enough detail to reproduce the issue, do not access or change other people's data or disrupt the service, and give us reasonable time to fix it before you disclose it. We do not run a paid bug-bounty program.
5. Your Part: Never enter credentials, API keys or other secrets in any form, and keep your own accounts and keys secure.
Draft pending counsel. Version 0.12, 12 November 2026.
Acceptable use policy (Draft pending counsel)
1. Defensive and Authorized Use Only: OmniConflux security tooling and agentic capabilities must be used solely for authorized system verification, defensive code audits, and legitimate software development.
2. Prohibited Activities: Users may not use OmniConflux to conduct unauthorized penetration testing, launch denial of service attacks, distribute malicious software, or bypass access controls on third-party systems without prior written consent.
3. Compliance with Laws: All operations conducted using the software must comply with applicable local and international computer crime statutes and export regulations.
4. Accounts and Third-Party Terms: Do not share a seat between people, create accounts by automated means, or use the software in a way that breaks the terms of a model, tool or service you connect to it.
5. Aura and Referrals: Do not view or click ads to earn from them, automate views or clicks, refer yourself, create accounts to collect credits, or run a campaign that breaks the advertising policies.
6. Enforcement: We may suspend or end access, remove a campaign, withhold or cancel credits earned through a breach, and report unlawful activity to the authorities.
Draft pending counsel. Version 0.12, 12 November 2026.
Intellectual property and trademarks (Draft pending counsel)
OmniConflux and Aura by OmniConflux are trademarks of the project. Any open-source components we release will be governed by their repository licenses. Brand assets, logos, and marks may not be altered or used in ways that imply official endorsement without permission. You may use the OmniConflux name to say truthfully that you work with us, but not as part of your own name, logo, domain, handle or product, and not more prominently than your own. If you believe something on this site infringes your copyright, email dev@omniconflux.com with the subject Copyright, and tell us what the work is, where it appears and how to reach you.
Draft pending counsel. Version 0.10.
Complaints (Draft pending counsel)
1. How to Complain: Email dev@omniconflux.com with the subject Complaint. Tell us the email address you used with us, what happened and what outcome you want. Do not include passwords or keys.
2. What We Do: We acknowledge your complaint promptly, look into it with someone not involved where possible, keep a record, and answer in writing. If you are not satisfied, reply asking for a senior review.
3. Other Routes: You may also contact the authority that applies to you, such as a data protection authority for privacy matters or your state consumer protection office.