Questions, answered

Metered actions, such as an AI contract analysis, a royalty run, a contract parse or a generated split sheet, draw credits from your wallet. Your plan’s monthly credits expire at the end of each billing period; credits you buy don’t expire while your account is open. You’re charged only when a result is delivered, and a OneClick result or contract parse you’ve already paid for isn’t charged again in the same billing period.

Your plan’s monthly credits don’t. They reset on your billing date. Credits you buy don’t expire while your account is open, and they’re spent after your monthly credits. Track both on your profile’s Usage tab.

No. You’re charged only when the result reaches you. A run that fails isn’t charged, and neither is a OneClick result you leave before it arrives. When OneClick pauses to ask you about a contract, that isn’t charged either.

Not for a OneClick result or contract parse you’ve already paid for in the same billing period: pressing Calculate Royalties again with the same contracts and statement brings back the saved result. Recalculate reads everything again from scratch, so it’s charged each time. Split sheets and Zoe answers are charged each time too. Use Recalculate only after you change something.

Yes, at any time from your billing settings. Cancelling takes effect at the end of the period you’ve paid for, and partial periods aren’t pro-rated.

Open your profile’s Plan & billing tab. On the Free plan, Upgrade or View plans shows what each plan includes. On a paid plan, Manage subscription changes your plan or billing period.

You can create or join a team. Teams are for Basic and Pro: everyone uses their own credits, and there are no seat limits. Every team is covered by one admin’s plan, which provides its team slot and storage. Artists, projects and boards held by a team belong to the team, not to the person who added them.

Every active member of the team sees its artists and everything under them: projects, works, files, audio and logins. A suspended member loses access until an admin reactivates them. People outside the team see only what they’re added to: a project they’re a member of, or a single work they’re invited to.

There’s no seat fee, but joining a team needs a Basic or Pro plan. Your AI work on the team is paid from your own credits, the same as anywhere else, and admins see only what you spend on the team’s work. If your plan ends, your seat is paused until you renew. On the Free plan you can still be invited to a single project or work.

The contracts or split sheets as PDFs, and the royalty statement as an Excel (XLSX) or CSV file. Text-based PDFs work better than scans. OneClick reads master royalties from streaming earnings, so a split sheet that covers publishing only won’t be picked up.

OneClick only counts an amount as owed when everything behind it was read from your documents or confirmed by you. Anything else shows greyed out as not counted yet; click it to see why. Answering I’m not sure to a question also puts that payment on hold, and amounts waiting for the label to earn back its costs stay on hold until it has.

Go to Tools → OneClick → Royalty Tracking and press Draft payouts, or Pay Royalties on a OneClick result. Tick each person, then press Draft payouts: everyone gets their own draft with a full breakdown. Open a draft and press Pay now, or choose Mark as paid if you paid another way. Every paid payout has a receipt.

The Bank of Canada’s official daily rates, the mid-market rate with no markup. Remediio checks them once a day and keeps them, so changing a currency is quick. Converting between two currencies other than the Canadian dollar goes through it. On weekends and holidays the last published rate is used. Each draft uses the rate from the day it was made, and paid payouts never change.

Master royalties from streaming, one track at a time. For each run, choose the contracts or split sheet for that track and the royalty statement that lists its earnings. To pay several tracks, run OneClick once for each. Publishing royalties aren’t covered yet.

Saved OneClick results that used the contract are removed. Amounts that came only from that contract are removed from Royalty Tracking; amounts other contracts also cover stay. Payouts are never removed, paid or not: if someone was already paid more than they’re now owed, the difference shows as a credit. You’re shown what will change before the contract is deleted.

Its saved OneClick results are removed, but the amounts it added to Royalty Tracking stay, and so do payouts. That way a corrected statement can replace the old numbers (Replace old numbers) without losing your payment history. To clear the amounts too, use Clear royalty entries.

To remove one unpaid payout, open its draft’s ⋯ menu and choose Cancel payout. To start a whole project over, open the project’s Settings tab and press Clear royalty entries (project owner only): its royalty entries and saved OneClick results are cleared, payout records are kept, and the next OneClick run works everything out from scratch. You don’t need to delete anything just to recalculate: running the same statement again updates its numbers.

Yes. Right after Mark as paid, the Marked as paid notice has an Undo button. Later, a payment you recorded yourself can go back with ⋯ → Revert to draft. A payout sent from inside Remediio can’t be reverted, because the money has already moved.

No. We never use your content to train our proprietary AI models. Zoe reads the contracts you pick only to answer your question.

Images (PNG, JPG, WEBP), PDF, Word, text, CSV or Excel files, up to 10 MB each and 10 per chat. An attachment belongs to that chat only and is kept for a limited time, after which the chat shows it as No longer attached. Contracts you pick from your projects stay in your projects.

Yes. Every chat is saved automatically, so you can pick it up later from the chat list or start fresh with New chat. Chats are stored per person, not per team, so nobody else in your workspace can read them. Deleting a chat removes it.

As soon as you add it. A work is registered to the person who created it, and inviting collaborators never changes that. Each invitation is Pending until that person accepts or declines, and People & access on the work page shows each person’s answer.

On the work page, Invite collaborator sends them an email showing their split, with a link to review it. They click Accept invitation to confirm, or Accept or Decline under Shared with me, then Pending, in their Metadata Registry, which still works after the email link expires. A collaborator sees only that work: their own split, plus anything you choose to share.

PDF is for signing and sharing; Word is an editable document. Pick one on the Summary step and press Generate. The document ends with a signature section.

Yes. Each generated document is charged once, and PDF and Word count separately. Your plan may also limit how many split sheets you can make each billing period.

You do. Uploading a contract, a statement, a master or a split sheet doesn’t transfer any ownership to us, and we never use your content to train our proprietary AI models.

Yes, with Delete account on your profile’s Security tab. You’re signed out at once, sign-in is blocked, your subscription is cancelled and your team seats are suspended. Everything is permanently deleted 90 days later. Until then, email us and we can restore the account. Export anything you want to keep first.

For 90 days nothing is erased, so an accidental deletion can be undone. After that, your files, audio, Zoe chats and their attachments, your personal artists with their projects and works, your profile and your login are permanently deleted and can’t be recovered. Artists that belong to a team stay with that team. Invoices and payment records are kept for seven years because tax law requires it, and encrypted backups roll off on their normal schedule.

Yes. The partner API lets your own software calculate royalties, read splits from contracts, make split sheets and ask Zoe. Every team gets API access: a team admin creates the keys, and they spend the team’s API credits.