Help & getting started

Your words.
Your account. Connected.

Sign in once for the website and extension

  1. Open the Linkuage menu in your extension and its account/sign-in option.
  2. Sign in on linkuage.com with Google or an email sign-in link.
  3. Your installed extension automatically uses that verified account. There is no separate Connect or approval step.
  4. Return to the extension. Its account and credit display should match your website account.

Your website sign-in, sign-out and account changes also apply to the current extension. Account names and credit come from that same server account. Signing in never activates a waiting package by itself. Old test identities are not merged by matching email; their saved records remain separate and are not deleted.

Existing beta installations: update files in the same unpacked extension folder, Reload it in Chrome’s Extensions page, then refresh the page you are reading. Do not uninstall or clear browser storage to update. Ask support for an approved installation package; no public store listing is advertised here.

Requested, waiting and active are different

  1. Requested: awaiting the administrator’s decision. It is not credit yet.
  2. Waiting: approved or granted, but its clock has not started.
  3. Active: started on the next paid AI request from that account, or by explicitly activating it on the AI Credit page.
  4. Expired or exhausted: the next eligible waiting pack can start. A previous remainder retained after an allowance rejection keeps its original expiry.

The $5 pack lasts 14 days from activation. Larger packs show their own validity. A clearly labelled, administrator-issued short test pack is a separate testing exception. Waiting packs are not combined into one active balance.

When no usable credit remains, open AI Credit and select Activate waiting package. Review the expiry confirmation. If a large request is rejected despite a positive balance, a smaller request may still fit; follow the account’s waiting-credit choice instead of repeatedly buying or granting packs.

An activation marked “needs review” may mean the provider created a key but its response was lost. Contact support; repeating grants will not repair that state. No automatic purchase is made. Public payments remain disabled while merchant setup is completed.

Understand which tool is running

Source / YT uses available video captions or YouTube translation. AI translation, linking, Video Map, sponsor detection, generated subtitles, Explain, Linkuage Ask and read-aloud can require paid processing. Existing results may be reused without generating them again. Video Map and sponsor controls are independent of translation.

My AI opens your own connected chatbot and does not require Linkuage credit. Your chatbot’s subscription and limits still apply; optional Linkuage speech is separate. Signing in with Google does not authorize Linkuage to spend a ChatGPT subscription.

Warnings on tool buttons explain a failure when hovered or focused. A warning is not necessarily a credit failure: captions, audio downloads or model output can also fail. Keep completed work and inspect the message before retrying. Platform access and AI accuracy cannot be guaranteed for every video.

Keep saved work separate from cache

Your Saved library contains text and source links synced to your account. Audio and large media are not part of that text-library export. The Account page lets you search, edit, export or explicitly delete synced items. Deletion propagates to connected devices while sync is active; exporting first preserves a separate copy.

Cached processing results and deliberately saved items serve different purposes. Do not clear browser data to fix a balance or account problem. You can sign out or revoke sessions from the Account tab without deleting saved work or credit history.

Get a real support reply

Open Account → Help & support, choose a category and send a request. Replies appear there; use Refresh replies. If you cannot sign in, email support@linkuage.com.

Include the account email, affected feature, pack/order reference or video URL if relevant, and the visible error. Never send passwords, sign-in links, API keys, cookies or payment-card details. For privacy requests, choose the privacy category; account ownership will be verified before sensitive changes.