Privacy policy

Data used by the extension

The extension stores the settings and tool data you save in Chrome extension storage. This can include authenticator account names and secrets, saved tab sessions and their URLs, saved tokens, preferences and Pixel Perfect profiles. Data stored in Chrome’s sync area may also be synchronized by Chrome according to your browser settings.

Website inspection and editing tools access browser tabs, storage and page information to perform the actions you request. Google Drive backups cover saved extension data; they do not separately copy live website cookies, website storage or Chrome-managed keyboard shortcuts.

Web Authenticator

The Authenticator at /auth can scan a QR code with the camera, read a QR image you choose, or accept account details you enter. Camera frames and chosen images are processed on your device and are not uploaded to the developer.

An encrypted copy of the authenticator vault may be cached in the browser so codes remain available offline. Decrypted account data is kept in memory while the app is open and is rebuilt from the encrypted cache when you return on the same device.

Google account access

Google Drive is optional. When you connect, Chrome handles Google sign-in and authorization. The extension and web Authenticator request only the drive.appdata scope to create, read, verify, restore and remove this application’s backup and authenticator-vault files in your private Drive app-data folder. It does not request access to other Drive files, Gmail or contacts.

Google access tokens authorize requests directly from the extension to Google. The web Authenticator keeps its short-lived Google access token in memory. Connection credentials and temporary restore data are excluded from extension backup snapshots.

Authenticator vault encryption

The shared Authenticator list uses AES-GCM encryption before upload. A random encryption key is created once and stored in the application’s private Google Drive app-data folder and on each connected device. This avoids a separate vault password and lets a returning device open codes offline. Access to the connected Google account or an already connected device can open the Authenticator list.

Backup storage and recovery

Snapshots are encrypted with AES-GCM before upload. An automatically generated recovery key is stored in the same Google Drive app-data folder and retained locally by the extension. Access to the same Google account through this application provides access to both backups and their recovery key; the key is not a separate password protecting against access to that Google account.

Daily backups run while Chrome is available, catch up after missed runs and retry failures. The extension retains the latest 14 backup versions per installation after verifying a new upload. Recovery keys are retained so existing backups remain recoverable. Expired burner authenticator accounts are excluded.

Standalone encrypted file exports can use an optional passphrase. Restore previews temporarily keep decrypted data in local extension storage for up to ten minutes. Applying a restore saves a local undo copy until a later restore replaces it, you use Undo, or the extension’s local data is removed.

Sharing and other network requests

Backup data is sent directly to Google Drive and is not sent to a developer-operated backup server. The extension does not sell Google user data, use it for advertising, or use it to train AI models. Its use of Google API information follows the Google API Services User Data Policy, including the Limited Use requirements.

User-agent preset updates contact official browser release feeds from Google, Mozilla and Microsoft. API testing and website tools may contact the destinations you choose. These requests expose ordinary network request information to their recipients.

Your controls and deletion

Disconnect in Backup & Restore to stop automatic backups; existing Drive backups remain. You can revoke the app’s access in your Google account’s third-party connections settings. To delete the app’s stored Drive data, use Google Drive’s Settings → Manage apps → Adel Dev Tools → Options → Delete hidden app data. Deleting this data also removes recovery keys and can make Google-dependent backup files unrecoverable.

Removing the extension removes its local data. Remove any synchronized data through Chrome’s controls and delete exported backup files separately. Keep a usable backup before removing data you still need.

Contact and policy updates

For questions, use the developer support contact shown on this application’s Google consent screen. Updates to this policy will appear on this page with a revised effective date.