Privacy

An account is an email address, a password and, if you give one, a name, and you need to be at least 18 to create one. The password travels encrypted to the sign-in service and is stored there only as a one-way hash, which nobody can read back, the maker included.

Your email receives the codes that confirm your address and reset your password. It is never shown to other members: on the leaderboard and in Visualizers you appear by the handle and display name you choose.

On your computer, the app keeps your session encrypted by the operating system. Accounts are personal, so keep your password to yourself.

An account stays signed in on up to 5 computers at a time — at home and at work, or the computers Share Audio plays between. Signing in on one more signs out the computer used least recently, within the hour.

Everything the app sends to FluidEQ’s service, always over an encrypted connection. The other places FluidEQ connects to are listed further down.

• Your email and password, and the name you give when you sign up

  When

  When you create an account, sign in, confirm your address or reset your password

  Who can see it

  The sign-in service keeps your email and name, and the password only as a hash nobody can read.

• Your sign-in token and account id

  When

  When the app starts, when you sign in, when you come back to the computer (at most every few hours), and when you press Check again

  Who can see it

  Only you and the maker. The service confirms a membership you already have, looks for a Buy Me a Coffee payment made with your confirmed email, and reads which version of these terms you agreed to, so the app can tell you when they change. The same token asks how a free trial or an earned month on this account stands.

• The email you pay with, your membership status and period, and Buy Me a Coffee’s ids for your membership, sent by Buy Me a Coffee

  When

  When you pay, renew or cancel

  Who can see it

  The maker, to match the payment to your account. It is matched only to a confirmed email address, so pay with the email you sign in with.

• Your sign-in token, to read your credits, the scenes you own, which of your own scenes are published and which of FluidEQ’s scenes are free

  When

  When the app starts, when you sign in, when you come back to the computer (at most every few hours, and every time while a payment you started is not in yet), and when you open your credits or get a scene

  Who can see it

  Only you and the maker. Your computer keeps the answer encrypted, so the scenes you own play without a connection.

• The pack you choose and the terms version you agreed to, and then, from Stripe: the email you pay with, the amount, the pack, and Stripe’s ids for the payment

  When

  When you choose a pack and continue to payment, and when Stripe confirms, refunds or disputes that payment

  Who can see it

  The maker, to give the pack’s credits to your account, and to take them back if the payment is refunded or disputed. Your card goes only to Stripe.

• Your sign-in token, to read where your payouts stand; if you set up payouts, the country you live in and which version of the creator terms you accepted; and then, from Stripe, your Stripe account’s id and whether Stripe can pay you

  When

  When you open the Account panel, when you press Set up payouts, Finish setting up or Check again, and when you come back from Stripe’s page; Stripe tells FluidEQ’s service when your account there changes

  Who can see it

  Only you and the maker. You see what is held, ready to pay and paid, never who bought; the maker sees what each creator is owed, to pay it. Your identity, bank and tax details go only to Stripe.

• Which scene you get with a credit, and the starter credits when you take them

  When

  When you confirm getting a scene, and when you take the starter credits

  Who can see it

  Kept with your account, so the scene stays yours. When it was got with a paid credit, the maker of a member’s scene earns from it — money once Stripe can pay them, a credit until then — and never learns who got it.

• Which version of these terms you agreed to, and when

  When

  When you continue to payment for credits, export a scene or publish one

  Who can see it

  The maker. It is kept with your account, even if you do not go on to pay.

• Your sign-in token, and the ids of the FluidEQ scenes you have installed that have a new version, to download them

  When

  When the app starts, when you come back to the computer and when you open the list of looks, to fetch new versions and to learn which shared scenes were taken down

  Who can see it

  Nothing is kept. Every look is signed, and your computer checks the signature before playing it.

• Nothing about you

  When

  When FluidEQ starts, at most every few hours, to show which Plus looks exist, with or without an account

  Who can see it

  Nothing is kept. The request only fetches the public list of looks.

• The handle and display name you choose

  When

  When you choose them on the leaderboard

  Who can see it

  Every signed-in account: on the leaderboard, on the scenes you publish and on your maker page in Visualizers, where they can be searched. Names that pose as FluidEQ or its staff are refused.

• One number per day from each of your computers: the whole minutes of music that played, up to 16 hours, with its date and a random number that tells your computers apart

  When

  Only if you join the leaderboard: when you join, when you come back to the computer at most every 4 hours, and when you open the board or a maker’s page in Visualizers

  Who can see it

  Your handle, display name, rank, points and what they are made of: every signed-in account, on the board and on your maker page.

• A scene you export: its code, settings, pictures, 3D models and ambient elements

  When

  When you press Export in the Studio

  Who can see it

  The service checks the scene, removes the comments from its code and signs it, adding your display name and account id to the file. It keeps a record of which scene and version you exported, when, and a fingerprint of the file. Whoever you send the file to sees your display name and account id; the scene plays for them once they own it.

• Which member’s scene is on screen, and your like on it

  When

  When a member’s scene plays, to show its likes, and when you press the heart or take a like back

  Who can see it

  Your like is kept with your account. Members see how many likes a scene has, never who gave them. How long each scene is on screen is the next line.

• How long each Plus scene was on your screen: one number of seconds per scene per day, with the scene and the date

  When

  While you have Plus, once you have been shown this version of these terms: when FluidEQ starts, when you come back to the computer, and at most once an hour while a scene plays

  Who can see it

  Only FluidEQ’s maker, with your account, to learn which scenes members enjoy and make more like them. Members never see it. Your computer keeps the last 14 days.

• Which audio engine you chose: the FluidEQ Engine or Equalizer APO

  When

  While you have Plus, once you have been shown this version of these terms: when FluidEQ starts, when you come back to the computer and when you switch engines

  Who can see it

  Only FluidEQ’s maker, with your account, to know which engine to work on. Only the last one is kept.

• Your sign-in token, to ask whether FluidEQ has announced new scenes

  When

  When FluidEQ starts, when you sign in and when you come back to the computer

  Who can see it

  Nothing is kept. Which announcements you have already seen stays on your computer.

• A scene you publish, as for an export, with one cover picture, up to two categories and a note about what is new, if you write one

  When

  When you press Publish in the Studio

  Who can see it

  Once FluidEQ’s maker approves it, in Visualizers, until you unpublish it, anyone signed in to FluidEQ sees its picture, name, categories, version notes, likes and adds, with your display name, handle and maker page, and can watch it for 10 seconds. Members who own it — got with a credit, or with Plus — play it and add it. FluidEQ’s maker keeps the scene and the record that you published it, as for an export.

• In Visualizers: what you search for, the scenes and makers you open, the scenes you add, and any scene you report with its reason

  When

  When you browse Visualizers or press Add or Report, and when the app looks for new versions of the scenes you added by asking for their makers’ scenes

  Who can see it

  Searches and what you open are not kept. An add is kept with your account; members see how many added a scene, never who. A report is kept with your account and a fingerprint of the scene as it was; FluidEQ’s maker sees how many reports a scene has and why, never who sent them.

• In the Forum: your GitHub sign-in, and then what you read, search, preview, post, edit or react to

  When

  Opening the Forum downloads its public topics from GitHub, which carries nothing about you; the rest only after you sign in with GitHub

  Who can see it

  GitHub, under its own terms; posts are public in the project’s GitHub Discussions. Signing in, staying signed in and signing out pass your GitHub sign-in through FluidEQ’s service, which adds FluidEQ’s key and keeps nothing.

• Your audio, and anything about what you play: track names, artists, files, folders and playlists.
• Your EQ settings, presets and profiles.
• Your audio devices, monitors and RGB lights, their names, and the other apps on your computer.
• Your Studio projects, their photos, their 3D models and your notes, unless you export or publish a scene. The prompt you copy for your AI assistant goes only where you paste it.
• What FluidEQ remembers on your computer to work: your desktop backgrounds and lighting, your Library — the folders you added, what it read from the files in them, and their cover pictures — the scene versions you have seen, and any scene that made your graphics driver reset.

• Every request is encrypted on its way.
• The rules live on the server, not in the app: each account can change only its own data, and a modified copy of FluidEQ gets exactly the same answers.
• The board and Visualizers show handles and display names, never email addresses. Account ids are never shown, but they are inside scene files and in what Visualizers sends to the app.
• The maker runs the service and can see what it stores, to keep it working, to match payments and to moderate what members publish. Nothing is sold or used for advertising, and there is no tracking or analytics.
• The service runs on Supabase (sign-in, database and files) and sends email through Resend; credits are paid through Stripe, which also pays creators, Plus through Buy Me a Coffee, and the Forum goes through GitHub. Each receives only what its part needs.
• FluidEQ keeps no IP addresses. Supabase records the address of each request in short-lived logs, and keeps the address and app details of each signed-in computer with that computer’s session and in Supabase’s own sign-in security log, to keep sign-in working and safe.
• Scenes are signed, and your computer checks the signature before playing one. An app update installs only after FluidEQ’s own signature on it has been checked.

• Leaderboard: the days you send stay on the board until you remove them. “Remove all my data” in the Account panel deletes every day you ever sent, at once; leaving the board only stops sending. Your computer keeps only the last 14 days of totals.
• Your handle and display name: kept while you have an account, and deleted with it.
• Membership: your payment email, status and Buy Me a Coffee’s ids for your membership are kept to match payments to your account, and are deleted with it. The record of each payment event keeps only Buy Me a Coffee’s ids and the time.
• Your account: ask for it to be deleted and it is gone within 30 days, together with your profile, leaderboard days, credits, the scenes you own, membership, free trials and earned months, agreements, likes, adds, reports, and the scenes you published with their files. Credits left on an account that is deleted are gone with it. A gift of Plus to your email stays until the maker removes it.
• Scenes: unpublishing removes a scene from Visualizers with its picture, file and version history. Likes, adds and reports on it stay until those accounts are deleted, and count again if you publish it once more. A scene blocked for breaking these terms keeps a fingerprint made from your account id and the scene’s id, with the reason and the date, so it stays blocked.
• Credits: each pack you paid for, each credit you spent and each scene you own are kept with your account, so your scenes stay yours on every computer; Stripe’s ids for each payment are kept to give its credits and to take them back after a refund. All of it is deleted with your account.
• Payouts: your Stripe account’s id, your country, the version of the creator terms you accepted, each sale your scenes earned and each payout are kept to pay you and to account for the payments, and are deleted with your account. When a buyer’s account is deleted, the sales it made stay in the creator’s earnings, without the buyer. What Stripe keeps is under its own terms.
• On your computer: the Plus looks and the scenes you added, encrypted; your credits and the scenes you own, encrypted; gallery pictures, up to 128 MB; and the list of blocked scenes. They stay until you remove them or uninstall FluidEQ.

• Updates: when it starts and when you come back to the computer, FluidEQ checks its release feed for a new version, and installs one only after checking its signature. The request carries a random number the updater keeps on this computer, and nothing about you.
• Headphone presets: when FluidEQ opens, it checks GitHub for new headphone presets, and the Convolution tab downloads AutoEq files from GitHub when you open it or choose a headphone.
• The “First steps with FluidEQ” video in the User guide: nothing is fetched until you press play; then the video and its English captions stream from fluideq.com, FluidEQ’s own site. The request carries no cookie and nothing about you or your account, and the site keeps no record of it. If it cannot play, “Open on fluideq.com” shows it in your browser instead. The short films on What’s new slides come from fluideq.com in the same way, starting by themselves when a slide opens: no cookie, nothing about you or your account, and no record kept. Without a connection, a slide shows its drawing instead.
• Models you use: the Karaoke Maker downloads its speech, vocal and melody models from Hugging Face, and the voice denoiser its model from GitHub. Your audio is processed on your computer.
• Your AI assistant: only while “Let your AI see the stage” is on in the Studio (copying the prompt for your AI turns it on, unless you turned it off yourself), an AI tool on this computer that has your key can ask FluidEQ for pictures of your Studio scenes, with FluidEQ’s reasons when one cannot play, and for numbers describing how the music you play moves — never the sound itself, and never which song it is. What that tool does with them is under its own terms.
• Share Audio: the audio, what is playing and this computer’s name go only to the computer you pair with on your local network, encrypted. This computer’s name is also announced on that network, so the other computer can find it.
• Online Media: YouTube, Bandcamp, Twitch and the other sites you open inside FluidEQ receive what you do there, under their own terms.
• Report a problem: opens a public GitHub issue in your browser or a private email to FluidEQ’s maker in your mail app, or copies the report for you, with recent log lines you can read before you send it. FluidEQ sends nothing itself.
• Lighting and desktop backgrounds: lighting talks only to Razer Chroma and Windows on this computer, and desktop backgrounds never go online.
• Your browser: payment for credits on Stripe and for Plus on Buy Me a Coffee, Stripe’s sign-up and dashboard for creator payouts, your membership page, the support links and the Forum’s GitHub sign-in open there, under those sites’ own terms.

Questions, deleting your account, or reporting a scene that uses your work: support@fluideq.com.