Support

Get started

Mivia Sign embeds an inaudible signature in your audio so its provenance travels with the file. You can sign tracks from the web at /sign or, on Pro, automatically from inside your DAW. Anyone can verify a signed file at /scan without an account.

Sign up to start. The free tier covers five lifetime signs and unlimited scanning; Pro unlocks unlimited signing, the plugin, leak tracking, and the activity feed.

Sign your first track

1. Open /sign.
2. Drop a WAV, FLAC, AIFF or MP3 file. Stems and full mixes both work.
3. When the signed file streams back, save it. The signature is embedded below the noise floor and isn't audible.

Your file is never kept on our side after signing. See Privacy for details.

Sign in

Sign in with your email and password, or with a passkey if your device has one available. There's no third-party login on Mivia Sign. Sessions last thirty days, so you won't be asked to sign in every visit.

Forgot your password

On /login, click the "Forgot password" link, enter your email, and we'll send you a reset link. The link expires in one hour. If the email doesn't arrive within a few minutes, check spam first, then mail [email protected].

Lost access to your authenticator

If you have two-factor authentication on and can't get the six-digit code from your authenticator app, click "Use a backup code" on the sign-in code prompt and enter one of your backup codes. Each works once. If you've used them all, or didn't save them, email [email protected] from the address on the account and we'll verify you and turn 2FA off manually.

Locked out

If you've tried to reset and still can't sign in, email [email protected] from the address on the account. We'll verify it and reset things manually.

Account security

Add a passkey, turn on two-factor authentication, or both. Both options live in /settings.

Passkeys

A passkey is a sign-in credential held by your device or its keychain. The private half lives there; we only see the public half. They are phishing-resistant: a fake site can't trick your device into using a passkey registered for Mivia.

Add a passkey

In /settings, click Add on the passkey row. Your device will prompt you for Face ID, Touch ID, Windows Hello, or whichever method it uses. If your device syncs passkeys (iCloud Keychain or similar), that one key works on every device it syncs to. Otherwise, add a passkey from each device you sign in from. We label each entry with the device and browser you used to register it (for example Mac · Safari) so you can tell them apart later.

Remove a passkey

In /settings, click the passkey row to open it, then click Manage. You'll see every key registered on your account, each labelled by device. Click Remove next to the one you don't want. Removal is immediate. Do this if you sell or lose the device a passkey lived on.

My browser doesn't support passkeys

On browsers without passkey support, the passkey row in /settings doesn't appear at all. You can still sign in with your password (and your authenticator code, if you have 2FA on). Passkeys you registered on other devices still work on those devices. If you have keys already and you visit /settings from a device that can't add new ones, the row stays visible so you can still remove existing keys, but the option to add new ones is locked.

Two-factor authentication

2FA pairs your account with an authenticator app (Google Authenticator, Authy, 1Password, etc.). On every sign-in, after your password, we ask for a six-digit code the app generates. You can have both 2FA and a passkey enabled. When you sign in with the passkey, we don't ask for a code, since the passkey itself already counts as two factors (your device, plus the biometric or PIN that unlocked it).

Turn it on

In /settings, click Set up on the 2FA row. You'll be asked for your password, then we show a QR code and the secret as text. Either scan the QR with your authenticator app or copy the secret in manually. Enter the six-digit code your app shows to finish enrolment. We then give you nine single-use backup codes for emergencies. Save them somewhere safe straight away. The Download button gives you a text file you can stash. They are shown only once.

Reset your backup codes

In /settings, click the 2FA row to open it, then click Reset backup codes. Confirm your password and we'll generate a fresh set of nine. Every previously-issued code stops working the moment you reset.

Turn it off

In /settings, click the 2FA row to open it, then click Disable. Confirm your password. We delete the shared secret and the backup codes. The next sign-in will not ask for a code.

Sign tracks

Two paths: drop files at /sign, or auto-sign every bounce from your DAW with the plugin (Pro). The web path embeds a watermark in the waveform; the plugin path stores a fingerprint of your bounce against your account. Either is scannable later.

Supported formats

WAV, FLAC, AIFF and MP3. We re-encode losslessly where possible. The signature survives the modifications a track normally picks up in distribution: lossy compression, format conversion, reasonable EQ and dynamics work, even a screen capture of someone playing it back. Heavy time-stretching, large pitch shifts, and re-recording through a microphone in a noisy room are the cases where it can fail.

Per-recipient variants

On Pro you can sign up to ten unique variants of the same track. Send variant 1 to the A&R, variant 2 to the manager, variant 3 to the mix engineer. If a copy leaks, scanning it will tell you which variant it was. See Leak tracking.

Plugin

The Mivia Sign plugin signs every bounce from your DAW automatically. It's included with Mivia Pro and ships as AU, VST3 and CLAP. Download and first-time setup live on the plugin page; this section covers how it works day to day, screen by screen, and the questions that come up once it's installed.

Installing

Mivia Sign runs on macOS 11 and later and Windows 10 and later. On macOS the installer drops the AU, VST3 and CLAP formats into the system plug-in folders (~/Library/Audio/Plug-Ins). Restart your DAW after install so it rescans. On Windows the VST3 and CLAP land in C:\Program Files\Common Files\VST3 and the equivalent CLAP folder; restart your DAW the same way.

First-time authentication

On first load the plugin opens a browser tab at /plugin-auth to pair the install with your account. The pairing happens once per install. You can run the plugin on multiple machines; each install gets its own token tied to a device name you pick.

Mivia Pro and signing

Signing needs an active Mivia Pro plan. On the free tier, or if your Pro plan lapses, the plugin shows an upgrade prompt in place of the signing screen and your bounces pass through unsigned, with nothing about your audio changed. Signing picks back up on its own once Pro is active again. Joining a session to be credited is free; only the person signing the bounce needs Pro.

How signing works

Add Mivia Sign to your master bus, or to any channel you want signed. It passes your audio through untouched and stays out of the way while you work. The moment you bounce or export, the plugin signs that render: it sends the audio to Mivia over a secure connection, files it in your library as proof of where and when it came from, then deletes the audio from our servers once that's done. Your exported file on disk is never modified or re-encoded, and the plugin only acts when you bounce. It doesn't monitor or stream your audio at any other time.

It runs as a zero-latency passthrough and does the signing on a background thread after the bounce, so it never adds latency or changes how your mix sounds. Each bounce can be mono or stereo and up to twenty minutes long; longer or surround exports aren't signed. For exactly what's stored alongside a signed bounce, see our privacy policy.

The Credits screen

Credits is the plugin's main screen, and it shows everyone who worked on the track: you at the top as the owner, and any collaborators below. Everyone listed here is credited automatically on your next bounce, in their own Mivia library as well as yours.

To add someone, have them scan the QR code with their phone. It takes them to Mivia, they sign in or create a free account, and they join the session. They show up in the list within a few seconds and stay credited from your next bounce onward, so there's no typing names or emails. To remove someone, hover their row and click Remove; they can scan again to rejoin. A session holds up to ten collaborators.

The Bounces screen

Bounces is a running list of the signed exports from the project you're working in, newest first. Each row shows how long ago it was signed, the export's filename, and a View in library link that opens that bounce's page on the web. The count at the top tells you how many the project has, and Open library takes you to your full library in the browser.

The filename is the real name you gave the export, read by the Mivia Helper described below. If the helper can't read it, the bounce is still signed and listed, just labelled Untitled bounce. The list here is a quick view of the current project; your complete history across every project lives in your library.

The Settings screen

The Settings tab is where you manage the install:

• Plugin size. Default, M, L and XL resize the plugin window to suit your screen. It's a display preference only and changes nothing about signing.
• Sign method. Fingerprint is the method in use today. Watermark is marked Coming soon and can't be selected yet.
• Account settings. Opens your account on the web, where you manage your profile and subscription.
• Check for updates. Checks whether a newer build is available. If there is one, the button changes to offer the update and links straight to the download.
• Log out. Signs this install out and returns the plugin to the login screen.

The line along the bottom shows the plugin version, the helper version, and whether the helper is currently connected.

The Mivia Helper

The plugin installs a small companion called the Mivia Helper. It runs quietly in the background, starts when you log in, and has one job: to read the filename of your export so each signed bounce is named correctly in your library. Plug-in formats can't see that filename on their own, so the helper handles it. It installs and updates alongside the plugin, so there's nothing separate to manage.

On macOS, reading the export dialog in Logic, Ableton, Cubase and Pro Tools needs Accessibility permission. The first time you bounce you may be asked to grant it under System Settings, Privacy and Security, Accessibility. Reaper and FL Studio don't need it. Without permission your bounces are still signed; they may just read as Untitled bounce until you grant it. If the helper ever stops, the plugin shows a Launch Helper prompt in place of the main screen; click it to start the helper again.

DAW coverage

Logic, Ableton, FL Studio and Reaper are covered by our automated render harness, meaning every plugin build is bounce-tested in the real host before shipping. Cubase, Bitwig and Pro Tools are supported but covered by manual testing.

Revoking an install

Lost a machine, sold a laptop, or just want a clean slate? Open /settings and revoke the install from the Plugin installs panel. Your other installs keep working.

Updates

Plugin updates are manual for now. You can check from inside the plugin under Settings, or visit /plugin when a new build ships, and download the latest installer. It overwrites the existing install in place, with no uninstall step needed, and your account token and device name carry over. Restart your DAW afterwards so it rescans and picks up the new build, the same as a first install.

To see which version you're on, open the plugin's Settings tab. The line along the bottom shows the plugin version alongside the helper version, so you can confirm an update landed.

Leak tracking

Pro lets you create up to ten per-recipient variants of a track. Each recipient gets a unique signed copy. If one of those copies appears somewhere it shouldn't, scanning it returns the specific recipient label you assigned.

Set it up at /sign with the per-recipient mode. Add the recipient labels (names, emails, internal codes; whatever you'll recognise later) and Mivia generates the variants in a single pass.

Need more than ten variants for a single track? Email [email protected] and we'll set up a label or team plan.

Scanning

Anyone can scan a signed file at /scan. No account, no install. A scan returns the signature's author, when it was signed, and (for per-recipient variants) which specific recipient the variant was assigned to.

If a scan returns nothing, the file either wasn't signed by Mivia Sign or the signature was damaged past recovery. The latter is rare in normal workflows. Troubleshooting covers the common cases.

Mivia IDs and certificates

Every track you sign gets a Mivia ID. It's a 16-character code derived from the audio file (for example, 9F88EF8FACBE6709). The same file always produces the same ID, so it acts as the track's permanent reference on Mivia.

Every Mivia ID has a public certificate page at /c/<id>. The certificate shows when you signed the track, the title and creator name you signed it with, the Mivia ID itself, and the Bitcoin transaction the signature is anchored to. A QR code on the page opens the same URL when scanned with a phone.

The certificate is publicly accessible. Anyone can open it without a Mivia account. There are several ways to reach it:

• From your library: open any signed track and the certificate appears on the track page.
• From the audio file: drop it at /scan to read the signature.
• From the Mivia ID: paste it at /database to open the matching certificate.
• From a link or QR code: scan the QR on a certificate, or visit /c/<id> directly.

Sharing your certificate

A screenshot of the certificate is enough to share on its own. The Mivia ID is visible on the certificate, so the recipient can read it off the image, look it up at /database, and confirm the certificate is genuine. They don't need your file or a Mivia account.

You can also share your track's URL on Mivia directly. Sending someone the /track/<id> link redirects them to the public /c/<id> certificate if they aren't signed in to your account. They never see your library view, only the certificate.

Bitcoin anchoring

We anchor every signature to a Bitcoin transaction we broadcast on your behalf. Your Mivia ID is included in the next batch we send to Bitcoin. Once that transaction confirms, usually within a few hours, the signature is locked and the creation date can no longer be faked or backdated. The privacy notice's Bitcoin anchors and erasure section explains what happens to the anchor if you later delete a track.

Library and activity

Every track you sign drops into your /library. It's your catalogue: track titles, when you signed each one, any per-recipient variants you made, any collaborators on the track, and a link to its public certificate (see Mivia IDs and certificates).

On Pro, /activity is the real-time scan log: every scan of every track you signed, when it happened, where the scanner was, and (for per-recipient signs) which variant they hit. Useful for spotting unauthorised listeners while a release is still in-flight.

Collaborators

Tracks can carry collaborators alongside the owner. When someone scans the file, the collaborators show up in the scan result so credit goes to everyone who worked on it, not just whoever clicked Sign. Up to five collaborators per track.

The owner adds collaborators from the track's page in /library: open the track, click Add collaborator, and search by @username or email. Each collaborator needs an existing Mivia Sign account.

Letting others add you

Other people can add you as a collaborator only if the "Allow collaborations" toggle is on in /settings. It's on by default. Switch it off if you'd rather not appear on tracks you didn't sign yourself.

Account

Everything lives on /settings: your artist name, public @username, email, password, and a few preferences. Changes save when you click Save in the page hero.

Change your name or username

Edit the Artist Name or Username fields and save. Your username is the public @handle that shows up next to your signatures on scan results, so pick something stable. Username rules: lowercase letters and numbers plus dot or underscore, must start with a letter or digit, 3 to 30 characters.

Change your email

Edit the Email field and save. The change takes effect immediately. We send a security notification to your previous address so an unexpected change would be obvious. Your new email starts as unverified; you can verify it from the email field on /settings whenever you want.

Email notifications

Open /settings and expand the Email notifications section to pick which Mivia emails you want. Toggles save when you hit Done.

Available to everyone:

• Collaborator activity. When someone adds you to a track they signed.
• Plugin updates. When a new plugin version ships.
• News and updates. Occasional product news and feature updates.

Mivia Pro adds three more:

• Scan alerts. Every time someone scans one of your tracks.
• Weekly digest. A weekly summary of activity on your tracks.
• Anomaly alerts. Sudden scan spikes or scans from new countries.

Account-essential emails always send and can't be turned off: email verification, password resets, password and email change confirmations, two-factor and passkey change alerts, the account-deletion confirmation, and welcomes when you sign up or upgrade to Mivia Pro. They're tied to keeping your account safe and to acknowledging key events.

Change your password

Hit the Change password link at the bottom of /settings. The modal asks for your current password plus the new one. Existing sessions on other devices stay valid; if you'd rather sign every device out, use Log out from the avatar menu in the nav after changing.

Billing

Pro is $12.99 a month or $129 a year (two months free). Stripe handles payment; we never see your card details. Switching cadence, updating payment methods, downloading invoices, and cancelling all happen inside Stripe's customer portal, which you can open from the Manage button on /pricing or /settings.

Cancel

One click in the portal. Pro access continues until the end of your current billing period; after that you drop to Free. Everything you signed on Pro stays valid forever and anyone can still verify it. Cancelling doesn't invalidate anything.

Refunds

Annual plans are refundable prorated by month. If you bought yearly and want out after three months, you'll get nine months back. Email [email protected] and we'll process it.

After Pro ends

Once the billing period ends and you're back on Free, new signs fall under the Free 5-sign quota and the plugin refuses to sign new bounces. Everything you already signed on Pro keeps working: scans return your authorship, per-recipient variants still scan to their assigned recipients, and the historical entries in /library and /activity stay visible. Leak tracking and the activity feed just stop accepting new entries.

VAT and invoices

Stripe Tax adds VAT for EU customers automatically at checkout. Invoices for any past payment are downloadable from the customer portal under Billing history.

Privacy

Mivia doesn't keep your audio. The web signer uploads your file briefly so the signature can be written, then deletes it as soon as the signed version streams back. The plugin doesn't send audio at all; it computes a fingerprint hash locally and sends only that.

What we do keep is the manifest: the cryptographic record of authorship for each track you sign, plus your account row (email, name, password hash, your preferences, and a small set of timestamps we use to measure how the service is being used in aggregate). Per-recipient variants and plugin install records are stored against your account so you can manage them. The privacy policy has the full list.

Delete your account

Open /settings and click Delete account at the bottom of the page. This wipes your account row and any signatures you've created. Public files signed under your account remain scannable (we can't pull them off other people's devices), but the scan no longer ties them to a Mivia user.

See the privacy policy for the full GDPR-shaped detail.

Troubleshooting

A scan returns nothing

The signature didn't survive what happened to the file. The usual culprits are heavy time-stretching, large pitch shifts, re-recording the playback through a microphone, or aggressive transcoding (e.g. 32 kbps MP3). If the file went through normal distribution channels (Spotify, SoundCloud, mp3 export, format conversion) it should still scan, so reach out to [email protected] and we'll take a look.

The plugin doesn't appear in my DAW

Restart the DAW; most hosts only rescan plug-in folders on launch. If it still doesn't appear, check the install path matches what your DAW scans: macOS reads ~/Library/Audio/Plug-Ins/Components (AU), ~/Library/Audio/Plug-Ins/VST3 (VST3), and ~/Library/Audio/Plug-Ins/CLAP (CLAP). Windows reads C:\Program Files\Common Files\VST3 and the equivalent CLAP folder.

I'm on Pro but features are locked

Sign out and sign back in to refresh the tier flag on your session. If it still reads as Free, click Manage on /pricing to confirm the subscription is active in Stripe. If Stripe shows it's active but Mivia doesn't, the webhook probably hasn't fired yet (rare); email [email protected] and we'll sync it manually.

Plugin bounce hangs or shows an error

The plugin needs an internet connection to register each bounce. If you lose connectivity mid-bounce, the audio still passes through unsigned and the plugin shows an error chip. The next bounce tries again from scratch; nothing is queued.

The plugin shows Launch Helper or says it's offline

The plugin needs the Mivia Helper running to capture your export filenames, and an internet connection to register each bounce. If it shows a Launch Helper prompt, click that button to start the helper again. If it keeps happening, reinstall from /plugin, which reinstalls the helper too. If it says you're offline, check your connection and it returns on its own once you're back.

My bounces show as Untitled bounce

The Mivia Helper reads the export name from your DAW, and on macOS it needs Accessibility permission to do that in Logic, Ableton, Cubase and Pro Tools. Grant it under System Settings, Privacy and Security, Accessibility, then run the bounce again. Reaper and FL Studio don't need this. The bounce is signed either way; this only affects the name shown in your library.

Payment failed or card declined

Stripe retries failed payments on a schedule. You'll get an email from Stripe with a payment-update link. Pro stays active during the retry window, then drops to Free until the next successful payment. To swap card details before then, open Manage on /pricing and update inside the portal.

Get help

Email [email protected] for anything not covered here. We reply within one business day. For partnerships, label plans, or sales questions, use [email protected] instead.