Legal

Terms of Service

Last updated: 2026-09-03

The changes of 22 July 2026 to Sections 4.2–4.5 and 4.7 (automatic funding, post-pay, fee schedule, negative balances) take effect for existing accounts on 21 August 2026; for accounts created on or after 22 July 2026 they apply immediately.

The changes of 9 August 2026 to Sections 4.7, 5.5 and 9 (chargebacks, campaign-end grace period, account closure and final settlement) take effect for existing accounts on 21 August 2026; for accounts created on or after 9 August 2026 they apply immediately.

The change of 3 September 2026 adding Section 5.6 (ad-spend share) takes effect for existing accounts on 1 November 2026; for accounts created on or after 3 September 2026 it applies immediately.

These Terms of Service (“Terms”) govern your access to and use of Revdeo, the distribution marketplace operated by Optinize GmbH (“Revdeo”, “we”). By creating an account, installing the Shopify app, or otherwise using the Service you agree to these Terms. If you do not agree, do not use the Service.

1. Definitions

• Revdeo — the operator of the Service. Acts as a neutral intermediary between Builders and Revs and facilitates attribution and payouts.
• Builder — a business (D2C brand, Shopify merchant or Stripe-billable SaaS) that posts a Bounty to acquire short-form distribution.
• Rev — an independent creator of faceless short-form content (TikTok, Instagram Reels, YouTube Shorts) who accepts Bounties from Builders.
• Bounty — a campaign published by a Builder defining payout terms (CPM, CPA, revenue share with cap), assets, brief and duration.
• Service — revdeo.io plus the Builder app (app.revdeo.io), the Rev app (rev.revdeo.io), the Shopify embedded app, and all related APIs.
• Attributed Revenue — revenue from a Conversion that our attribution engine ties to a Rev with a confidence score we accept under the then-current attribution policy.

2. Eligibility and accounts

You must be at least 18 years old and capable of entering into a binding contract. Builders must be legally registered businesses with a verifiable VAT-ID or equivalent. Revs must complete Stripe Connect onboarding, including identity verification, before any payout.

You are responsible for the security of your credentials. Notify us immediately at hello@revdeo.io if you suspect unauthorised access.

3. Role of Revdeo (marketplace disclaimer)

Revdeo provides infrastructure: brief publication, click attribution, view polling, conversion matching, and payout mediation via Stripe Connect. Revdeo is not a party to individual arrangements between a Builder and a Rev beyond payout-mediation. Creative choices, brief acceptance, posting cadence and content compliance are the responsibility of the Builder and the Rev respectively.

Revdeo does not guarantee any specific level of views, conversions or revenue. Past performance of Bounties or Revs is not indicative of future results.

4. Pricing, wallet and fees

4.1 Take-rate and on-top fee

Revdeo earns on each bounty payout through two components: a fixed take-ratededucted from the Rev’s payout (the same across all tiers), and an on-top feeadded to the Builder’s cost that decreases with the Builder’s subscription tier:

The current pricing page on revdeo.io is binding for new subscriptions. Existing subscriptions are grandfathered for the remainder of their billing period. All prices exclude VAT, which is added where applicable.

4.2 Pre-paid budget wallet

Bounty payouts to Revs are funded from a pre-paid budget wallet held by the Builder. The Builder tops up the wallet by card through Stripe Checkout; the balance is credited once Stripe confirms the payment. Each bounty payout debits the wallet by the total cost defined in 4.3. If the available balance is insufficient, payouts pause unless they can be funded automatically from a saved payment method (4.4) or are covered by a granted post-pay limit (4.5). Per-campaign budget limits (weekly, monthly or lifetime) set by the Builder are enforced in addition to the wallet balance.

4.3 On-top fee

An on-top feeis added to each bounty when it is paid out. The rate depends on the Builder’s tier (4.1): 20 % on the Free tier, 15 % on Growth and 10 % on Scale. It covers payment processing, currency conversion (FX) and the Revdeo margin. Example: on the Free tier a €100 bounty debits €120 from the wallet; the Rev receives the bounty net of the 20 % take-rate (€80), and Revdeo retains the take-rate margin plus the on-top fee. The on-top fee is displayed in the Builder app and itemised in the wallet ledger.

4.4 Automatic funding and auto-recharge

Automatic funding.By saving a payment method, the Builder authorizes Revdeo to charge it off-session (merchant-initiated) for the following purposes: (a) auto-recharge as configured below, (b) funding bounty payouts that have become due when the wallet balance is insufficient, and (c) settling outstanding (negative) balances under 4.5 and 4.7. Each charge appears in the wallet ledger and is documented by an invoice issued to the Builder (available in the billing portal linked in the Builder app). Automatic charges require complete billing details (company name and address); Revdeo may withhold automatic charges — and payouts may pause under 4.2 — until the Builder has provided them. The Builder can end this authorization at any time by removing all saved payment methods in the Builder app; payouts that cannot be funded then pause under 4.2. Amounts already outstanding remain due.

Auto-recharge. A Builder may additionally enable auto-recharge: when the wallet balance falls below a chosen threshold, Revdeo charges the stored payment method by a chosen amount to refill the wallet off-session. The Builder sets, changes or disables the threshold and amount at any time in the Builder app; the recharge amount must be at least the threshold. Auto-recharge never overrides per-campaign budget limits.

4.5 Post-pay

Revdeo may, at its discretion, grant a Builder a post-pay limit (based, among other things, on payment history): the wallet may then run negative up to the granted limit instead of requiring pre-funding. The outstanding amount is charged to a saved payment method (4.4) and/or invoiced when the limit is reached, and at the latest at the end of each calendar month. Post-pay settlements are billed as a consolidated invoice: one invoice aggregates all creator payouts and platform fees accrued since the previous settlement. The service period is stated on the invoice; the itemised breakdown per payout is the wallet ledger in the Builder app, which forms part of the billing records for that invoice. The on-top fee (4.3) still applies. Revdeo may adjust or revoke the limit at any time with effect for the future; amounts already outstanding remain due.

4.6 Wallet refunds

Unused wallet balance remains the Builder’s funds. A Builder may request a refund of the remaining wallet balance to the original payment method where that balance is at least €50; balances below €50 are not separately refundable but remain available as credit. Refunds are processed via Stripe against the Builder’s prior top-ups and may take several business days. Amounts already committed to pending payouts are not refundable until those payouts settle or are cancelled. A refund request under this Section must be made while the account is active; the treatment of balances remaining at account closure is set out in Section 9.

4.7 Negative balance, set-off and collection

Any negative wallet balance constitutes a due and payable claim of Revdeo against the Builder, regardless of how it arose — post-pay usage (4.5), automatic funding (4.4), refunds, chargebacks, reversals or corrections. Revdeo may set off this claim against any wallet balance and future top-ups, charge saved payment methods (4.4) and invoice the outstanding amount. The statutory rules on default apply, including default interest and reasonable collection costs (Sections 286, 288 of the German Civil Code, BGB). Revdeo may pause payouts, campaigns and further use of the Service while an amount is overdue.

Chargebacks.Blocking a payment card, revoking a direct debit or filing a chargeback does not extinguish a claim under this Section; Revdeo remains entitled to pursue and collect the outstanding amount. Initiating a chargeback or payment dispute against a charge that was authorised under these Terms (top-ups, automatic funding, post-pay invoices, subscription fees) constitutes a material breach. In that event Revdeo may suspend the account immediately — campaigns stop, no further commissions accrue and payouts are held — and may recover the disputed amount, dispute fees charged by the payment provider and reasonable handling costs from the Builder. Opening a new account to circumvent a suspension, an unpaid balance or a closure under Section 9 is prohibited; Revdeo may refuse, suspend or close such accounts and apply this Section to them.

5. Payouts to Revs

Payouts are calculated per period and transferred to Revs via Stripe Connect once the Rev’s cumulative cleared balance reaches the minimum payout threshold of €50; balances below the threshold roll forward. Payouts are processed in EUR only.

Revdeo deducts its take-rate from the bounty before transferring the net amount to the Rev; the take-rate margin and the on-top fee (4.3) are retained by Revdeo. Stripe’s own processing fees apply per Stripe’s terms.

Payouts above €500, or payouts flagged by the anti-fraud engine, are subject to manual review before release. For Builders in regulated (high-risk) verticals, Revdeo may withhold payouts until business verification (KYB) is complete.

Refunds, chargebacks and order cancellations within the attribution window reverse the corresponding payout. If a Rev’s pending balance is insufficient, Revdeo may offset the amount against future earnings.

5.1 Self-billing (credit-note procedure)

Because Revs are typically not set up to issue VAT invoices for each payout, Revdeo settles the Rev’s remuneration by way of self-billing— a credit note (Gutschrift) within the meaning of § 14 (2) of the German VAT Act (Umsatzsteuergesetz, UStG). By accepting these Terms the Rev agrees in advance that Revdeo issues such credit notes on the Rev’s behalf for the remuneration paid out through the platform.

The Rev must provide and keep current complete and accurate billing details — legal name, address, country, the applicable tax status (standard-rated, small business under § 19 UStG, EU business, non-EU, or private individual) and, where applicable, a VAT-ID or tax number — in the Rev app. The Rev is responsible for the correctness of these details and bears any tax disadvantage resulting from incorrect or outdated information.

VAT is shown on the credit note according to the Rev’s tax status: standard German VAT for standard-rated Revs; no VAT with a § 19 note for small-business Revs; and the reverse-charge procedure (§ 13b UStG) for EU and non-EU businesses. A credit note is issued only once the required details are complete.

Each credit note is made available to the Rev. A credit note is deemed accepted unless the Rev objects in text form within 14 days of it being made available; a timely objection causes the credit note to lose effect (§ 14 (2) sentence 3 UStG) and the parties will reissue a corrected document. Either party may terminate this self-billing arrangement in text form with effect for future payouts.

5.2 Campaign participation, removal and ongoing commission

Where a campaign pays a share of reorders or recurring revenue, that share is tied to the Rev’s active participation in the campaign, not to the customer relationship as such. A Builder may set an activity window for a campaign: a Rev who submits nothing within that window is removed automatically. Builders may also remove a Rev at any time, and a Rev may leave.

From the moment a Rev is removed from a campaign, conversions occurring after that point no longer earn that Rev a commission on that campaign— including reorders by customers the Rev originally referred. Amounts already earned before removal remain payable and are unaffected; payouts for periods already settled are never reversed for this reason. Views already delivered continue to count toward view-based payouts.

Where an activity window applies, the Rev is notified in the app before the window expires and again on removal. The window and any participation requirements are shown on the campaign before the Rev joins. A removed Rev may re-apply at any time; participation and the ongoing commission resume only once the Builder approves them again, and only for conversions occurring after that approval.

5.3 Deals with a delivery target

A Builder and a Rev may agree an individual deal (a fixed monthly retainer, a signing bonus, an individual revenue share, or a combination). Such a deal may contain a delivery target expressed as a number of submissions per week. The target is shown to the Rev before the deal is accepted.

Where a target is agreed, the retainer for a given period is payable only if the target was met in the preceding period; the retainer is paid in advance for the coming period on that basis. A period in which the target is not met does not become payable later. Both parties are notified when a period is not paid out for this reason. Signing bonuses and revenue shares are not affected by the target.

5.4 Builder default, insolvency and departure

Revdeo mediates payment between Builder and Rev; it does not act as guarantor for a Builder’s obligations (see Section 3).Revdeo’s obligation to pay out is limited to funds that Revdeo has actually received or holds for the Builder concerned. Revdeo does not advance its own funds to cover amounts a Builder has not paid, and it does not underwrite a Builder’s creditworthiness.

Where a campaign was funded from a pre-paid wallet balance (4.2), the amount is held before the work is delivered and is unaffected by the Builder’s later departure or insolvency. Exposure can arise only where a Builder used post-pay (4.5) or automatic funding failed — that is, where earnings accrued before the corresponding amount was collected.

In that case the outstanding amount is a claim of Revdeo against the Builder. Revdeo pursues it under Section 4.7, including reminders, default interest and, where warranted, debt collection or legal proceedings. Revdeo passes on to the affected Revs what it actually recovers, less the collection costs it is unable to recover from the Builder. Recovery can take considerable time — typically months, and in insolvency proceedings substantially longer — and it may fail entirely. Revdeo will inform affected Revs of the status and of any partial recovery. Where a recovery is partial, it is distributed among the affected Revs in proportion to their outstanding amounts.

Beyond this, Revdeo is not liable for a Builder’s failure to pay. Section 11 remains unaffected: this does not limit liability for intentional misconduct or gross negligence, for injury to life, body or health, or for any other liability that is mandatory by law.

5.5 Campaign end and grace period

A Builder may pause or end a campaign at any time. When a campaign is paused, content already posted keeps earning under the campaign’s terms; new submissions are not accepted until the campaign resumes. When a campaign is ended, new submissions are closed immediately, and content posted before the end continues to earn commission for a grace period of seven (7) daysafter the end. After the grace period, no further commissions accrue on the campaign — including on conversions from links or promo codes that remain publicly reachable, and irrespective of any longer attribution window configured for the campaign. Amounts earned up to the cut-off are unaffected and are paid on the normal payout schedule. Revs are notified when a campaign is paused or ended, including the exact cut-off date.

The grace period does not apply where a campaign stops because the Builder’s account is suspended for non-payment or a chargeback (Section 4.7) — in that case commissions stop accruing immediately at suspension, because further accrual would increase an uncollected claim.

5.6 Ad-spend share (Ad Performance)

(1) Subject.Where a campaign offers an ad-spend share, the Rev receives a percentage of the advertising spend the Builder incurs on an advertisement that uses the Rev’s creative. The percentage is set by the Builder per campaign and is shown to the Rev with the campaign terms before joining.

(2) Basis of calculation.The basis is the advertising spend reported by the advertising platform — not the revenue generated by the advertisement. Only the figures Revdeo retrieves through the platform’s interface are decisive.

(3) Attributability requirement.A claim arises only for advertisements that Revdeo can technically attribute to the creative — either through the tracking parameters in the advertisement’s destination URL, or through a Revdeo redirect link used as the destination URL. Without such attribution there is no claim, even if the advertisement uses the Rev’s creative.

(4) Responsibility.Setting these parameters is the Builder’s responsibility. Where the advertisement is launched through Revdeo, they are set automatically. Revdeo cannot detect advertisements that carry no attribution and gives no warranty that all eligible advertising spend is captured.

(5) Start of measurement. Measurement begins on the day of first attribution. Advertising spend incurred before that day is not remunerated.

(6) Platform changes. If the advertising platform changes its interface or the availability of data, measurement may cease. A claim exists only for advertising spend actually captured.

(7) Cap. The Builder may set a maximum amount. Where a maximum is set, the ad-spend share is limited to that amount per advertisement and per payout period; the excess is neither paid later nor carried over into subsequent periods. The maximum applies per advertisement, not per campaign. Campaign budgets under Section 4.2 apply independently and in addition.

6. Licences and content

6.1 Builder grants to Rev

By publishing a Bounty, the Builder grants each Rev who accepts that Bounty a non-exclusive, royalty-free, time-limited licence to use the provided assets (raw footage, hooks, B-roll, product imagery, trademarks) solely for the purpose of producing and posting content under that Bounty for its duration. The licence terminates on the Bounty close date.

6.2 Rev grants to Revdeo and Builder

By submitting a post URL, the Rev grants Revdeo and the Builder the right to collect public performance data (views, likes, comments, post URL), to display the post URL on the public leaderboard subject to the Rev’s opt-in, and to reference the Bounty in marketing materials with the Rev’s handle redacted unless the Rev explicitly opts in to attribution.

6.3 Usage rights for submitted content

Every video a Rev submits — a post URL or a video uploaded for Builder review — carries a usage licence that the Rev sets at the moment of submission and can review at any time under Usage rights in their account. A licence consists of one term (one, three, six or twelve months, or unlimited; three months with automatic renewal by default) and the usage types the Rev grants:

• Organic repostson the Builder’s own channels.
• Paid ads and whitelisting, including use as an ad creative and Partnership Ads. This usage type is opt-in and is never granted implicitly.
• Other media — website, newsletter, retail and comparable placements.

Outside the granted usage types and after the term ends, the Builder has no right to use the content. Where a Rev submitted content before this clause took effect and no licence record exists, organic reposting remains permitted and paid-media use does not.

6.4 Ending and withdrawing a licence

The Rev may switch off automatic renewal at any time; the licence then ends on its expiry date. The Rev may also withdraw the licence with a stated reason — in particular where the content is used in a manner that damages the Rev, outside the granted usage types, or in a context the Rev cannot reasonably be expected to be associated with.

A withdrawal takes effect immediately on the platform: Revdeo blocks further distribution, download and ad launches of that content, and notifies the Builder. The Builder must then cease using the content, including in advertising running outside Revdeo. Revdeo cannot delete content a Builder has already transferred to a third-party system — for example a video already uploaded into the Builder’s own Meta ad account. Stopping that use is the Builder’s own obligation. Revdeo reviews every withdrawal after the fact and may reinstate a licence where the withdrawal is unfounded; reinstatement never extends a term that has already expired. Withdrawal does not affect remuneration already earned.

Revdeo records every grant, change, renewal, expiry, withdrawal and reinstatement with a timestamp, and makes that record available to both parties in the event of a dispute.

6.5 Meta advertising via Revdeo

Where a Builder connects a Meta (Facebook / Instagram) ad account — by Facebook Login for Business or by sharing assets with Revdeo’s Business Manager (concierge setup) — the Builder authorises Revdeo to create, manage and report on ads in that account on the Builder’s behalf and on their instruction. The Builder remains the advertiser of record and is solely responsible for compliance with the Meta Advertising Standards and Meta’s Platform Terms. Revdeo only runs ads the Builder has approved, and the Builder may disconnect at any time (see Data Deletion), which revokes Revdeo’s access. Revdeo manages a connected or shared ad account strictly on the Builder’s instruction, acting as the Builder’s processor under Art. 28 GDPR for that processing. Running a Rev’s clip as a paid ad requires an active usage licence covering paid ads under 6.3 — Revdeo blocks the ad launch without it; Partnership Ads under a Rev’s own handle additionally require that Rev’s explicit authorisation via a Meta partnership ad code.

7. Acceptable use

The following are prohibited:

• Bot traffic, view-bots, engagement manipulation, click fraud, coordinated inauthentic behaviour, or any attempt to inflate metrics that drive payouts.
• Off-platform monetisation of Bounty assets without disclosure (e.g. re-selling raw footage, sub-licensing without consent).
• Posting content that infringes third-party IP, defames a person, is unlawful in the audience’s jurisdiction, or violates platform rules of TikTok, Instagram or YouTube.
• Concealing the commercial nature of a post. Revs are responsible for compliance with disclosure rules (e.g. § 6 (1) Nr. 1 TMG in Germany; FTC Endorsement Guides for US audiences).
• Reverse-engineering, scraping, or otherwise interfering with the Service or its attribution mechanics.

Revdeo may suspend or close accounts that violate these rules without notice and withhold suspect payouts pending review. Confirmed violations result in forfeiture of the affected balance.

8. Anti-fraud and manual review

Revdeo operates a view-spike detection engine and an account-reputation score. Any payout above €500 is subject to manual review with a service-level target of 48 business hours. Revdeo may request additional information (post analytics screenshots, platform verification) before releasing such payouts.

9. Term and termination

These Terms apply for as long as you maintain an account.

• Starter (free) — either party may terminate at any time. Account-closure takes effect immediately. Outstanding payouts above threshold are paid on the next Friday cycle.
• Paid tiers (Growth, Scale)— 30 days’ written notice to the end of a billing period. Pre-paid subscription fees are not refunded, but the Builder retains access for the paid term; remaining wallet balance is governed by Section 4.6.
• For cause — Revdeo may terminate immediately for material breach, fraud, or insolvency. The Builder / Rev may terminate immediately if Revdeo materially breaches and fails to cure within 14 days of written notice.

9.1 Builder account closure and final settlement

When a Builder’s account closure takes effect, all campaigns end and Section 5.5 applies (7-day grace period for content already posted; no grace where the closure follows a suspension for non-payment or a chargeback). Affected Revs are notified. Active custom deals end with the closure; retainer periods already paid in advance are not clawed back, so the current retainer period remains the Rev’s. Escrow amounts reserved for offers that have not been consumed are released back to the wallet for the final settlement.

The final settlement runs on the normal payout schedule: commissions earned up to the cut-off clear and are paid in the regular cycles, and Revdeo may continue to charge the saved payment method for amounts the Builder owes (Sections 4.4, 4.7) until the final settlement is complete. Personal data is erased or anonymized after the final settlement (Section 13 and our privacy policy); records subject to statutory retention are kept in anonymized form.

Wallet balance remaining after the final settlement and after set-off under Section 4.7 is forfeited when the closure becomes final; refund requests under Section 4.6 must be made before the closure takes effect. Closing an account does not release the Builder from payment obligations that arose before or during the final settlement, and does not affect content licences already exported to the Builder’s own systems, whose termination is governed by Section 6.4.

10. Warranty disclaimer

The Service is provided “as is” and “as available”. To the extent permitted by law, Revdeo disclaims all implied warranties including merchantability, fitness for a particular purpose, and non-infringement. We do not warrant uninterrupted operation, attribution accuracy beyond what our confidence-score model reports, or any specific business outcome.

11. Limitation of liability

Revdeo’s aggregate liability for any claim arising from or relating to these Terms or the Service is capped at the total fees you paid to Revdeo in the twelve (12) months preceding the event giving rise to the claim. Revdeo is not liable for indirect, incidental, special, consequential or punitive damages, including lost profits, loss of goodwill, or loss of data.

Nothing in these Terms limits liability for damages caused by intentional misconduct or gross negligence, for injury to life, body or health, or under the German Product Liability Act (Produkthaftungsgesetz) where mandatory by law.

12. Indemnification

Each Builder indemnifies Revdeo against third-party claims arising from assets the Builder provided (IP infringement, false advertising, regulatory non-compliance). Each Rev indemnifies Revdeo against third-party claims arising from the Rev’s posts, including platform-rules violations and disclosure failures.

13. Data protection

Our processing of personal data is described in the Privacy Policy. For Builders acting as data controllers (e.g. Shopify merchant data), Revdeo acts as a processor under Art. 28 GDPR; a Data Processing Agreement is available on request at privacy@revdeo.io.

14. Tax and DAC7

Revs are responsible for declaring earnings to their local tax authority. Revdeo, as a digital platform operator, reports Rev earnings to the German Federal Central Tax Office (BZSt) under EU Directive 2021/514 (DAC7) where reporting thresholds are met. See the DAC7 disclosure for details.

15. Changes to the Terms

We may modify these Terms. Material changes are announced at least 30 days in advance via in-app notice and email. Continued use after the effective date constitutes acceptance. If you reject a change, you may terminate per Section 9 with effect from the effective date.

16. Governing law and jurisdiction

These Terms are governed by the laws of the Federal Republic of Germany, excluding the UN Convention on Contracts for the International Sale of Goods. Exclusive place of jurisdiction for merchants, legal persons under public law and special funds under public law is Halle (Saale), Germany.

For consumers within the EU, the EU Online Dispute Resolution platform is available at ec.europa.eu/consumers/odr. Revdeo is not obliged and not willing to participate in dispute-resolution proceedings before a consumer arbitration board.

17. Contact

Optinize GmbH, Halle (Saale), Germany. Contact: hello@revdeo.io. Full company details in the Imprint.