Privacy Policy

Last reviewed: 24 October 2026

Spinrola is a Windows desktop application for converting, editing, and working with files. This policy describes the behavior of the Spinrola application. The website that hosts this policy may have separate hosting practices.

Files you use with Spinrola

Spinrola reads files you select or drag into the application and processes conversions and edits on your device. Its conversion and editor code does not upload file contents to a Spinrola server. Results are saved on your device, either beside the source file or in the output folder you choose. Processing may read and carry over embedded metadata, such as image or media metadata, depending on the operation and your settings. Spinrola also offers tools to inspect or remove certain metadata.

The optional Share action passes the files you select to the Windows share sheet. If you then choose a sharing app or service, that destination handles the files under its own privacy practices. The Copy Path and metadata-copy actions put the selected information on the Windows clipboard. Files kept on Spinrola's floating shelf are held in the running application's memory; the source code does not save a shelf history. Files in a network or cloud-synced folder may also be handled by that folder's provider independently of Spinrola.

Information collected by Spinrola

Spinrola does not require an account. Its source code contains no advertising, application analytics, or publisher-operated telemetry or crash-report upload. Spinrola does not send your selected file contents, settings, or application logs to its publisher. Local settings and logs can nevertheless contain personal information, such as a folder path or a file name. If automatic updates are enabled in your build, the update host receives ordinary network request information as described below.

Spinrola uses Windows and the Windows App SDK. Microsoft's license for the Windows App SDK states that its software may send diagnostic information to Microsoft. Windows and Microsoft control those practices; they are separate from Spinrola's own logging and update requests.

Information stored on your device

• %APPDATA%\Spinrola\settings.json stores your wheel appearance and behavior, enabled actions, shortcuts, output options and any custom output-folder path. Saving uses a temporary settings.json.tmp file. If settings cannot be parsed, Spinrola may keep a dated settings.json.corrupt-* copy. On first launch, it may copy settings from an older DropDial test installation into this folder.
• %LOCALAPPDATA%\Spinrola\logs\ contains local host and editor logs. These record operational events, timings, job counts and errors. Error text can include file names or paths. Host logs rotate at about 2 MB and the editor log is recreated after about 1 MB; the app does not upload these logs.
• When automatic updates are configured and a newer version is offered, %LOCALAPPDATA%\Spinrola\updates\ stores the highest offered version and a staged installer, signed update manifest, updater copy, and potentially installation backup, setup log and result file. The source code does not automatically remove successful update staging folders.
• File operations use temporary work files in a hidden .spinrola-work folder inside the output folder and ImageMagick may use %TEMP%\Spinrola\magick. Normal output-work cleanup is attempted when a job ends; interrupted work or library temporary files may remain. Converted or edited output files remain wherever you saved them.
• If Start with Windows is enabled, Spinrola writes a per-user Windows Run registry entry pointing to its executable.

Automatic update network requests

Automatic update checks run only in a build with an embedded update feed and trusted signing key, and only for a recognized installer-based installation. The source repository's default update policy is empty; release builds can embed a configured feed. For a configured installation, Spinrola checks after startup and approximately every six hours while running. A manual check can also be started from the app. It sends HTTPS GET requests to the configured update feed and, when a newer signed update is available, to the installer URL in that feed. HTTPS redirects may lead to other hosts. The release workflow's default feed host is GitHub, but the feed can be changed when a release is built.

These requests include a Spinrola-Updater/1.0 user-agent. Spinrola does not add cookies, account credentials, a unique user or device identifier, selected files, settings, or logs to these requests. As with ordinary HTTPS requests, the receiving host and its delivery providers can see request information such as your IP address, request time and requested URL, and apply their own privacy policies. If the build has no configured update policy, Spinrola makes no update request.

Sharing with others

Spinrola's application code does not sell information or send files or logs to its publisher or an analytics provider. Update hosts receive the update requests described above. Files leave Spinrola through its Share action only when you choose that action and a destination in Windows. Microsoft or other Windows components may process diagnostic or sharing information under their own terms and settings.

Your choices and deletion

You can change or reset Spinrola settings in the app. To remove the application, use Windows Settings > Apps > Installed apps > Spinrola > Uninstall. The installer uninstaller removes the app's local logs and Start with Windows entry. In an interactive uninstall, it asks whether to remove %APPDATA%\Spinrola settings; silent uninstall does not ask or remove those settings.

After Spinrola has exited, you can remove remaining app data by deleting %APPDATA%\Spinrola, %LOCALAPPDATA%\Spinrola (including updates), and %TEMP%\Spinrola if those folders exist. Remove any leftover .spinrola-work folders from output locations you used. Delete converted or edited output files from their saved locations if you no longer want them. Removing these local files does not recall files you deliberately shared through Windows or remove copies held by a cloud or network-folder provider.

Changes

We may update this policy when the application's behavior changes and will revise the date above.