Privacy Policy

This policy explains what Ninja MDE S.A.S. ("Vrenvo", "we") collects when you use vrenvo.com, and what we do with it. Questions: ninja@vrenvo.com.

1. What we collect

• Account data — your email address, password (stored as a hash, never in plain text), and optional display name. If you choose to continue with Google, Google tells us your email address, whether it has verified it, your name, and an identifier for your account with them; we keep the identifier so we recognise you the next time.
• Your uploads — audio files you submit for hosting, analysis, or mastering, the origin you declare for each track (made by people, by AI, or both — shown publicly with the track once you publish it), plus the results we compute from them.
• Your voice, when you keep a Sing take — Sing records your microphone in your browser while you sing over a track you own. The recording stays on your device while you record and preview; it is sent to our servers only when you choose Keep, where it is mixed with the track and then deleted (section 2).
• Covers you paint — when you run Cover, the four pictures it paints for your track, kept so you can pick one; the one you pick becomes your track's cover (sections 2 and 5).
• Usage data — plays, likes, tips, tool runs, credit transactions, and technical logs (IP address, browser type) used for security, rate limiting, and abuse prevention. When you are signed in, a tap on a next step after a result, a paywall shown to you, and a checkout you open are each recorded against your account — which step, where it happened (a result, Ship, a tool or the Wallet; a plan or a credit pack for a checkout) and when, and nothing else — so we can see how many members reach each step each week. These records are never shown to anyone, are not sent to any other company, and are deleted with your account.
• Purchases — for each credit pack or plan you pay for, a record of the sale: what you bought, the credits it added, the amount and currency our payment processor (Paddle) charged, when, and Paddle's transaction id for it. If you delete your account, these records are kept for accounting with your identity removed (section 6).
• Feedback you send — when you use "Send feedback" (in Profile, in the site footer, or on a page that failed to load), we store your words, the email address you leave (optional, and only asked for when you are signed out), the page you were on, the app version, whether your device had a signal, your browser's name, the last error the page showed, if there was one, and the player's last 40 events from this browser — which track, what the audio reported, when the page was hidden or woken — so we can see where playback stopped; never your words and never an address (the list itself is described in section 3). If you are signed in, the report is linked to your account. We also keep the IP address the report came from for 24 hours, only to cap how many reports can be sent in a day, and then delete it. A copy may be sent to our own inbox through our transactional email processor.
• Your YouTube connection — if you connect YouTube to post your videos, Google tells us your channel's id and name and gives us a key that lets Vrenvo upload to that channel. We keep the key encrypted, use it only when you tap Post or confirm a Release that posts, and delete it when you disconnect or delete your account. For each video you post we keep a record of which render, the video's YouTube link, whether you chose Public or Unlisted, when, and the premiere time you set, if any.
• Notifications, if you turn them on — when you tap Tell me when it's done (or the switch in Profile › Notifications) and allow it, your browser's push service — or, in the iOS app, Apple — gives this device an address for Vrenvo's notifications, and we keep that address with your account, one for each device you turn them on for. A notification tells you a fact about your own song: its title with a number of plays or views, or that a render landed, a walk finished or a video was posted, and the link it opens — never your audio, your email address or your name. In a browser it travels through the push service of the browser's maker — Google (Chrome and Android, the Play app included), Microsoft (Edge), Apple (Safari) or Mozilla (Firefox) — encrypted so that only your browser can read it; in the iOS app it travels through Apple's push service, which receives it as written, to show it on your lock screen. Turn them off for a device in Profile › Notifications.

2. How audio is processed

Tracks you upload for hosting, Analyze or Master are processed server-side: our servers measure the audio (loudness, true peak, spectral balance and similar signals). Analyze, Master and Amplify then send those derived measurements and the genre you chose — not your audio — to an AI model hosted by Anthropic to write the analysis or the mastering decisions; Amplify also sends the track's title. When you describe a release in one sentence on the Release page, we send that sentence, your device's current time and your time zone to Anthropic, which reads it into the settings the page shows you — never your audio, your account or user id, your name or a track's title.

Genre suggestion. After an upload, we may send a 30-second excerpt of the track — never the full file, with its metadata stripped — to a music-classification model hosted by Replicate, Inc. to suggest a genre. The suggestion is private to you until you confirm it; the excerpt is used only to answer that one request. Genre suggestions from the model can be switched off platform-wide, and are never used to train anything.

Stems. When you run Stems, we send your whole track — re-encoded as an MP3, with its metadata, file name and title removed — to a source-separation model hosted by Replicate, Inc. — or, when we run it ourselves, on a GPU server Vrenvo operates on Google Cloud in the United States, which keeps nothing after it answers — which sends back the separated stems. Rebalance mixes the stems we already hold and sends nothing.

Sing. The microphone is used only after you tap Record, and the preview of your take over the track plays in your browser — nothing is uploaded for it. When you choose Keep, we upload that recording to our own servers, mix it with the track there, and delete the recording as soon as the mix is made; it is never stored. Nothing is sent to anyone else. The mix is kept as a new version of your track, which is yours until you delete it; when you sing over the instrumental, it is made from the stems we already hold for you.

Cover. When you run Cover, we send four short text prompts, one per picture — your confirmed genre, up to six lines of your own transcribed lyrics, your track's measured tempo and key as words (slow or driving, dusk or daylight), a few words describing other measurements we already made, the style you chose and, if you type them, the few words of your own you add — never your track's title — to an image model hosted by Replicate, Inc., which sends back four pictures. Never your audio, never your name or email. The picture you pick is copied onto your track as its cover, with your track's title and your artist name set on it by us (never by the image model) unless you choose no type.

Lyrics. When you use Lyrics to read a song's words, we send the whole track — or its vocal stem, if you have already run Stems on it — re-encoded as a small mono MP3 with its metadata, file name and title removed, to a speech-recognition model hosted by Groq, Inc., which sends back the words. When you ask Lyrics to rewrite them, we send the transcribed lines, what you asked for, and the track's title, genre and declared origin — not your audio — to Anthropic. If you switch on Show lyrics on your track page, the lines Lyrics read from that track are shown, with their timings, to anyone who opens its public page, until you switch it off.

When you are signed in, after an Analyze we send the measured numbers of that run — loudness, peak, noise, dynamics — and the genre you chose, and after Lyrics reads a song's words we send the transcribed lines — never your audio — to a decision model hosted by Jev AI, which answers which step to take next and how the lyrics score; we store the answer with the run.

Post to YouTube. When you connect YouTube and tap Post on a video you rendered, we send that video file, its title, the description and tags Vrenvo wrote for it, and the privacy you chose (Public or Unlisted) to YouTube (Google LLC), which publishes it on your own channel under your YouTube account and its terms. Nothing is sent until you tap Post — or confirm a Release that posts, which sends the video when its renders finish, with no second tap: at once, or scheduled for the premiere time you set, which is sent to Google so YouTube publishes the video then — and nothing else from your account goes with it.

3. Storage, cookies and analytics

We set no advertising cookies, and we never sell or share what we store with an advertiser. What Vrenvo keeps in your browser is listed below, in full. Our servers also keep standard request logs (IP address, page requested, timestamp) for security and rate-limiting only.

What we store in your browser. All of it is browser storage on vrenvo.com, never readable by another site, and none of it is a cookie but two: when you choose to continue with Google, a sign-in cookie (vrenvo_oauth) that only our server can read holds that one sign-in's security check for at most ten minutes, and is deleted when you come back; and when you connect YouTube, a connection cookie (vrenvo_youtube) does the same for that one connection, for at most ten minutes.

• vrenvo_token_v1 — your sign-in token. Without it you would be signed out on every page load. Removed when you sign out.
• vrenvo_me_v1 — a copy of your account details as our server last confirmed them (your account id, display name, email address and account type, how you sign in, and whether you have accepted the generation terms — never a balance or anything about payments), so the app can open signed in when you have no signal. Refreshed every time the app opens with a signal, and removed when you sign out.
• vrenvo_queue_v1 — the play queue you built, so a reload does not lose it. After six hours it is no longer restored, and it is removed the next time Vrenvo opens. It never starts playing by itself.
• vrenvo_autoplay — your Autoplay setting, on or off, so the player remembers whether to keep playing more music when your queue ends. It is kept when you sign out.
• vrenvo_keep_v1 — the list of tracks you chose to keep for offline: each track's title, its artist's name and profile id, cover address, size and when you kept it, so the Kept shelf can show them with no signal. The audio itself, and a small copy of each cover, sit in this browser's own storage on this device only — they are never uploaded anywhere and never shared with another device. Kept tracks stay on this device until you remove them ("Remove from offline") or clear site data — signing out does not remove them. If a kept track is taken off Vrenvo, its copy is deleted from this device the next time the app has a signal and learns the track is gone.
• vrenvo-handoff — when you drop a track on the home page or on /decode, a copy of that one file is kept in this browser's own storage on this device, so that if you then create an account or sign in your upload starts with it and you do not have to find it again. It is never uploaded until you choose Upload; it holds one file at a time, is removed as soon as the upload screen takes it, and is no longer used after 30 minutes. Beside it, vrenvo_handoff_landed_v1 notes the file's name, size and date — never its contents — for this visit only, so that signing in opens the upload screen for that file once and not every time.
• vrenvo_first_landing_v1 — set for this visit only when you create an account, so the first page you land on tells you once about your own invite link; it holds no personal data and is removed the moment that page has shown it.
• vrenvo_ping_queue_v1 — a play that happened with no signal (which track, and when), so the track's play count still includes it. It is sent when your signal returns, then deleted.
• vrenvo_journal_v1 — the player's last 40 events in this browser: which track played or ended, what the audio element reported, and when the page was hidden or woken. It holds player events only — never your words and never an address — and it is kept so that a report you send after the app was closed or restarted still shows what the player did before. It leaves this browser only inside a feedback report you choose to send. Each new event pushes out the oldest; signing out does not remove it, and clearing site data does.
• vrenvo_studio_returning_v1 — notes whether this browser has seen your runs on the Create home, so the next visit draws the right size of upload area from the first moment instead of resizing it once your runs load. It holds a single yes and nothing about the runs themselves; it is replaced on every visit and cleared with site data.
• vrenvo_consent_v1 — the choice you made on the privacy bar, so we stop asking.
• vrenvo_anon_claim_v1 — when you score a song without an account and tap to sign up and save it, the run's reference and a code our server gave this browser for that one score, so that once your account exists the score becomes yours. It holds those two values and nothing else, is kept for this visit only, and is removed the moment you sign up.
• vrenvo_origin_v1 — how your last upload was made (by people, with AI, or both), so the next upload on this device opens with that answer already chosen; you can change it on every upload. It holds that one word and nothing else, and stays until you clear site data.
• vrenvo_go_v1 — which tool and which of your tracks you just opened from a "next step" card, so that tool starts its free step (your free first score, or reading your song's words) only because you tapped the card, never because a link was opened. It holds that tool's name and the track's number and nothing else, is kept for this visit only, and is removed the moment that tool opens.
• vrenvo_haptics_v1 — set to off only if you turn off touch feedback (the small buzz a phone gives when you press a control), so Vrenvo stays silent on this device; it holds that one word and nothing else, and stays until you clear site data.
• vrenvo_locale_v1 — the language you chose for Vrenvo's screens (one of five codes, such as es), so the app opens in it. It is written only when you pick a language, holds nothing else, and stays until you pick another or clear site data.
• vrenvo_ref_v1 — the referral code of the link you arrived on, kept for this visit only (it is cleared when you close the tab).
• vrenvo_twa_v1 — set when Vrenvo is opened from Vrenvo's Android app, or from a link another Android app opened (a link tapped in an email app, for example): a flag noting that this visit came from an Android app, so that a page inside Vrenvo's Android app knows it is there. It holds no identifier and is kept for this visit only. The iOS app sets none.
• vrenvo_route_reload_v1 — the address of a page that reloaded itself once after a new version of VRENVO was published, so it never reloads twice in a row; kept for this visit only.
• vrenvo_feedback_draft_v1 — the words you had typed into "Send feedback", kept only when you tap its Privacy link, so they are still in the box when you come back from this page. Kept for this visit only, and removed as soon as the box takes them back, or when the report is sent.
• vrenvo_release_intent_v1 — the release you had set up on the Release page (its switches, the time you picked and the sentence you typed), kept only while you go to YouTube to connect your channel, so the page is as you left it when you come back. Kept for this visit only, and removed as soon as the page reads it back.
• vrenvo_push_result_ask_v1 — notes that Vrenvo offered to turn on notifications under a finished result, so it offers that once and not on every result; kept for this visit only. It holds no message and no address.
• vrenvo_rail_tab_v1 — on a wide screen, which list a tool page's side column shows (its tools or your tracks), so it stays as you left it while you move between tools; kept for this visit only. It holds no track, no message and no address.
• vrenvo_score_seen_v1 — notes which of your Analyze scores you have opened from the Ship page, so it shows you the score first only until you have seen it; kept for this visit only. It holds the runs' random ids and nothing else — no score, no track, no message and no address.
• vrenvo_oauth_pending — set only when you choose to continue with Google, so that this tab, and no link from anywhere else, can finish that sign-in. Kept for this visit only, and cleared when you come back.
• vrenvo_anon_v1 — a random id for this browser, used only for product analytics. It is created only if you choose "Accept all", and never otherwise.

Analytics, only if you allow it. On your first visit we ask one question: accept all, or essential only. Nothing optional runs until you answer, and "Essential only" is a complete answer — the product works the same either way. If you accept, we use PostHog as our analytics processor and send a small number of product events: which screen a paywall was seen on, that a share link was copied, that a checkout was opened, and similar. Each event carries the random browser id above (or, once you are signed in, your account id), the event name and a short list of non-identifying properties. We never send your email address, your display name, your track titles, your audio, or the contents of anything you upload. We do not join your anonymous browsing to your account: the events from before you signed in are never merged into your account's history.

Analytics run only when both are true: we have enabled a key for them, and you have allowed them. If either is missing, nothing is sent at all.

Error reporting is essential and is not optional. When a page fails we send the error and the technical context around it to Sentry, our error-reporting processor, so the failure can be fixed. These reports carry no analytics id and no marketing use. A product that cannot see its own crashes cannot be repaired, so this is described here rather than offered as a choice.

Changing your mind. Use the button below to forget your choice — we will ask again on your next visit, and any analytics id we hold in this browser is deleted with it. Clearing this site's data in your browser settings removes everything in the list above, including your sign-in.

Change your privacy choice

4. What we do not do

• We do not sell your personal data.
• We do not use your uploads to train AI models.
• We do not share your data with third parties except the processors needed to run the Service, each bound to their own privacy obligations: payment processing (Paddle), cloud hosting and backups (Railway; an S3-compatible backup store), AI analysis of derived measurements, lyric rewriting and reading your one-sentence release (that sentence, your device's time and your time zone), never your audio (Anthropic), music classification of a 30-second excerpt, when you run Stems, separation of your whole track and, when you run Cover, image generation from a text prompt (Replicate), separation of your whole track when you run Stems (Google Cloud — only when Stems runs on our own worker), lyric transcription when you use Lyrics (Groq), next-step and lyric-score decisions over measured numbers and transcribed lines, never your audio (Jev AI), transactional email (Resend), error reporting (Sentry), sign-in when you choose it (Google), posting a video to your own YouTube channel when you connect it and tap Post or confirm a Release that posts (Google — the video, its title, description and tags, the privacy you chose, and the premiere time you set, if any), notifications you turn on (the push service of your browser's maker — Google, Microsoft, Apple or Mozilla — which receives your device's notification address and each notification encrypted so that only your browser can read it; in the iOS app Apple, which receives the device's address and the notification itself: a song's title with a number, or a word that it landed or was posted, and the link it opens, never your audio, your email address or your name), and — only with your consent, as section 3 describes — product analytics (PostHog).

5. Retention

Account and transaction records are kept while your account exists and as required for accounting and legal obligations. Tracks you publish are kept until you delete them or your account.

The files our tools make from your tracks are kept for a limited time, counted from the day you ran the tool, and then deleted automatically. The record of the run itself stays with your account.

• Master — the mastered WAV for 30 days, and its MP3 preview for 90 days.
• Stems — the separated stems for 30 days.
• Cleanup — the cleaned files for 30 days.
• Layers — the mix with your added layer for 30 days.
• Rebalance — the rebalanced mix for 30 days.
• Clip — the vertical MP4 clip for 30 days.
• Video — the MP4 video of your whole track for 30 days.
• Cover — the four covers it paints for 7 days. The one you pick is copied onto your track as its cover and stays until you change it or delete the track.
• Sing — the mixed take for 30 days. Your raw recording is deleted as soon as it is mixed, and the take you keep is a version of your track, kept until you delete it; the instrumental Sing makes from your stems goes when they do.

If you connect YouTube, the encrypted key that lets Vrenvo post to your channel is kept until you disconnect YouTube or delete your account, then deleted. The record of each video you posted stays with your account, and is part of your data export; the key is never exported. The videos themselves live on your YouTube channel, where you manage them.

If you turn on notifications, each device's notification address is kept until you turn them off for that device, until the push service tells us the address no longer works, or until you delete your account — then deleted. It is not part of your data export.

We take nightly encrypted backups. When you delete something, it leaves our live systems immediately and ages out of our backups within 30 days.

6. Your rights and deletion

You can delete your account yourself, from inside Vrenvo: Profile → Delete account. It asks for your password and removes your account, your uploaded tracks and their audio, your tool runs, and the notification addresses of your devices. Unspent credits are forfeited and are not refunded. Records we must keep by law — billing and transaction history — are retained without your identity attached to them, and tips you sent stay with the artists who received them. Feedback you sent stays too — the words and the page context around them — with your account, your email address and your IP address removed from it, so it no longer points to you. You may also request access to or correction of your personal data by emailing ninja@vrenvo.com from your account address. Colombian data protection law (Ley 1581 de 2012) grants you habeas data rights; residents of other jurisdictions retain any rights their local law provides.

7. Children

The Service is not directed at children under 13, and we do not knowingly collect their data. If you believe a child under 13 has an account, contact us and we will delete it.

8. Changes

We may update this policy; material changes are announced on the Service or by email.

Change log: October 20, 2026 — three browser storage items added, the language saved to your account, your public address and your Spotify link (listed at the top); the Release page — the one sentence you type, your device's time and your time zone read by Anthropic, a confirmed Release that posts to YouTube with no second tap, at once or at the premiere time you set, and one item kept for the visit while you connect YouTube (vrenvo_release_intent_v1). October 3, 2026 — previous version.

9. Contact

Ninja MDE S.A.S. · Medellín, Colombia · ninja@vrenvo.com