On your device
Your patches, recordings, samples, settings and installed plugins stay on your device. Flyback does not upload them. Sound coming in from a microphone or a line input, MIDI from a keyboard or a controller and anything you play are processed on the device and go nowhere unless you record them to a file yourself.
The Android app
The Android app asks for two permissions. Internet access is used only to reach the preset site described below. The microphone is asked for the first time a patch with a Line In module plays, and only then; what it hears is played through the patch on the device and is never uploaded or saved unless you record it yourself. Refusing it leaves everything else working. The app does not ask for your location, your contacts or anything that identifies the device. It sends no usage counts, has no self-updater, holds no assistants and keeps what it saves in its own private folder. Android's backup of app data is switched off for it.
Presets, plugins and letters
The editor and the Android app read the shared presets and plugins from flybackmodular.app, as this website does. Browsing them sends nothing about you beyond the request itself, search words included, and the site keeps none of it. Some of what you can do there sends something of your choosing:
- Sharing a preset or a plugin publishes the file you send, with the name, author, description and tags it carries, for everyone to see and download.
- Writing to the author (the last glyph on the editor's status bar) sends your message, what it is about, the Flyback version, the operating system, and the names of the plugins and sound backend in use. A reply address is optional, and only the author reads it.
- Rating or reporting a preset or a plugin sends the rating or the reason. A rating is kept under a one-way hash of your network address, so one person counts once and the stored rating says nothing about who gave it.
To keep the site from being flooded, it counts requests per network address for one hour and then deletes the count. The site sets no cookies for visitors and runs no analytics.
Usage counts
The desktop editor can count how it is used, to show which features matter. It is off until you tick it under Settings → Privacy, and off again the moment you untick it. When on, it sends coarse bands, never exact figures: the version, the operating system, which of Flyback's own plugins loaded and which sound backend opened, roughly how many cores, how much memory and what screen size, how many of each kind of module a playing patch holds, whether an assistant was asked and which, and at the end of a run which kinds of module were picked, how long it lasted, which features it used and how fast the picture drew. A crash sends the kind of error and where in Flyback's code it happened, never its message.
No patch, nothing you type, no file name, no account or machine name and no identifier is sent. Each run gets a random id made at launch and never saved, so two runs cannot be told apart from one. The counts go to Aptabase, which keeps aggregate figures.
Updates
The desktop editor checks the project's GitHub releases once a launch and downloads a new release when there is one, installing it only if it is signed with Flyback's release key. The request carries the version and nothing else of yours. Turn it off under Settings → Privacy. Copies installed from an app store update through the store instead.
Assistants
The desktop editor can ask an AI assistant for help with a patch, but only one you set up yourself with your own account or key: OpenAI, Google Gemini, or a command line tool such as Codex or Claude Code installed on your machine. What you ask, and the patch it is about, then go to that provider under your agreement with them and their privacy policy. Flyback never sees the conversation, and your key is kept in your operating system's own secret store, sent only to the provider it belongs to.
Your choices
Everything that sends something optional can be left off: usage counts and updates under Settings → Privacy, and sharing, letters and ratings by not using them. Since nothing Flyback keeps identifies you, there is no profile to download or erase; to have a preset, a plugin or a letter you sent taken down, ask below and say which. Flyback is not directed at children and collects nothing about anyone's age.
Contact
Mail hello@flybackmodular.app, write to the author from inside Flyback, or open a discussion on GitHub. Changes to this policy are made on this page, with a new effective date at the top, and are visible in the repository's history.