Information processed
Account identity, workspace membership, worker configuration, commands, execution events, approvals, usage estimates, notification delivery status and audit metadata may be processed to provide the service.
When you use NAVINES Operator
Operator helps with a task on the page you explicitly approve. Your task text is sent to NAVINES when you request a price. Starting a task sends screenshots of the approved page, its address and title, your instructions and the results of permitted page actions to NAVINES for AI processing. Other tabs are not sent as task content. Work pauses when you switch away from the approved tab.
Chrome asks for a broad standard automation permission when you install or update NAVINES. NAVINES uses it only for the page you choose, after you approve that page and choose Start. Chrome displays its own safety banner during temporary control. Pause, Stop, closing the page or changing websites releases that control; reopening the panel does not resume work automatically.
Screenshots may contain personal information visible on the page. Detected sensitive fields are masked locally before an image is sent, but this is not a guarantee that every private detail is hidden. Avoid tasks on pages containing passwords, payment details, health information or confidential messages. Uploads, camera use, purchases and sending forms are not automatically authorized by a general request to review a page.
NAVINES can prepare supported ordinary forms, but you always make the final Submit click. If a page might send information while a field is edited, NAVINES asks you to take control before that step. NAVINES releases browser control and pauses while you review or submit; waiting is free. You explicitly return control before NAVINES checks the current page for a visible result. An unknown result is never submitted again automatically. No automatic-submission destination is enabled.
Form fields are inspected and masked in Chrome. Values used to prepare fields are not retained in browser-command records or diagnostic logs. The small saved handoff record contains only the task, page and control stage. Personal details you choose to write in your task or messages are still part of that conversation and its retention policy. NAVINES does not monitor network requests or collect submission bodies.
What stays in Chrome
When you explicitly request an unpublished draft, NAVINES can edit supported draft controls and choose Save draft. Draft websites may save those edits as you type. This does not authorize publishing, submission for review, payment or legal acceptance. Ordinary forms still require your final Submit click.
You can select files for the approved website in the extension panel. Only those files may be attached to your requested draft. Their names and metadata, and up to 8 KB of text references, are sent to NAVINES and its AI processor for task planning. File bytes are uploaded from Chrome to the approved website, not to NAVINES. Selected files stay in Chrome extension storage for this task; access expires after 24 hours and expired files are removed on the next file access. Starting a new task removes the selection. The destination website controls retention of any copy you upload or save there.
The extension stores its device credential, connection state, approved-page information, current task state, messages, final receipt and small action/cancellation records in Chrome extension storage. This allows a normal update or browser restart to preserve your connection and prevents a stopped action from being repeated. Unsent task drafts are not intentionally saved to disk. Starting a new task clears the active panel binding, not the saved task history in your Console.
Connected systems
Access tokens for connected services are encrypted and used server-side to perform user-authorized work. Disconnecting erases stored grants while preserving non-secret audit history. Google Search Console is read-only. GitHub uses a repository-selected App grant with a code-owned tool allowlist and protected branch/draft-pull-request writes.
Purposes and retention
Data is used to authenticate operators, execute configured workers, enforce limits, maintain security and provide an inspectable record. Workspace data remains until deletion or an applicable retention process removes it.
Approved-page content is used only to provide the assistance you requested, maintain security and troubleshoot that feature. It is not sold or used for advertising, credit decisions or unrelated profiling. Access by people is limited to your consent, necessary security or legal purposes. NAVINES follows the Chrome Web Store Limited Use requirements.
Screenshots are transmitted securely for AI processing; they are not written to the Operator task tables as image files. Task text, page scope, results, timing, cancellation evidence and financial history can remain in your workspace. AI processing can involve temporary storage by a processing partner. NAVINES requests removal of obsolete AI response records on a best-effort basis; immediate deletion is not guaranteed. We do not claim a fixed automatic deletion period where one has not been implemented.
Data deletion
A workspace owner can request deletion from Console settings after recent authentication. The operation removes tenant records and the associated authentication user and cannot be reversed.
Who helps us run NAVINES
The product uses carefully scoped processing partners for sign-in, configured AI execution, transactional email, application hosting and scheduled dispatch.
Stopping and revoking access
Stop blocks new work and releases unused task budget. If Chrome is offline, NAVINES shows that it is waiting to confirm the stop. An action that had already begun cannot always be withdrawn; its known outcome is preserved without repeating it. Revoking a device in Console blocks its ability to start more tasks. Site permissions can be removed in Chrome’s extension settings. Revocation does not silently erase financial history or remove the extension’s local storage; removing the extension removes its Chrome data.
Contact
Privacy questions may be submitted to hello@navines.com. Do not send authentication credentials or sensitive connector data.