Privacy Policy
What this website collects, what the product does with your files, and who to ask.
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.
I‑Ops Operations Intelligence LLC, registered in Delaware. Mail reaches us at 2261 Market Street, STE 91631, San Francisco, CA 94114, US — a mailing address only, not an office, so please do not visit. Email is faster: ashwinth@i-ops.dev.