Privacy policy

About this policy

This policy covers the ALTA TAB (ALTATAB) Chrome extension, including beta versions. ALTATAB organises links and browser tabs into collections and folders. Developer contact for support and privacy enquiries: abilov.st@gmail.com.

Data processed

ALTATAB processes saved website titles and URLs; folder and collection names, order, favourites and creation dates; saved tab-group metadata; open tab titles and URLs and bookmark structure for visible session-management features; language, theme, zoom, layout and expansion preferences; recently deleted items and recovery copies.

Folder and collection protection stores a password verification hash and salt rather than the original password. When you connect Google, the extension processes the account identifier and email address or display name, plus an OAuth token used to call Google APIs. It does not request your complete Chrome browsing history or extract page bodies, form contents, messages, website passwords or your Google password. Saved URLs may themselves contain sensitive parameters.

Purpose and local storage

Data is used to display, search, save, edit, organise and reopen collections, manage browser sessions, preserve preferences and recover data. The primary database is stored locally in the extension’s Chrome storage and works offline. Session storage holds temporary quick-save records. Local recovery snapshots, a legacy migration backup and downloaded exports may retain previous collection data. The extension has no advertising analytics or behavioural click/keystroke tracking and does not upload collections to a developer-operated server.

Optional Google Drive sync

You enable sync by choosing to sign in with Google. The requested scope is https://www.googleapis.com/auth/drive.appdata, for ALTATAB’s hidden application-data folder. This scope does not allow the extension to read your ordinary Drive documents and folders.

Sync uploads saved collections, URLs, folders, preferences, recently deleted records, password verification hashes and salts, and revision metadata such as timestamps, IDs, a data hash and a random device identifier. OAuth tokens and the local account label are excluded from the collection database and exports. Current open browser windows are not automatically synchronised; collections you save from them are.

Google API requests use HTTPS. Google processes data under its terms and privacy policy. Sync does not give the developer a separate copy of your collection database.

Limited Use

Google API data is used only for the stated user-facing sync and recovery features. Its use and transfer follow the Google API Services User Data Policy, including Limited Use, and Chrome Web Store user-data requirements. Data is not sold or used for personalised advertising, credit decisions or unrelated purposes. The developer does not inspect private collections through Google APIs.

Passwords and security

Folder and collection passwords restrict viewing in the ALTATAB interface; they do not encrypt URLs in local storage, cloud revisions or exported files. Password verification uses PBKDF2 with a salt and SHA-256. Interface protection does not replace device and Google-account security. OAuth tokens are used during operation and are not included in collection backups.

Data transfers and support

Google receives data needed for your chosen sign-in and sync features. Opening a saved website makes a normal browser request to that website under its own policies. Website icons use Chrome’s favicon mechanism. Copy and export actions place data in your clipboard or a file that you control; the extension does not read the clipboard. If you email support, the developer receives your sender address and the information you choose to send, for handling your enquiry. Do not include tokens, passwords or unnecessary private links.

Retention and deletion

Collections remain until you remove them. Deleted items may remain in Recently deleted until permanently removed or displaced by storage limits. The current version keeps up to three local recovery snapshots; a legacy migration backup may be retained separately. Previous cloud revisions and downloaded exports can retain older information even after it is removed from the current database.

Disconnecting Google stops sync but does not itself erase local or cloud data. You can also revoke access in your Google-account connection settings. To erase cloud revisions, disable sync on all devices and remove ALTATAB’s hidden app data using Google Drive’s app-management settings. Uninstalling the extension alone should not be treated as deletion of cloud history.

Uninstalling from the relevant Chrome profile removes its local extension database and internal backups. Delete downloaded exports and copies on other devices separately. Reconnecting a device with remaining data may upload it again. Support correspondence is kept for resolving and following up on the enquiry or applicable obligations. Contact the developer for access, correction or deletion enquiries; the developer cannot directly erase your local database or Drive folder without access to them.

Permissions and your choices

Tabs and tabGroups support session management; bookmarks supports bookmark display, copying and legacy migration; favicon supplies icons; storage and unlimitedStorage hold the local database and recovery copies. Identity and Google API host access support optional sign-in and sync; alarms support sync checks and expiring undo records; contextMenus enables user-triggered saving; clipboardWrite enables user-triggered address copying. Collection management works without Google sign-in.

This page and policy changes

This page has no custom advertising trackers, sign-up forms or analytics scripts. The hosting provider may process technical request information to deliver and protect the service under its own rules. This policy is updated when data practices change, with the revision date shown. Material new processing requires appropriate notice and consent where applicable. Contact: abilov.st@gmail.com.