Privacy,
in plain sight.

LODE saves campaign and daily progress, creature discoveries, earned Flux, owned cosmetics, temporary trial access and preferences on your device. A previous-save backup is also kept locally. The core puzzles work without a developer account.

The game sends no custom gameplay analytics to ARKIV STUDIO. Your local save is not uploaded to a studio server. Exporting a backup gives you a copy of gameplay progress and preferences; it does not include card details, purchase tokens or a cloud account.

Keep exported backups somewhere you trust. Anyone who receives a backup can read the progress and preferences in it. LODE cannot recover a local save after you erase it unless you kept a usable export.

A video is requested only after you choose an optional reward or cosmetic trial. The closed test uses Google's demo rewarded ad unit. These are test advertisements and generate no real advertising revenue. Closing or failing a video does not grant a reward.

LODE stores completed-video counts, pending trial credit and trial expiry times in your local save. Ten-minute trials need one completed video. A 24-hour trial needs two videos, each chosen explicitly; the first completion keeps its credit without starting access.

What Google's SDK processes

Google AdMob and the User Messaging Platform (UMP) consent service communicate with Google. Test advertisements still use Google's SDK and network services. The Mobile Ads SDK can collect and share the following data for advertising, analytics and fraud prevention:

IP address & network information

Your IP address can indicate your approximate location. Device and network information support ad delivery.

Interactions

App launches, taps, video views and other interactions with the SDK or advertisements.

Diagnostics

Information about app and SDK performance, such as launch time, hangs and energy use.

Identifiers

App set ID and advertising or device-account identifiers where available under the build, device settings and consent choices.

Google encrypts Mobile Ads SDK data in transit using TLS. Its processing and retention are described in Google's Mobile Ads data disclosure and Google's Privacy Policy.

Consent before a video

LODE refreshes UMP consent information at app launch and presents a consent form when required. It checks UMP's permission before initializing the ad service or requesting a video. Starting the app or opening privacy choices does not request a reward video. If consent information cannot be refreshed, LODE does not request an ad.

When Google requires a privacy-options entry point, Ad privacy choices appears in Materials and in Settings under Privacy & credits. It remains available after an app restart. The choices shown depend on Google's requirements for your device and region.

Some closed-test builds may enable Google Play Games profile authentication. In those builds, Google can authenticate a Play Games profile and make profile information, such as a player ID, display name and profile image, available to the game. Google may authenticate an existing profile when the game starts. Guest puzzle play remains available.

This does not upload your LODE save. The current test has no Snapshots cloud-save sync, global leaderboard or studio account backend. Google handles Play Games profile information under Google's Privacy Policy. You can manage your Play Games profile and game data through Google's Play Games settings.

Availability depends on the test build and Google's account configuration. Configuring a Google service does not make cloud saves or competitive scores available in LODE.

Purchases

Checkout, paid Flux and Coils are disabled in this test. LODE does not collect card numbers or run a purchase-validation or paid-wallet service. The Store may display future paid offers, but they cannot complete a payment.

This policy website is hosted on Cloudflare Pages. Cloudflare processes network requests to deliver and protect the page. This can include IP addresses, request and routing information, device or browser information, and network or security logs. Its handling and retention are described in Cloudflare's Privacy Policy.

ARKIV STUDIO does not add analytics scripts, advertising, tracking pixels, forms or external fonts to this site. The page does not read your LODE save. Its reading controls use only the current tab's memory; we do not set cookies or save those choices to browser storage.

Cloudflare may use necessary security cookies if a protection feature is triggered. These are separate from this page's code; see Cloudflare's cookie documentation. Links to Google and Cloudflare open their websites, which follow their own policies.

1. Back up your progress

   Open Settings → Back up progress in LODE. Copy the export and store it somewhere you trust. Use Import progress to bring that backup to another device.

2. Erase local progress

   Open Settings → Reset progress and confirm the game's reset prompt. Clearing the app's storage also removes local saves. Delete any exported copies separately. Export first if you may want to restore later.

3. Change ad privacy choices

   Open Materials → Ad privacy choices, or Settings → Privacy & credits → Ad privacy choices, when that control is available. Review the Google form and submit your choices. You can keep playing the core puzzles without choosing a reward video.

4. Manage Google data

   Use Google Account and Play Games settings for Google profile and service data. Erasing LODE's local progress does not erase information already processed by Google or Cloudflare.