DeskModia

DeskModia Privacy Policy

English reference version

This page presents the complete DeskModia Privacy Policy. No sign-in or JavaScript is required.

Effective Date: August 28, 2026
Application version reviewed: DeskModia 1.0.0
Operator: Ayumu Kurimune

This English document is the reference version of the DeskModia Privacy Policy. A Japanese translation is provided separately.

1. Scope

This Privacy Policy explains how the DeskModia Windows application accesses, uses, stores, and transmits information. It covers both the Microsoft Store (MSIX) version and the standalone EXE version where their behavior differs.

This policy is based on the implementation of DeskModia 1.0.0 and primarily applies to the DeskModia Windows application. The official DeskModia website is currently publicly available. The website does not use cookies, analytics, tracking, advertising, contact forms, external JavaScript, or third-party content. Except for this description of the website's current operation, the data practices described below concern the Windows application.

2. Summary

DeskModia needs broad local access to the Windows desktop in order to switch wallpapers, visible desktop items, standard Windows desktop icons, and icon layouts. It processes and saves desktop-related information on the user's device.

The Microsoft Store version does not use DeskModia-operated telemetry, analytics, advertising, cloud sync, or an app-originated update check. Information described as local in this policy is not automatically sent to the DeskModia developer.

The standalone EXE version contains an optional HTTPS update mechanism. It operates only when an update manifest URL has been configured. The default configuration in version 1.0.0 contains no update manifest URL.

3. Information DeskModia accesses and processes on the device

3.1 Desktop files, folders, and shortcuts

To show different items in different modes, detect newly created desktop items, and recover safely from an interrupted switch, DeskModia may access:

DeskModia does not normally read the contents of a registered document or ordinary folder merely because it is registered to a mode. It does read or copy content when necessary for a selected feature, including wallpaper images, custom mode icons, shortcuts, migration files, settings or recovery files, and Steam shortcut or installation metadata used to identify a selected game. Moving a registered folder moves the folder and its contents as a normal Windows file operation.

When the user explicitly chooses to move an eligible shortcut from the shared desktop to the personal Desktop, DeskModia asks Windows User Account Control for administrator approval and runs its own elevated helper to perform that move. The helper only moves the shortcut files the user selected; it does not run a command shell.

3.2 Desktop icon layouts and standard Windows icons

DeskModia reads and stores desktop icon coordinates, virtual screen dimensions, icon size, the applicable monitor-layout profile, and the identifiers needed to match registered items. It also reads and changes the Windows visibility settings for Recycle Bin, This PC, Network, the user files icon, and Control Panel according to each mode. Original settings are stored locally so that DeskModia can restore them.

3.3 Wallpapers and custom mode icons

When the user selects a wallpaper or custom mode icon, DeskModia reads the selected image and saves an app-managed copy. It may create rendered JPEG copies of wallpapers using the selected crop position, zoom, monitor resolution, and multi-monitor layout. The user's original selected image is not edited by this rendering process.

DeskModia also reads the current Windows wallpaper setting and may read a Windows theme cache copy when the configured wallpaper path is not directly accessible.

3.4 Monitor and display information

DeskModia accesses monitor device names or device paths, connected-monitor order, primary-monitor status, screen bounds, resolution, virtual-desktop geometry, and effective DPI or scale. This information is used to keep icon positions and wallpaper appearance separate for different monitor configurations.

DeskModia does not create a general hardware profile and does not read hardware serial numbers, advertising identifiers, MAC addresses, or precise location for this purpose.

3.5 Running applications and automation

If app-based automatic switching or mode-based app launching is used, DeskModia may locally inspect:

Process IDs, window titles, and executable paths obtained for the running-app picker are used transiently. The saved automatic-switch setting contains process names. Full paths of applications selected to launch with a mode are stored in the mode settings.

3.6 Windows account, language, package, and startup information

DeskModia reads the Windows display language to select the automatic app language. It also checks whether it is running with Microsoft Store package identity.

For Windows startup setup or cleanup, DeskModia may read the current Windows security identity name and SID. In the standalone EXE version, these values are used by Windows Task Scheduler to create per-user startup tasks. The Microsoft Store version uses the package startup registration and removes legacy EXE startup tasks or Run entries when applicable.

DeskModia does not provide account sign-in and does not call Microsoft account profile APIs to obtain a user's Microsoft account information.

3.7 Windows settings and Registry

For its desktop-management features, DeskModia reads or changes local Windows settings related to:

These operations are performed on the user's device to provide the requested mode, startup, and recovery behavior.

4. Information DeskModia stores locally

4.1 Main local data folder

DeskModia uses %LocalAppData%\DesktopModes as its main logical data location. In the Microsoft Store version, Windows may map newly created AppData files to package-private storage. The folder can contain:

The settings and recovery files are ordinary local files. DeskModia does not apply its own password protection or encryption to them. Their access is governed by the Windows account, file-system permissions, device security, and any storage or sync software selected by the user.

4.2 Backups and recovery records

Before certain saves, DeskModia may make an automatic settings backup. At most one automatic backup is created per minute, and the automatic-backup folder is normally limited to the 10 newest backups.

If a settings file is unreadable, DeskModia may create a timestamped corrupt-file copy. DeskModia keeps the 10 newest corrupt-file copies and makes a best-effort attempt to delete older copies. A copy can remain if Windows or another program prevents its deletion.

Temporary transaction and recovery files are used to undo or continue an interrupted desktop switch. They are normally deleted after successful recovery, but may remain if recovery or cleanup cannot be completed.

4.3 Local logs and crash information

DeskModia writes a local app.log file. It can contain timestamps, app events, mode names or identifiers, monitor topology or timing information, file or folder paths involved in an error, and exception details. Exception details can include error messages and stack traces. A full path may include the Windows user-folder name.

DeskModia does not automatically upload this log. Before a normal log entry would make app.log exceed 5 MB, DeskModia rotates it and keeps up to three older generations (app.log.1 through app.log.3). Rotation is best effort so that a temporary file lock cannot prevent app startup or a desktop operation; a locked log can temporarily exceed the limit until a later write succeeds. The current log and its retained generations remain until they are rotated, reset, or removed with applicable local data.

DeskModia also writes a small running-session marker containing the DeskModia process ID, session start time, and app version. It is deleted after a normal shutdown and is used only to detect a possible previous abnormal termination. DeskModia does not automatically send crash reports, crash markers, exceptions, stack traces, or dump files to the developer.

4.4 Asset and temporary-file retention

App-managed wallpaper and custom-icon copies that are no longer referenced are normally removed after a successful settings save. Copies still referenced by automatic backups are retained. Cleanup failures can leave unused copies behind.

Imported migration assets and generated wallpaper images are not all subject to an automatic age or size limit in version 1.0.0. EXE update installers downloaded into the local Updates folder also remain until replaced, reset, manually removed, or removed with applicable app data.

5. Microsoft Store safe storage: DeskModia Files

The Microsoft Store version cannot run a custom cleanup program at every possible uninstall entry point. To avoid leaving an original desktop file or folder hidden and inaccessible after package removal, DeskModia uses a normal user-owned folder named DeskModia Files.

Registered items that are on the personal Desktop and are not visible in every mode may be moved into this safe-storage folder. DeskModia then displays shortcuts to the stored originals as required by each mode. The purpose is preservation and uninstall safety, not deletion. Restoring the desktop may recreate shortcuts while the originals remain in DeskModia Files.

For new Microsoft Store storage, DeskModia uses one canonical root at %UserProfile%\DeskModia Files. Rendered wallpapers used by the Store version are saved below the same root in %UserProfile%\DeskModia Files\Applied Wallpapers so that Windows can continue to read them. Earlier DeskModia builds could create safe storage beside a redirected Desktop, for example %UserProfile%\OneDrive\DeskModia Files. To avoid moving, overwriting, or losing user files during an update, DeskModia continues to use an already-recorded legacy location for those existing items and does not automatically merge or delete it.

DeskModia Files and its contents may remain after DeskModia is reset or uninstalled. Users can inspect and manage these files in File Explorer. Deleting or moving them while they are still referenced by a DeskModia mode can cause shortcuts or wallpapers to stop working.

DeskModia itself does not upload DeskModia Files. The new canonical root is independent of the current Desktop redirection path. An already-recorded legacy folder may still be inside OneDrive or another sync area, and a user can independently configure broader profile-folder synchronization. In those cases, that separate product may sync the folder according to the user's settings and its own privacy terms. DeskModia does not disable or reconfigure that synchronization.

6. Migration and export files

The user can choose to create a .desktopmodespack migration file and choose where to save it. In version 1.0.0, this file can contain:

Before export, DeskModia removes registered desktop file and folder entries, saved icon positions and layout profiles, app-launch paths, automatic-switch process names, keyboard shortcuts, favorites, active-mode state, and switch history from the migration data.

A .desktopmodespack file is not automatically uploaded. It is an ordinary archive and is not password-protected or encrypted by DeskModia. The user controls its storage, copying, sharing, and deletion. Anyone who receives it may be able to view its settings and included images.

DeskModia can also read compatible legacy JSON settings files selected by the user. Those files may contain full settings or paths created by an earlier version, but the import process removes PC-specific mode data before adding portable modes to the current settings.

7. Network communication and external transmission

7.1 Microsoft Store (MSIX) version

DeskModia 1.0.0 does not perform its own update request when it is running as the Microsoft Store package. It does not send DeskModia settings, desktop paths, wallpapers, icons, process information, logs, crash information, or usage telemetry to the DeskModia developer or a DeskModia server.

Microsoft Store and Windows may independently use network connections and Microsoft account or device information to download, install, license, or update Store apps. Those Microsoft operations are separate from DeskModia's own data processing and are governed by Microsoft's terms and privacy statement.

DeskModia uses Windows.Services.Store APIs provided by Microsoft to retrieve Microsoft Store product, price, purchase-status, and license-entitlement information for DeskModia Pro and to display Microsoft Store purchase UI. Purchase and license communications are handled by Microsoft Store. DeskModia does not send purchase information to a DeskModia-operated server and does not receive or store Microsoft account IDs, email addresses, payment details, authentication tokens, or full receipts.

7.2 Standalone EXE version

The standalone EXE version contains an optional update feature. It makes an HTTPS request only if an update manifest URL has been configured. Version 1.0.0 uses an empty URL by default, so the default build makes no update request.

When configured, the feature retrieves update metadata from the configured host. If the user agrees to download an available update, it retrieves the installer and verifies its SHA-256 value locally. The update implementation does not attach DeskModia settings, desktop paths, logs, or a device identifier to these requests. The receiving host can receive ordinary request information such as the IP address, request time, requested URL, and HTTP headers. HTTPS protects the contents in transit, although network providers may still observe connection metadata such as the destination host, IP addresses, timing, and traffic volume.

7.3 Features not used by the current app

Based on the implementation of version 1.0.0, DeskModia does not use:

8. Disclosure, sale, and advertising use

DeskModia uses Windows components locally to perform file, shortcut, wallpaper, Registry, Explorer, and startup operations. This is not an upload to the DeskModia developer.

DeskModia does not sell the device-local information described in this policy and does not use it for advertising. It does not automatically disclose that information to outside services. Information can leave the device when the user chooses to share an export file, stores data in a folder synchronized by another product, uses the standalone EXE updater with a configured host, or otherwise sends information to support or another party by the user's own action.

9. User choices, access, and deletion

Users can control local processing by editing or deleting modes, changing which desktop items appear, disabling app-based or scheduled automation, disabling Windows startup, removing registered items, or resetting DeskModia.

DeskModia provides an option to open its local data folder. The in-app reset removes most DeskModia-managed settings, backups, logs, imported data, cached wallpaper/icon copies, rendered EXE wallpapers, transaction files, and downloaded EXE updates when those files can be deleted. It then creates fresh default settings. Files that are in use or could not be removed may remain.

The reset does not delete user-created .desktopmodespack files or other exports saved elsewhere, and it does not delete DeskModia Files or Store-version applied wallpapers. Users can inspect and delete those separately in File Explorer after confirming they are no longer needed.

DeskModia currently has no developer-operated user database. Therefore there is no server-side DeskModia profile for the user to access or delete. Questions about this policy may be sent to DeskModia Support below.

10. What may remain after uninstall

Microsoft Store version

New AppData files created by a normally virtualized Store package are generally placed in package-private storage and removed by Windows when the package is uninstalled. However, DeskModia does not receive an uninstall callback and cannot promise removal of files that are outside that package-private storage. In particular, the following may remain:

Standalone EXE version

The standalone uninstaller first asks DeskModia to restore desktop visibility. If restoration succeeds, the installer is configured to remove %LocalAppData%\DesktopModes and the DeskModia desktop shortcut. User-created exports and files stored elsewhere are not removed. If restoration cannot be completed, the uninstaller is designed to stop rather than silently remove DeskModia while desktop items may still need recovery.

11. Security

DeskModia limits its automatic external communication as described above. Local settings, logs, migration archives, and recovery files are not protected with DeskModia-specific encryption or passwords. Users should protect their Windows account and device, review files before sharing them, and store exported files in an appropriate location.

When the standalone EXE updater is configured, DeskModia requires HTTPS and verifies the downloaded installer against the SHA-256 value provided by the update manifest. This does not replace the user's normal Windows and network security controls.

12. DeskModia Free and DeskModia Pro

DeskModia is distributed as a Free application. DeskModia Pro is offered through Microsoft Store as a non-consumable, one-time-purchase durable add-on. DeskModia checks the Microsoft Store license to decide whether Pro features are available.

DeskModia does not create a separate DeskModia account or independently manage a permanent Pro entitlement. Microsoft Store licensing remains the source of truth, and a temporary license-check failure does not cause DeskModia to delete saved modes, automation settings, or other user data.

13. Children

DeskModia is a general Windows desktop utility and is not designed or directed specifically to children. The app does not provide account registration, social features, or advertising. Parents and guardians should supervise use of Windows utilities and the files selected for them as appropriate.

14. Changes to this policy

This policy may be updated when DeskModia's features, distribution methods, data practices, or legal requirements change. The revised policy will show a new Effective Date. Users should review the current policy when installing a significant update.

15. DeskModia Support

Operator: Ayumu Kurimune
Email: deskmodia.help@outlook.com

Please do not send logs, migration files, screenshots, or other files containing personal information unless support asks for specific information and you have reviewed what the file contains.