Garbled Text Fixer
Privacy Policy
Garbled Text Fixer repairs the character encoding of a webpage you choose. Page decoding and encoding detection run in your browser. Account and membership features use a separate ShipLang-hosted service, as explained below.
1. Webpage information and network requests
When you request a repair, the extension accesses the selected tab's URL, downloads that page's original HTML bytes, reads encoding and language hints, and processes its text locally. It uses this information to detect or apply a character encoding and update the displayed page. The extension does not upload the page's HTML or text to the developer or ShipLang.
Repairing a page is not an offline operation: the extension makes another request to the original page URL. Chrome may include the same-origin session credentials, such as cookies, that apply to that website. Images, stylesheets and other retained page resources can also be requested from their original hosts. Those websites handle these requests under their own privacy policies.
Page content and the applied encoding are processed in the page's execution context. The extension does not save page HTML or a browsing-history database in its persistent storage. Reloading or closing the page clears its temporary execution state.
2. Information stored in your browser
The extension uses Chrome's local extension storage, not its browser-sync storage, for the following purposes:
| Category | Information and purpose |
|---|---|
| Account and membership | When a sign-in or membership response is accepted, version 1.3.6 stores four account fields: the user identifier (uid), product identifier (appid), account email (mail), and membership expiration (end_at). These identify the account and product, determine membership access, and configure the uninstall contact link. Other fields in a new account response are not retained by the extension. |
| Trial usage | A count of successful trial repairs and any pending repair task, including a generated task identifier, tab identifier, browser document identifier when available, and whether it counts toward the trial. The document identifier binds a task to its original page; the pending-task record does not store the webpage URL. These records prevent overlapping operations from using the same remaining trial allowance and allow interrupted tasks to be recovered. |
| Temporary repair results | A task identifier, operation result and chosen encoding. Completed results are removed after the extension updates the corresponding usage record. |
| Uninstall-link registration | A local uninstallUrlSet flag records that the browser uninstall link has been configured. Chrome stores the registered link, which includes the account user identifier and extension version, with the interface language in its path. See section 5 for when that link is opened and what the hosted page processes. |
Account and accumulated trial records have no automatic expiration in the extension. Upgrading alone does not rewrite an older saved account response; the next accepted account update replaces it with the four-field record described above, or you can clear the local storage. Pending records are cleared after completion or when recovery detects that the original tab or document is gone; a genuinely unresolved task can retain its record until resolved. These local records do not contain the repaired page's HTML or text.
3. ShipLang accounts, membership and checkout
When you open an account or payment flow, the extension opens a page at crx.shiplang.com. The request includes the product identifier, Chrome extension identifier, extension version and browser interface language. If an account is already stored, it also sends the account user identifier (uid) and locally recorded membership expiration (local_end_at). These values are sent as URL query parameters to that service. The extension does not directly include the account email in this initial request; the hosted service can associate the identifier with its account records. Later redirects and pages within the hosted flow can include the account email (mail), user identifier (uid) and membership expiration (end_at) in their URL query parameters.
The hosted account and payment flow uses https://crx.shiplang.com and, for some completion pages, https://e.shiplang.com. The extension accepts account-result messages of the expected type only from the service window it opened on one of these two HTTPS origins, for the matching product, and retains the four account fields described above. Normal connection information, such as the requesting IP address and requested URL, is visible to the service handling the request. Page content being repaired is not included in this account request.
The hosted sign-in implementation uses Google to obtain the account's email and basic profile information, such as name and avatar, and uses a callback hosted at login.chromeextensions.workers.dev. See the Google Privacy Policy.
The hosted service implementation also processes user, product and extension identifiers, IP address, interface language, account creation and login times, login counts, membership status, and payment-page access times and counts. Creating an order can produce a transaction record containing the account email, user and product identifiers, selected plan and price, IP address, language, order status, and creation or payment times.
For compatibility with previous memberships, the hosted payment flow may send the account email to the legacy membership service at pay.extensiondata.com to check eligibility. Hosted payment pages also include remote images from img.icons8.com and tpc.googlesyndication.com; those resource hosts receive the network requests needed to load those images. The presence of these images alone does not establish what further processing those hosts perform.
Checkout takes place on hosted service pages; the extension itself does not implement a payment-card form. The service supports PayPro Global, Stripe and Paddle routes. The provider actually used depends on the plan and checkout presented to you; listing these routes does not mean that every purchase is sent to all providers. When offered and used, the relevant provider policy applies: PayPro Global Privacy Policy, Stripe Privacy Policy, or Paddle Privacy Policy.
ShipLang's supplied account-service policy states that login and membership records are retained until deletion is requested and that no backup of deleted account records is retained. To request account deletion, email support@shiplang.com, identify the extension by name or download link, and describe your request. Its stated processing period is seven days. This account-deletion statement does not specify the retention periods of separate operational, legacy-membership, uninstall-feedback or transaction records; contact ShipLang and the relevant provider for those records. Service-side retention is separate from the extension's local browser storage.
4. Why the extension requests permissions
| Permission | Purpose |
|---|---|
activeTab | Temporarily access the active webpage after your interaction with the extension, so the requested page can be inspected and repaired. |
scripting | Run the bundled encoding detector and repair code in the selected tab, read encoding information, and update that page's display. |
storage | Keep local account and membership information, trial usage, pending tasks and temporary operation results. |
The reviewed version does not request persistent host permissions and does not install an always-running content script across websites. It does use the current tab's identifier and URL when performing a requested operation.
5. Uninstall contact and feedback page
When a saved account for this product has a user identifier, the extension registers a browser uninstall link once. The registered address is on crx.shiplang.com; it contains the account user identifier (uid) and the extension version at registration (ver) as URL query parameters, and the browser interface language in the URL path. Registering the link does not itself request that page. Chrome can open it when you uninstall the extension.
Opening the hosted uninstall page creates a service-side uninstall record. The service uses the user identifier to look up the associated account email, product and extension identifiers, and links the record to its existing membership/payment status, renewal count and plan/payment-page visit counts. It also records the request IP address, language and extension version. The extension does not send the repaired webpage's URL, HTML or text in this link.
The hosted page automatically reports browser-provided device information when available: browser user agent and brands, platform, interface languages, timezone, screen dimensions and pixel density, color depth, display and motion preferences, touch support, processor count, approximate device memory, WebGL graphics information, and battery level or charging status. These measurements are collected by the hosted webpage, not by the extension's page-repair routine. This version does not include an installation timestamp in the uninstall link, so the page's installation-duration field defaults to zero rather than measuring actual extension use.
Selecting an uninstall reason on that page sends the selected reason to the service; submitting an optional comment sends that comment. If you claim a membership offer on the page, its claim status is recorded. The page can use its own browser site storage for an identifier when needed and a claimed-offer flag. If you choose a WhatsApp contact link, the reason and any entered comment can be included in a prefilled message; WhatsApp processes that interaction under its Privacy Policy.
These records support uninstall feedback, account identification and the page's support or membership-offer functions. To request deletion of the service-side uninstall and feedback records, contact support@shiplang.com; the account-service deletion statement in section 3 does not establish a separate retention period for these records.
6. Sharing, advertising and analytics
The extension's reviewed code contains no advertising or analytics SDK and no mechanism for selling personal information. It does not transmit repaired webpage content or a browsing-history collection to the developer or ShipLang. Network requests to the original website, retained resource hosts, ShipLang account services and the hosted uninstall-feedback page are described above. This statement does not imply that those separate services keep no connection or operational logs.
7. Your choices and deletion
You control which webpage to repair. You can reload the page to restore the website's original display, and you can stop extension processing by disabling or removing the extension.
To remove local account and usage records, clear the extension's local storage through Chrome's extension tools or uninstall the extension. This version has no built-in account-deletion or local-storage reset button. Uninstalling can open the registered ShipLang feedback page described in section 5. Removing local extension data does not delete an account, uninstall-feedback record or other record held by ShipLang or a payment or identity provider; request service-side deletion from the relevant provider. Hosted pages use their own site storage, which can be cleared separately in your browser.
8. Contact and policy updates
For questions about Garbled Text Fixer and this policy, contact the developer at e@shiplang.com. For ShipLang account-record deletion, use support@shiplang.com.
The developer and ShipLang are cooperating parties. Garbled Text Fixer is the developer's product and does not represent ShipLang. ShipLang supplies development tooling and the login and payment technology used by the integration.
This policy describes the reviewed extension version above. If its data practices change, this page will be updated with a new effective date.