Privacy Policy

1. Who this policy applies to

This policy applies to the A360 BotKit Chrome extension developed by Anand S Kale.

2. What the extension is for

A360 BotKit has a single purpose: improving Automation Anywhere A360 bot editing inside Control Room. It provides tools for line-number updates, copy and patch workflows, and autosave.

3. What data the extension handles

The extension may access the following data when you use it on an A360 bot editor page:

• the current page URL and bot file ID
• the A360 auth token already present in your browser session
• bot JSON returned by your A360 Control Room
• current unsaved editor data used for autosave
• extension settings such as autosave preferences and theme preference

The extension does not ask for your A360 password and does not operate its own login system.

4. How the extension uses that data

The extension uses the data above only to provide its user-facing features:

• fetching the current bot content
• updating log placeholders with line numbers
• copying bot JSON to your clipboard
• patching a bot from valid JSON you provide
• running native or silent autosave inside the current editor
• showing status information in the popup and on the A360 page

5. Where data is sent

A360 BotKit sends bot content and save requests only to the same Automation Anywhere A360 Control Room that you are already signed in to.

The extension does not send your auth token, bot data, clipboard contents, or autosave payloads to the developer, analytics providers, ad networks, or unrelated third parties.

6. What the extension stores locally

• Theme preference: stored in extension local storage as botkit-theme
• Autosave settings: stored in chrome.storage.local under the extension's storage area

The extension does not intentionally persist your bot content or auth token in its own long-term storage.

7. Permissions and site access

activeTab

Used so the popup can interact with the current tab when you run extension features.

storage

Used to save autosave settings locally in Chrome.

HTTPS page access

A360 Control Room can be hosted on many different customer domains. For that reason, the extension is packaged to work across HTTPS sites. In practice, its bot-editing behavior is limited by runtime checks to supported A360 bot editor pages.

8. Data sharing

We do not sell user data. We do not use user data for advertising. We do not share user data with data brokers or analytics platforms.

The only expected transfer of data is between your browser and your own A360 Control Room when you use the extension's features.

9. Security

The extension communicates with A360 over your existing HTTPS session. We recommend using the extension only on trusted devices and following your organization's A360 security practices.

10. Your choices

• You can disable or uninstall the extension at any time.
• You can turn autosave off from the Settings tab.
• You can clear the extension's local settings from Chrome if needed.

11. Changes to this policy

This policy may be updated when the extension changes or when legal or platform requirements change. The latest version will be published at this page.

12. Contact

13. Independent product notice

A360 BotKit is an independent tool and is not affiliated with or endorsed by Automation Anywhere.