CyrFlip in the Microsoft Store
The Store build is the same CyrFlip - the same features in the same release, the same privacy policy, the same one small program. Microsoft signs the package, so Windows does not show the unsigned-ZIP warning, and the Store keeps it updated. Four of its rules differ from the Portable ZIP and winget build, and this page states them once.
Windows owns its startup
The portable build turns autostart into a per-user Run entry. A Store app may not write
one, so the Store build declares a Windows startup task instead: turn it on or off in
Settings ▸ Apps ▸ Startup, next to every other Store app. The
Start CyrFlip with Windows checkbox on CyrFlip's General tab shows that state and
clicking it opens that Windows page - Windows owns the switch, CyrFlip only reads it.
Its files live in the package folder
A Store app keeps its data under the package folder, so the files the guide names sit in
%LOCALAPPDATA%\Packages\SZA.CyrFlip_fdk7e19xt9z9j\LocalCache\Local\CyrFlip\ - the layout
file the VS Code extension reads, the clipboard-history and quick-notes journals and the diagnostics.
They are the same files with the same Windows DPAPI encryption; only the folder differs. One honest
consequence: a change on the Windows languages tab writes Windows' own input settings,
and inside the package Windows may redirect those writes - the tab says so when it happens and links
to the Windows settings, and a sign out and back in settles them.
It never downloads or runs an installer
Store certification does not allow an app to download and run an installer, so the
Translation tab's "install Ollama" button opens ollama.com in the browser
instead. Ollama and the model remain your own one-time install, exactly as in the portable build -
CyrFlip bundles neither and has no key or account.
The Store handles updates
You do not re-download anything: the Store updates the app in the background. The
build version on the About tab carries the same YY.M.D.HHmm stamp as the
release ZIP and says it is a Store build, so a fix is recognisable in either channel.
Everything else is the same product: 13 interface languages, the theme, the marker at the caret - and the privacy policy is one page for every channel; the Store listing points at it in every language. Back to the install section of the guide.