Version 11.0 · 19 October 2026 · English is the binding version · replaces version 10.0 of 18 October 2026
This policy describes RiD Flow for Windows as the application stood on 18 October 2026. Where the application changed at a particular version, the text says so at the point where it matters. Section 10 says what we do when a newer version changes what is recorded.
RiD Flow records what you work on, and it records it on your computer. We do not receive your activity data, we cannot read it, and we could not hand it over if we were asked to.
RiD · Ĺubomír Roth · Emanuel Veit-Gasse 20, 7423 Pinkafeld, Austria
Contact: hello@madebyrid.com
We have not appointed a Data Protection Officer. We are not required to, and appointing one voluntarily would bring duties that do not fit a business of this size.
Everything the application records stays on your computer.
What is recorded
example.com, never the full address). This is off unless you switch it on.We say this plainly because it is the most intrusive thing the application does: a window title can contain a document name, a customer name, a subject line. It never leaves your computer by itself — but it is recorded, it is readable, and you cannot switch it off.
Audit notes
An audit asks you about a block of time — "14:05–14:30 — how was it?" — and keeps your answer. Each note holds its start and end, the name you give it, and three things you say about yourself: whether it was planned or came up, how much it cost you, and whether it moved you forward. The application also keeps, for this computer, how long a block is, how far it has already asked, and the block it is asking about right now.
Since version 0.126.0 the application also asks after a break. If you come back to this computer after a gap of at least the length you set — ten minutes by default — in which no device of yours recorded anything, the small window opens once and asks what that time was. If the break ends on your phone, the phone asks and this computer does not.
An audit note records how something felt at the time you answered. It cannot be edited or deleted on its own, and that is deliberate: a note you change a day later is a memory, not a measurement. The audit puts its result in front of you; what you make of it is yours. Removing all of this computer's data removes the notes with everything else.
Where it is kept
| What | Where |
|---|---|
| The database, with everything above | %APPDATA%\com.ridflow.desktop\rid-flow.db (plus -wal and -shm working files) |
| Device identifier and folder settings | separate small files in the same folder. How often it syncs is not one of them — that is kept with your other settings, in the database above |
| The sync code, if you set up sync | a small file in the same folder. It is stored in readable form — see section 3.2 |
| A diagnostic log | rid-flow.log and one rotated copy, in the same folder, each at most 256 KB. It contains full local paths — and therefore your Windows user name — and the device identifier. Since version 0.124.1 it also records that an audit is running, in which mode, the clock time and length of each block it asked about, whether the question window opened, and whether you answered. It never contains window titles, application, group or project names, your ratings or the text of a note, and it never contains the sync code. |
| A readable copy, once you ask for one | rid-flow-export.db, next to the database |
| The browser engine's own data | %LOCALAPPDATA%\com.ridflow.desktop\EBWebView, written by Microsoft's WebView2 runtime, not by us |
| If you enabled autostart | a shortcut in your user's Startup folder |
The portable edition keeps its database in the same place as the installed one — in your Windows profile, not next to the program file. If you start it on a computer that has never run RiD Flow, it asks first, in a Windows dialog, whether to keep this computer's copy, remove it again when you close Flow, or stop. If you choose to stop, Flow closes without having written anything. Installed editions never ask, because the computer they run on is yours.
One honest point about "remove it when you close Flow": that cleanup runs when Flow closes normally. If the machine is switched off under it or the program is killed, it may not run. Remove this computer's data below shows you what is there and removes it.
The device identifier is a random value generated when the application first runs. It is not derived from your hardware, and it does not identify you to us — we never receive it.
The device name is shown in the version line and travels inside every export file — encrypted in the files Flow writes outside your device, readable in the copy you export for yourself.
Deleting it. The application has a function called "Remove this computer's data". It deletes %APPDATA%\com.ridflow.desktop\, %LOCALAPPDATA%\com.ridflow.desktop\ including the browser engine's data, and the autostart shortcut. It tells you what it removed and what it could not remove, and it tells you what it cannot reach at all:
Both earlier versions of this policy were wrong here, in opposite directions, and both corrections stay on the record rather than being quietly dropped. Version 1.0 said that deleting the data folder removes everything — it did not. Version 2.0 said there is no function that removes everything — on 7 October that was correct; since 8 October there is one.
If your computer is shared or unencrypted, anyone with access to your user profile can read these files — the database, and the sync code with it. We recommend full-disk encryption; your operating system includes it.
Nothing, by itself.
As this version is built, the application makes no outgoing network connections at all — not to us, not to anyone. There is no account, no server of ours, no licence check, no update check, no analytics, no error reporting to third parties. This was verified in the source code, not assumed: the application code calls no HTTP client, and the dependency list contains no TLS library at all.
One honest consequence of that, so you are not surprised by it. Because the application cannot fetch anything itself, the links in it — to this policy and to our imprint — open your own browser. From that moment your browser is talking to our website, as it would with any link you click, and our website's privacy policy covers what happens then. The contact addresses open your mail program, and Third-party licences opens a file that is already on your computer, in whatever program you use for text — nothing is fetched for it. The application itself still connects to nothing.
Two honest limits to that sentence, because they are outside our code:
| You do this | What goes where | Encrypted? |
|---|---|---|
| Export a readable copy | A complete, readable copy of the database — including window titles — is written as rid-flow-export.db next to the database, on your own computer. Anyone who opens that file reads everything. The application says so above the button, every time |
No, deliberately. It exists so that you can read your own data |
| Export for another device | The same contents, sealed, as a file you can carry | Yes |
| Set up a sync folder | Each sync round writes a sealed copy into the folder you chose. How often that happens, you set yourself — Sync every … minutes, and separately during an audit every … minutes, anything from 5 minutes to 6 hours, on each computer. If you change nothing it is every hour, every 15 minutes while an audit is running, and every 3 hours for a portable copy. If that folder is in cloud storage, the file goes to that provider — your provider, under your contract with them, not ours. It is unreadable to them without your code | Yes |
| Set up a sync folder and write audit notes | In addition to the copy above, a second sealed file carries the audit notes of the last 14 days to your phone. Since version 0.127.0 it is written immediately after you answer, not at the next sync round. Once there are no notes left from the last 14 days, the application stops writing it — and from version 0.129.0 it also removes its own file from every sync folder, at the next sync round. Files that your other devices wrote are left alone. Up to version 0.128.0 the file stayed where it was, sealed, with whatever it last held, until you deleted it yourself | Yes |
| Set up a USB stick | A sealed copy is written to the stick. A stick you have not set up is not touched, whatever is already on it | Yes |
| Use the Bluetooth option | The sealed file is handed to the Windows Bluetooth transfer assistant and sent to the device you pick | Yes |
| Use the companion app's share menu | The phone hands the sealed file to whatever app you choose. Whoever receives it cannot open it without your code, so in practice this is a way to move the file to another device of your own — not a way to share your log with someone | Yes |
Without a sync code, nothing is written outside the device at all, and the application says why rather than failing silently.
When you set up sync, the application generates a code: a random value produced by your operating system, shown to you as a short code to write down or print. You do not choose it, and you do not invent a password. You type it once on each further device. After that it stays in each device's own profile and never travels with the files again.
What this protection does not cover. We list this because a protection described without its edges is worth less than none:
| Not covered | Why it is here |
|---|---|
| Whoever sits at your unlocked computer | They can read the database directly, and the sync code with it. This is what your operating system's disk encryption and your screen lock are for |
| The sync folder itself, without opening a single file | The file names are readable, and so are file sizes and modification times. They show that RiD Flow is in use and from how many devices; they show when each device last wrote — as often as the interval you set, and once more each time you answer an audit question; and because each kind of data has its own file, the presence of one file shows that audit notes were written on that computer. The device identifier in each name also carries the moment it was created, so a name shows when RiD Flow first ran on that device. None of this lets anyone read what is inside. If that matters to you, choose a folder nobody else can see |
| The readable copy you export yourself | See the table above. It is readable on purpose, and it stays readable wherever you put it |
| Files written before this version | Earlier versions wrote readable files. The application lists the ones it finds and removes them when you say so. For a transitional period it still reads readable files written by your other devices, and it names the date on which it stops; after that it ignores them and keeps naming them. Old versions and recycle-bin copies held by a cloud provider are outside its reach and yours — if that matters to you, clear them with your provider |
| The database on your own computer | It is not encrypted, deliberately. Encrypting it would break the promise that you can open, copy and read your own data with ordinary tools. Your operating system's full-disk encryption is the right measure there, and we recommend it |
It reads Android's own usage statistics into a database on the phone, and — only if you switch that on — records when the phone was connected to a car, using the Bluetooth connection and no location data at all. It has no internet permission whatsoever, so it cannot send anything anywhere. It passes data to the desktop application only through a file you place where you choose, and that file is sealed with the same code.
It can also run audits of its own and ask you about a block of time on the phone. While an audit that asks is running, it checks every fifteen minutes whether it should ask you — and it does the same outside an audit if you switch on the soft setting described in its own policy, which is off until you do. That policy, not this one, describes what the phone reads and keeps. Since this version it can also show you the audit notes you wrote on the computer, read from the sealed file described above.
The companion application has its own privacy policy, published with it in the store listing. It describes what the phone keeps and for how long, which is not the same as on the desktop.
The purchase is not handled by us. Our authorised reseller sells in its own name, takes the payment, issues the invoice and is the controller for the payment data. Its own privacy policy applies to that part, and we never see your payment details.
What reaches us from a purchase is your email address and the licence key, so that we can issue the licence and answer you if you write.
If you email hello@madebyrid.com, we process what you write, your email address and anything you attach, in order to answer you — Article 6(1)(b) or (f) GDPR. The mail is hosted with our provider in France. Support correspondence is kept for as long as the matter may still need it, and in any case deleted after three years, unless it is part of a transaction we have to keep under tax law.
You can ask us for access to your data (Article 15), correction (16), erasure (17), restriction (18), portability (20) and you can object to processing based on legitimate interest (21). Where you gave consent, you can withdraw it at any time, with effect for the future.
One honest limitation. Almost nothing the application holds is held by us. For your activity data there is nothing for us to give you, correct or delete, because we never had it — the files are on your computer and in your hands. "Export a readable copy" is the practical form of your right of access here, and it needs nothing from us. What we do hold is your licence record and any correspondence, and those rights apply in full there.
Write to hello@madebyrid.com. We answer within one month.
If you think we are handling your data unlawfully, you may complain to the Austrian Data Protection Authority (Datenschutzbehörde, Barichgasse 40–42, 1030 Vienna, dsb@dsb.gv.at), or to the authority where you live.
The application transfers nothing anywhere. The only processing on our side is your correspondence, and our mail provider runs its servers in France.
Where a service we use processes data outside the European Economic Area, it does so under the Standard Contractual Clauses adopted by Implementing Decision (EU) 2021/914, and, where applicable, under the EU-US Data Privacy Framework.
RiD Flow is not aimed at children. We do not knowingly process data of persons under 14 years of age, the age limit that applies in Austria.
We will publish a new version of this policy at madebyrid.com/privacy-app before the application changes what it records or sends — not afterwards. The version and date at the top tell you which one you are reading. Where a change requires your consent, we will ask for it rather than assume it.
RiD Flow Privacy Policy, Version 11.0, 19 October 2026.