Only the information needed to operate visible, user-approved tab workflows: tab URLs/titles, explicit commands, status messages, and DOM results from allowed pages.
🔐 Privacy policy
Local-first browser automation, without a hidden data layer.
Remote Tab Opener Manager controls visible browser tabs through a local extension bridge. It is designed to stay transparent: no backend, no analytics, no cookie reading, no network traffic inspection, and no silent allow-list changes.
✅ No data collection
🧭 Visible tabs only
🛡️ Explicit allow-list
🔒 No cookie access
📍 Local browser execution
No cookie reading, no site-storage harvesting, no traffic inspection, no server-side logs, no tracking pixel, no remote relay, no cloud automation account.
RTO actions are designed around explicit allow-listing. A trusted page can ask; the user remains responsible for approving where automation may run.
🧩 Extension permissions
Why the extension needs browser permissions
RTO uses standard browser-extension permissions to open, focus and control visible tabs. These permissions are powerful, so the product policy is deliberately restrictive: no backend, no telemetry, explicit allow-listing, and documented commands only.
| Permission | Used for | Not used for |
|---|---|---|
tabs / activeTab |
Open, focus, update and report state for controlled visible tabs. | No browsing-history profiling, no background surveillance, no user tracking. |
storage |
Keep local extension settings such as allow-list entries, options and small UI preferences. | No cloud sync controlled by RTO, no server upload, no analytics profile. |
scripting |
Run documented commands in pages that are permitted by the extension and RTO policy. | No arbitrary remote code execution, no hidden script fetched from the RTO website. |
| Host permissions | Let the extension technically reach normal web pages when the user authorizes an RTO workflow. | No automatic trust: host access is not presented as a silent permission to automate everything. |
| Content scripts | Provide the local bridge needed for visible tab control and safe DOM actions. | No cookie reading, no network interception, no hidden data collection. |
Current public extension packages use tabs, storage, scripting, activeTab, host permissions for normal web pages, and content scripts. They do not declare cookie or webRequest permissions.
📦 Data handling
What data is handled, and where it stays
RTO is not a hosted automation service. It does not receive your workflows, page data, browsing sessions, form values, logs or screenshots. The extension runs locally, and its small settings live in browser extension storage.
- No server account. You do not need a Remote Tab Opener account to use the extension.
- No analytics. The extension does not phone home with usage events.
- No cookie access. RTO does not read, copy or modify browser cookies.
- No network interception. RTO is not a proxy and does not inspect HTTP traffic.
- No hidden scraping engine. Automation is visible and constrained to approved workflows.
- No silent allow-list change. A page cannot grant itself permission without user confirmation.
🛡️ Allow-list model
A page may request permission. You decide.
The allow-list is the central trust boundary. RTO is designed for workflows launched from trusted pages toward visible tabs that the user has explicitly approved.
1. Request
A trusted page can ask for a domain to be allowed.
2. Review
The user sees the requested host and decides whether it is appropriate.
3. Run visibly
Approved actions happen in real browser tabs, not in an invisible cloud runner.
4. Remove anytime
The user can remove allowed hosts from the extension settings.
💾 Local storage
Small local settings, not a remote profile
| Item | Where it lives | Purpose |
|---|---|---|
| Allow-list | Browser extension storage | Remember which hosts the user has approved. |
| Options | Browser extension storage | Keep local extension preferences and safety toggles. |
| Tab state | Local browser context | Track visible tabs participating in a workflow. |
| Runtime messages | Current page / extension messaging | Report command status back to the trusted page. |
| Website content | Target page only | Used only during an authorized local command; not uploaded to RTO. |
🚧 Security boundaries
What RTO is not
Remote Tab Opener should not be described as a browser-security bypass, a scraping platform, a proxy, a cookie reader, or a hidden RPA runner. Its role is narrower and more honest: local visible tab workflows with explicit user control.
- No Same-Origin Policy bypass. RTO does not make one website magically read another website’s private internals.
- No cookie or credential extraction. Password, hidden and credential-like fields are not a supported extraction target.
- No remote code execution model. Commands must be documented and constrained, not arbitrary code downloaded from a server.
- No traffic spy role. The extension is not designed to inspect HTTP payloads or collect network traffic.
- No autonomous cloud agent. Human review, visible tabs and local execution remain the product model.
👤 User controls
How to stay in control
Pause or stop
Close the controlled tab, stop the workflow, or disable the extension when you do not need it.
Review hosts
Keep your allow-list tight. Remove old or unnecessary domains.
Clear data
Remove the extension or clear extension storage from your browser settings.
❓ Privacy FAQ
Quick answers
| Question | Answer |
|---|---|
| Does RTO send data to remote-tab-opener.com? | No. The extension is local-first and does not upload workflows, page content, logs, form values or browsing data. |
| Does RTO use analytics? | No. The extension does not send telemetry or analytics events. |
| Does RTO read cookies? | No. Cookie access is not part of the RTO model. |
| Can a website authorize itself? | No. A trusted page can request; the user decides. |
| Why are host permissions broad? | The extension needs technical reach to ordinary web pages, but runtime automation is constrained by explicit RTO policy and user-approved workflows. |
| Is RTO a Selenium or Playwright replacement? | No. RTO is for visible, local, user-controlled tab workflows, not a full headless test framework. |