What this site knows

Page views are counted by Vercel Web Analytics, which sets no cookie and stores nothing on your device. Visitors are told apart by a hash derived from the request itself, and it is discarded after twenty-four hours — it cannot be reversed, and it cannot be used to recognise you here tomorrow or anywhere else ever.

What a recorded view may contain: the time, the path, the referring page, filtered query parameters, an approximate location down to a city, your operating system and browser and their versions, and whether the device is a phone, a tablet or a desktop. There is nothing in that list that names anybody, and nothing is joined up across sites. Vercel describes it in full in their analytics privacy documentation.

The installers live in a private GitHub repository. This site holds a read-only token so it can ask GitHub what the current release is and where its files are; the token stays on the server, never reaches your browser, and can read that one repository and nothing else. It is used to look up a file, not to look at you.

The download itself is a redirect: the button hands you to GitHub and GitHub serves the bytes, so the request for the file is between you and them under their privacy statement. That is also how the download is counted — GitHub keeps a tally per file, which is the only download figure anybody here has.

The address of the thanks page carries an asset number. That identifies which file you asked for, and nothing about who asked.

The floating Buy Me a Coffee button is a script of theirs, and it sets a single first-party cookie named visited which records that it has been shown to you. It is the only cookie this site sets beyond what it technically needs, which is why it is the only thing you are asked about. Decline and the script is never requested at all — not loaded and hidden, not loaded.

The button on the thanks page is a different thing: a plain image served by Buy Me a Coffee, so loading that page fetches it from them. It sets nothing here, and following either of them takes you to their site, on their terms.

The paid-tier waitlist is a form hosted by Tally and linked to rather than built as a field of ours. An address you give it is held by them and reaches us through them; this site runs no database for it to sit in, which is the reason it was done that way.

The satisfaction survey is the same arrangement — the same host, nothing of it stored here. It asks for a name and an address at the end and neither is required: leave them blank and what you sent is anonymous, which is the point of saying so on the form itself.

Ripple Effect works on files on your own disk and needs no network to do it. Nothing you write is sent anywhere, and nothing counts what you do: there are no performance measurements and no record of which boards you open or how long you spend in them. From version 1.5 the app can send anonymous usage statistics, and they are opt-in — asked once, with the complete list of what would be sent in front of the question, neither answer preselected, and switchable off afterwards. No build before 1.5 collected any.

From version 1.5 the app asks you to accept the licence at first launch, and makes no network request of any kind until you have. Everything below happens after that, and only then.

A few requests then leave the machine without your having to ask for them. Once per launch it asks this site whether a newer version exists — a plain request for a release number, carrying nothing about you, your projects or what you were doing. From version 1.5 it also asks, once per launch and unless you switch it off in Settings, whether a fix exists for its engine — the part that plays and compiles campaigns — naming that engine's version and the platform; a fix is downloaded from GitHub and used from the next launch. And if you open the About box, it asks this site for the contributor list, which the site fetches from GitHub on its own behalf — versions before 1.5 asked api.github.com directly. Their pictures are the one exception: each contributor's avatar is loaded from avatars.githubusercontent.com by your machine rather than through this site, so opening the About box does make a request to GitHub for the images. From version 1.5.1 — once you have accepted version 2.0 of the licence, and unless you switch it off in Settings — it also asks this site once per launch for the news it shows on its home screen, and loads the pictures that go with it from this site and nowhere else; which items you have read stays on your machine. From version 1.6, dictation listens with a speech-recognition model that runs on your computer, and the app downloads it from Hugging Face only when you ask for it — one file at a time, carrying nothing about you. What you say is turned into text on your computer and sent nowhere, and the same goes for the location and the time a story may read if you allow it. The rest reach this site the way any other request does, so an address and a browser-style identifier appear in a server log; nothing distinguishes one installation from another, because nothing in the request is unique to one.

The one thing that can carry anything of yours is a crash report, and it is asked for one report at a time. After a crash, the next launch shows you what it saved — every file, its size, and what is in it — and sends nothing unless you answer yes to that report. There is no setting that answers in advance, in either direction. Your username, your home folder, the folders of your projects, e-mail and network addresses and anything shaped like a key are masked before you are even shown the question; a memory snapshot may still hold fragments of the text the app was working on, which is the one thing no masking can promise and the dialog says so.

The full notice — what is processed, on what basis, for how long, and who else touches it — is the Privacy Notice. It is the formal one, it covers the hosted service as well as the app, and it is the document to read if you want the complete answer rather than this page's summary of the part about the website.

The typefaces are built into the site at compile time and served from it, so reading a page here sends no request to Google Fonts. There are no advertising scripts, no tag manager, no session recorder, no heat map and no embedded video.

Withdrawing is meant to be exactly as easy as agreeing was, so the choice lives here as well as in the notice that asked for it.

Write to legal@ripplefx.app, which is also where a request to see, correct or delete your data goes. For help with the app rather than a question about data, support@ripplefx.app or a thread in Discussions will get there faster.

Last updated 30 September 2026.