This Privacy Policy explains what data Operun (“Operun”, “we”, “our”) processes when you use the Operun browser extension and the Operun cloud service (together, the “Service”), and how that data is handled. Operun is a local-first browser automation tool. We built it so that the sensitive parts of your browsing — credentials, cookies and session tokens — are handled in memory on your device and never uploaded to our servers.
1. What Operun does
Operun automates repetitive, user-initiated web operations. A cloud “brain”
orchestrates work that “edge hands” — the extension running in your browser —
execute: navigating, clicking, typing, waiting and capturing. The extension ships
as a Chrome Manifest V3 extension that follows the principle of
minimum reach, and its store build does not request the debugger
permission.
2. Our privacy commitments at a glance
- Zero debugger — the store build never requests
chrome.debugger. - Zero
eval— the extension never useseval()ornew Function(). - Zero remotely hosted code — all extension logic is compiled locally and never loaded from a URL.
- Zero third-party tracking probes — the extension contains no analytics SDKs, no advertising libraries and no third-party trackers.
- Local-first memory — credentials, cookies and session tokens are processed in memory on your device only and are never written to disk or uploaded to the cloud.
3. Information we process
3.1 Credentials, cookies and session tokens
When a task requires it, Operun may read a credential or cookie for the tab you are operating on, and it is scoped to that tab's own document only — never the whole browser cookie jar. This material is held in memory for the duration of the action and is cleared immediately afterwards. Operun never stores credentials or plain-text cookies to disk and never transmits them to the cloud.
3.2 Action payloads
Automation tasks are expressed as small JSON action payloads (for example, a navigation target or a selector to click). These payloads exist only in memory during execution and are cleared as soon as the task completes. A payload contains the minimum information required to perform the step you asked for — not your browsing history, not your profile.
3.3 Account and billing data
To provide the Service we process your account identifier, connection tokens, usage/quota counters, and billing records (including the purchases you make). Usage is metered so each action is settled against your credit balance through an in-flight escrow; this processing is necessary to deliver and bill the Service.
3.4 Network capture (operator feature only)
The operator build of Operun — a separate artifact for people
automating their own browser — can record the network traffic of a single tab for
debugging. A capture is operator-initiated, held in memory only
(never written to disk), bounded in size, and dropped entirely when you stop the
capture or the tab closes. This feature is not present in the store
build, because it requires the debugger permission the store
build intentionally omits.
4. What we do not do
- We do not sell, rent or trade your personal data.
- We do not use your data for advertising or ad targeting.
- We do not run third-party analytics or trackers inside the extension.
- We do not request whole-web access (
<all_urls>) in the store build. - We do not upload credentials, cookies or session tokens to the cloud.
5. Permissions and host access
The store build requests only the permissions required to perform automation on pages you choose, and nothing more. They are:
storage— to persist lightweight connection settings and preferences locally.activeTab— to act on the current tab only after you invoke the extension.scripting— to inject the minimal action functions that perform clicks, typing and queries.downloads— to handle file downloads your workflow triggers.alarms— to keep the MV3 service worker responsive between sessions.tabs— reads tabtitleandurlmetadata inlist_tabsfor reporting honesty and tab addressing; it never injects scripts into, or reads the DOM of, non-allow-listed tabs.
Host access is limited to three categories: the Operun API, your local loopback
(127.0.0.1 / localhost), and a fixed allow-list of
business domains. Operun interacts with these domains only under operator
instruction, and never requests <all_urls> or any other
whole-web host pattern in the store build.
The business domain allow-list is:
taobao.com— Taobao merchant analytics and reporting.tmall.com— Tmall merchant analytics and reporting.jinritemai.com— Douyin E-commerce merchant reconciliation.oceanengine.com— Ocean Engine / Qianchuan advertising financial flow.xiaohongshu.com— Xiaohongshu creator backend data management.zhipin.com— BOSS Zhipin recruitment and candidate pipeline reach.bing.com— Search engine benchmarking and connectivity validation.
6. How data flows
Operun is local-first by design. The browser-side extension executes actions; the cloud control plane sends commands and receives the minimum results needed to orchestrate the workflow. The cloud never receives your credentials, cookies or session tokens, and never receives the full content of your browsing session.
7. Third-party services
We may use infrastructure providers (for example, hosting and payment processors) to operate the Service. These providers process data only on our instructions to provide their service, and never for their own independent purposes. We do not embed third-party tracking or advertising code in the extension.
8. Data retention and deletion
In-memory automation data (credentials, cookies, session tokens, action payloads) is transient by design and cleared immediately after the task completes. Account and billing records are retained only as long as needed to provide the Service and meet legal obligations. You may request access to, correction of, or deletion of your account data by contacting us at [email protected].
9. Security
We apply access controls, encryption in transit, and strict scoping of the extension's reach to protect your data. The extension's local control plane is locked to loopback by default and requires authentication for any remote caller.
10. Google Limited Use Policy
Operun's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. We use such data only to provide and improve the core automation functionality of the Service, and we do not use it for advertising, do not sell it, and do not transfer it to third parties for independent purposes.
11. Microsoft Edge Add-ons store
Operun complies with the privacy requirements of the Microsoft Edge Add-ons store. The extension does not collect, transmit or sell personal data, and any access it has is limited to what is necessary to perform the automation you request.
12. Children's privacy
The Service is not directed at children under the age of 18, and we do not knowingly collect personal information from children.
13. Changes to this policy
We may update this Privacy Policy from time to time. When we make material changes, we will update the effective date above and, where appropriate, provide notice. Continued use of the Service after a change constitutes acceptance of the updated policy.
14. Contact
Questions about this policy or our data practices? Contact us at [email protected].