Terms of Service

1. These terms, and who they apply to

These terms cover your use of Dailies, an API that renders finished talking-actor ad variants from a manifest your scheduled job posts, billed per finished second. They are a contract between Dailies Render, Inc., of 1355 NW Everett Street, Suite 200, Portland, OR 97209, United States (“Dailies”, “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

Dailies is a job endpoint. Your scheduled job posts a manifest of up to 200 variants, each a script in three parts, an actor and a voice from our catalog, and references to the brand kit and product clips your workspace uploaded. For each variant the service generates speech, renders the actor's performance from it, aligns captions to the spoken words, cuts at the part boundaries, inserts your clips at the markers the script names, adds your end card and encodes a 1080 by 1920 MP4. It returns a signed URL per variant, a job report with each variant's finished seconds, cost, sync score and any screen flag, and a webhook when the job closes. Files stay in hold until a member or your runner makes an approve call; on approval the service can create the file as a paused ad in an ad set you name.

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 custom likeness. The service does not build an AI twin or an avatar of your founder, your customers or your staff from footage you supply. The actors are the licensed performers in the catalog and nobody else.

Not an editor. There is no timeline and no per-cut adjustment. A change to a caption, a cut or a clip is a change to the manifest and a new render, which is billed again unless the variant is unchanged and served from cache.

Not a copywriter or a media buyer. The service does not write hooks or scripts, choose winners, read performance data or manage spend. A push creates paused ads and nothing else; whether they run is decided in your ad account.

Not a desktop engine. Nothing installs. If your pipeline has to run offline or on a machine without network access, this service is not the tool for it.

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.

Rights in what you upload. You hold the rights to your scripts, your brand kit and your product clips, and a release for any person who appears in a clip. You are responsible for the use of any trademark in a script or an end card.

The claims your scripts make. You are responsible for the truth of every claim in a script and for meeting each ad platform's policies. The screen holds a variant for a named member to look at; it is not a legal or regulatory review and does not make a claim compliant.

A runner and somewhere to keep the files. You run the scheduled job that posts manifests, catch the webhook or poll the job, and copy finished files into your own storage within the 90 days we keep them.

Review and release. You name the members who may release, hold or drop a variant. The default state of every file is hold, and a push to an ad account happens only on an approve call from your workspace.

Disclosure of synthetic media. You label AI-generated advertising wherever a platform or the law requires it. We set the label on TikTok pushes and write provenance metadata into every file; the rest of the disclosure is yours.

Keys. You keep your live key secret and rotate it in Settings if it is exposed. Every job posted under your key is billed to you.

5. Getting started, and what is free

A sandbox key is free without a time limit and without a payment card: 720p output with a watermark, up to 120 finished seconds a day, the full catalog and the full assembly. A live key needs a card on file and bills from its first finished second.

There is no trial of the live rate. The first live job is billed like every other; a failed render never is.

6. Fees

The rate. $0.12 per finished second of each variant, measured on the finished file from its first frame to its last, including the end card, and rounded up to the next whole second once per variant. Prices are in US dollars and exclude tax.

What is not billed. Sandbox renders. Failed or timed-out renders. Re-renders our own sync check triggers. A variant posted again unchanged within 24 hours, which is served from cache. Uploads, storage within the 90-day window, webhooks, job reports, and pushes into an ad set.

Billing. Finished seconds are billed monthly in arrears by card on the first of the month, with an invoice listing each job, each variant and its finished seconds. A live key can be capped at a dollar amount per month in Settings; a job that would pass the cap is refused when posted, not queued.

No minimum, no term, one rate. There is no minimum and no contract term: stop posting and the bill is zero, and a key can be deleted in Settings at any time. The published rate applies to every workspace and we do not negotiate a different one. A change to the rate is announced by email 60 days before it applies.

7. Delivery, availability and support

Files and the webhook. Each variant returns a signed URL valid for 90 days, and a signed webhook fires when the job closes. The time a job takes depends on the number and length of its variants and on the night's load, and we commit to no render time.

Limits. A job holds up to 200 variants, a live key may have 4 jobs in flight, and a script may not exceed 60 seconds spoken. A job refused for capacity returns a Retry-After header. Sandbox keys carry lower limits.

Versioning. The endpoint is /v1/jobs. A change that breaks a manifest ships as /v2, and /v1 keeps working for 12 months after that.

Support. Support is by email and is answered by the next business day in Portland, Oregon.

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

8. Jobs, files and the cost line

Job reports are not edited. A variant's finished seconds, cost line, sync score and screen flag are written once when the render completes. A release, hold or drop is added with the member's name and time, and every earlier state stays in the job's history.

The cost line is the invoice. Every invoice line references a job identifier and a variant name. If we mis-measure a file, we correct the invoice and write the correction onto the job report.

Export. Job reports, cost lines and labeled records can be exported as JSONL from Settings at any time, and for 30 days after a workspace is closed.

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 do not promise that a rendered variant will be accepted by an ad platform, that the script screen catches every claim a platform rejects, that an actor's performance matches a direction a script implies, or that a second render of the same manifest is identical to the first. Render times vary with load and are not committed.

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 are not liable for ad spend on a variant you released; for a claim in a script you posted, whether or not our screen flagged it; for a platform's rejection, restriction or labeling of your ads; for footage you uploaded without the rights to it; for files you did not copy from us before the 90-day window closed; or for jobs posted under a key you did not keep secret.

10.4 Cap. Our total liability under these terms in any 12-month period is limited to the fees you paid us in that period, or $500 if you paid none.

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

Each of us keeps the other's confidential information confidential and uses it only to perform these terms. Your manifests, brand kits, product clips, finished files and job reports are your confidential information. We use them only to render your jobs and to run your workspace's own screen, and we do not use them to train models shared with other customers unless your workspace has opted in as described in our Privacy Policy.

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

You own your scripts, your brand kit, your product clips and the finished files we render for you, and you may use the finished files in advertising and marketing anywhere for as long as you like. Each performer in the catalog has licensed their likeness to us for use in customer advertising; that license does not let you present the performer as endorsing your product in their own name, or use a rendered performance outside advertising and marketing.

We own the service, the models, the catalog and the voices. Labeled records created when your members release, drop or correct a variant belong to your workspace and are never shared with another customer. They tune your workspace's own screen, and they are used to train the screen all customers use only if your workspace owner opts in; the opt-in is off by default, covers the script line, the flag and the decision and nothing else, and can be withdrawn for future training at any time.

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

Dailies Render, Inc., 1355 NW Everett Street, Suite 200, Portland, OR 97209, United States
[email protected]

← Back