chrome extension

A-TABS: Links Organizer

by Aleks Frame

Responsible publisher: Aleksandr Khrushch · Argentina

Data Handling Statement and Chrome Web Store Limited Use Disclosure

Last Updated: May 11, 2026

Extension: A-TABS: Links Organizer

Last Updated: May 11, 2026

Chrome Web Store Publisher Name: Aleks Frame

Responsible Publisher / Provider: Aleksandr Khrushch

This statement explains how A-TABS: Links Organizer handles Chrome API data and user information.

1. Single purpose

The single purpose of A-TABS: Links Organizer is to help users save, organize, search, and reopen browser tabs and links as local collections.

The Extension is focused only on tab and link organization. It does not provide unrelated functionality.

2. Local-first data handling

The Extension stores its main data locally on the user’s device. This may include:

  • saved links and URLs added by the user;
  • tab titles and favicons for saved tabs;
  • user-created folders, categories, labels, notes, ordering, and collections;
  • local preferences and Extension settings.

This data is used only to provide the Extension’s core functionality.

3. No transmission to developer servers

In its current version, the Extension does not upload saved links, tab collections, folders, labels, notes, settings, or browsing data to developer-controlled servers.

The Extension does not currently include cloud synchronization, account login, advertising, analytics, telemetry, crash reporting, or remote user tracking.

4. Chrome permissions

The final permission list depends on the published manifest.json. Use only the explanations for permissions actually present in the final manifest.

storage

Used to save the user’s tab collections, saved links, categories, labels, notes, preferences, and local Extension settings on the user’s device. This data is stored locally and is not uploaded to developer-controlled servers.

tabs

Used to read the titles, URLs, favicons, and tab status of tabs selected by the user or included in a saved browser session. This is necessary for the Extension’s core function: saving, organizing, searching, and reopening tab collections.

activeTab

Used only when the user actively clicks or interacts with the Extension to save or manage the current active tab. This permission provides temporary access to the active tab after a user action and is required to save the current page into a collection.

tabGroups

Use this explanation only if the permission is present. Used to read or recreate Chrome tab group names, colors, and grouping structure if the Extension supports saving and restoring tab groups.

sessions

Use this explanation only if the permission is present. Used to restore recently closed tabs or browser sessions if the Extension implements such functionality.

contextMenus

Use this explanation only if the permission is present. Used to add right-click menu actions that let users save or organize tabs, links, or pages.

5. Permissions to avoid unless strictly necessary

The Extension should avoid broad or unrelated permissions unless they are necessary for the product’s single purpose and clearly disclosed. In the current local-first concept, avoid permissions such as history, cookies, identity, webRequest, declarativeNetRequest, scripting, unlimitedStorage, and broad host_permissions unless a future feature clearly requires them and the Store Listing, Privacy Policy, and Chrome Web Store privacy disclosures are updated.

6. Limited Use commitment

The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.

Chrome API data is used only to provide or improve the Extension’s single purpose: allowing users to save, organize, search, and reopen tabs and links as local collections.

Chrome API data is not used for advertising, profiling, creditworthiness, unrelated analytics, sale, resale, or transfer to data brokers.

7. No sale or sharing of user data

The Extension does not sell, rent, trade, or transfer saved tab collections, links, or local Extension data to third parties.

8. Remote code

The Extension should not load or execute remotely hosted code. All JavaScript, HTML, CSS, and other executable resources should be included in the extension package submitted to the Chrome Web Store.

If remote code, remote configuration, cloud synchronization, or a remote service is introduced in the future, it must be reviewed for Chrome Web Store compliance, disclosed in the Developer Dashboard, and reflected in the Privacy Policy before release.

9. External project links

The Extension may include a link to the project website:

https://alarcev.n8nrgimprovise.space/a-tabs

If a user voluntarily contacts support by email or submits information through an external website, that information is handled separately from the local operation of the Extension and only for the purpose for which the user submitted it.

10. Public URLs