Local Data & Device Permissions
Local project files, settings, diagnostics, app package paths, Store/package checks, and device boundaries.
Page sections
Purpose
This page explains local device boundaries for the OptionForge desktop app, including local project files, settings, diagnostics, cache files, package installation paths, and Store-related access checks.
Local-first posture
OptionForge is designed as a desktop analytics app. App projects, local settings, diagnostics, cached assets, and user-imported data may be stored on the user's device or in folders the user selects or authorizes.
Store and package context
When distributed through the Microsoft Store, app installation paths, package identity, update handling, and Store/package checks are part of the Windows and Store environment.
Diagnostics and logs
Logs may include app version, timestamps, non-sensitive error messages, stack traces, configuration context, file paths, feature names, and troubleshooting state. Users should redact sensitive information before sending logs to support.
User-controlled files
Users are responsible for choosing where to save project files, exports, screenshots, imported broker files, local data files, and backups, and for protecting those files on their devices.
Permissions boundaries
OptionForge should only use device access needed for app functionality, local files chosen by the user, settings, diagnostics, charting resources, market-data/broker features initiated by the user, and Microsoft Store/package integrity behavior.