Able Browser Assistant — Privacy Policy

Able Browser Assistant is a browser extension for Chrome and Microsoft Edge published by Search Rebel Inc., d/b/a Able Software (“Able,” “we,” “us”). It connects an Able application you are signed in to with the websites you choose to work on, and lets the application’s assistant work such a website for you, with you in control. This policy explains what the extension does with data. Our general Privacy Policy covers the Able Platform itself.

What the extension does with data

The Able application. The extension’s side panel frames a page of the Able application on the hosts the extension declares: the Able platform’s own domains (*.searchrebel.com, *.ablesoftware.io) and the domains our customers serve their Able application from. You sign in to that application as you always do, and your browser sends the application’s own session cookie to that page. The extension does not read cookies, passwords or tokens, and it stores no credential.

The website tab the assistant works on. When the application’s assistant works a website for you, the extension attaches Chrome’s debugger to that one tab, and Chrome shows its “is debugging this browser” bar for as long as it stays attached; Cancel on that bar ends the session, and so does closing the tab or the side panel. On that tab the assistant reads the page (its accessibility tree, every frame included, and an image of the page when it asks for one), fills the form from the application’s data, attaches a document the application handed it, and reads the confirmation the site shows. It never types into a password or one-time-code field, never acts on a sign-in page, and never presses the site’s own Submit button, which you press.

The websites you connect. You can record one of your own submissions on a website you connected with the “Connect this site” button. The recorder keeps the steps you take there — your clicks, the values you type or choose in a field, the keys that move through or submit a form (Enter, Tab, Escape, Space, the arrows), the text you copy or paste and the pages you visit — with each page’s controls and HTML and images of the page; it never keeps a password’s or a one-time code’s value, and nothing of a page where one was typed but its address. It never records a site you did not connect.

What leaves the browser. What the assistant reads on the tab it works on, and what a recording keeps, are sent to the Able application you are signed in to, where they are recorded with your name and the time. Nothing is sent anywhere else: no analytics, no third-party service, no advertising.

What stays in the browser. The application host you chose in the extension’s options, and a recording while it runs, kept in session memory and cleared when the browser closes.

Recipes. A recipe is a list of steps (which field to fill with which value) that your own organization recorded or that the assistant wrote down while it worked. It is data, stored in the Able application, and it contains no password.

Permissions, and why each one exists

• Side panel — the assistant lives in the browser’s side panel beside the website you work on.
• Scripting — to put the recorder into the pages of a site after you connected it, and to ask a connected tab whether a sign-in form is showing, so the panel can tell the application you must sign in first.
• Storage — the application host you chose, and a running recording’s state in session memory.
• Tabs — to know which tab is the website, its address and its title, so the panel can say what it is connected to, the website’s tab comes to the front instead of a second one opening, and the assistant can list and switch the window’s tabs.
• Alarms — a 30-second tick that ends the assistant’s session on a tab or a panel that is gone, so Chrome’s debugger never stays attached.
• Debugger — the assistant works the website tab the way a person at the keyboard would: while the application holds a session on that one tab, the extension reads the tab’s accessibility tree and clicks and types with real input events, and Chrome shows its debugging bar. It detaches when the session ends, the tab closes or the panel closes. It refuses a password or one-time-code field, a sign-in page, and the site’s own Submit, which you press.
• Active tab — when you opened the panel from the toolbar on the website’s tab and record a submission, the extension can capture images of that tab on each page the recording visits. Nothing is captured on a page where a password or a one-time code was typed.
• Able application hosts — to frame the signed-in application page in the side panel.
• Other websites, one at a time — only the sites you connect with the “Connect this site” button; you can revoke a site at any time in the browser’s extension settings.

The extension runs only the code it was installed with. Recipes and recordings are data, never code.

What the extension never does

• Store or type a website password.
• Read cookies, passwords or browsing history.
• Run code it was not shipped with.
• Sell data, share it with third parties, or use it for advertising.
• Act on a tab without Chrome’s debugging bar showing.
• Record a website you did not connect.
• Use any data to determine creditworthiness or for lending purposes.

Retention and control

The records the extension creates live in the Able application, under your organization’s retention rules and the Able Platform’s Privacy Policy. Removing the extension removes its options and session state from your browser. You can disconnect a website at any time from the extension’s site access settings in your browser, and end the assistant’s session on a tab at any time from Chrome’s debugging bar.

Changes to this policy

We may update this policy from time to time. Material changes are posted on this page with an updated effective date.

Contact

Questions about this policy or the extension? Email privacy@ablesoftware.io or support@ablesoftware.io.