RTX AI Activity Monitor — Windows privacy

RTX AI Activity Monitor — privacy notice
Last updated: 8 September 2026. Applies to the Windows Store edition, version 1.0.2.
Store publisher: Vellora Studio One. Product/privacy contact: https://vellorastudio.one/support/index.html

LOCAL PROCESSING AND NETWORK ACCESS
The application processes monitoring information on your Windows device. It does not require an app account, include advertising or analytics, make application network API requests, or automatically send monitoring records to the publisher or external services. It does not inspect AI prompts, responses, model contents, documents, process command lines or process memory.
Hardware readings come from your installed NVIDIA driver and Windows GPU performance counters. The app loads those local system components; it does not download a GPU driver, AI model or monitoring engine. Microsoft Store, Windows, your GPU driver, backup/synchronization software and websites you choose to visit have their own behavior and privacy terms. This notice describes this application, not those separate services.
Cooperating applications can report activity through a local named pipe restricted to the current Windows user. There is no app TCP/UDP listener or local web server. The pipe name incorporates a hash of the current Windows user SID to separate users' endpoints; it is not sent to a publisher service. The monitor checks the connecting machine and Windows-reported process ID and obtains the process name. The GPU ID and session state are reported by the other application, not independently verified GPU execution. Other software running as the same Windows user is within this trust boundary.

INFORMATION PROCESSED AND STORED
Live monitoring processes GPU identifiers and names, available utilization and memory readings, temperature and power readings, process names/IDs, engine activity and availability diagnostics. Stored files contain:
settings.json: selected GPU identifier, appearance and startup preferences, process-name rules and exclusions, activity threshold, recording preference and retention days. Windows' actual startup state remains authoritative.
history.jsonl: sample timestamps, GPU identifier, utilization, dedicated-memory usage, classification and observed process names/IDs. These records do not contain a history of every displayed temperature or power reading.
sessions.jsonl: completed application-reported sessions containing start/end times, Windows-attributed PID and process name, application-reported GPU/session identifiers and the reason the reported session ended.
The app requests storage beneath the current user's LocalApplicationData directory, in Sortcapital\RTX AI Activity Monitor. That existing local directory name is a technical storage name; the Store publisher is identified above. Windows may manage or redirect packaged-app storage. The app can also create temporary files while updating its settings and history. The Store package includes no pre-recorded user history.

RECORDING, RETENTION AND STOPPING MONITORING
Recording is enabled by default. Retention defaults to seven days and can be set from one to 90 days. Persistent samples are normally recorded about every ten seconds while the monitor runs. Short activity between samples may not appear. Completed app-reported sessions are separate records; their durations are not independently measured GPU execution and overlapping sessions are not unique active time.
At launch the app filters expired history/session records and attempts to rewrite the retained files. During recording, history is pruned in memory and rewritten at a 360-record count boundary, approximately hourly at the nominal sampling rate. This is a count trigger, not a guaranteed hourly purge. Sessions are rewritten when completed-session processing or retention removal changes them. Saving settings also applies retention to both files. Expired records can remain on disk until a successful rewrite; file-access errors can prevent writing or purging.
In Settings, disable Record local history and save to stop new persistent recording; live monitoring continues. Existing records are not immediately deleted by disabling recording. Clear history removes the app's retained sample and completed-session records after confirmation. It does not delete settings, user-created exports or backups. If recording remains enabled, further activity can create new records, including completion of already-active reported sessions.
Process exclusions affect classification and newly recorded process labels/reported sessions. They do not erase older records, remove total GPU activity measurements, or conceal a process from all live telemetry. Use Clear history when you want to remove stored records rather than only change future rules.
Closing the window hides it while monitoring continues in the tray. Choose Exit from the tray menu to stop the monitor. Windows controls whether its icon is visible beside the clock or in the tray overflow area.

OPTIONAL SIGN-IN STARTUP
The Store edition's Windows StartupTask is disabled by default. Startup is requested only when you explicitly change Start with Windows and save. The app reads the actual Windows state and respects user-disabled and policy-controlled states; it does not silently enable startup on launch or when saving unrelated settings. If Windows reports that you disabled it there, re-enabling must be done in Windows Startup settings. The Store edition does not use the standalone edition's current-user Run registry integration.

EXPORTS AND REMOVAL
The Export control offers CSV/JSON records for the selected GPU and interval, or a PNG of the current window. Completed sessions are selected by their end time in the interval and include their full reported start/end times. Exports can expose GPU/process/session identifiers and other visible metadata. CSV textual metadata is quoted and formula-like text is prefixed to reduce spreadsheet formula interpretation; review any exported file before sharing it.
Pressing Export may create RTX AI Activity Monitor Exports inside your Documents directory before the Save dialog appears. The export file itself is written only after you choose a destination and confirm. Existing-file replacement prompts are enabled. If you choose a synchronized or network location, that location's software or service may transfer your file; the app does not automatically upload it to the publisher.
Exports, copies and backups are outside the app's retention controls. Windows may remove package-managed data during uninstall, but uninstall is not a guaranteed way to erase copies, legacy standalone-app folders, exports or backups. For deliberate removal, clear stored history in the app, exit it, and remove any remaining copies you control. Do not delete unrelated files.

CONTACT
For app support or privacy questions, contact Vellora Studio One through https://vellorastudio.one/support/index.html. If you choose to send a support message or attachment, that communication is separate from the app's local monitoring. Do not include prompts, sensitive process information or complete exports unless you intend to share them.