Legal.

1. What this covers

This explains how I-Ops handles information collected through this website, the private access process, and related correspondence. It does not describe how your own copy of the product handles your files. That is section 4.

2. What this website collects

This website sets no cookies at all. No advertising cookies, no tracking pixels, no third-party analytics, and nothing that follows you to another site. Nothing is collected from you here until you choose to fill in a form. That is also why there is no cookie banner: asking your consent for something that does not happen would be theatre.

One exception, and it is a real one. The private download pages keep your verified access code in your browser’s session storage, so that entering it once carries you to the download page. It is strictly functional, it never leaves your browser, and closing the tab erases it. We mention it because a page claiming to store nothing, while storing something, is worth less than a page that tells you exactly what the something is.

When you submit the private access form or the partner form, we receive what you typed:

• Your name and email address.
• Your role, company or project, and location, where you provide them.
• A LinkedIn or GitHub link, if you choose to include one.
• Anything you write in the free text fields.

Our hosting provider keeps ordinary server logs, which include IP addresses and request times, as any web host does. We do not use those logs to build a profile of you.

3. Where form submissions go

Form submissions are delivered to a spreadsheet we control, hosted by Google. Google acts as a processor for that data and its own terms apply to the storage. We name this because a privacy policy that says we hold your data, while a third party actually holds it, is not a description of what happens.

Website hosting and the early access download are served by our infrastructure providers, who see request metadata in the ordinary course of delivering the page or the file.

The two typefaces are served from our own origin rather than from a font service, so reading this site contacts nobody but us. There are no third-party requests on any public page: no font host, no analytics, no embedded media, no social widgets. You can check that in your browser’s network panel rather than taking our word for it.

4. The product, and your files

The product is designed to run on your own machine. Your files stay where they are. Content does not leave your machine except to endpoints you configure, and each run records the setting it executed under, so the posture is a fact you can check rather than a promise you have to take.

There is no default-on telemetry that carries the content of your work. If we ever offer a setting that widens where processing happens, it will be explicit, per workspace, and off until you turn it on.

We do not collect the contents of your business files through this website.

5. How we use what you send

• To reply to you, and to run the access or partner conversation you started.
• To tell you about availability, builds, and changes that affect you, and to send you occasional updates about I-Ops and what we release. Every such message carries a way to stop receiving them, and one reply asking us to stop is enough.
• To understand what people need, so the product is shaped by real work.
• To keep the service secure and to prevent misuse.

We do not sell personal information, and we do not share it for advertising.

6. Sharing

We share information only with service providers who need it to operate the site and communicate with you, such as hosting, form storage, and email. We may disclose information where the law requires it, or to protect the rights and safety of people using the service. If the business is ever sold or merged, information may transfer with it, and this policy follows the data.

7. How long we keep it

We keep enquiry and contact information for as long as the conversation is live and for a reasonable period afterwards, so that we can pick it back up and meet our record-keeping obligations. Ask us to delete it and we will, unless we are required to keep it.

8. Your choices

Write to hello@i‑ops.dev to see, correct, export, or delete the information you have sent us. Depending on where you live you may have additional rights, including the right to object to processing or to complain to a supervisory authority. We honour those requests wherever they apply, and we do not require you to invoke a specific law to be taken seriously.

9. Security, stated honestly

We take reasonable technical and organisational measures to protect what you send us. No transmission over the internet and no storage system is completely secure, and anyone who tells you otherwise is selling something.

10. Children

This is a product for businesses. It is not directed at children, and we do not knowingly collect information from anyone under 16.

11. Changes

We may update this page. The date at the top moves when we do. Material changes that affect people who have already contacted us will be sent by email rather than only posted here.

12. Contact

Privacy questions go to hello@i‑ops.dev.

1. Agreement

By using this website, requesting private access, or running a build we provide, you agree to these terms. If you do not agree, do not use them. If you are agreeing on behalf of a company, you confirm you are allowed to bind it.

2. Access is invited, and it can be withdrawn

Access may be limited, invite-based, or subject to approval. We may grant, pause, narrow, or revoke access at our discretion while the product is early. Access codes are issued to a person, not to a company, and are not to be shared or published.

3. Product status

What we provide is a preview, pilot, or early access build. Features will change. Some will be incomplete, some will be delayed, and some will be removed after we learn something. Nothing here is a commitment that any particular feature will ship, or ship on a date.

4. Acceptable use

You agree not to:

• Attempt unauthorised access to systems, accounts, or data.
• Interfere with the operation or security of the service.
• Reverse engineer, decompile, or attempt to derive source code, except where that right cannot lawfully be restricted.
• Resell, sublicense, rent, or provide the product as a service to a third party.
• Use the product for unlawful activity, or to build a competing product.
• Process content you do not have the right to process.

5. What you remain responsible for

You are responsible for reviewing outputs before acting on them, for how you configure the product in your own environment, and for approving anything that touches your files, systems, or business.

Outputs produced with the help of a model may be incomplete or wrong, and should be read by a person before they are relied on. The product is built to make that review possible and to check work independently. It is not a substitute for your judgement, and no part of it should be treated as legal, financial, medical, or professional advice.

6. Regulated and sensitive data

Do not put health records, payment card data, government identity numbers, or other regulated categories into an early access build unless we have signed an agreement that specifically covers it. We will tell you plainly when we have not, rather than accept the data and work it out afterwards.

7. Your content, and your licence to us

You keep all rights in your own files and data. We claim nothing in them. We do not acquire a licence to your content by virtue of your using the product, and where the product runs locally we do not receive that content at all.

8. Our intellectual property

The website, the product, its design, its interfaces, the underlying software and methods, and the I-Ops name and marks belong to I-Ops Operations Intelligence LLC or its licensors. You get permission to use the product under these terms. You do not get ownership, and nothing here transfers any right by implication.

9. Feedback

If you send us suggestions, requests, bug reports, or ideas, we may use them without restriction, without payment, and without attribution. Feedback does not become confidential to you, and giving it does not give you any right in the product. This is section 5 of the partner terms as well, and it is deliberate in both places.

10. Third parties

The product can connect to services you configure, and can run models you choose. Those are governed by their own terms and we are not responsible for them. Choosing to route work to an external provider is your decision and changes what leaves your machine.

11. Disclaimers

The website, early access materials, and product previews are provided as is and as available, without warranties of any kind, express or implied, including merchantability, fitness for a particular purpose, and non-infringement. We do not warrant that the service will be uninterrupted, error free, or suitable for any particular use.

12. Limitation of liability

To the maximum extent the law allows, I-Ops will not be liable for indirect, incidental, special, consequential, or punitive damages, or for lost profits, lost data, or business interruption, arising from the website or the product. Our total liability for any claim will not exceed the greater of the amount you paid us in the twelve months before the claim, or one hundred US dollars. Early access is typically provided at no charge, so that figure is usually the latter, and we would rather say so than bury it.

13. Indemnity

You will defend and indemnify us against claims arising from your use of the product in breach of these terms, or from content you had no right to process.

14. Termination

Either of us may end this at any time. On termination you stop using the product and delete any build we gave you. Sections 7 to 13 survive.

15. Governing law

Where you and I-Ops have a signed agreement, the governing law and the venue named in that agreement control, and they control over this page. We do not fix a single jurisdiction here in advance, because the right one depends on who is signing and where.

Where there is no signed agreement, these terms are governed by the laws applicable at I-Ops Operations Intelligence LLC’s principal place of business at the time the claim arises, without regard to conflict of law rules.

16. Changes

We may update these terms. The date at the top moves when we do, and continuing to use the service after a change means you accept it.

17. Contact

Questions go to hello@i‑ops.dev.

These apply from the first conversation until a signed agreement replaces them. They exist so that both sides know where they stand before anyone has signed anything, which is the part most early-stage companies leave vague and then regret.

1. Nothing here is an agreement

This page, the partner form, our emails, our calls, a demo, a proposal, a shared document, and anything either of us says in conversation create no binding obligation on either side. Only a written agreement signed by both parties does that. No exclusivity, no commitment to buy, no commitment to supply, no commitment to build anything, and no obligation to proceed at all.

Either of us can stop talking at any point, for any reason, without liability.

2. What a design partner engagement is

A design partner gives us a real workflow with real constraints, and gets the product shaped around it, a direct line to the person building it, and visibility into what we find, including the parts that do not work.

What it is not: a guarantee that any specific request is built, a reserved position in a market, a pricing commitment, or a promise of continued access. Design partner access is normally provided at no charge, and that does not create an entitlement to future access or to any particular price.

3. Confidentiality, both ways

Information either side marks as confidential, or that a reasonable person would understand to be confidential, is to be kept confidential and used only for evaluating whether to work together. That binds both of us equally.

It does not apply to information that is already public, that the receiving side already had, that it develops independently, or that it receives lawfully from someone else. Where disclosure is required by law, the disclosing side gets notice first where that is lawful.

This obligation lasts three years from disclosure. Trade secrets stay protected for as long as they remain trade secrets.

4. Intellectual property does not move

We own the product, the runtime, its architecture, its interfaces, the methods behind it, and everything we create before, during, or after an engagement. You own your data, your business content, and your own systems. An evaluation, a pilot, or a design partner engagement transfers no ownership in either direction, and grants no licence beyond what is needed to run the evaluation itself.

Work we do during an engagement, including anything built in response to what we learn from you, belongs to us. That is the point of the arrangement and it is stated here rather than assumed.

5. Feedback belongs to us to use

Suggestions, requests, critiques, bug reports, feature ideas, and anything else you tell us about the product may be used by us freely, without restriction, without payment, and without attribution. Feedback is not confidential to you, and giving it creates no ownership interest, no co-authorship, and no claim on the product.

This is deliberate and it protects both of us. Without it, a company that suggested an improvement could later claim a stake in a product thousands of other people use.

6. Your data during an evaluation

Use synthetic or non-sensitive material for a first look. Do not put health records, payment card data, government identity numbers, privileged material, or other regulated categories into an evaluation before we have a signed agreement that specifically covers that category.

We will say no to receiving regulated data we are not covered for. That will sometimes slow a conversation down, and it is the correct answer every time.

7. Neither side uses the other's name without asking

We will not name you, use your logo, or describe you as a customer or partner in public, to investors, or in marketing without your written consent. The same applies to you about us. Consent for one use is not consent for every use.

8. No conflict, and no poaching clause here

We work with more than one company, sometimes in the same industry, and we are not restricted from doing so. Nothing here prevents either side from working with anyone else, and nothing here restricts hiring.

9. Costs

Each side carries its own costs during evaluation unless a signed agreement says otherwise. Nothing on this page obliges either side to pay the other anything.

10. What replaces this

When we do work together, a signed agreement sets out the actual terms: scope, data handling, service levels, support, fees, term, and liability. That agreement supersedes this page entirely for everything it covers. Until it is signed by both sides, this section is what applies, and nothing more has been agreed.

11. Getting started

The partner page is the way in, or write to hello@i‑ops.dev. Everything reaches one person and gets a reply.