Skip to main content

Legal

Privacy Policy

Last updated: September 25, 2026

In short. OpenEng is local-first. The work you do in the five engineering apps and with the OpenEng AI engine — your terminals, repositories, clusters, databases, chats, agents, memory, code, and secrets — runs on your own machine, and the five apps never send any of it to us. The personal data we handle is limited: the account information from Google sign-in, the keys that let your engines start, what you save in the Console, the approval requests your engine registers if you use Human-in-the-Loop, what passes through the Web Console (your requests, and the engine data it loads, such as thread history and memory, which our Broker routes between your browser and your engine and keeps for 7 days by default), requests to the included Cloud Planner, paid from planning credit, which pass through our API, your subscription state (payments are processed by Razorpay), feedback and email you send us, and basic analytics on this website. We never sell your data.

1. Who we are & what this covers

This Privacy Policy explains how OpenEng Labs Private Limited, Bangalore, Karnataka, India (“OpenEng”, “we”, “us”, or “our”) handles personal information across the OpenEng products and services (collectively, the “Services”):

You can reach us at hello@openeng.app. By using the Services you agree to this Policy. If you do not agree, please do not use the Services.

2. Information we collect

2.1 Account information (when you sign in)

Signing in is handled by Google Sign-In through Firebase Authentication (a Google service), and one OpenEng account works across the Services. When you choose to sign in, we receive from your Google account: your name, email address, profile picture, and a unique account identifier. We do not receive your Google password. We use this to create and secure your OpenEng account, to identify you across the Services, to pair your browser with your local engine, to manage your subscription, and to respond to you. We do not sell it or use it for advertising.

2.2 Engine keys and sessions

Your engines run on your machine, but they need to know it is you:

  • Engineering apps. When you start an app’s engine, the app asks our API for a one-time key tied to your account and shows it in the start command. The engine exchanges that key for a short-lived access token and a rotating refresh token (valid for up to 30 days), which it keeps on your machine (under ~/.openeng/<app>/). Our API records the keys it issues so it can verify and refresh them.
  • OpenEng AI. The AI engine starts with an OpenEng key — an API key you create in the Console. We store only a hash of each key; you see its value once. When the engine starts, it registers the key with our API, which checks your plan and records an engine session (an engine identifier and the engine’s public key) so the Broker can route your requests to it. While it runs, the engine also presents the key to fetch your published configs and to check for updates, and it polls our API for approval requests about once a second.
  • Update checks. Engines contact our release service to check for a newer version. The app engines check when they start and every 30 minutes while they run, and send no credential. The AI engine checks when it starts and periodically while it runs, authenticated with its OpenEng key. Neither sends content from your work.
  • The Terminal engine’s suggestion model. The Terminal engine downloads a small embedding model (BGE-small-en-v1.5, about 130 MB) from Hugging Face once, for command suggestions. Hugging Face sees an ordinary download request, including your IP address. The Kubernetes and Data engines make no such download.

2.3 Console configurations, files, and preferences

When you use the Console, we store what you create there: the configurations you build and publish (models, agents, templates, loops, schedulers, and their settings), the files you attach to agents or templates (up to 10 MB each, kept in our cloud storage), your plan status, and your preferences, such as the theme, so they apply wherever you sign in. This is tied to your account identifier. Configs refer to secrets only by ${ENV} placeholder name — the Console and our servers reject raw secret values in a config, and the real values are resolved on your machine. If you choose, you can instead save a value for a placeholder in the optional per-config vault from the Web Console: we store it encrypted at rest, it can never be read back into a browser, it is released only to an engine that presents your API key, and an environment variable on the engine machine always takes precedence. You can clear a stored value at any time. None of this contains content from your terminals, repositories, or files unless you attach a file yourself.

If you use Human-in-the-Loop, we also store the approval requests your engine registers — the run, thread, and config identifiers, the boundary where the run paused, and the requested behavior — together with your decision. Approvals expire after 24 hours.

2.4 What passes through the Broker when you use the Web Console

The Web Console reaches your AI engine through the OpenEng Broker. Three kinds of data pass through it:

  • Your requests. What you type — your prompts and instructions — travels encrypted to the Broker, which opens each request to route it to your engine and stores it, encrypted at rest.
  • The engine’s streamed replies. The answers your engine streams back while it works are sealed end to end to your browser when your browser’s session key is available, so the Broker cannot read them; it stores them in that sealed form. Otherwise (for example, when the Broker no longer holds your browser’s session, or for a turn our API starts) they are sealed to the Broker like the other engine data it delivers, and the Broker can read them.
  • Engine data the Web Console loads. When the Web Console shows you your thread list and thread history (every past prompt and answer in a thread you open), the memory your engine has learned, the running config, the names of its placeholders (never their values), or loop, warm-up, and device status, your engine seals that data to the Broker, not end to end. The Broker opens it to deliver it to your browser and stores it, encrypted at rest.

The Broker keeps everything it routes for a retention window of 7 days by default, then deletes it by age, whether or not it has already been delivered. We do not use any of it for model training, advertising, analytics, or any purpose other than carrying it between your browser and your engine. The five engineering apps do not use the Broker at all.

Your browser is not the only sender. Our API can also reach your engine through the Broker, over an authenticated channel of its own, to send it control messages — for example, telling it to forget a config you deleted in the Console.

2.5 Website analytics, fonts, and server logs

This website uses Google Analytics for Firebase to understand usage — for example, which pages are viewed, the approximate region derived from your IP address, and your device and browser type. This is collected via cookies and similar identifiers and is used in aggregate to improve the site. Analytics runs on this website only: the engines, the five apps, the Web Console, and the Console contain no analytics. Google’s advertising features are switched off — we tell Google Analytics not to use advertising storage, ad personalization, or ad user data — and analytics does not load at all in a browser that sends a Global Privacy Control or Do Not Track signal.

Pages on this website load the Inter and JetBrains Mono typefaces from Google Fonts, so your browser requests them from Google’s servers, which receive your IP address and browser details. Standard server logs (such as IP address and request metadata) are processed by our hosting provider to deliver the Services securely.

2.6 Subscription & payment information

The engineering apps are free and need no payment details. Paid OpenEng AI plans (Pro, Enterprise, and pay-as-you-go credit) launch in Q4 2026. If you subscribe, payment is processed by Razorpay. We do not receive or store your card or bank details — Razorpay handles them under its own privacy policy. We receive and store your subscription status (plan, trial state, subscription identifier, and billing events) so we can unlock paid features wherever you sign in.

2.7 Communications and feedback

If you email us (for example, support or a security report), we receive your email address and the contents of your message. If you send feedback through feedback.openeng.app — a rating, a bug report, or a feature suggestion, with any files you attach — we store it with your account identifier so we can act on it and follow up.

3. What stays on your device

OpenEng is designed to be local-first. Everything you do inside an OpenEng app executes in a local engine on your hardware, and the OpenEng AI engine runs its models and agents on your machine too. The following stay on your own machine — in the OpenEng home directory (~/.openeng by default) or wherever your tools already keep them — and are not sent to us, except as described in sections 2.2–2.4 and 6 and listed below:

  • your source code, files, working directories, repositories, diffs, commits, and git credentials;
  • your terminal sessions, commands, command history, output, and saved commands;
  • your kubeconfigs, cluster data, logs, and secrets;
  • your database connection strings, queries, and results;
  • Chat projects, conversations, repository indexes, and model files;
  • the AI engine’s skills and usage ledger, and the on-device models; and
  • passwords and private keys, and the provider keys the AI engine stores (encrypted at rest).

These are the exceptions:

  • your OpenEng key is sent to our API when the AI engine registers, fetches your configs, and checks for updates (section 2.2);
  • vault values you choose to save are stored by us, encrypted (section 2.3);
  • the AI engine’s threads — including anything a conversation quotes from your files — and its memory pass through the Broker when the Web Console loads them, and the Broker keeps them for 7 days by default (section 2.4);
  • requests to the included Cloud Planner, paid from planning credit, pass through our API, and a hosted model you choose receives what you send it (section 6); and
  • the CI/CD API token you give the Git app stays in that browser and goes only to your own forge (section 6).

In the five apps, the browser and the engine talk over loopback (127.0.0.1) on your own machine, and after the key-exchange handshake the web app seals every frame of its session — no OpenEng server sits between them. The engines ship no analytics SDKs, no crash beacons, and no usage telemetry. Beyond sign-in, key registration, update checks, and the downloads described in section 2.2, what leaves your machine is what you choose to send: requests you type in the Web Console, and the engine’s replies and data it shows you there (section 2.4), content you save in the Console (section 2.3, including any vault values you choose to store), and hosted models or services you connect (section 6).

4. How we use information

  • to authenticate you, connect your browser to your local engine, and start your engines;
  • to route the requests you send from the Web Console to your engine, and your engine’s replies and data back to your browser;
  • to provide, maintain, and secure the Services;
  • to store and serve the configs, files, and preferences you save in the Console;
  • to manage your subscription and billing;
  • to respond to your requests, feedback, and support questions;
  • to detect, prevent, and address security incidents, fraud, or abuse;
  • to understand and improve this website (in aggregate); and
  • to comply with legal obligations.

We do not use your content to train AI models or for advertising.

Where required by law (e.g., in the EEA/UK), we rely on the following legal bases: performance of a contract (to provide the Services you request) and our legitimate interests (to secure and improve the Services, including measuring this website in aggregate with Google Analytics for Firebase). You can object to website analytics at any time, as described in section 9. Where we ask for your consent for something, you can withdraw it at any time.

5. How information is shared

We do not sell your personal information. We share it only as follows:

  • Service providers. We use Google Firebase and Google Cloud (Authentication, Firestore, Cloud Storage, Cloud Functions, Cloud Run, Cloud SQL, Vertex AI, Hosting, and Analytics) to operate the Services. They process your account data, and the content described in sections 2.3 and 2.4 and in section 6, only to the extent needed to run the Services or to comply with the law. Google processes this data on our behalf under its own terms; see Google’s Privacy Policy.
  • Payment processing. Paid plans are billed through Razorpay, which processes your payment details under its own Privacy Policy. We share with Razorpay only what is needed to create and manage your subscription (such as your account identifier and email).
  • Legal & safety. We may disclose information if required by law or to protect the rights, safety, and security of our users, the public, or OpenEng.
  • Business transfers. If OpenEng is involved in a merger, acquisition, or asset sale, information may be transferred as part of that transaction, subject to this Policy.

6. Third-party services you choose to use

Some features connect to services you configure. When you use them, your data goes directly from your machine to that provider under their privacy terms — not through us:

  • Cloud AI models (bring-your-own-key). If you point a role at a hosted model with your own provider key, your prompts and the key are sent to that provider — through the AI engine’s gateway on your machine — when you use that model.
  • Model registries. When an engine downloads model weights, it fetches them from the registry you chose — such as Hugging Face, the Ollama library, or ModelScope — which sees an ordinary download request. The Terminal engine also downloads its small suggestion model from Hugging Face once, without your choosing a registry (section 2.2).
  • Your own infrastructure. SSH hosts, Kubernetes clusters and cloud providers, databases and object stores, git servers and CI systems, and the MCP servers and connectors you attach: the engine on your machine connects to them directly, with credentials you keep. The one exception is the Git app’s CI/CD view: your browser calls your forge’s API directly (GitHub, GitLab, Bitbucket, or Gitea), with the API token you enter, which is kept in that browser.
  • Agent cells. Agent cells are deployed to your own cloud account; OpenEng does not host them or receive their data.
  • On-device models. Local models run on your hardware and send nothing externally. The AI engine’s built-in models run in its enclosed model daemon; catalog models run in a local Ollama daemon that you install and run yourself.

One option does go through us: the included Cloud Planner (launching Q4 2026), the Console’s default option for the planner role, paid from planning credit (Pro’s included credit and any pay-as-you-go top-ups). If you use it, your planning requests pass through our API, which forwards them to Google’s Gemini on Vertex AI and meters the tokens against your planning credit.

7. Data security

We use industry-standard safeguards: encryption in transit (TLS) on every connection to our services; per-frame sealing (X25519, HKDF, ChaCha20-Poly1305) between each app and its loopback engine; the AI engine’s streamed replies sealed end to end to your browser when its session key is available, with Web Console requests and the engine data the Web Console loads encrypted in transit and at rest; OpenEng keys stored only as hashes; provider keys on your machine encrypted at rest (AES-256-GCM) with a key file only your user can read; least-privilege access controls; and input validation at every trust boundary. No method of storage or transmission is 100% secure, but we work to protect your information and to keep as much of it as possible on your own device. See Security for the full model.

8. Data retention

The work you do in the five apps stays on your machine, so there is nothing for us to retain about it. OpenEng AI runs your work on your machine too; what we hold is what the Broker routes — your Web Console requests and the engine data the Web Console loads (such as thread history and learned memory), both encrypted at rest and readable by the Broker, and the engine’s streamed replies, in end-to-end sealed form we cannot read when your browser’s session key was available and otherwise sealed to the Broker like the other engine data — for 7 days by default, after which it is deleted (see section 2.4). We retain account information, what you save in the Console, and subscription records for as long as your account is active or as needed to provide the Services. You can delete your account and associated data at any time by contacting us (see below); we will delete or anonymize it within a reasonable period, except where we must retain it to comply with legal obligations (such as billing and tax records) or resolve disputes. Server logs are kept by our hosting provider under Google’s standard operational and security retention periods.

On-device data is removed when you delete it — for example, the OpenEng home directory (~/.openeng) — or uninstall an engine. Revoking an OpenEng key in the Console stops it from starting an engine.

9. Your rights & choices

Depending on where you live — including under India’s Digital Personal Data Protection Act, 2023, the GDPR and UK GDPR, and the CCPA/CPRA — you may have the right to:

  • access the personal information we hold about you;
  • correct inaccurate information;
  • delete your information;
  • export your information (data portability);
  • object to or restrict certain processing;
  • withdraw consent wherever we rely on it, at any time; and
  • have your grievances addressed.

To opt out of website analytics, turn on Global Privacy Control or Do Not Track in your browser — analytics then does not load on openeng.app — or block or clear cookies for openeng.app, or use Google’s Analytics opt-out browser add-on. Because we sell no personal information and run no targeted advertising, there is no “sale” or “sharing” to opt out of under the CCPA. To exercise any right or raise a grievance, email hello@openeng.app. We will not discriminate against you for exercising your rights, and you may lodge a complaint with your local data-protection authority.

10. International data transfers

OpenEng is operated from India. Our service providers (notably Google) operate globally, so your account and analytics information may be processed in countries other than your own, including India and the United States. Where required, such transfers are protected by appropriate safeguards such as the European Commission’s Standard Contractual Clauses.

11. Children’s privacy

OpenEng is intended for developers. The Services are not directed to children under 16, and we do not knowingly collect personal information from them. If you believe a child has provided us information, contact us and we will delete it.

12. Cookies & local storage

This website uses cookies and similar technologies for analytics (section 2.5) and, on its sign-in pages (/subscribe, /oauth), browser storage to keep you signed in. The apps, the Web Console, and the Console use cookies and browser storage to keep you signed in, remember your preferences, cache a one-time pairing key until it is used, and — in the Git app — hold the CI/CD API tokens you enter, which never leave your browser except to your own forge. We do not use advertising cookies or third-party advertising trackers. You can control cookies through your browser settings.

13. Changes to this Policy

We may update this Policy from time to time. When we do, we will revise the “Last updated” date above and, for material changes, provide a more prominent notice. Your continued use of the Services after an update means you accept the revised Policy.

14. Contact us

For any privacy question, request, grievance, or security report, email hello@openeng.app. We aim to acknowledge security reports promptly. See also our Terms of Service.

OpenEng Labs Private Limited, Bangalore, Karnataka, India