An automation extension gets a broad view of your browser by design, so it should be explicit about how it uses that. This page is the plain version: every permission, the reason it exists, where your data sits, and what never leaves the machine.
These are the permissions ORCA requests, each with what it enables and what it does not. Nothing here is hidden behind “to improve your experience”.
| Permission | What it lets ORCA do | Why it is needed, and where it stops |
|---|---|---|
activeTab | Act on the tab you are looking at, when you start a run or open the panel. | Without it the extension cannot see the page you want to automate. |
| Host permission for the sites you automate | Read and act inside the pages you open, so one install works on a portal, a CRM and an internal tool alike. | Chrome cannot grant a browser automation tool one site at a time and keep it usable. Why the broad host permission exists. |
scripting | Inject the picker and the runner into a page so it can highlight a target, type a value or read a table. | It runs while a workflow is building or executing, not continuously in the background. |
storage | Keep your workflow profiles, rules, extracted values and run logs on your own machine. | This is the local repository; it is not a sync service and nothing here is mirrored to us. |
alarms | Wake the scheduler at the time you set for a recurring run. | An alarm starts a saved workflow; it does not collect anything by itself. |
offscreen | Keep long runs and scheduled work alive while the service worker goes idle, as Manifest V3 requires. | No extra page access: the document is a lifecycle mechanism, not a data collector. |
webNavigation | Follow the tab as a workflow moves between pages, so a step can wait for the next page to be ready. | Used to time steps and to notice a redirect; not to build a browsing history. |
Two columns, and the split is the whole design: automation state on your machine, cloud calls only when you choose an AI step.
It leaves your device only if you export a profile or share a workflow yourself.
Processed in memory to decide the next action and returned. Not sold, rented or traded to brokers or advertisers, and not used to build a profile of you.
Rule-based and scheduled runs do not send page content anywhere, so they also do not draw on your monthly AI balance.
The store requires publishers to declare the data an extension handles. ORCA’s declaration says it handles personally identifiable information, user activity and website content — because that is what filling a form and reading a page involves. We would rather you read that from us first.
It also carries the three limited-use promises: not sold to third parties outside approved use, not used for anything unrelated to the core function, and never used for creditworthiness or lending decisions.
Automation is only acceptable where you are allowed to act. Read the target site’s terms; a schedule is no excuse for hammering someone’s server.
Privacy and security questions go to privacy@orcamatic.com; anything that breaks your workflow goes to support@orcamatic.com. Both reach the people who build the extension.
