AI Credit Helper privacy policy

Purpose and reading scope

After site-by-site authorization, AI Credit Helper processes only explicitly displayed balances, breakdowns, expiry, refresh or confirmed renewal dates, recurring allowances, and the minimum identifier needed to distinguish an account or workspace. An unconfirmed page balance stays separate and is not used for account alerts, local sharing, or confirmed-account exports.

It never reads or stores creations, prompts, chats, complete browsing history, payment credentials, passwords, cookies, or sign-in tokens. It never signs in, claims rewards, generates, spends, purchases, renews, or cancels for you.

Storage and transmission

Credits and settings stay in extension-local browser storage. Browser cloud sync is not used, and nothing is uploaded to a developer server, advertising service, analytics SDK, or AI service. Only enabled sites are processed. A background account summary is opened only when necessary and ends after success or timeout.

Raw account identifiers are not persisted. A SHA-256 hash is stored using a random per-install salt. Credit snapshots, alerts, settings, and salt use AES-GCM 256-bit encryption with a fresh random initialization vector per write; the non-exportable CryptoKey stays in extension IndexedDB. Key and ciphertext are on the same device, so this cannot protect a controlled computer or browser. Exported JSON is plaintext.

Optional local-app connection

You may separately install a general local connector and explicitly select platforms to share. It sends only standardized credit snapshots and never reads raw identity, cookies, tokens, or full page text; it cannot trigger collection, claiming, spending, or generation. The connector does not upload data, but an authorized AI client may send selected fields to its model service.

Connector cache is plaintext under the current Windows user. A normal disconnect removes shared balances immediately; an abnormal exit expires within 45 seconds. Source-level no-balance status may remain for up to 7 days. Copies already received by another application cannot be remotely recalled.

Retention and deletion

Each account keeps the current and previous successful snapshot until clearing or uninstalling. Pause stops new observations and alerts. Revoking access stops site access while retaining records. Clearing a platform deletes its local account labels, snapshots, and alert state and leaves it paused. Clearing all resets settings and revokes requested site, notification, and local-connection permissions. Downloaded files must be deleted by the user.

LibTV remains; LiblibAI was removed. Its collection, alerts, sharing, and permission stop after upgrade. Old encrypted records remain available for local preview, export, or separate clearing.

Notifications and permissions

Site access is requested per platform; system notifications and native messaging are requested separately. The extension does not request all-sites, cookies, browsing history, or debugger access. Alerts use the latest successful observation and are not guaranteed to be real-time or timely while the browser is closed, offline, or suppressing notifications.

Contact and changes

Product support: 934026@qq.com. WeChat / QQ: 934026. Community participation is optional. Add WeChat 934026 with the note “Credit Helper” to ask how to join the user community. Joining is never required to use the product or send feedback by email.

Never send passwords, cookies, tokens, or complete account data. Diagnostics are not uploaded automatically. This policy will be updated when features or data processing change.