Privacy policy
This policy explains how the Neo Saarthi browser extension and the local Neo Saarthi Browser app handle your information.
Effective
- Operated by
- Gaurav NagraniIndividual operator
- Location
- Maharashtra, India
- Contact
- info@neosaarthi.si
What the extension does
Neo Saarthi connects browser tabs opened or claimed for your requested task to the Neo Saarthi Browser app running on the same Windows computer. After you accept the extension's first-use data disclosure, connection is automatic through a native messaging helper restricted to the official extension ID. No pairing code is needed. Chrome requests HTTPS website access during installation; additional browser features remain separately gated. The local app must stay running.
Data handled
For requested browser tasks, the extension can process page URLs, titles, visible text, ordinary form values, selected text, screenshots, page-control metadata and action results. Depending on the pages you authorize, this may include personal information, communications, financial information or other sensitive page content. Grant access only to sites you want processed.
Where the relevant browser permission and feature setting are already enabled, requested tasks can use browser-tab information, history, bookmark information, download details or tab-group information. These grants are not required for every task. HTTPS access is requested at installation. Optional browser-feature permissions are not automatically enabled. The popup shows connection status; password approval and pause/resume are in the local app.
The extension retains local connection credentials, disclosure acceptance, access settings, pause state, recent job identifiers and managed-tab information. The local app keeps settings, connection records, audit metadata, browser-action logs and learned task trajectories. If used, saved workflows and captures can contain task information. Website actions and downloads may also create records at the destination website or files on your computer.
Protected fields and saved passwords
Ordinary extension filling blocks protected fields. Page observations redact protected values and URL queries; screenshot handling masks identified protected fields and iframe contents, including inside accessible open web-component roots. Closed component internals and website changes can limit detection. Redaction does not make every page anonymous: ordinary text or images can still contain personal information.
Saved-password entry is off by default. You must approve it explicitly in local app Settings and save. You can revoke it there; revoking during a task also pauses native input. If you approve it and request a supported CAMS/KFintech task, the Windows desktop resolves the saved login or report password locally, checks the destination and focused field, and enters it into the intended website. The extension prepares the field and verifies only whether it is populated. Saved password values are not included in extension bridge messages, AI prompts, task-history entries or recordings by this feature. Other website text could independently contain sensitive information, which is why access should be limited to intended task sites.
The local app stores saved API keys and website credentials in an encrypted settings file, with its encryption key protected by Windows DPAPI. A separately configured .env file is not encrypted by this settings mechanism. These protections do not encrypt every local file or all local traffic. Password approval does not authorize report submission, payments or other sensitive actions.
Email-recipient matching is performed locally in the authorized report page. Returned recipient metadata contains checkbox identifiers, counts and selection flags rather than discovered email addresses. Karvy's current runner selects one available registered recipient; an explicit exact-recipient task uses its specified matching rule.
Purposes and recipients
We use browser data to carry out your requested browser tasks, maintain the local connection, enforce access controls, record task results and support the desktop's task-continuation and trajectory features.
The extension sends task data to the authenticated Neo Saarthi Browser app on your computer. This local connection does not mean that all processing stays on your computer. The desktop can send information needed for the task to configured AI services.
The browser engine uses OpenCode as its default AI gateway. Jev, a TypeSafe AI System One model, handles structured browser decisions. Browser text generation, screenshot-based decisions, calendar vision assistance and portal image reading use DeepSeek V4.1 Flash (deepseek-v4.1-flash). These browser helpers do not select or fall back to Muse Spark Contributor; the browser app does not provide a separate chat-model selector. An administrator can configure a different HTTPS gateway for the same pinned browser model, which requires separate verification of that gateway's practices. This policy covers the extension and local browser app; a separate assistant integration can have additional data practices.
Information supplied for AI processing can include task instructions, relevant page/control information and, when needed, screenshots or portal images. Requested portal image-reading can include a CAPTCHA image. Provider processing, storage locations, retention and training depend on the actual model, account and applicable service terms; local password entry does not make these other requests local.
Provider retention, processing locations, training and deletion depend on the selected route, account and applicable agreements. OpenCode publishes model-specific privacy terms and exceptions; TypeSafe states that Jev requests and responses are not used for training, while other processing and retention depend on its terms and any agreed arrangement. These statements do not guarantee permanent zero retention, erase local records or establish a special agreement for your account. Review OpenCode model privacy, OpenCode Go privacy and TypeSafe data-use information for your actual service.
Requested website actions transmit the relevant task inputs to those websites. Their own terms and privacy policies apply. The extension also supports requested YouTube transcript retrieval from YouTube.
The extension does not include an advertising or browser-data-sale feature. Browser information is handled for the requested browser-task purpose and related connection, access-control and task-record functions. This does not mean that no third party receives task data, or that every third-party use is controlled by the extension.
Storage and retention
| Record | Current implemented behavior |
|---|---|
| Connection credentials | Kept in trusted extension-local storage until removed or replaced. Connection tokens expire after 30 days and can be renewed through authenticated native setup when automatic connection is enabled. Disconnection revokes access; it does not erase every stored record. |
| Website grants, disclosure and local settings | Remain until changed, cleared or removed with extension-local storage. Browser permission grants can be revoked in browser settings. |
| Managed tabs | Stale closed-tab IDs are removed; browser restart clears task-tab ownership and tasks must open or claim tabs again. |
| Recent attempted job IDs | Bounded to the latest 256 identifiers for replay protection, including across worker replacement. These are identifiers, not page-content records. |
| Live paused-task context | Kept in desktop memory for up to five minutes while the backend remains running; backend restart loses that continuation context. |
| Download observations | Bounded in-memory cache, with old observations pruned on subsequent updates after one hour; this does not delete downloaded files. |
| Browser audit metadata | Default retention is 30 days, configurable from 1–365. Cleanup is triggered during audit access/write activity; it is not an unconditional scheduled erase at the deadline. These records have a separate authenticated deletion API. This is not the retention period for all task data. |
| Saved settings and credentials | Encrypted local settings remain until cleared or replaced. Clear saved values removes the values from that store, not a separately configured .env file, backups or provider accounts. |
| Native helper configuration | Local helper files and browser registration remain until removed. The encrypted helper authentication secret is replaced when the app starts. Removing the extension does not remove the local app or its helper registration. |
| Recent task results | The local app keeps up to 20 task entries in process memory. They are lost on app restart; separate logs and learned trajectories can remain. |
| Browser logs, learned trajectories, confirmations and optional captures | Separate local records remain until removed or affected by their specific cleanup mechanism. There is no universal age-based expiry for these stores in the current implementation. The action log rotates at 5 MiB with one backup; this does not impose a retention duration on other files. Learned trajectories are local task playbooks, not by themselves third-party model training. |
| AI-provider and destination-website records | Governed by the actual services, account settings and applicable policies. Deleting a local record does not itself remove their copies. |
Your controls and deletion
You can pause and resume an eligible retained task in the local app or with the Windows shortcut. Disconnect browsers in the local app to revoke access and disable automatic connection. Website and optional browser permissions can be removed in browser extension settings. Optional saved-password entry is approved or disabled in the local app Settings.
Removing the extension removes its extension-local storage. Disconnect browsers in the app disables automatic setup and revokes current connections; it does not delete earlier logs, audit metadata, files, saved workflows, learned trajectories, website records or provider data. Clear saved values affects encrypted app settings only. A separately configured .env file must be changed or removed separately, and provider keys can also be revoked with their issuer. Scoped audit and workflow deletion mechanisms do not erase every task record.
The current implementation does not provide one control that erases all these separate stores. Local logs, playbooks, confirmations, captures and downloaded files may need separate removal. Copies in backups or external services require separate handling. For assistance with the records and controls available to you, or to make a privacy/deletion request, contact info@neosaarthi.si. We do not promise that revoking access, uninstalling the extension or deleting a conversation erases every copy everywhere.
Security
The Windows native helper is restricted to the official Store extension ID and authenticates to the local app with an encrypted per-launch secret. Browser task traffic remains on this computer's loopback interface and uses connection tokens and access checks. The local browser app trusts the verified Store identity listed above; the extension's Store public key keeps that identity consistent. Packaged operations reject externally supplied JavaScript. The local bridge uses HTTP rather than TLS; local authentication is not equivalent to encryption. Browser-to-native same-computer communication has a specific exception in Google's published encryption FAQ; that exception does not cover internet transmission to AI providers or websites. Internet model connections must use the supported provider's secure endpoints.
No protection guarantees security against malware already running with access to the same computer/account. We do not assert that every desktop record is encrypted or that page redaction removes every possible sensitive detail.
Limited Use, changes and contact
Browser information must be used and transferred only for the disclosed user-facing purpose and permitted related uses under the Chrome Web Store User Data Policy, including Limited Use. It must not be sold for advertising, used for unrelated profiling or creditworthiness, or made available for unrelated human review. A provider's separate policy does not waive these requirements.
If data practices change, we will update this policy and provide additional notice or consent where required. Questions and deletion requests should be sent to info@neosaarthi.si.
polchmmnbnamnpkoiipldgdngmdllgbc