GROUPY TABSooMAE handles GROUPY TAB storage, sync, authentication and support as follows. Account provisions apply to builds with account authentication; Secret provisions apply when using the feature in version 1.0.3 or later. Publishing this notice does not announce a store release or provider approval.
1. Saved items and browser sync
Tab/folder titles, URLs, icon URLs, order, opening options, settings and undo history are stored locally. After you choose a source, bookmarks are read from the current browser or your selected HTML file. Import caches remain in that installation. We do not collect web page bodies or form input.
Enabled browser sync sends ordinary items and settings to that browser service, excluding undo history and authentication sessions. We do not bridge Chrome and Whale sync. A storage API success does not confirm another device received the data.
2. Secret workspace and backups
Secret items and history are encrypted in the browser using a password-derived key (PBKDF2-SHA256, AES-256-GCM). Decrypted contents exist in extension memory while unlocked. The password and decryption key are not sent to the license server; the operator cannot recover forgotten passwords or decrypt your backup. This is not a Google/Naver or separate sign-up password.
When both Secret and browser account sync are allowed, ciphertext is sent to browser sync storage. Ciphertext is also included in backups. Ordinary backup items/settings are not encrypted; including the license on export includes its readable key. Import has a separate license option. Passwords, authentication tokens and sessions are excluded from backups.
3. Accounts and licenses
Chrome checks the primary browser account and uses Google openid. Whale uses a separate Naver login with its basic user identifier. We do not request Gmail, contacts, Drive or Naver name/email/photo access. Google and Naver remain separate identities even with matching email addresses.
Keys and authentication proof are sent over HTTPS to the GROUPY TAB license service. The server validates the provider identity and sends the key/product identifier to Gumroad to check purchase validity, cancellation and Seats. Account authentication does not increment Gumroad uses. Gumroad handles payments; the extension does not collect card details.
Local storage holds the key, activation intent, account hash and retry records. The private Supabase application database holds product/key and provider/user hashes, binding time, seat order, short-lived authentication and rate-limit records. Hashes are pseudonymous, not anonymous. The application database does not retain readable keys, original account IDs, emails or provider access tokens. Network processing and infrastructure logs are separate.
A standard key allows one authenticated account; multi-seat keys allow their verified capacity. Each bound account has unlimited devices. Recovery is for the existing account only, not transfer to another account. Older builds without account authentication use direct Gumroad verification and may retain legacy local/sync copies. Updating does not erase all legacy copies.
4. Providers and international processing
Supabase hosts the license API/database; Google and Naver provide authentication and respective browser sync; Gumroad verifies purchases/licenses; Cloudflare Pages hosts the website; Naver Mail handles support. Ordinary tab/bookmark lists and Secret ciphertext are not sent to our Supabase server.
The primary database is in Seoul, South Korea. Edge execution, backups, logs and Google, Gumroad, Cloudflare or subprocessors may process data outside Korea, including the United States. A Seoul database does not mean all processing is domestic. Network transfers occur when syncing, authenticating, verifying purchases or visiting a service.
External icon requests may disclose connection information such as your IP address to image servers. Website/API providers may process IP, paths, timestamps and errors for operation and security. GROUPY TAB has no advertising or behavioral analytics SDK and does not sell personal information. The UI icon font is bundled rather than downloaded from Google Fonts.
5. Retention
Local items, settings, history and import caches remain until deleted or removed with extension data. Conflict copies and migration backups may remain locally to prevent loss. Binding records remain while needed to use/recover a valid license, then are deleted after their purpose ends or a verified request is processed, subject to legal obligations. Bindings do not expire automatically.
Naver flows are valid for five minutes, exchange tickets for two minutes and server sessions for one hour. Expired rows are cleaned on subsequent writes, not physically erased at expiry. The extension uses browser session storage for Naver and requires authentication after restart. Google caches are managed by the browser Identity API.
Support correspondence and ownership proof are retained for one year after the case closes, then deleted. Legally required records have separate purposes, grounds and durations. This is not a universal statutory transaction-retention period. Provider logs, backups and purchase records follow their applicable contracts and security/legal policies, not the one-year support period.
6. Deletion and recovery requests
Item deletion, sync pause, Secret reset, deactivation, logout and uninstall are different actions. Pausing sync does not erase remote copies. Secret reset resets current state but does not guarantee secure physical erasure of exports, offline devices or older conflict copies. Delete exported files separately.
Deactivation/logout does not delete or transfer a binding. Authenticate as the original account and activate the existing key to recover. Request access, correction or deletion by email; the operator verifies ownership, scope and license effects before acting, without arbitrarily deleting other seat holders.
Start with your version, browser, error text and steps. Never send passwords, authentication codes, tokens or card details. If purchase proof is needed, its minimum fields and purpose are explained privately. Effects of deletion on future use/recovery are explained before processing.
7. Safeguards
We use HTTPS, least privilege, short-lived authentication proof, private database access, Secret encryption and masked keys. Server secrets are excluded from the extension and website. A workspace lock is not complete protection from other extensions, malware or device access; protect the device and backups too.
8. Contact and changes
Operator and privacy contact: SooMAE / eveia@naver.com / https://groupytab.pages.dev/
Material changes are announced here and in product update information. Revised September 9, 2026; feature applicability is stated in the introduction.