Privacy, explained.

This page describes this website preview and the current Ascend Tweaks development build. It is information about the present implementation; policies for a future commercial release will be published with that release.

This website

This website includes a checkout price preview but no active payment form, order processing, marketing signup or custom analytics integration. Discount entries stay in browser memory in this preview; no valid coupon is embedded in the page or submitted to a payment service. The interactive example stores its simulated state in browser memory and resets when the page reloads. It does not read or modify your Windows settings, inspect your running apps, or send network probes.

The hosting service may handle access controls, authentication and ordinary connection logs under its own policies. The website’s owner-only preview access is separate from any future Ascend account or Pro subscription.

The Windows development build

The Windows app keeps its settings backups, session recovery journal, manual benchmark entries, saved gaming profiles and connection history on your PC. Applying a native change requires a local operation; the website cannot perform that operation for you. An optional report export writes a file to a location you choose.

The live monitoring page reads local CPU/RAM counters and supported NVIDIA driver sensors. A PresentMon CSV is read only after you select it; its path is kept in memory and it is not uploaded. Readings are sampled while the monitoring page is visible. No CPU sensor driver is bundled.

The source build includes an optional Google identity flow and local account workspaces, but no active payment system, cross-device cloud sync, analytics service or automatic upload of performance reports. OS network diagnostics send probes only when you choose a connection test. Windows and other installed products have their own network behavior and privacy settings.

Local Autopilot and advanced experiments

The default Pro Autopilot is a deterministic local rules engine. While enabled and the desktop app stays open, it checks for six fixed game process names and retains the selected process identity and setting originals locally to manage recovery. This path calls no AI service and has no inference usage fee. The enabled preference is stored locally. Stop is available without Pro.

Optional advanced experiments are separate. When a local model is selected, bounded hardware and frame-time summaries are sent to a separately installed loopback Ollama service. A separately configured owner cloud advisor can receive the bounded summaries when that advisor is explicitly selected. The default Autopilot and one-time local game profiles do not call it. No advisor is configured in the distributed build.

Optional Google sign-in

The desktop source implements Google sign-in through your system browser, with only openid, email and profile scopes. It verifies Google's signed identity response and uses the account identifier, verified email and display name to identify a local workspace. It does not receive your Google password or request Gmail, Drive, contacts or calendar access.

When configured, Google identity and refresh tokens are encrypted using Electron safeStorage (Windows credential encryption on Windows) before being stored locally. Account snapshots hold favorites, appearance preferences and saved gaming profiles on the same PC. This is not cross-device sync. Windows Recovery remains machine-specific and is never moved into a Google account. Signing out removes Ascend's locally saved Google token record, keeps local workspace/recovery data, and does not sign you out of your system browser or grant Pro.

Google registration is not configured or tested in this download. The app owner must create a Desktop OAuth client and complete the relevant audience/branding requirements before customer sign-in is offered. Google and the system browser handle their own network connections and data under their respective policies.

Recovery and local data

Original settings are saved before supported native changes. Keep recovery files until you restore the associated changes. Rebranding retains the legacy Windows data directory so originals are not lost. Deleting recovery records before restoring may remove the app’s way to recover those original values.

Plans and activation

The app stores a first-launch choice, a random installation identifier and, after valid activation, a signed Pro license locally. When the separately configured activation service is connected, the app submits the activation code and installation ID to that HTTPS service. It does not include hardware fingerprints, game processes or performance reports in activation requests. Signed licenses can be verified offline after activation.

The owner service is a separate private deployment, with authenticated code creation and a persistent single-use redemption ledger. It stores hashed codes, private labels, installation IDs, signed receipts and short-lived session/rate-limit records. It has not been connected to this app preview. No owner password or private signing key is distributed in customer downloads. Recovery remains available in Free.

Before a public commercial release

Contact details, final terms, support channels and any policies for accounts, licensing, payments or analytics will need to reflect the services actually introduced. None of those future services should be assumed to exist in this preview.