Privacy, Versions, and Troubleshooting

Network Activity

Seer establishes network connections only under the following conditions:

  • Implicitly:
    • Markdown/HTML Preview: Requests external resources (images, styles) to render content correctly.
    • License Verification: Occurs only during the activation process. No recurring validation requests are made.
    • Update Checks: Initiated once within the first minute of startup.
    • Note: This can be disabled by unchecking Automatically check for updates in Settings.
  • Explicitly:
    • Downloads: When you trigger a plugin download, the actual network request is handled by your system's default browser.

Understanding Version Indicators

The icon next to the Seer logo indicates the current execution state:

  • U: Microsoft Store version.
  • No U: Website (Desktop) version.
  • +: Running with Administrator privileges.
  • No +: Running with standard user privileges.

Log & Crash Reports

To assist with debugging, locate the log and dump files:

  1. Press Win + E to open File Explorer.
  2. Enter %TEMP%\Seer in the address bar.
  3. Look for Seer.log (logs) and any .dmp files (crash reports).
  4. Submitting Reports: Open the About window in Seer, click the support email address, and attach these files along with steps to reproduce the issue.

Customizing Configuration Paths

If Seer fails to persist settings due to file permission issues, you can force it to use a specific location:

  1. Ensure Seer is not running.
  2. Navigate to %USERPROFILE%\Documents.
  3. Create a directory named Seer.
  4. Inside Documents\Seer\, create an empty text file:
    • Desktop Version: Name it config.ini
    • Store Version: Name it uwp.ini
  5. Restart Seer. It will now use this file for all configuration read/write operations.

Tip: You may create a user.ini in the same directory to further customize configuration paths.