Resonance Run: Offline Jumping Game

Privacy Policy

Effective date: November 8, 2026 · Subscription update

Core campaign play works offline. Gameplay saves stay on your device. Optional online sign-in and subscription checkout process account and membership information to provide additional benefits. The extension has no advertising, analytics or cloud save synchronization.

Gameplay data on your device

The game stores completed stages, collected items, best times, earned and selected appearances, inventory, equipment used in a run, and run checkpoints. A death or revive continuation can include the current local position, hazards and boss state needed to continue safely. Settings, custom trails and their names, local creator-support timers, import/share allowances and internal operation identifiers are also local gameplay data.

The extension requests only the storage permission. Game saves and a previous valid backup are held in chrome.storage.local. Separate local records hold one-time trial-use counters, operation receipts, a pending membership action and cached account status. The background worker coordinates writes between this extension's popup and its expanded game tab. It does not read browsing history, other websites, contacts or clipboard contents.

A web preview uses its own IndexedDB/local storage, separate from installed-extension data. Code, art and language files are bundled; sound is generated locally.

Optional account and subscription service

When you choose Sign in, Restore membership or Subscribe, the extension opens https://crx.shiplang.com. It sends the product identifier, extension runtime identifier, extension version, browser UI language and, when available, the cached account identifier and membership expiry time. These fields let the service associate sign-in and subscription benefits with this product. Your saves, death location, score, inventory, trail names and backups are not attached.

The current callback returns an account identifier, account email, product identifier and membership expiry. Only these fields are cached locally as userInfo. The extension checks the product and expiry when authorizing benefits; the configured Simplified Chinese browser-language entitlement is granted locally. Offline access uses cached expiry, rather than a real-time server revocation check.

Google sign-in requests basic profile and email information under the Google Privacy Policy. The observed flow uses login.chromeextensions.workers.dev as the OAuth callback host. The extension callback does not store a Google password, OAuth access token or avatar.

Subscription price, billing period, renewal, cancellation terms and the payment provider are shown on the hosted checkout page. Payment details are entered there. The extension receives membership status rather than payment-card information; the service and identified processor handle checkout under the policies displayed on that page.

ShipLang supplies account and payment infrastructure to this independently developed product; the product does not represent ShipLang. According to the configured service terms, ShipLang stores the profile/email and membership information needed for its account service until deletion is requested, without keeping backups. Request account-data deletion at support@shiplang.com, including this extension's name or download link and the request and reason. Requests are handled within seven days. The extension developer's contact is e@shiplang.com.

Trials, expiry and local action records

Local trial counters record successful use of optional revive, early-level and equipment benefits. They are separate from exported gameplay backups and are not uploaded. Pending action records keep the selected local game action available when you return from sign-in or checkout. Closing a checkout window is not treated as successful payment.

Subscription benefits last for the authorization period. Expiry does not erase earned progress, owned equipment or saved creations. Uninstalling the extension does not cancel recurring billing; use the hosted service's subscription controls to manage or cancel billing.

Backups, trail codes and clipboard

Exporting progress creates a JSON file on your device; restoring reads and validates the file locally. Account credentials, membership authorization, the trial ledger and pending checkout actions are excluded from gameplay backups. Custom trail codes and downloaded files do not publish to a hosted community. The game writes a code to the clipboard only when you choose to copy it and does not read clipboard contents. Backups and codes can contain progress and user-entered trail names; you choose whom to share them with.

External links and uninstall feedback

Optional creator support opens the creator's YouTube channel only when selected, without attaching saves or gameplay identifiers. YouTube handles ordinary navigation under the Google Privacy Policy. The local five-minute reward timer does not verify video playback, subscriptions or watch history.

After an account has been cached, the extension configures a one-time uninstall feedback URL on the same hosted service. If you uninstall it, Chrome can open that page with the cached account identifier, extension version and language. Saves and scores are not included. Opening this policy or a contact link also produces a normal request to the relevant host or email provider.

Retention, deletion and use

Local data remains until extension data is removed or the extension is uninstalled. The developer has no server copy of gameplay saves and cannot recover or remotely erase them. Delete downloaded backups, shared codes and clipboard copies separately. For a web preview, clear that site's stored data. Closing a window does not delete progress. Removing local account data or uninstalling does not delete the service account or cancel a subscription; use the service controls or deletion contact above.

Data is used to provide gameplay, restore progress, honor preferences, authorize optional subscription benefits and avoid duplicate local actions. The developer does not sell it, use it for personalized advertising, or transfer it to data brokers. Use of data follows the Chrome Web Store User Data Policy, including Limited Use requirements.

Contact and changes

Contact e@shiplang.com for questions, giving the extension name and only the information needed to answer. If data practices change, this policy and effective date will be updated and any required disclosures will appear before the new handling begins.