Privacy Policy

Last updated: 30 July 2026

CyrFlip does not collect, store, log, or transmit any personal data. It runs entirely on your own device. It has no servers of its own, no telemetry, analytics, advertising, tracking, or user accounts. The developer receives no data about you or your use of the app.

There is exactly one feature that sends text anywhere, and it is off by default: the optional translator. When you switch it on and press a translation shortcut, the text you selected is sent to the Ollama server address configured in CyrFlip - by default http://localhost:11434, which is a program running on your own computer, so the text does not leave your device. If you change that address to another machine, the selected text is sent to that machine; CyrFlip says so next to the setting. See the translator section below.

What the app accesses, and why

• Keyboard. CyrFlip installs a global keyboard hook for two purposes only: to detect its activation hotkey (default Ctrl+Shift+F12) and to read the currently active keyboard layout code (any layout installed in Windows, including the 13 curated EN, ZH, HI, ES, FR, AR, BN, PT, RU, UR, DE, IT and UK ones) so it can show the on-screen indicator. Besides that hotkey it also watches the chords you assign to the case fix, the clipboard manager, each row of your layout-conversion table, each row of your translation table, and any quick-launch scenario you give a shortcut to. While a translation is being written it additionally watches for Esc, so that key can cancel it - the key is passed on to the app you are in either way. It does not record, log, store, or transmit your keystrokes. It is not a keylogger.
• Clipboard. When you press the hotkey to transliterate a selection, CyrFlip temporarily reads the selected text (via a synthesized copy), converts it between layouts, and pastes the result back, then restores your previous clipboard contents. This happens locally and only at the moment you trigger it. Nothing from the clipboard is sent or shared.
• Optional clipboard history. Clipboard history is off by default. If you explicitly enable it, CyrFlip stores captured Unicode text locally so you can reopen it later. The history is encrypted with Windows DPAPI for the current Windows user; it can be paused, cleared, or disabled at any time from CyrFlip. CyrFlip never sends this history anywhere.
• Active-window / layout info. The app reads which window is focused and its keyboard layout to position and update the indicator. This information is used in memory only and is never stored or transmitted. When you switch on yield hotkeys to the remote desktop, and only when one of CyrFlip's own chords is actually pressed, it also reads the executable name of the focused window to recognise a remote-desktop client.
• Windows input settings. The Windows languages tab edits Windows' own configuration on your behalf: the installed keyboard layouts (HKCU\Keyboard Layout\Preload and HKCU\Control Panel\International\User Profile), the language-cycle chord, and the per-language switch shortcuts (HKCU\Control Panel\Input Method\Hot Keys). These are system settings that stay on your device and keep working when CyrFlip is closed. Before its first change CyrFlip stores a one-time snapshot of the previous state in its own registry key, so you can restore it.
• Optional quick launch. The scenario launcher is off by default. When you enable it, CyrFlip starts the programs, scripts and yt-dlp downloads you defined, and only when you ask it to - from the tray, the settings table, a shortcut you assigned, or the taskbar Jump List. It requests administrator rights only for a scenario you marked "run as administrator", and the link you type for a yt-dlp download is handed to that tool for the single run and is not stored. Enabling the module also publishes your scenario names to the Windows taskbar Jump List, which Windows keeps in your own user profile.
• Optional translator. The translator is off by default; while it is off CyrFlip opens no network connection at all. When you enable it and press a translation shortcut, CyrFlip takes the selected text (the same synthesized copy as above) and sends it over HTTP to the Ollama address in its settings - http://localhost:11434 unless you change it, which means a program on your own computer. The tray entry Translate clipboard, which appears only while the translator is enabled, sends the text currently on your clipboard to that same address instead of a selection. Ollama is a separate, free product you install yourself; CyrFlip does not bundle it and has no account or key of its own. The translation is shown in a window and, only if you turn those options on, copied to the clipboard (where the optional history stores it like any other copy) or pasted over your selection. CyrFlip stores no translations, keeps no log of them, and sends nothing to the developer. In the portable version the Install Ollama button downloads the official installer from ollama.com; the Microsoft Store version only opens that website.

Local files CyrFlip writes

• Layout file. CyrFlip writes the current layout code - a two-letter value such as EN, ZH, RU, or AR - to a small local file (%LOCALAPPDATA%\CyrFlip\layout.txt, or %ProgramData%\CyrFlip\layout.txt in the Microsoft Store version) so the optional companion VS Code extension can display the marker at the editor caret. This file contains no personal data and never leaves your device.
• Configuration and history. Settings are stored in HKCU\Software\CyrFlip - including your layout-conversion table and the one-time backups of the Windows input settings described above. When enabled, clipboard history is stored locally in the CyrFlip application-data folder in DPAPI-protected form. A legacy config.json may be read once during migration. None of these data leave your device.
• Quick-launch scenarios. Each scenario you create is stored as its own XML file in %APPDATA%\CyrFlip\Scenarios, holding exactly what you entered: the name, the program or script path, its arguments and working folder. They stay on your device, are yours to edit or delete, and remain untouched if you switch the module off. The module also appends a short activity log (launcher.log, next to the layout file) recording that a scenario started and why one failed - it never records a yt-dlp link, clipboard contents, or keystrokes.
• Diagnostics report. Only when you run Diagnose caret position… yourself, CyrFlip writes caret-diagnostics.txt next to the layout file. It records what Windows and UI Automation report about the focused text field; it is never sent anywhere, and you can delete it.
• Log archive for the author. Only when you press Send logs to the author.. yourself, CyrFlip packs its own diagnostic logs and a configuration report into a ZIP in the reports folder next to the layout file, and opens a message to the developer with that file attached. Clipboard history is never part of that archive. The logs do contain file paths, and with them your Windows account name; the dialog says so plainly and lets you open the archive before any message exists. Nothing is sent until you press Send in your own mail program - CyrFlip has no sending channel of its own.

Data sharing

None. CyrFlip does not share any data with the developer or any third party. The one thing it ever sends is the text you selected, to the translator address you chose yourself - by default a program on your own computer - and only while that optional feature is switched on. The Send logs to the author button is no exception: it prepares a message in your own mail program, with an archive you can inspect first, and only you can send it.

Children's privacy

CyrFlip does not collect any data from anyone, including children.

Open source

CyrFlip is open source. You can review exactly what it does in the source code at github.com/SerZhyAle/CyrFlip.

Changes to this policy

If this policy changes, the updated version will be posted on this page with a new "Last updated" date.

Contact

Questions about this policy: sza@ukr.net.