Our billing promises

Your credit balance has no expiry date. This is not a policy we promise to remember — there is no expiry date stored against your balance for anything to check, and nothing that runs on a schedule looks at it.

Only one thing reduces your balance: running a job that costs credits. Letting a plan lapse, buying a smaller plan next time, or not signing in for a year all leave it exactly where it was. Free credits, plan credits, and credit-pack credits are the same balance — none of them is treated differently, and none of them is use-it-or-lose-it.

Credits are not transferable between accounts and are not redeemable for cash.

If a job fails after its credits were debited, those credits return to your balance automatically. You do not have to ask, and there is nothing to claim.

The refund is written in the same database transaction as the failure itself, rather than as a follow-up step — so there is no window in which a job can be marked failed while the refund goes missing. It is also recorded on the job, so a retry cannot refund the same job twice.

This covers every way a job can end badly that we know of:

• The tool errored, or the AI provider was unreachable.
• The job ran past its time limit and was stopped.
• You cancelled it yourself from Job History.
• The worker crashed or was killed without recording anything. A sweep runs every five minutes to find jobs whose worker died, mark them failed, and refund them; its backstop for a job that is merely slow is 65 minutes.
• The queue was unreachable when you submitted, so the job never started. It is reclaimed and refunded by that same sweep — within the hour, not instantly.

If you are billed by audio minutes rather than credits, a failed job costs you nothing for a simpler reason: minute-metered jobs are charged on completion, so a job that never completes is never charged at all. If a job runs past the last of your minutes, it still finishes and still gives you the result — your balance floors at zero rather than going negative.

Refunds fire on failure. They do not fire on disappointment, and we would rather say so here than let you discover it.

A job that runs to completion and hands back a poor result — words misheard, timings loose, a language read wrong — is, as far as the system is concerned, a job that worked. It stays charged. There is no automatic quality-based refund, and there is no button anywhere in the product that requests one: every refund described on this page is triggered by a job failing, not by a person judging the output.

So if a job burns credits and gives you something useless, email support@lrcsong.com and we will sort it out. We are describing that as a person reading your message, because that is what it is. It is the one promise on this page with no mechanism behind it, and pretending otherwise would make the rest of the page worth less.

Paid plans are one-time purchases. You are charged once, for the period you select, at the moment you buy. There is no trial that converts and no deferred charge.

Concretely: the checkout our pricing page opens creates a Razorpay Order — a single charge, for a single amount we hand over at that moment. It does not create a Razorpay Subscription, which is the object that would be needed to register a mandate and charge your card again. No mandate is registered, so no further charge can be taken without you deliberately making a new purchase.

An endpoint that could enrol you in auto-renewal does exist in our codebase. It is switched off behind an operator flag, and no page or button in the app calls it — the pricing page reaches for the one-time path directly.

Because each purchase is charged once and in full, a later price change can never reach back and affect a purchase you have already made.

When your period ends, access ends. There is nothing to cancel, because nothing renews — you simply do not buy again.

Your credits stay. No path that ends, expires, or changes a plan touches your balance; the plan status and the credit balance are separate records and the former is not consulted when spending the latter. Credits you bought or were granted remain yours to spend on the free tier.

What does stop are the plan perks that are checked live against an active plan: your position in the job queue and the number of jobs you can run at once. Those follow the plan, not the balance. If that is what you paid for, it is worth knowing they end when the plan does.

We do not auto-delete your job history. The retention window ships set to zero, which the cleanup task reads as keep forever and stops without deleting anything. Your jobs and the lyrics they produced stay until you delete them or close your account.

The generated files are a different thing, and this one surprises people. Your uploaded source audio and large media outputs are removed by a scheduled cleanup roughly 24 hours after the job — the job record and its lyrics text survive, but the file itself is gone. Download anything you want to keep.

If you pin or rate a job, both it and its files are spared — from the file cleanup, and from the history cleanup even if an operator ever turns one on. That is the supported way to keep a result indefinitely.

The exact timings, and what happens to everything else, are in the Privacy Policy.

Prices are per tool, not per job. The lyric tools — generating an LRC, extracting lyrics, aligning words to audio — cost a single credit each. The heavier video and voice tools cost more, and a few tools that scale with media length compute their price from the length of your file.

The price a tool page shows you is the price the backend charges. Both read the same table, so the number you agree to and the number you are billed cannot drift apart.

Audio minutes, if you switch to that meter, apply to the four audio-transcription tools that record how long your audio was: LRC generation, lyrics extraction, word alignment, and speech transcripts. Every other tool bills credits whichever meter you are on.

Everything above this section describes something the software does, which means you could in principle catch us if it were untrue. The two commitments below are not that. They are things we intend to do, enforced by nothing but us doing them. They are in their own section so you can tell the difference at a glance.

• We will not remove features you have paid for, mid-period. If a change materially disadvantages paying users we will give reasonable notice and, where appropriate, a pro-rata refund. There is no code that enforces this and no automatic pro-rata mechanism; it is a commitment, and it is also in our Terms.
• If a paid job wastes your money, tell us and we will make it right. As set out in section 3, nothing automates this. It is a person and an inbox.

If anything on this page turns out not to match what actually happened to your account, that is a bug in the page and we want to hear about it — email support@lrcsong.com. A page like this is only worth the accuracy of its worst sentence.