Privacy Policy

Last updated: 16 October 2026

CyrFlip does not collect any personal data, and the developer receives none. It has no servers of its own, no telemetry, analytics, advertising, tracking, or user accounts, and it does not log your keystrokes. It runs on your own device; the only things that ever leave it are the two optional, off-by-default features described next, and only to a place you chose.

There are exactly two features that send anything anywhere, and both are off by default: the optional translator and the optional clipboard on the server.

When you switch the translator 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.

The clipboard on the server sends what is on your clipboard - a text, a picture or one file - to the exchange server you signed in to, and only when you press its button, chord or shortcut. It is encrypted on your computer first, for your own devices only. See the exchange-server section below.

What the app accesses, and why

• Keyboard. CyrFlip installs a global keyboard hook for one purpose only: to recognise its own shortcuts, such as the layout-conversion chord (default Ctrl+Shift+F12). The keyboard layout the indicator shows (any layout installed in Windows, including the 13 curated EN, ZH, HI, ES, FR, AR, BN, PT, RU, UR, DE, IT and UK ones) is not read through the hook - CyrFlip asks Windows for the layout of the focused window. Besides that chord 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.
• Mouse. Only while you have switched on CyrFlip's own context menu (it is off by default), CyrFlip installs a global mouse hook so it can recognise the one mouse chord that opens that menu (default Ctrl + right click). It passes every other click and movement on untouched and records, stores and sends nothing. With the context menu off, no mouse hook exists at all.
• Text cursor. The option that shows the layout on the mouse pointer (off by default) replaces the Windows text-selection cursor (the I-beam) for every program while CyrFlip runs. CyrFlip puts the standard cursor back when it exits, and also when it closes because of an error; only if the process is killed outright does the replacement stay until you sign out.
• Start with Windows. CyrFlip starts with Windows only if you tick that option. The portable version then writes one entry to HKCU\Software\Microsoft\Windows\CurrentVersion\Run in your own user profile, and unticking the option removes it; the Microsoft Store version uses a Windows startup task instead, which you can also switch in Settings > Apps > Startup.
• 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 by this; the only feature that ever sends the clipboard is the optional clipboard on the server below, and only when you press its button.
• 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. Each entry is encrypted whole - the copied text together with the name and window title of the app it came from and its date. Earlier versions kept the app name and window title readable; those entries go when the history is cleared. Deleting an entry with × erases it from the file.
• 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.
• Optional clipboard on the server. This feature is off by default; while it is off CyrFlip opens no network connection for it. It needs an account on an exchange server that you or someone you trust runs, and CyrFlip only signs in to it: you give it the server's connection string, your login and your password once. The password is used for that one sign-in and is never stored; the device token the server returns and a private key CyrFlip makes for this account are kept encrypted with Windows DPAPI for your Windows user. When you press Send clipboard to server (tray menu, shortcut or chord), CyrFlip sends exactly what is on the clipboard at that moment - a text, a picture or one file, a password you copied a minute ago included. There is no preview, no confirmation and no filter, so press it only when you mean it. The value is encrypted on your computer for the other devices of your account before it leaves, and the server keeps only the last value, in its memory. Get clipboard from server puts the server's newest value on your clipboard; a received file is saved in a folder you can see (Downloads\CyrFlip by default) and never overwrites another file. Nothing is sent by itself - there is no monitoring, no timer and no send at start. The exchange server connects your devices, so it knows the names of your account, devices, folders and broadcasts, sees which devices are online, and how much is sent and when. It cannot open what goes through it: folders and their files, broadcasts and the clipboard are encrypted on your device and opened only on your other devices or by the people you gave access to. To look inside, whoever runs the server would have to add a device of their own to your account, and it would appear in your list of devices. CyrFlip keeps a log of kinds, sizes and result codes only - never a clipboard value, a file name, a login or an address - and that log is the only trace it writes about this feature besides the account entry itself (the server's address, your login, a name, the pinned certificate and the public keys of your other devices), which you remove with Remove account.
• Screen capture. Only when you press the screen capture shortcut or pick Screen region capture in the tray menu does CyrFlip take one picture of your screens as they are, lets you select a rectangle, and puts only that rectangle on the clipboard as an image. By default nothing is written to disk and nothing is kept. Only if you also switch on saving is the selected rectangle written, unencrypted, as a PNG file into the folder shown in the settings (or, when that folder is unreachable, into Pictures\Screenshots or Downloads, and CyrFlip tells you where at that moment). CyrFlip never deletes, uploads or indexes those files, the clipboard history does not record the image, and the log archive for the author never contains it. CyrFlip's own layout marker and translation window are kept out of every screen capture.

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 in the Microsoft Store version layout.txt in the app's own folder in your profile, %LOCALAPPDATA%\Packages\SZA.CyrFlip_fdk7e19xt9z9j\LocalCache\Local\CyrFlip) so the optional companion VS Code extension can display the marker at the editor caret. Beside it, layout-klid.txt holds the identifier of that keyboard layout (eight hexadecimal digits, such as 00000409), so the extension can use the same colour. The extension, if you install it, writes editor-caret.txt into the same folder while it draws the marker; it holds only the layout code and a time. CyrFlip removes its two files when it exits. The Microsoft Store version also keeps a copy of its two files under %ProgramData%\CyrFlip for older versions of the extension; other accounts on the same PC can read that copy - it holds nothing but these values. Logs and quick notes that earlier Store versions kept there are moved into your own profile folder on the first start. None of these files contains personal data or ever 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. When enabled, quick notes are stored in the same folder in a DPAPI-protected file - the title as well as the body - and that file is never part of the log archive described below.
• 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; the usual ones no longer carry your Windows account name, but one in an unusual shape still can. 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.

If Windows or your antivirus warned you about CyrFlip when you downloaded or first started it, see Why Windows or an antivirus may warn about CyrFlip - its list of what CyrFlip never does says the same as this page.

Data sharing

None. CyrFlip does not share any data with the developer or any third party. What it can send is only what you tell it to, to the place you name, and only while the optional feature is switched on: the text you selected, to the translator address you chose yourself (by default a program on your own computer); and what is on your clipboard, to the exchange server you signed in to, encrypted for your own devices. 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.

This website

This section is about the pages you are reading, not about the app. The app does not contact this website, and the website receives nothing from the app.

The site is static and is served by GitHub Pages, which, like any web host, sees each visitor's address in its own logs. It has no analytics, no advertising, no forms and no accounts, and its pages set no cookies. The typefaces come from the site itself, so no font provider sees your visit. Your browser keeps two preferences on your own device - the theme and the language (under the keys sza-theme and sza-lang) - and they are never sent anywhere.

Exactly one request goes to a third party, and only from the home page: it asks api.github.com (GitHub's public API, the address /repos/SerZhyAle/CyrFlip/releases/latest) which release is the newest, so that the download button can point to it. Like any web request, it carries your IP address and the usual browser details, such as the user agent; nothing else is sent, and CyrFlip stores nothing. If the request fails or is blocked, the button keeps its fallback link to the latest-release page and nothing else changes. What GitHub does with such a request is described in GitHub's own privacy statement. Links to other sites (Microsoft Store, GitHub) load nothing until you follow them.

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.