Lyriff

Last updated: October 27, 2026

Lyriff (lyriff.com) is a free browser tool that helps you co-write paste-ready Style, Exclude, Key, lyrics, and titles for Suno Advance Mode workflows, plus Audio Lab, which de-noises and masters a finished song on your own device. This notice explains what happens to information when you use the site.

Who operates Lyriff. Lyriff is a product of Astralis Media Group, LLC. Contact: hello@lyriff.com.

What you provide

When you use Lyriff, you may type song ideas, genres, premises, themes, pasted lyrics, refine notes, chat messages with Pauly, and similar text so we can generate Style / Exclude / Key / lyrics / titles (and related coaching) for you.

In Audio Lab, you may load an audio file and type a song title for the download name. Those stay on your device (see Audio Lab below).

Optional: if you use Report a bug or a product-feedback form, you may also send a short description and an optional email.

What we do with it

1. Your text is sent to our generation server (currently hosted on Fly.io) so we can return a response to your browser.
2. Generation uses a third-party AI provider under our server-side API key — xAI (models in the Grok family). Today we typically use Grok 4.7 for heavier creative modes (for example Advanced Cowrite / Advanced Improve drafts and some Quick Style paths) and Grok 4.3 for lighter Style / Key / glue tasks. Exact model choice can change as we tune quality and cost; this notice names the provider and family so you know who receives the text.
3. Results are returned to your browser so you can copy, refine, export, or discard them.
4. We do not use your prompts or lyrics to train our own models. Under xAI’s Enterprise API terms (as of their published terms), xAI states it does not use API User Content to train foundation models without permission. See xAI Enterprise Terms and xAI API Security FAQ.

What we don’t do

• No accounts or sign-in required for the core tool today.
• We do not keep a browseable personal library of your generations. By default, what you type is processed to return results and is not saved on Lyriff as a history you can reopen later. Optional Quick Style share packs (below) are the exception.
• We do not sell your prompts or lyrics.
• We do not build public “what people generated” feeds. A share link is not a catalog — only someone with the URL can open that pack.
• Optional PDF downloads are created in your browser / session for you to keep locally; we do not use PDF export as a cloud library.

AI provider retention (xAI)

When text is sent to xAI for generation, xAI’s default API policy may store requests/responses encrypted for about 30 days for abuse/security auditing. Our xAI API team uses Zero Data Retention, so xAI does not keep your prompts or outputs after the response is returned. Lyriff’s stack uses chat-style generation and does not require xAI Files, Collections, or Batch APIs.

Fly.io and Netlify may still process technical request metadata (IP, timestamps, status codes) for hosting, security, and reliability under their own policies — that is separate from xAI’s content retention.

Your content and authorship (short form)

You keep what you bring in (your ideas, lyrics, notes). As between you and Lyriff, you own the outputs Lyriff returns to you, to the extent the law and our AI provider’s terms allow. We do not claim authorship of your songs. Outputs are AI-assisted; similar lines can appear for other users; you remain responsible for reviewing and deciding what to use. Full wording lives in our Terms of Use.

Shared style packs

Sharing is optional. After Quick Style results, Copy share link creates an anonymous public pack. No account is required to create or view one. These packs are style-only: Style, Exclude, and Key — not lyrics, titles, or descriptions. Cowriter and Lyric Improve share is not available yet.

• We store the Style, Exclude, and Key text, plus related pack fields (created/expiry), so the link can be opened later.
• The page is https://lyriff.com/p/<id>. Anyone with that URL can view the pack. Open in Lyriff loads it into Quick Style.
• Packs are kept for up to 60 days, then expire.
• You also receive a delete link with a secret token (we store only a hash). Use it to remove the pack early. Keep it — we can’t show the token again.

Audio Lab

Audio Lab processes audio entirely in your browser, on your own device. De-noising, clipping repair, mastering, the before/after player, stem mixing, and the WAV or MP3 download are all done locally.

• Your audio files and their filenames are never uploaded to Lyriff and are not stored by us. Audio is not sent to our generation server or to xAI. A mastered file exists only in your browser until you download it.
• Mix & Master Stems (on a computer): the stems you load (WAV or MP3 files, or a .zip of them), their filenames, any names or icons you give them, and the song title you type are read and mixed entirely in your browser. They are never uploaded and not stored by us; a .zip is unpacked on your device. The mix and its master exist only in your browser until you download them, and closing or reloading the page clears them. Your mixer settings are not saved.
• MP3 downloads are encoded in your browser too. The encoder is loaded from lyriff.com the first time you tap the MP3 button; your audio never leaves your device.
• Your Audio Lab settings (style, strength, loudness, and hiss cleanup) are saved in your browser’s localStorage on that device so they’re there next time. Reset to defaults, or clearing this site’s data, removes them.

Hosting & technical logs

The site is hosted on Netlify. Generation runs on Fly.io. Like most hosts, they may process standard technical data (IP address, timestamps, request metadata) for security, reliability, and abuse prevention under their policies.

Cookies / local storage

Lyriff may store small preferences in your browser (theme, text size, UI choices, your Audio Lab settings, a simple “visited before” flag for analytics). We do not use that for advertising profiles.

Analytics

We use Plausible, a privacy-friendly analytics service, for aggregate site stats. Events may include mode chosen, pack generated, copy, export, pack shared/opened, and text-size / theme changes. Attribution fields (campaign source, landing page, new vs returning visitor, rough pack-count bucket) may be included; they do not include Style, Exclude, Key, or lyric text, and they do not identify you by name or email.

Audio Lab sends these Plausible events: audio_lab_nav_click, audio_lab_file_loaded, audio_lab_pauly_suggestion, audio_lab_style_selected, audio_lab_strength_changed, audio_lab_path_selected, audio_lab_denoise_started, audio_lab_denoise_done, audio_lab_master_started, audio_lab_master_done, audio_lab_play_compare, audio_lab_export, audio_lab_stems_loaded, audio_lab_stem_master_it, audio_lab_stem_bounce, and audio_lab_stem_genre_mix. Their properties only describe the kind of choice or file: style, genre, strength, loudness preset, hiss cleanup on or off, file format, mono or stereo, a rough length bucket, which version you played and whether same-loudness was on, whether Pauly’s suggestion was used, which path you picked (Denoise & Master, Repair Only, or Mix & Master Stems), and which Audio Lab link you clicked. They can also include:

• Whether Pauly heard clipping in your song, and how much (noticeable, light, or none).
• Whether clip repair was on when you mastered or repaired.
• Whether hiss cleanup was on when you used Repair Only.
• Whether you downloaded a WAV or an MP3.
• For Mix & Master Stems: how many stems you loaded (audio_lab_stems_loaded, a count only), that you opened mastering in the mixer (audio_lab_stem_master_it, no properties), and which download you made (audio_lab_stem_bounce: the file type of the mastered mix, wav_mastered or mp3_mastered), and which genre you picked for a starting mix (audio_lab_stem_genre_mix with genre: one of pop, rock, indie, hiphop, rnb, funksoul, country, edm, folk, metal, punk, jazz, reggae or latin; nothing about your audio).

These events never include audio, filenames, song titles, or personal data.

Bug reports & feedback forms

Details you submit (and optional email) go through Netlify Forms so we can fix issues or read product feedback. Don’t include full lyrics, stems, or API keys. We use that info only to investigate and reply if you left contact details.

Optional feedback survey

Now and then, after you copy or export a pack or download a master, a small card may ask a few quick questions (how likely you are to recommend Lyriff, and one or two about what you just made). Answering is optional and we don’t ask who you are: we save your answers, which part of the site you were using (packs or Audio Lab), and the page address. There’s no name, email, or account. Answers go through Netlify Forms, which, like any form on this site, also records the IP address, browser type and the page you came from with each answer; we don’t use these to identify you. Whether you answered, chose Not now (we ask again in about two weeks), or chose Don’t show me this again is saved in your browser’s localStorage on that device, not in a cookie. Analytics counts when the card is shown, answered, or dismissed, with only a rough score group (low, middle, or high), never your typed answer.

Free while we learn

Lyriff is currently free while we learn what helps songwriters. If we add accounts, payments, or other features, we will update this notice to match how the product actually works.

Changes

We may update this notice. The “Last updated” date at the top will change when we do. Material changes that affect how we handle your content will be reflected here.

Contact

Privacy questions: hello@lyriff.com.

← Back to Lyriff · Terms of Use