Understudy

Terms of Service

Understudy

Last updated: 26 August 2026 · Version 1.0

1. These terms, and who they apply to

These terms cover your use of Understudy, A REST endpoint that returns an interactive demo built for one named prospect from a recording you uploaded, billed per generated demo.. They are a contract between Understudy, of Understudy Software Ltd, 12 Hanover Quay, Dublin 2, D02 XY45, Ireland (“Understudy”, “we”) and the company that signs up (“Customer”, “you”).

The service is for businesses only, not consumers. By signing up you confirm that you are acting for your business and that you have the authority to commit your company.

The person who accepts these terms accepts them for the company, not for themselves. If you don’t have that authority, please don’t go ahead.

If documents disagree. This order applies: (1) a signed order form or agreement between us, (2) the data processing agreement, (3) these terms, (4) our Privacy Policy, (5) anything else on our website.

2. What the service is

Access to the generation API on the key issued to you, storage and serving of the demos it returns for their lifetime, the review queue for flagged spans, and email support on the API.

3. What the service is not

These limits are deliberate, and they are part of what you are buying. They are not defects.

Not a platform. There is no editor, no library UI and no analytics dashboard. Rivia.AI sells a platform with dashboards and a Chrome extension around this job; we return a URL and post a webhook.

Not a recorder. We do not capture. You bring the recording from whatever you already use, and if you have no capture workflow this product has nothing to stand on.

Not a generator. We never invent a screen. Every frame in a returned demo came from your recording. If the prospect's use case needs a screen you never captured, we cannot make one.

Not an engagement or feedback suite. One endpoint, one job. Nurture sequences, in-app surveys and feedback collection are somebody else's product.

4. What you need to do, and why it matters

What you get from the service depends a lot on things only you control. Please read this section carefully, because sections 9 and 10 build on it.

The recording and its tenant. You capture, and whatever was on screen is what we hold. Use a seeded tenant unless you have decided otherwise, deliberately.

The context you send. Every string in a context object appears on a screen a prospect will see. Sending the wrong figure produces a demo showing the wrong figure, quickly and reliably.

The review queue. Flagged spans stay unsubstituted until somebody on your side rules on them. Ignoring the queue makes demos more generic rather than more wrong, which is the safe failure and still a failure.

Distribution. You decide who receives a demo URL and how. We do not send anything to a prospect.

Expiry. Demos expire in 30 days by default. If you extend one, the version of your product it shows is your problem to keep true.

5. Getting started, and what is free

The first 200 generated demos each month are free, on every account, permanently. No card to start.

The free allowance is not a trial and does not end. A team generating under 200 demos a month never pays us.

We may decline or end the free allowance where an account appears to be for competitive evaluation, or where usage is automated at a volume the offer plainly does not contemplate.

If you stop, every demo you generated stays live until its expiry and then goes, and you owe nothing.

6. Fees

Per generated demo. EUR 0.40 per demo returned by the API beyond the free 200 each month, invoiced monthly in arrears. Views are not counted: a demo sent to one person and a demo opened four hundred times cost the same.

Failures are free. A call that does not return a demo is not billed, and an identical context regenerated within 24 hours is billed once.

No seats. Keys, reviewers and viewers are not counted. There is nobody to add and nobody to license.

No commitment. No minimum, no annual term, no platform fee. Stop calling the endpoint and the bill stops.

7. Delivery, availability and support

The endpoint. A REST API over HTTPS with a bearer key you issue and revoke yourself. Rate limits are published and raised on request.

The demo. Served from AWS eu-west-1 in Ireland at an unguessable URL, with a webhook when a viewer finishes it.

Support. Email, weekdays, on the API and on the review queue. We do not write your context objects and we do not advise on your demos.

Support. Support is by email at [email protected]. We aim to reply within one business day. That is a target, not a guarantee.

8. Demos, their context and what you can audit

Every demo keeps its inputs. The recording identifier, the context object and the substitution rules applied are stored with the demo, so what a prospect saw can be reconstructed exactly.

The reviewer log. Every approval and correction carries the person and the timestamp.

Export. Demos, contexts, analytics and the reviewer log export as JSON from the API without asking us.

Deletion. Deleting a demo deletes its context and analytics with it. Closing the account removes recordings, demos and corpus within 30 days.

9. What we promise, and what we don’t

We promise to provide the service with reasonable skill and care, and that we have the right to provide it.

We warrant that a returned demo contains only frames from the recording it names and only substitutions permitted by rules you or your reviewer approved. We do not warrant that a substitution is appropriate, that a figure you supplied is correct, or that a demo will persuade anybody.

Beyond that we give no other warranty. As far as the law allows, we exclude all implied warranties, including merchantability, fitness for a particular purpose and non-infringement.

10. Liability

10.1 Neither of us limits liability for death or personal injury caused by negligence, for fraud or fraudulent misrepresentation, or for anything else the law says can’t be limited.

10.2 Losses neither of us covers. Neither of us is liable for lost profit, revenue, expected savings, business, goodwill or reputation, or for any indirect or consequential loss, however it arises.

10.3 Specific exclusions. We exclude liability for the contents of a context object you sent, for a demo forwarded beyond its intended recipient, for a recording made against a tenant containing real customer data, and for commercial outcomes of any demo.

10.4 Cap. Our aggregate liability in any twelve-month period is capped at the fees you paid us in that period, and a free-allowance account is capped at nil.

10.5 You accept that the limits in sections 9 and 10 are a fair way to share risk, given the price and your part under section 4, and that we could not offer the service at this price without them.

11. Confidentiality and data

Recordings, context objects, generated demos and anything you send us in support are confidential, are not used to train anything beyond your own account except the interface taxonomy described above, and are deleted on request.

How we handle personal data is set out in our Privacy Policy and in the data processing agreement between us, which forms part of these terms. If the DPA and these terms disagree about personal data, the DPA wins.

12. Who owns what

The API, the classifier, the renderer and the taxonomy remain ours, licensed to you for the term.

Your recordings, your context objects and every demo generated from them are yours. We claim nothing in them and we do not use them as examples.

The approved substitution rules in your account belong to you and export with everything else.

You may not use our name or logo in public, and we may not use yours, without written permission first.

13. How long this lasts, and how it ends

13.1 The contract starts when you sign up and runs until one of us ends it.

13.2 You can end it. Cancel at any time. It takes effect at the end of the current billing month, unless section 6 sets a minimum term.

13.3 We can end it. We can end it with 30 days’ notice. We can end it immediately if you seriously break these terms and don’t fix it within 14 days of being told, if you become insolvent, or if your use exposes us to legal risk.

13.4 What happens then. We stop delivering and stop billing. You keep everything already delivered to you, and your right to use it continues. We delete or return our working copies as the DPA says. Sections 9, 10, 11 and 12 continue to apply.

14. Changes to these terms

We may update these terms. A change that matters takes effect 30 days after we email you about it. If you don’t accept it, you can end the contract before then. Using the service after that date means you accept the change.

15. Contact

Understudy, Understudy Software Ltd, 12 Hanover Quay, Dublin 2, D02 XY45, Ireland
[email protected]

← Back

Your request has been received.

Expect a message from Understudy. It goes to the address you gave.