ASL PC Steward: your data and choices

Local diagnostics

PC Steward processes scans on this computer. It requires no ASL account or other product, displays no advertising, includes no third-party tracking, does not sell personal information and does not automatically upload diagnostics.

Scans inspect performance totals, processes/resources, executable paths and company metadata, embedded signer subjects, Windows sessions, drive capacities and mount types, startup entries, tasks, services, shares, antivirus registrations, local network configuration, Windows health and bounded reliability history. Executable paths displayed locally are excluded from exports. Certificate presence is not a trust verification. Network latency checks contact only the configured local gateway. Read-only loopback requests can check a local ASL GPU broker and its separate aggregate Parallel Work projection; no ownership journal is read.

Dated findings and local history

Recognized Application/System events are inspected within the available 14-day window, subject to record/time limits. Up to 500 sanitized events are retained for display. Product labels, categories, timestamps and applicable hexadecimal Windows Update codes support per-product findings. Raw messages/XML, crash payloads and paths are not retained as reliability history. Deduplication event identifiers and local navigation targets are excluded from exports. Incomplete history stays explicit; scan time is not substituted for missing incident time.

Current, historical, recovered, stale and unknown states and guidance are computed locally. Rechecks compare the original target with a fresh bounded scan; their before/after view is not a new persistent incident database. Dates and sanitized finding evidence may appear in requested exports under default minimization. Historical incidents do not repeatedly reduce current health. Last successful broker contact is memory-only, not an exact outage-start timestamp.

Up to seven days of lightweight samples contain time, health score, CPU/memory/GPU totals, process/finding counts and monitor origin. At most one sample is stored per 30 seconds. These exclude accounts, sessions, process/task/service names, paths, network addresses, shares and private broker information. Trends are local.

Exports and app-owned data

Export occurs only on request. Known account, path, share, volume and network identifiers are minimized by default, including nested guidance. Users can explicitly include identifying details. Minimization is not anonymity: review before sharing. Support ZIPs contain the minimized report, inclusion notice and SHA256 integrity manifest, not a digital signature. Action/thermal histories, fleet data and credentials are not included in those bundles.

Local action history records selected targets, requests and verified, failed or uncertain outcomes. Incomplete/corrupt journals do not authorize repeated actions. Local Data shows history/export locations and separately confirmed clearing. Export removal is restricted to the app's named JSON/ZIP reports. Uninstalling the package does not guarantee deletion of separately retained reports/recovery files; use Local Data and the help center's removal guidance.

Sensors and guarded maintenance

Hardware/firmware/installed drivers determine available readings. Thermal values stay in memory, not thermal history, exports or fleet uploads. Steward installs no display/sensor driver. Public provider links attach no local diagnostics.

Supported NVIDIA cooling requires separate confirmation/elevation for bounded boost and automatic-policy restoration. AMD desktop cooling saves the selected adapter PNP identity, operation ID, original fan curve and Zero RPM in an administrator/System-only ProgramData/ASL-PCSteward-AMD-Cooling recovery file before writing settings. Removal follows verified restoration only. Failed or interrupted recovery retains the file for explicit recovery. GPU names and aggregate outcomes may be journaled; PNP identities/curve points are not journaled or shared. No voltage, clock or unrelated tuning reset is requested.

Narrow task/session changes require target confirmation, Windows approval and revalidation. Current sessions, protected Windows/ASL tasks and security-service stop/disable are unavailable targets. Scanning itself makes no repair.

Safe Cleanup reads file names, sizes and dates only in approved current-user Temp and CrashDumps after preview or explicit rule consent. Permanent removal is limited to 500 files/512 MiB per run and minimum age seven days. Changed, locked, protected, inaccessible and linked files are skipped. History records categories, age and aggregate removed/skipped counts/bytes, not individual filenames. Previews stay in memory and out of exports. Optional automatic cleanup starts off, requires separate consent and stops on app close. No service/task is installed; documents, downloads and project files are outside scope.

Optional fleet connection and controls

Explicit Connect sends a viewer key only to the chosen trusted HTTPS server to read machine/work reports. It does not upload a scan, enroll a node or grant execution. The server receives ordinary connection metadata, including source IP; its operator controls access/retention. Work descriptions may identify people or projects. Keys and reports stay in page memory and are cleared on disconnect, navigation or close. Reference clearing is not cryptographic zeroization. Keys are not saved, automatically loaded, logged, exported, put in URLs or forwarded through redirects. Optional refresh starts off/stops on navigation. Reports can expire without another refresh.

Separately authorized Broker Controls transmits target node, command ID, expected revision, pause/resume and duration to that coordinator. No executable code, file content or PC scan is sent. Only opted-in compatible nodes apply bounded new-GPU- admission controls; current leases and Parallel jobs are unaffected. Action history records displayed node, command and outcome. The coordinator retains its latest encrypted control state; node directives follow operator event retention. Receipt and confirmed node application are distinct. Delivery expires after 60 seconds; pauses expire within 15 minutes.

Independent products and support

Master Suite supplies its own private state to shared health components and does not automatically import Steward history or other-app credentials. Standalone Steward remains independent. AI Hub/rBroker execution and file-transfer permissions belong to those products; Steward viewer access is not consent to either.

Help: https://steward.autosecurelogin.com/help/. Support: support@autosecurelogin.com. Share reviewed information only, never credentials, private signing identities or unreviewed personal/workload files.

Using this website

The web host receives ordinary access and security metadata when you visit. This notice describes the desktop product. Website and support submissions follow the platform privacy policy. Do not submit credentials or unreviewed private files.